Oct 5 00:19:14 storageqe-109 systemd[1]: Starting logrotate.service - Rotate log files... Oct 5 00:19:14 storageqe-109 systemd[1]: Reloading rsyslog.service - System Logging Service... Oct 5 00:19:14 storageqe-109 rsyslogd[1089]: [origin software="rsyslogd" swVersion="8.2506.0-2.el10" x-pid="1089" x-info="https://www.rsyslog.com"] rsyslogd was HUPed Oct 5 00:19:14 storageqe-109 systemd[1]: Reloaded rsyslog.service - System Logging Service. Oct 5 00:19:14 storageqe-109 systemd[1]: logrotate.service: Deactivated successfully. Oct 5 00:19:14 storageqe-109 systemd[1]: Finished logrotate.service - Rotate log files. Oct 5 00:30:34 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 00:30:34 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 00:30:34 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 00:49:33 storageqe-109 udisksd[1947]: Loading module lsm ... Oct 5 00:49:33 storageqe-109 udisksd[1947]: Error loading module: LSM: Failed to connect plugin via URI 'hpsa://', error code: -1, error message: (null) Oct 5 00:49:35 storageqe-109 systemd[1]: Reload requested from client PID 1917996 ('systemctl') (unit session-10.scope)... Oct 5 00:49:35 storageqe-109 systemd[1]: Reloading... Oct 5 00:49:35 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 5 00:49:35 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 00:49:35 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 00:49:35 storageqe-109 systemd[1]: Reloading finished in 134 ms. Oct 5 00:49:35 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 00:49:35 storageqe-109 iscsid[1915722]: iscsid shutting down. Oct 5 00:49:35 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 00:49:35 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 00:49:35 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 00:49:35 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 00:49:35 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 00:49:35 storageqe-109 multipathd[770]: Multipath configuration updated. Oct 5 00:49:35 storageqe-109 multipathd[770]: Reload multipathd for changes to take effect Oct 5 00:49:35 storageqe-109 systemd[1]: Reloading multipathd.service - Device-Mapper Multipath Device Controller... Oct 5 00:49:35 storageqe-109 multipathd[770]: reconfigure (operator) Oct 5 00:49:35 storageqe-109 multipathd[770]: reconfigure: setting up paths and maps Oct 5 00:49:35 storageqe-109 multipathd[1918097]: ok Oct 5 00:49:35 storageqe-109 systemd[1]: Reloaded multipathd.service - Device-Mapper Multipath Device Controller. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 00:49:37 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 00:49:37 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 00:49:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 00:49:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 00:49:58 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde'] #### INFO: #### will start test_reencrypt_token_keyring_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde'] #### Oct 5 00:50:04 storageqe-109 INFO: #### test_device before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde'] #### Oct 5 00:50:04 storageqe-109 INFO: #### will start test_reencrypt_token_keyring_header[npo2_linear] ##### Oct 5 00:50:04 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderZxK' luksFormat /dev/mapper/npo2linear -q Oct 5 00:50:09 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderZxK' luksFormat /dev/mapper/npo2linear -q Oct 5 00:50:18 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderZxK' reencrypt /dev/mapper/npo2linear -q Oct 5 00:50:19 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderZxK' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --header '/tmp/testheaderZxK' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 5 00:50:41 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --header '/tmp/testheaderZxK' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderZxK' token add /dev/mapper/npo2linear -q Oct 5 00:51:02 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderZxK' token add /dev/mapper/npo2linear -q cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '10' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderZxK' reencrypt /dev/mapper/npo2linear -q --token-only Oct 5 00:51:12 storageqe-109 journal: cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '10' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderZxK' reencrypt /dev/mapper/npo2linear -q --token-only cryptsetup --type 'luks2' --header '/tmp/testheaderZxK' open /dev/mapper/npo2linear qKnivmcYxG -q --allow-discards --token-only Oct 5 00:51:31 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderZxK' open /dev/mapper/npo2linear qKnivmcYxG -q --allow-discards --token-only cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderZxK' token remove /dev/mapper/npo2linear -q Oct 5 00:51:41 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderZxK' token remove /dev/mapper/npo2linear -q INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs xfs in remove_crypt Oct 5 00:51:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.iizbnvr3mount_test with fs xfs Oct 5 00:52:02 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 6d7fb8af-f4e6-47a4-896c-d55e6d0ca0f5 Oct 5 00:52:02 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 5 00:52:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iizbnvr3mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext4 in remove_crypt Oct 5 00:52:07 storageqe-109 systemd[1]: tmp-libblockdev.iizbnvr3mount_test.mount: Deactivated successfully. Oct 5 00:52:07 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 6d7fb8af-f4e6-47a4-896c-d55e6d0ca0f5 Oct 5 00:52:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs xfs in remove_crypt Oct 5 00:52:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kzbw59p3mount_test with fs ext4 Oct 5 00:52:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 50cd4809-9a21-4689-818d-0e1742c02b7e r/w with ordered data mode. Quota mode: none. Oct 5 00:52:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kzbw59p3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext3 in remove_crypt Oct 5 00:52:22 storageqe-109 systemd[1]: tmp-libblockdev.kzbw59p3mount_test.mount: Deactivated successfully. Oct 5 00:52:22 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 50cd4809-9a21-4689-818d-0e1742c02b7e. Oct 5 00:52:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext4 in remove_crypt Oct 5 00:52:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r37_7i4tmount_test with fs ext3 Oct 5 00:52:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 5 00:52:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2a046f2f-7819-44e2-88d0-a8e05d64eb3b r/w with ordered data mode. Quota mode: none. Oct 5 00:52:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r37_7i4tmount_test with fs ext3 Oct 5 00:52:37 storageqe-109 systemd[1]: tmp-libblockdev.r37_7i4tmount_test.mount: Deactivated successfully. Oct 5 00:52:37 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2a046f2f-7819-44e2-88d0-a8e05d64eb3b. INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext2 in remove_crypt Oct 5 00:52:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext3 in remove_crypt Oct 5 00:52:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ls94wjpumount_test with fs ext2 Oct 5 00:52:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 5 00:52:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9e264ad4-baec-4274-99ec-f3bf07ac3056 r/w without journal. Quota mode: none. Oct 5 00:52:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ls94wjpumount_test with fs ext2 Oct 5 00:52:52 storageqe-109 systemd[1]: tmp-libblockdev.ls94wjpumount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext2 in remove_crypt INFO: remove crypt device qKnivmcYxG INFO: finishe the remove crypt device qKnivmcYxG Oct 5 00:52:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9e264ad4-baec-4274-99ec-f3bf07ac3056. Oct 5 00:52:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qKnivmcYxG and fs ext2 in remove_crypt Oct 5 00:52:52 storageqe-109 INFO: remove crypt device qKnivmcYxG Oct 5 00:52:53 storageqe-109 INFO: finishe the remove crypt device qKnivmcYxG INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde'] #### INFO: #### END test_reencrypt_token_keyring_header[npo2_linear] #### Oct 5 00:52:58 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde'] #### Oct 5 00:52:58 storageqe-109 INFO: #### END test_reencrypt_token_keyring_header[npo2_linear] #### Oct 5 00:52:59 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:52:59 storageqe-109 INFO: #### test_device after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:54:03 storageqe-109 udisksd[1947]: Loading module lsm ... Oct 5 00:54:03 storageqe-109 udisksd[1947]: Error loading module: LSM: Failed to connect plugin via URI 'hpsa://', error code: -1, error message: (null) Oct 5 00:54:05 storageqe-109 systemd[1]: Reload requested from client PID 1920095 ('systemctl') (unit session-10.scope)... Oct 5 00:54:05 storageqe-109 systemd[1]: Reloading... Oct 5 00:54:05 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 5 00:54:05 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 00:54:05 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 00:54:05 storageqe-109 systemd[1]: Reloading finished in 141 ms. Oct 5 00:54:05 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 00:54:05 storageqe-109 iscsid[1918053]: iscsid shutting down. Oct 5 00:54:05 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 00:54:05 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 00:54:05 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 00:54:05 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 00:54:05 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 00:54:05 storageqe-109 multipathd[770]: Multipath configuration updated. Oct 5 00:54:05 storageqe-109 multipathd[770]: Reload multipathd for changes to take effect Oct 5 00:54:05 storageqe-109 systemd[1]: Reloading multipathd.service - Device-Mapper Multipath Device Controller... Oct 5 00:54:05 storageqe-109 multipathd[770]: reconfigure (operator) Oct 5 00:54:05 storageqe-109 multipathd[770]: reconfigure: setting up paths and maps Oct 5 00:54:05 storageqe-109 multipathd[1920194]: ok Oct 5 00:54:05 storageqe-109 systemd[1]: Reloaded multipathd.service - Device-Mapper Multipath Device Controller. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 00:54:07 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 00:54:07 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 00:54:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 00:54:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 00:54:29 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_init_nvme ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:54:30 storageqe-109 INFO: #### will start test_init_nvme ##### Oct 5 00:54:30 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_init_nvme #### INFO: #### will start test_ata_driver ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:54:43 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:54:43 storageqe-109 INFO: #### END test_init_nvme #### Oct 5 00:54:43 storageqe-109 INFO: #### will start test_ata_driver ##### Oct 5 00:54:43 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:54:49 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_ata_driver #### INFO: #### will start test_vdo ##### Oct 5 00:54:56 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:54:56 storageqe-109 INFO: #### END test_ata_driver #### Oct 5 00:54:56 storageqe-109 INFO: #### will start test_vdo ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:54:56 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:55:12 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 5 00:55:12 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 5 00:55:12 storageqe-109 kernel: loop0: Oct 5 00:55:14 storageqe-109 UDS/vdoformat[1921653]: INFO (vdoformat/1921653) Using 2 indexing zones for concurrency. Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo23:lvm: loading device '253:4' Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo23:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo23:lvm: starting device '253:4' Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:physQ0: VDO commencing normal operation Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:journa: Setting UDS index target state to online Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: creating index: 253:3 Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' started Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: Using 2 indexing zones for concurrency. Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:14 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:14 storageqe-109 systemd[1]: Started dm-event.service - Device-mapper event daemon. Oct 5 00:55:14 storageqe-109 dmeventd[1921687]: dmeventd ready for processing. Oct 5 00:55:14 storageqe-109 dmeventd[1921687]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: VDOPool /org/freedesktop/UDisks2/lvm/vg03/udisks_test_vdopool Oct 5 00:55:16 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/vg03/udisks_test_vdopool INFO: OperatingMode normal Oct 5 00:55:17 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 5 00:55:18 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 5 00:55:19 storageqe-109 INFO: IndexState online INFO: UsedSize 4988477440 Oct 5 00:55:20 storageqe-109 INFO: UsedSize 4988477440 INFO: Compression 1 Oct 5 00:55:21 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 5 00:55:22 storageqe-109 INFO: Deduplication 1 Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 5 00:55:22 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: beginning save (vcn 18446744073709551615) Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:22 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: finished save (vcn 18446744073709551615) Oct 5 00:55:22 storageqe-109 dmeventd[1921687]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:23 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 00:55:23 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 5 00:55:23 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:23 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:23 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:23 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:23 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is disabled Oct 5 00:55:23 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:23 storageqe-109 dmeventd[1921687]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 5 00:55:24 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: loading or rebuilding index: 253:3 Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is disabled Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: Using 2 indexing zones for concurrency. Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:24 storageqe-109 dmeventd[1921687]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:24 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: loaded index from chapter 0 through chapter 0 Oct 5 00:55:25 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 00:55:25 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 5 00:55:25 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:25 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:25 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:25 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:25 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 5 00:55:25 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:25 storageqe-109 dmeventd[1921687]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:28 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 2266112 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 00:55:28 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 5 00:55:28 storageqe-109 kernel: device-mapper: vdo23:lvm: Preparing to resize physical to 2266112 Oct 5 00:55:28 storageqe-109 kernel: device-mapper: vdo23:lvm: Done preparing to resize physical Oct 5 00:55:29 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:29 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:29 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:29 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:29 storageqe-109 kernel: device-mapper: vdo23:lvm: Physical block count was 1741824, now 2266112 Oct 5 00:55:29 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 5 00:55:29 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:29 storageqe-109 dmeventd[1921687]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: the 9281994752 8589934592 Oct 5 00:55:32 storageqe-109 INFO: the 9281994752 8589934592 INFO:before lv vdo 78622228480 Oct 5 00:55:33 storageqe-109 journal: INFO:before lv vdo 78622228480 Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 2266112 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: Preparing to resize logical to 95974656 Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: Done preparing to resize logical Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: Resizing logical to 95974656 Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: Logical blocks now 95974656 Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:33 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 5 00:55:33 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 5 00:55:33 storageqe-109 dmeventd[1921687]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: after lv vdo 393111142400 Oct 5 00:55:35 storageqe-109 INFO: after lv vdo 393111142400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 7 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 63 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 4872976 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 4191472 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 7 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics maxVIOs 63 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 4872976 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 4191472 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 23 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 95974656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9064448 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosInFua 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics instance 23 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 95974656 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9064448 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 5 00:55:35 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410015082 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 7 INFO: vdo.GetStatistics overheadBlocksUsed 1218244 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 54 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410015082 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 7 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 1218244 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics usedPercent 54 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2266112 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2266112 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 2 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 2 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 5 00:55:36 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 5 00:55:36 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 5 00:55:36 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 5 00:55:36 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 5 00:55:36 storageqe-109 kernel: device-mapper: vdo23:lvm: stopping device '253:4' Oct 5 00:55:37 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' stopped Oct 5 00:55:43 storageqe-109 kernel: loop0: Oct 5 00:55:43 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 5 00:55:43 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_vdo #### INFO: #### will start test_bz1567992_luks_resize ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:55:49 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:55:49 storageqe-109 INFO: #### END test_vdo #### Oct 5 00:55:49 storageqe-109 INFO: #### will start test_bz1567992_luks_resize ##### Oct 5 00:55:49 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:55:56 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 00:55:56 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 5 00:55:56 storageqe-109 kernel: loop0: INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks1'}, signature=dbus.Signature('sv')) Oct 5 00:55:57 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks1'}, signature=dbus.Signature('sv')) INFO: HintEncryptionType Oct 5 00:56:05 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 2097152 Oct 5 00:56:06 storageqe-109 INFO: MetadataSize 2097152 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 5 00:56:07 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: changed passwd to redhatredhat Oct 5 00:56:13 storageqe-109 INFO: changed passwd to redhatredhat Oct 5 00:56:13 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:56:13 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:56:13 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:15 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:17 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 INFO: changed passwd to test123456 Oct 5 00:56:23 storageqe-109 INFO: changed passwd to test123456 Oct 5 00:56:23 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:56:23 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:56:23 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:25 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:27 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 00:56:32 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 00:56:33 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:35 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:37 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 00:56:42 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 00:56:43 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:45 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:56:47 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 00:56:52 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 00:56:52 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 5 00:56:52 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 5 00:56:53 storageqe-109 stratisd[1277]: [2025-10-05T04:56:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:56:53 storageqe-109 stratisd[1277]: [2025-10-05T04:56:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:56:53 storageqe-109 stratisd[1277]: [2025-10-05T04:56:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:56:53 storageqe-109 stratisd[1277]: [2025-10-05T04:56:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 5 00:56:54 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 5 00:56:55 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 5 00:56:56 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 5 00:56:57 storageqe-109 INFO: foramt to luks2 Oct 5 00:56:57 storageqe-109 INFO: foramt to pbkdf2 INFO: changed passwd to redhatredhat Oct 5 00:57:03 storageqe-109 stratisd[1277]: [2025-10-05T04:57:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:03 storageqe-109 stratisd[1277]: [2025-10-05T04:57:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:03 storageqe-109 INFO: changed passwd to redhatredhat Oct 5 00:57:03 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:57:03 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:57:03 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:05 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:07 storageqe-109 stratisd[1277]: [2025-10-05T04:57:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:07 storageqe-109 stratisd[1277]: [2025-10-05T04:57:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:08 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 INFO: changed passwd to test123456 Oct 5 00:57:16 storageqe-109 stratisd[1277]: [2025-10-05T04:57:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:16 storageqe-109 stratisd[1277]: [2025-10-05T04:57:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:16 storageqe-109 INFO: changed passwd to test123456 Oct 5 00:57:16 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:57:16 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:57:16 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:18 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:20 storageqe-109 stratisd[1277]: [2025-10-05T04:57:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:20 storageqe-109 stratisd[1277]: [2025-10-05T04:57:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:20 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 00:57:28 storageqe-109 stratisd[1277]: [2025-10-05T04:57:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:28 storageqe-109 stratisd[1277]: [2025-10-05T04:57:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:28 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 00:57:28 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:30 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:32 storageqe-109 stratisd[1277]: [2025-10-05T04:57:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:32 storageqe-109 stratisd[1277]: [2025-10-05T04:57:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:32 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 00:57:41 storageqe-109 stratisd[1277]: [2025-10-05T04:57:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:41 storageqe-109 stratisd[1277]: [2025-10-05T04:57:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:41 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 00:57:41 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:43 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 00:57:45 storageqe-109 stratisd[1277]: [2025-10-05T04:57:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:45 storageqe-109 stratisd[1277]: [2025-10-05T04:57:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:45 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 00:57:53 storageqe-109 stratisd[1277]: [2025-10-05T04:57:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:53 storageqe-109 stratisd[1277]: [2025-10-05T04:57:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:53 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 5 00:57:54 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 5 00:57:54 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 5 00:57:54 storageqe-109 stratisd[1277]: [2025-10-05T04:57:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:54 storageqe-109 stratisd[1277]: [2025-10-05T04:57:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:54 storageqe-109 stratisd[1277]: [2025-10-05T04:57:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:57:54 storageqe-109 stratisd[1277]: [2025-10-05T04:57:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 5 00:57:55 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 5 00:57:56 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 5 00:57:57 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 5 00:57:58 storageqe-109 INFO: foramt to luks2 Oct 5 00:57:58 storageqe-109 INFO: foramt to pbkdf2 INFO: before convert luks dump info {'keyslots': {'0': {'type': 'luks2', 'key_size': 64, 'af': {'type': 'luks1', 'stripes': 4000, 'hash': 'sha256'}, 'area': {'type': 'raw', 'offset': '32768', 'size': '258048', 'encryption': 'aes-xts-plain64', 'key_size': 64}, 'kdf': {'type': 'pbkdf2', 'hash': 'sha256', 'iterations': 1000, 'salt': 'pT1SVSxtX0I6H0guHu7y2Xz5sN34Pf3S3MCFdZfmq24='}}}, 'tokens': {}, 'segments': {'0': {'type': 'crypt', 'offset': '16777216', 'size': 'dynamic', 'iv_tweak': '0', 'encryption': 'aes-xts-plain64', 'sector_size': 512}}, 'digests': {'0': {'type': 'pbkdf2', 'keyslots': ['0'], 'segments': ['0'], 'hash': 'sha256', 'iterations': 1000, 'salt': 'B8nn6nBXppVkpAq9S1DG/jEiX5V6cxkbN2Mvqd+Re/M=', 'digest': 'ZHx+AtjWJIC05ZJ4n2v1xAHupH8bkyb6cprvZ1aYbgk='}}, 'config': {'json_size': '12288', 'keyslots_size': '16744448'}} Oct 5 00:57:59 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:57:59 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:57:59 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 5 00:57:59 storageqe-109 INFO: before convert luks dump info {'keyslots': {'0': {'type': 'luks2', 'key_size': 64, 'af': {'type': 'luks1', 'stripes': 4000, 'hash': 'sha256'}, 'area': {'type': 'raw', 'offset': '32768', 'size': '258048', 'encryption': 'aes-xts-plain64', 'key_size': 64}, 'kdf': {'type': 'pbkdf2', 'hash': 'sha256', 'iterations': 1000, 'salt': 'pT1SVSxtX0I6H0guHu7y2Xz5sN34Pf3S3MCFdZfmq24='}}}, 'tokens': {}, 'segments': {'0': {'type': 'crypt', 'offset': '16777216', 'size': 'dynamic', 'iv_tweak': '0', 'encryption': 'aes-xts-plain64', 'sector_size': 512}}, 'digests': {'0': {'type': 'pbkdf2', 'keyslots': ['0'], 'segments': ['0'], 'hash': 'sha256', 'iterations': 1000, 'salt': 'B8nn6nBXppVkpAq9S1DG/jEiX5V6cxkbN2Mvqd+Re/M=', 'digest': 'ZHx+AtjWJIC05ZJ4n2v1xAHupH8bkyb6cprvZ1aYbgk='}}, 'config': {'json_size': '12288', 'keyslots_size': '16744448'}} INFO: will convert to luks1 Oct 5 00:58:29 storageqe-109 INFO: will convert to luks1 Oct 5 00:58:29 storageqe-109 INFO: will convert to luks2 INFO: will convert to luks2 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2i', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 5 00:58:29 storageqe-109 stratisd[1277]: [2025-10-05T04:58:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:29 storageqe-109 stratisd[1277]: [2025-10-05T04:58:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:29 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2i', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 5 00:58:37 storageqe-109 stratisd[1277]: [2025-10-05T04:58:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:37 storageqe-109 stratisd[1277]: [2025-10-05T04:58:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:39 storageqe-109 stratisd[1277]: [2025-10-05T04:58:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:39 storageqe-109 stratisd[1277]: [2025-10-05T04:58:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 5 00:58:41 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 5 00:58:42 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 5 00:58:43 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to argon2i Oct 5 00:58:44 storageqe-109 INFO: foramt to luks2 Oct 5 00:58:44 storageqe-109 INFO: foramt to argon2i Oct 5 00:58:48 storageqe-109 stratisd[1277]: [2025-10-05T04:58:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:48 storageqe-109 stratisd[1277]: [2025-10-05T04:58:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:48 storageqe-109 stratisd[1277]: [2025-10-05T04:58:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:48 storageqe-109 stratisd[1277]: [2025-10-05T04:58:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 00:58:51 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:58:51 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 00:58:51 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 5 00:58:56 storageqe-109 kernel: loop0: Oct 5 00:58:56 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 5 00:58:56 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1567992_luks_resize #### INFO: #### will start test_part_mount ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:59:02 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:59:02 storageqe-109 INFO: #### END test_bz1567992_luks_resize #### Oct 5 00:59:02 storageqe-109 INFO: #### will start test_part_mount ##### Oct 5 00:59:02 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:59:09 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 00:59:09 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 5 00:59:09 storageqe-109 kernel: loop0: Oct 5 00:59:17 storageqe-109 kernel: loop0: p1 Oct 5 00:59:17 storageqe-109 kernel: EXT4-fs (loop0p1): mounting ext3 file system using the ext4 subsystem Oct 5 00:59:17 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem db6b47b1-962a-400d-8233-07530b59f2d1 r/w with ordered data mode. Quota mode: none. Oct 5 00:59:17 storageqe-109 udisksd[1947]: Mounted /dev/loop0p1 at /run/media/root/db6b47b1-962a-400d-8233-07530b59f2d1 on behalf of uid 0 Oct 5 00:59:17 storageqe-109 systemd[1]: run-media-root-db6b47b1\x2d962a\x2d400d\x2d8233\x2d07530b59f2d1.mount: Deactivated successfully. Oct 5 00:59:17 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem db6b47b1-962a-400d-8233-07530b59f2d1. Oct 5 00:59:17 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/db6b47b1-962a-400d-8233-07530b59f2d1 (device 259:3 is not mounted) Oct 5 00:59:17 storageqe-109 udisksd[1947]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 5 00:59:17 storageqe-109 kernel: XFS (loop0p1): Mounting V5 Filesystem fbb4c1c8-33db-4678-a9d6-68acb5dc7427 Oct 5 00:59:17 storageqe-109 kernel: XFS (loop0p1): Ending clean mount Oct 5 00:59:17 storageqe-109 udisksd[1947]: Mounted /dev/loop0p1 at /run/media/root/fbb4c1c8-33db-4678-a9d6-68acb5dc7427 on behalf of uid 0 Oct 5 00:59:17 storageqe-109 kernel: XFS (loop0p1): Unmounting Filesystem fbb4c1c8-33db-4678-a9d6-68acb5dc7427 Oct 5 00:59:17 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/fbb4c1c8-33db-4678-a9d6-68acb5dc7427 (device 259:3 is not mounted) Oct 5 00:59:17 storageqe-109 udisksd[1947]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 5 00:59:17 storageqe-109 udisksd[1947]: Mounted /dev/loop0p1 at /run/media/root/dcaaec68-41aa-4d41-847a-858822741cf8 on behalf of uid 0 Oct 5 00:59:17 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem dcaaec68-41aa-4d41-847a-858822741cf8 r/w with ordered data mode. Quota mode: none. Oct 5 00:59:17 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem dcaaec68-41aa-4d41-847a-858822741cf8. Oct 5 00:59:17 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/dcaaec68-41aa-4d41-847a-858822741cf8 (device 259:3 is not mounted) Oct 5 00:59:17 storageqe-109 udisksd[1947]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 5 00:59:18 storageqe-109 systemd[1]: run-media-root-fbb4c1c8\x2d33db\x2d4678\x2da9d6\x2d68acb5dc7427.mount: Deactivated successfully. Oct 5 00:59:22 storageqe-109 kernel: loop0: Oct 5 00:59:22 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 00:59:22 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_part_mount #### INFO: #### will start test_bz1400056_md ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:59:28 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:59:28 storageqe-109 INFO: #### END test_part_mount #### Oct 5 00:59:28 storageqe-109 INFO: #### will start test_bz1400056_md ##### Oct 5 00:59:28 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 00:59:35 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 00:59:35 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 5 00:59:35 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 00:59:35 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 5 00:59:35 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 00:59:35 storageqe-109 INFO: raid level raid0 Oct 5 00:59:35 storageqe-109 INFO: raid name test_md Oct 5 00:59:35 storageqe-109 INFO: raid chunk 1048576 Oct 5 00:59:35 storageqe-109 INFO: raid bitmap None Oct 5 00:59:35 storageqe-109 INFO: raid version 1.2 Oct 5 00:59:35 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 INFO: Name test_md Oct 5 00:59:39 storageqe-109 INFO: Name test_md INFO: UUID e779257f:3ecfe417:379142b9:2f6a910f Oct 5 00:59:40 storageqe-109 INFO: UUID e779257f:3ecfe417:379142b9:2f6a910f INFO: Level raid0 Oct 5 00:59:41 storageqe-109 INFO: Level raid0 INFO: NumDevices 2 Oct 5 00:59:42 storageqe-109 INFO: NumDevices 2 INFO: Size 2141192192 Oct 5 00:59:43 storageqe-109 INFO: Size 2141192192 INFO: SyncAction Oct 5 00:59:44 storageqe-109 INFO: SyncAction INFO: SyncCompleted 0.0 Oct 5 00:59:45 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 5 00:59:46 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 5 00:59:47 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 5 00:59:48 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy Oct 5 00:59:49 storageqe-109 INFO: ConsistencyPolicy INFO: BitmapLocation dbus.Array([dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 5 00:59:50 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 5 00:59:51 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 5 00:59:53 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 5 00:59:54 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 5 00:59:55 storageqe-109 INFO: Running 1 INFO: bitma is , Oct 5 00:59:56 storageqe-109 INFO: bitma is , INFO: BitmapLocation Oct 5 00:59:57 storageqe-109 INFO: BitmapLocation Oct 5 01:00:03 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 5 01:00:03 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 3fa86574-0397-4c69-849e-d718fa47ba3e r/w with ordered data mode. Quota mode: none. Oct 5 01:00:03 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/3fa86574-0397-4c69-849e-d718fa47ba3e on behalf of uid 0 Oct 5 01:00:03 storageqe-109 systemd[1]: Starting raid-check.service - RAID setup health check... Oct 5 01:00:03 storageqe-109 systemd[1]: raid-check.service: Deactivated successfully. Oct 5 01:00:03 storageqe-109 systemd[1]: Finished raid-check.service - RAID setup health check. Oct 5 01:00:06 storageqe-109 systemd[1]: run-media-root-3fa86574\x2d0397\x2d4c69\x2d849e\x2dd718fa47ba3e.mount: Deactivated successfully. Oct 5 01:00:06 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 3fa86574-0397-4c69-849e-d718fa47ba3e. Oct 5 01:00:06 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/3fa86574-0397-4c69-849e-d718fa47ba3e (device 9:127 is not mounted) Oct 5 01:00:06 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:00:14 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem bb6ddacd-ad78-4072-b0f1-8c481f012b96 Oct 5 01:00:14 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/bb6ddacd-ad78-4072-b0f1-8c481f012b96 on behalf of uid 0 Oct 5 01:00:14 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 5 01:00:17 storageqe-109 systemd[1]: run-media-root-bb6ddacd\x2dad78\x2d4072\x2db0f1\x2d8c481f012b96.mount: Deactivated successfully. Oct 5 01:00:17 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/bb6ddacd-ad78-4072-b0f1-8c481f012b96 (device 9:127 is not mounted) Oct 5 01:00:17 storageqe-109 kernel: XFS (md127): Unmounting Filesystem bb6ddacd-ad78-4072-b0f1-8c481f012b96 Oct 5 01:00:17 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:00:25 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 68254a84-8f1b-4882-b62f-f4d1f9ad1b27 r/w with ordered data mode. Quota mode: none. Oct 5 01:00:25 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/68254a84-8f1b-4882-b62f-f4d1f9ad1b27 on behalf of uid 0 Oct 5 01:00:28 storageqe-109 systemd[1]: run-media-root-68254a84\x2d8f1b\x2d4882\x2db62f\x2df4d1f9ad1b27.mount: Deactivated successfully. Oct 5 01:00:28 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 68254a84-8f1b-4882-b62f-f4d1f9ad1b27. Oct 5 01:00:28 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/68254a84-8f1b-4882-b62f-f4d1f9ad1b27 (device 9:127 is not mounted) Oct 5 01:00:28 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:00:32 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 5 01:00:32 storageqe-109 kernel: md: md127 stopped. Oct 5 01:00:32 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:00:35 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 5 01:00:35 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:00:35 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 5 01:00:35 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:00:35 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:00:35 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 5 01:00:36 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md INFO: raid chunk 0 INFO: raid bitmap internal INFO: raid version 1.0 Oct 5 01:00:36 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 5 01:00:36 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:00:36 storageqe-109 INFO: raid level raid1 Oct 5 01:00:36 storageqe-109 INFO: raid name test_md Oct 5 01:00:36 storageqe-109 INFO: raid chunk 0 Oct 5 01:00:36 storageqe-109 INFO: raid bitmap internal Oct 5 01:00:36 storageqe-109 INFO: raid version 1.0 Oct 5 01:00:36 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:00:36 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:00:36 storageqe-109 kernel: md127: detected capacity change from 0 to 2097024 Oct 5 01:00:36 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:00:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:00:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:00:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:00:41 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 5 01:00:44 storageqe-109 INFO: Name test_md INFO: UUID c3fd917c:556b7b75:ee240784:f81c7124 Oct 5 01:00:45 storageqe-109 INFO: UUID c3fd917c:556b7b75:ee240784:f81c7124 INFO: Level raid1 Oct 5 01:00:46 storageqe-109 INFO: Level raid1 INFO: NumDevices 2 Oct 5 01:00:47 storageqe-109 INFO: NumDevices 2 INFO: Size 1073676288 Oct 5 01:00:48 storageqe-109 INFO: Size 1073676288 INFO: SyncAction idle Oct 5 01:00:49 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 5 01:00:50 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 5 01:00:51 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 5 01:00:52 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 5 01:00:53 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 5 01:00:54 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 5 01:00:55 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 0 Oct 5 01:00:56 storageqe-109 INFO: ChunkSize 0 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 5 01:00:57 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 5 01:00:58 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 5 01:00:59 storageqe-109 INFO: Running 1 INFO: bitma is -16, Oct 5 01:01:00 storageqe-109 INFO: bitma is -16, INFO: BitmapLocation -16 Oct 5 01:01:01 storageqe-109 INFO: BitmapLocation -16 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop2 at 0x7f34c19f60c0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop2 /org/freedesktop/UDisks2/block_devices/loop2 Oct 5 01:01:02 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 5 01:01:02 storageqe-109 udisksd[1947]: Set up loop device /dev/loop2 (backed by /home/loop0.img) Oct 5 01:01:02 storageqe-109 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop2 at 0x7f34c19f60c0> Oct 5 01:01:02 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop2 /org/freedesktop/UDisks2/block_devices/loop2 INFO: Oct 5 01:01:04 storageqe-109 INFO: INFO: Oct 5 01:01:07 storageqe-109 INFO: Oct 5 01:01:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:14 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 5 01:01:14 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 52b98eb5-139e-4660-b9fc-77afc1fa8b15 r/w with ordered data mode. Quota mode: none. Oct 5 01:01:14 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/52b98eb5-139e-4660-b9fc-77afc1fa8b15 on behalf of uid 0 Oct 5 01:01:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:17 storageqe-109 systemd[1]: run-media-root-52b98eb5\x2d139e\x2d4660\x2db9fc\x2d77afc1fa8b15.mount: Deactivated successfully. Oct 5 01:01:17 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 52b98eb5-139e-4660-b9fc-77afc1fa8b15. Oct 5 01:01:17 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/52b98eb5-139e-4660-b9fc-77afc1fa8b15 (device 9:127 is not mounted) Oct 5 01:01:17 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:01:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:25 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 4abad716-50ec-4216-869e-8e0b2218ffbf Oct 5 01:01:25 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 5 01:01:25 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/4abad716-50ec-4216-869e-8e0b2218ffbf on behalf of uid 0 Oct 5 01:01:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:28 storageqe-109 systemd[1]: run-media-root-4abad716\x2d50ec\x2d4216\x2d869e\x2d8e0b2218ffbf.mount: Deactivated successfully. Oct 5 01:01:28 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 4abad716-50ec-4216-869e-8e0b2218ffbf Oct 5 01:01:28 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/4abad716-50ec-4216-869e-8e0b2218ffbf (device 9:127 is not mounted) Oct 5 01:01:28 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:01:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:36 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/ede8e4de-dd72-42f7-b305-875e2a4202cb on behalf of uid 0 Oct 5 01:01:36 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem ede8e4de-dd72-42f7-b305-875e2a4202cb r/w with ordered data mode. Quota mode: none. Oct 5 01:01:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:39 storageqe-109 systemd[1]: run-media-root-ede8e4de\x2ddd72\x2d42f7\x2db305\x2d875e2a4202cb.mount: Deactivated successfully. Oct 5 01:01:39 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem ede8e4de-dd72-42f7-b305-875e2a4202cb. Oct 5 01:01:39 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/ede8e4de-dd72-42f7-b305-875e2a4202cb (device 9:127 is not mounted) Oct 5 01:01:39 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:01:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:43 storageqe-109 kernel: md127: detected capacity change from 2097024 to 0 Oct 5 01:01:43 storageqe-109 kernel: md: md127 stopped. Oct 5 01:01:44 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:01:46 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 5 01:01:46 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:01:46 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 5 01:01:46 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:01:47 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:01:47 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 5 01:01:47 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:01:47 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop11.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid4 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.2 Oct 5 01:01:48 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 5 01:01:48 storageqe-109 udisksd[1947]: Set up loop device /dev/loop3 (backed by /home/loop12.img) Oct 5 01:01:48 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 5 01:01:48 storageqe-109 INFO: raid level raid4 Oct 5 01:01:48 storageqe-109 INFO: raid name test_md Oct 5 01:01:48 storageqe-109 INFO: raid chunk 1048576 Oct 5 01:01:48 storageqe-109 INFO: raid bitmap internal Oct 5 01:01:48 storageqe-109 INFO: raid version 1.2 Oct 5 01:01:48 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 5 01:01:48 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 5 01:01:48 storageqe-109 kernel: md/raid:md127: raid level 4 active with 2 out of 3 devices, algorithm 0 Oct 5 01:01:48 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 Oct 5 01:01:48 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 01:01:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:01:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: Name test_md Oct 5 01:01:52 storageqe-109 INFO: Name test_md INFO: UUID 8efd0201:f44a6ef6:1dca87c8:933097e3 Oct 5 01:01:53 storageqe-109 INFO: UUID 8efd0201:f44a6ef6:1dca87c8:933097e3 Oct 5 01:01:53 storageqe-109 kernel: md: md127: recover done. INFO: Level raid4 Oct 5 01:01:54 storageqe-109 INFO: Level raid4 INFO: NumDevices 3 Oct 5 01:01:55 storageqe-109 INFO: NumDevices 3 INFO: Size 2141192192 Oct 5 01:01:56 storageqe-109 INFO: Size 2141192192 INFO: SyncAction idle Oct 5 01:01:57 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 5 01:01:58 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 5 01:01:59 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 5 01:02:00 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 5 01:02:01 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 5 01:02:02 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 5 01:02:03 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 5 01:02:04 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 5 01:02:05 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 5 01:02:06 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 5 01:02:07 storageqe-109 INFO: Running 1 INFO: bitma is +8, Oct 5 01:02:08 storageqe-109 INFO: bitma is +8, INFO: BitmapLocation +8 Oct 5 01:02:09 storageqe-109 INFO: BitmapLocation +8 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop4 at 0x7f34c19f6990> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop4 /org/freedesktop/UDisks2/block_devices/loop4 Oct 5 01:02:10 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 5 01:02:10 storageqe-109 udisksd[1947]: Set up loop device /dev/loop4 (backed by /home/loop0.img) Oct 5 01:02:10 storageqe-109 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop4 at 0x7f34c19f6990> Oct 5 01:02:10 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop4 /org/freedesktop/UDisks2/block_devices/loop4 INFO: Oct 5 01:02:12 storageqe-109 INFO: INFO: Oct 5 01:02:15 storageqe-109 INFO: Oct 5 01:02:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:22 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 5 01:02:22 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem ae2168cb-d867-47c2-b724-e2f147e3c07b r/w with ordered data mode. Quota mode: none. Oct 5 01:02:22 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/ae2168cb-d867-47c2-b724-e2f147e3c07b on behalf of uid 0 Oct 5 01:02:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:25 storageqe-109 systemd[1]: run-media-root-ae2168cb\x2dd867\x2d47c2\x2db724\x2de2f147e3c07b.mount: Deactivated successfully. Oct 5 01:02:25 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem ae2168cb-d867-47c2-b724-e2f147e3c07b. Oct 5 01:02:25 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/ae2168cb-d867-47c2-b724-e2f147e3c07b (device 9:127 is not mounted) Oct 5 01:02:25 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:02:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:33 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 92796cc4-4790-40c4-9754-c5d93b294aa9 Oct 5 01:02:33 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 5 01:02:33 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/92796cc4-4790-40c4-9754-c5d93b294aa9 on behalf of uid 0 Oct 5 01:02:33 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:36 storageqe-109 systemd[1]: run-media-root-92796cc4\x2d4790\x2d40c4\x2d9754\x2dc5d93b294aa9.mount: Deactivated successfully. Oct 5 01:02:36 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 92796cc4-4790-40c4-9754-c5d93b294aa9 Oct 5 01:02:36 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/92796cc4-4790-40c4-9754-c5d93b294aa9 (device 9:127 is not mounted) Oct 5 01:02:36 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:02:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:44 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/f07bfd86-d7c0-43d7-91df-22b70130ef3a on behalf of uid 0 Oct 5 01:02:44 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem f07bfd86-d7c0-43d7-91df-22b70130ef3a r/w with ordered data mode. Quota mode: none. Oct 5 01:02:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:47 storageqe-109 systemd[1]: run-media-root-f07bfd86\x2dd7c0\x2d43d7\x2d91df\x2d22b70130ef3a.mount: Deactivated successfully. Oct 5 01:02:47 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem f07bfd86-d7c0-43d7-91df-22b70130ef3a. Oct 5 01:02:47 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/f07bfd86-d7c0-43d7-91df-22b70130ef3a (device 9:127 is not mounted) Oct 5 01:02:47 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:02:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:51 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:51 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:52 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 5 01:02:52 storageqe-109 kernel: md: md127 stopped. Oct 5 01:02:52 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:02:55 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 5 01:02:55 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:02:55 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 5 01:02:55 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:02:55 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 5 01:02:55 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop3 Oct 5 01:02:55 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:02:55 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 5 01:02:55 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:02:55 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop11.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid5 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.2 Oct 5 01:02:56 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 5 01:02:56 storageqe-109 udisksd[1947]: Set up loop device /dev/loop3 (backed by /home/loop12.img) Oct 5 01:02:56 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 5 01:02:56 storageqe-109 INFO: raid level raid5 Oct 5 01:02:56 storageqe-109 INFO: raid name test_md Oct 5 01:02:56 storageqe-109 INFO: raid chunk 1048576 Oct 5 01:02:56 storageqe-109 INFO: raid bitmap internal Oct 5 01:02:56 storageqe-109 INFO: raid version 1.2 Oct 5 01:02:56 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 5 01:02:56 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 5 01:02:56 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 01:02:56 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 Oct 5 01:02:56 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 01:02:56 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:56 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:02:56 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: Name test_md Oct 5 01:03:00 storageqe-109 INFO: Name test_md INFO: UUID 824a2ccd:a086e78e:1b75b3f0:2467fbb4 Oct 5 01:03:01 storageqe-109 INFO: UUID 824a2ccd:a086e78e:1b75b3f0:2467fbb4 Oct 5 01:03:01 storageqe-109 kernel: md: md127: recover done. INFO: Level raid5 Oct 5 01:03:02 storageqe-109 INFO: Level raid5 INFO: NumDevices 3 Oct 5 01:03:03 storageqe-109 INFO: NumDevices 3 INFO: Size 2141192192 Oct 5 01:03:04 storageqe-109 INFO: Size 2141192192 INFO: SyncAction idle Oct 5 01:03:05 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 5 01:03:07 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 5 01:03:08 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 5 01:03:09 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 5 01:03:10 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 5 01:03:11 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 5 01:03:12 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 5 01:03:13 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 5 01:03:14 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 5 01:03:15 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 5 01:03:16 storageqe-109 INFO: Running 1 INFO: bitma is +8, Oct 5 01:03:17 storageqe-109 INFO: bitma is +8, INFO: BitmapLocation +8 Oct 5 01:03:18 storageqe-109 INFO: BitmapLocation +8 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop5 at 0x7f34c1b7dd30> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop5 /org/freedesktop/UDisks2/block_devices/loop5 Oct 5 01:03:18 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 5 01:03:18 storageqe-109 udisksd[1947]: Set up loop device /dev/loop5 (backed by /home/loop0.img) Oct 5 01:03:18 storageqe-109 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop5 at 0x7f34c1b7dd30> Oct 5 01:03:18 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop5 /org/freedesktop/UDisks2/block_devices/loop5 INFO: Oct 5 01:03:20 storageqe-109 INFO: INFO: Oct 5 01:03:23 storageqe-109 INFO: Oct 5 01:03:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:30 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 5 01:03:30 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 812c0583-30fd-4801-8043-937220ea4330 r/w with ordered data mode. Quota mode: none. Oct 5 01:03:30 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/812c0583-30fd-4801-8043-937220ea4330 on behalf of uid 0 Oct 5 01:03:30 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:33 storageqe-109 systemd[1]: run-media-root-812c0583\x2d30fd\x2d4801\x2d8043\x2d937220ea4330.mount: Deactivated successfully. Oct 5 01:03:33 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 812c0583-30fd-4801-8043-937220ea4330. Oct 5 01:03:33 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/812c0583-30fd-4801-8043-937220ea4330 (device 9:127 is not mounted) Oct 5 01:03:33 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:03:33 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:42 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 890f3357-1cce-4e18-8fc1-2dabb048f67b Oct 5 01:03:42 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 5 01:03:42 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/890f3357-1cce-4e18-8fc1-2dabb048f67b on behalf of uid 0 Oct 5 01:03:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:45 storageqe-109 systemd[1]: run-media-root-890f3357\x2d1cce\x2d4e18\x2d8fc1\x2d2dabb048f67b.mount: Deactivated successfully. Oct 5 01:03:45 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 890f3357-1cce-4e18-8fc1-2dabb048f67b Oct 5 01:03:45 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/890f3357-1cce-4e18-8fc1-2dabb048f67b (device 9:127 is not mounted) Oct 5 01:03:45 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:03:45 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:53 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/84ffa846-3447-4775-8ec1-c5b0fe2fdac0 on behalf of uid 0 Oct 5 01:03:53 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 84ffa846-3447-4775-8ec1-c5b0fe2fdac0 r/w with ordered data mode. Quota mode: none. Oct 5 01:03:53 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:56 storageqe-109 systemd[1]: run-media-root-84ffa846\x2d3447\x2d4775\x2d8ec1\x2dc5b0fe2fdac0.mount: Deactivated successfully. Oct 5 01:03:56 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 84ffa846-3447-4775-8ec1-c5b0fe2fdac0. Oct 5 01:03:56 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/84ffa846-3447-4775-8ec1-c5b0fe2fdac0 (device 9:127 is not mounted) Oct 5 01:03:56 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:03:56 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:03:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:00 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 5 01:04:00 storageqe-109 kernel: md: md127 stopped. Oct 5 01:04:00 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:04:03 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 5 01:04:03 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:04:03 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 5 01:04:03 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:04:03 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 5 01:04:03 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop3 Oct 5 01:04:03 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:04:03 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 5 01:04:04 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:04:04 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 5 01:04:04 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 5 01:04:04 storageqe-109 udisksd[1947]: Set up loop device /dev/loop3 (backed by /home/loop12.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] INFO: raid level raid6 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:04:05 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 5 01:04:05 storageqe-109 udisksd[1947]: Set up loop device /dev/loop6 (backed by /home/loop13.img) Oct 5 01:04:05 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] Oct 5 01:04:05 storageqe-109 INFO: raid level raid6 Oct 5 01:04:05 storageqe-109 INFO: raid name test_md Oct 5 01:04:05 storageqe-109 INFO: raid chunk 1048576 Oct 5 01:04:05 storageqe-109 INFO: raid bitmap None Oct 5 01:04:05 storageqe-109 INFO: raid version 1.2 Oct 5 01:04:05 storageqe-109 kernel: md/raid:md127: not clean -- starting background reconstruction Oct 5 01:04:05 storageqe-109 kernel: md/raid:md127: device loop6 operational as raid disk 3 Oct 5 01:04:05 storageqe-109 kernel: md/raid:md127: device loop3 operational as raid disk 2 Oct 5 01:04:05 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 5 01:04:05 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 5 01:04:05 storageqe-109 kernel: md/raid:md127: raid level 6 active with 4 out of 4 devices, algorithm 2 Oct 5 01:04:05 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 Oct 5 01:04:05 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:04:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:10 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 5 01:04:12 storageqe-109 INFO: Name test_md INFO: UUID 777cfab9:6dd985f8:0943023d:cf2a6c32 Oct 5 01:04:13 storageqe-109 INFO: UUID 777cfab9:6dd985f8:0943023d:cf2a6c32 INFO: Level raid6 Oct 5 01:04:14 storageqe-109 INFO: Level raid6 INFO: NumDevices 4 Oct 5 01:04:15 storageqe-109 INFO: NumDevices 4 INFO: Size 2141192192 Oct 5 01:04:16 storageqe-109 INFO: Size 2141192192 INFO: SyncAction idle Oct 5 01:04:17 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 5 01:04:18 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 5 01:04:19 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 5 01:04:20 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 5 01:04:21 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy resync Oct 5 01:04:22 storageqe-109 INFO: ConsistencyPolicy resync INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 5 01:04:23 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 5 01:04:24 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6'), dbus.Int32(3), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 5 01:04:26 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 5 01:04:27 storageqe-109 INFO: Running 1 INFO: bitma is none, INFO: looks don't set bitmap Oct 5 01:04:28 storageqe-109 INFO: bitma is none, Oct 5 01:04:28 storageqe-109 INFO: looks don't set bitmap Oct 5 01:04:28 storageqe-109 kernel: md127: bitmap file is out of date (0 < 17) -- forcing full recovery Oct 5 01:04:28 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery INFO: BitmapLocation +8 Oct 5 01:04:30 storageqe-109 INFO: BitmapLocation +8 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop7 at 0x7f34c19f5be0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop7 /org/freedesktop/UDisks2/block_devices/loop7 Oct 5 01:04:31 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 5 01:04:31 storageqe-109 udisksd[1947]: Set up loop device /dev/loop7 (backed by /home/loop0.img) Oct 5 01:04:31 storageqe-109 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop7 at 0x7f34c19f5be0> Oct 5 01:04:31 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop7 /org/freedesktop/UDisks2/block_devices/loop7 INFO: Oct 5 01:04:33 storageqe-109 INFO: INFO: Oct 5 01:04:36 storageqe-109 INFO: Oct 5 01:04:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:43 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 5 01:04:43 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 597e934b-cd32-47f4-8bca-ae16f8760a9a r/w with ordered data mode. Quota mode: none. Oct 5 01:04:43 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/597e934b-cd32-47f4-8bca-ae16f8760a9a on behalf of uid 0 Oct 5 01:04:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:46 storageqe-109 systemd[1]: run-media-root-597e934b\x2dcd32\x2d47f4\x2d8bca\x2dae16f8760a9a.mount: Deactivated successfully. Oct 5 01:04:46 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 597e934b-cd32-47f4-8bca-ae16f8760a9a. Oct 5 01:04:46 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/597e934b-cd32-47f4-8bca-ae16f8760a9a (device 9:127 is not mounted) Oct 5 01:04:46 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:04:46 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:54 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 5183a3b4-7022-472b-8516-f2dfef5a4629 Oct 5 01:04:54 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/5183a3b4-7022-472b-8516-f2dfef5a4629 on behalf of uid 0 Oct 5 01:04:54 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 5 01:04:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:04:57 storageqe-109 systemd[1]: run-media-root-5183a3b4\x2d7022\x2d472b\x2d8516\x2df2dfef5a4629.mount: Deactivated successfully. Oct 5 01:04:57 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 5183a3b4-7022-472b-8516-f2dfef5a4629 Oct 5 01:04:57 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/5183a3b4-7022-472b-8516-f2dfef5a4629 (device 9:127 is not mounted) Oct 5 01:04:57 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:04:57 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:05 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 7f9e4bea-f625-44b0-ae42-130eb4ab8d81 r/w with ordered data mode. Quota mode: none. Oct 5 01:05:05 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/7f9e4bea-f625-44b0-ae42-130eb4ab8d81 on behalf of uid 0 Oct 5 01:05:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:08 storageqe-109 systemd[1]: run-media-root-7f9e4bea\x2df625\x2d44b0\x2dae42\x2d130eb4ab8d81.mount: Deactivated successfully. Oct 5 01:05:08 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 7f9e4bea-f625-44b0-ae42-130eb4ab8d81. Oct 5 01:05:08 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/7f9e4bea-f625-44b0-ae42-130eb4ab8d81 (device 9:127 is not mounted) Oct 5 01:05:08 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:05:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:12 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:13 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 5 01:05:13 storageqe-109 kernel: md: md127 stopped. Oct 5 01:05:13 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:05:16 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 5 01:05:16 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:05:16 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 5 01:05:16 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:05:16 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 5 01:05:16 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop3 Oct 5 01:05:16 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop6 (was backed by /home/loop13.img) Oct 5 01:05:16 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop6 Oct 5 01:05:16 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:05:16 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 5 01:05:16 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:05:16 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 5 01:05:17 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 5 01:05:17 storageqe-109 udisksd[1947]: Set up loop device /dev/loop3 (backed by /home/loop12.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] INFO: raid level raid10 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.2 Oct 5 01:05:17 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 5 01:05:17 storageqe-109 udisksd[1947]: Set up loop device /dev/loop6 (backed by /home/loop13.img) Oct 5 01:05:17 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] Oct 5 01:05:17 storageqe-109 INFO: raid level raid10 Oct 5 01:05:17 storageqe-109 INFO: raid name test_md Oct 5 01:05:17 storageqe-109 INFO: raid chunk 1048576 Oct 5 01:05:17 storageqe-109 INFO: raid bitmap internal Oct 5 01:05:17 storageqe-109 INFO: raid version 1.2 Oct 5 01:05:17 storageqe-109 kernel: md/raid10:md127: not clean -- starting background reconstruction Oct 5 01:05:17 storageqe-109 kernel: md/raid10:md127: active with 4 out of 4 devices Oct 5 01:05:17 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 Oct 5 01:05:17 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:05:18 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:18 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:18 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:28 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 5 01:05:30 storageqe-109 INFO: Name test_md INFO: UUID 3f9366cd:88fb4f22:e3b51c94:052eae07 Oct 5 01:05:31 storageqe-109 INFO: UUID 3f9366cd:88fb4f22:e3b51c94:052eae07 INFO: Level raid10 Oct 5 01:05:32 storageqe-109 INFO: Level raid10 INFO: NumDevices 4 Oct 5 01:05:33 storageqe-109 INFO: NumDevices 4 INFO: Size 2141192192 Oct 5 01:05:34 storageqe-109 INFO: Size 2141192192 INFO: SyncAction idle Oct 5 01:05:35 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 5 01:05:36 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 5 01:05:37 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 5 01:05:38 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 5 01:05:39 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 5 01:05:40 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 5 01:05:41 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 5 01:05:42 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6'), dbus.Int32(3), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 5 01:05:44 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 5 01:05:45 storageqe-109 INFO: Running 1 INFO: bitma is +8, Oct 5 01:05:46 storageqe-109 INFO: bitma is +8, INFO: BitmapLocation +8 Oct 5 01:05:47 storageqe-109 INFO: BitmapLocation +8 Oct 5 01:05:47 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop8 at 0x7f34c1b7e0c0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop8 /org/freedesktop/UDisks2/block_devices/loop8 Oct 5 01:05:47 storageqe-109 udisksd[1947]: Set up loop device /dev/loop8 (backed by /home/loop0.img) Oct 5 01:05:47 storageqe-109 INFO: new_disk_obj :1.26 /org/freedesktop/UDisks2/block_devices/loop8 at 0x7f34c1b7e0c0> Oct 5 01:05:48 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop8 /org/freedesktop/UDisks2/block_devices/loop8 INFO: Oct 5 01:05:50 storageqe-109 INFO: INFO: Oct 5 01:05:53 storageqe-109 INFO: Oct 5 01:05:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:05:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:00 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 5 01:06:00 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 25e9141b-22c2-4f4e-93cd-6c62c04cf88b r/w with ordered data mode. Quota mode: none. Oct 5 01:06:00 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/25e9141b-22c2-4f4e-93cd-6c62c04cf88b on behalf of uid 0 Oct 5 01:06:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:03 storageqe-109 systemd[1]: run-media-root-25e9141b\x2d22c2\x2d4f4e\x2d93cd\x2d6c62c04cf88b.mount: Deactivated successfully. Oct 5 01:06:03 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 25e9141b-22c2-4f4e-93cd-6c62c04cf88b. Oct 5 01:06:03 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/25e9141b-22c2-4f4e-93cd-6c62c04cf88b (device 9:127 is not mounted) Oct 5 01:06:03 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:06:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:11 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 9aec4753-c9af-42b7-9ac6-c458e7ad1d1b Oct 5 01:06:11 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 5 01:06:11 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/9aec4753-c9af-42b7-9ac6-c458e7ad1d1b on behalf of uid 0 Oct 5 01:06:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:14 storageqe-109 systemd[1]: run-media-root-9aec4753\x2dc9af\x2d42b7\x2d9ac6\x2dc458e7ad1d1b.mount: Deactivated successfully. Oct 5 01:06:14 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 9aec4753-c9af-42b7-9ac6-c458e7ad1d1b Oct 5 01:06:14 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/9aec4753-c9af-42b7-9ac6-c458e7ad1d1b (device 9:127 is not mounted) Oct 5 01:06:14 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:06:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:17 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 01:06:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:17 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 01:06:17 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 01:06:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:22 storageqe-109 udisksd[1947]: Mounted /dev/md127 at /run/media/root/e0bb0fe4-6c9c-4a51-b34a-3583bec700e7 on behalf of uid 0 Oct 5 01:06:22 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem e0bb0fe4-6c9c-4a51-b34a-3583bec700e7 r/w with ordered data mode. Quota mode: none. Oct 5 01:06:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:25 storageqe-109 systemd[1]: run-media-root-e0bb0fe4\x2d6c9c\x2d4a51\x2db34a\x2d3583bec700e7.mount: Deactivated successfully. Oct 5 01:06:25 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem e0bb0fe4-6c9c-4a51-b34a-3583bec700e7. Oct 5 01:06:25 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/e0bb0fe4-6c9c-4a51-b34a-3583bec700e7 (device 9:127 is not mounted) Oct 5 01:06:25 storageqe-109 udisksd[1947]: Unmounted /dev/md127 on behalf of uid 0 Oct 5 01:06:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:06:29 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 5 01:06:29 storageqe-109 kernel: md: md127 stopped. Oct 5 01:06:29 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:06:32 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 5 01:06:32 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:06:32 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 5 01:06:32 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:06:32 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 5 01:06:32 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop3 Oct 5 01:06:32 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop6 (was backed by /home/loop13.img) Oct 5 01:06:32 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop6 Oct 5 01:06:33 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop8 Oct 5 01:06:33 storageqe-109 udisksd[1947]: udisks_state_check_loop_entry: unexpected name for /dev/loop7 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 5 01:06:33 storageqe-109 udisksd[1947]: udisks_state_check_loop_entry: unexpected name for /dev/loop2 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 5 01:06:33 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop2 Oct 5 01:06:33 storageqe-109 udisksd[1947]: udisks_state_check_loop_entry: unexpected name for /dev/loop4 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 5 01:06:33 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop4 Oct 5 01:06:33 storageqe-109 udisksd[1947]: udisks_state_check_loop_entry: unexpected name for /dev/loop5 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 5 01:06:33 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop5 Oct 5 01:06:33 storageqe-109 udisksd[1947]: udisks_state_check_loop_entry: unexpected name for /dev/loop7 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 5 01:06:33 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop7 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1400056_md #### INFO: #### will start test_bz1710257_iSCSI_initiator_byte ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:06:38 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:06:38 storageqe-109 INFO: #### END test_bz1400056_md #### Oct 5 01:06:38 storageqe-109 INFO: #### will start test_bz1710257_iSCSI_initiator_byte ##### Oct 5 01:06:38 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1710257_iSCSI_initiator_byte #### INFO: #### will start test_bz1668291_snapshot ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:06:51 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:06:51 storageqe-109 INFO: #### END test_bz1710257_iSCSI_initiator_byte #### Oct 5 01:06:51 storageqe-109 INFO: #### will start test_bz1668291_snapshot ##### Oct 5 01:06:51 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:06:57 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:06:57 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 5 01:07:02 storageqe-109 dmeventd[1921687]: Monitoring snapshot vg03-snap01. Oct 5 01:07:03 storageqe-109 dmeventd[1921687]: No longer monitoring snapshot vg03-snap01. Oct 5 01:07:10 storageqe-109 kernel: loop0: Oct 5 01:07:10 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 5 01:07:10 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1668291_snapshot #### INFO: #### will start test_bz1534904_get_thin_size ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:07:16 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:07:16 storageqe-109 INFO: #### END test_bz1668291_snapshot #### Oct 5 01:07:16 storageqe-109 INFO: #### will start test_bz1534904_get_thin_size ##### Oct 5 01:07:16 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:07:22 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:07:22 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 5 01:07:22 storageqe-109 kernel: loop0: Oct 5 01:07:24 storageqe-109 dmeventd[1921687]: Monitoring thin pool vg03-tp3. Oct 5 01:07:27 storageqe-109 dmeventd[1921687]: No longer monitoring thin pool vg03-tp3. Oct 5 01:07:28 storageqe-109 dmeventd[1921687]: Monitoring thin pool vg03-tp3-tpool. Oct 5 01:07:30 storageqe-109 dmeventd[1921687]: No longer monitoring thin pool vg03-tp3-tpool. Oct 5 01:07:37 storageqe-109 kernel: loop0: Oct 5 01:07:37 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 5 01:07:37 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1534904_get_thin_size #### INFO: #### will start test_bz2120697_ata_secure_erase ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:07:44 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:07:44 storageqe-109 INFO: #### END test_bz1534904_get_thin_size #### Oct 5 01:07:44 storageqe-109 INFO: #### will start test_bz2120697_ata_secure_erase ##### Oct 5 01:07:44 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:07:51 storageqe-109 systemd[1]: Started run-p1934549-i1934849.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 5 01:07:51 storageqe-109 systemd[1]: Starting man-db-cache-update.service... Oct 5 01:07:51 storageqe-109 systemd[1]: Reload requested from client PID 1934553 ('systemctl') (unit session-10.scope)... Oct 5 01:07:51 storageqe-109 systemd[1]: Reloading... Oct 5 01:07:51 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 5 01:07:51 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 01:07:51 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 01:07:51 storageqe-109 systemd[1]: Reloading finished in 146 ms. Oct 5 01:07:51 storageqe-109 systemd[1]: man-db-cache-update.service: Deactivated successfully. Oct 5 01:07:51 storageqe-109 systemd[1]: Finished man-db-cache-update.service. Oct 5 01:07:51 storageqe-109 systemd[1]: run-p1934549-i1934849.service: Deactivated successfully. Oct 5 01:07:51 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:07:51 storageqe-109 iscsid[1920151]: iscsid shutting down. Oct 5 01:07:51 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:07:51 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:07:51 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:07:51 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:07:51 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 01:07:52 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 01:07:52 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 01:07:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz2120697_ata_secure_erase #### INFO: #### will start test_journalctl_log_check ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:08:08 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:08:08 storageqe-109 INFO: #### END test_bz2120697_ata_secure_erase #### Oct 5 01:08:08 storageqe-109 INFO: #### will start test_journalctl_log_check ##### Oct 5 01:08:08 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_journalctl_log_check #### INFO: #### will start test_bz1983602_iscsi_login_failed ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:08:21 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:08:21 storageqe-109 INFO: #### END test_journalctl_log_check #### Oct 5 01:08:21 storageqe-109 INFO: #### will start test_bz1983602_iscsi_login_failed ##### Oct 5 01:08:21 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:08:22 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 5 01:08:27 storageqe-109 INFO: Setting up local iSCSI target... Oct 5 01:08:27 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 5 01:08:27 storageqe-109 INFO: Creating test disk files... Oct 5 01:08:27 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 5 01:08:27 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 Oct 5 01:08:27 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 Oct 5 01:08:27 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 5 01:08:27 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 5 01:08:28 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 5 01:08:28 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 5 01:08:28 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 5 01:08:30 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 5 01:08:30 storageqe-109 kernel: dev[000000004058b9a7]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:08:30 storageqe-109 kernel: dev[00000000ef0cf0b5]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:08:30 storageqe-109 kernel: dev[000000003a5a18c0]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:08:30 storageqe-109 kernel: dev[000000000bc39720]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:08:30 storageqe-109 kernel: dev[000000003ca0c13f]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:08:30 storageqe-109 kernel: dev[000000005799707d]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:08:30 storageqe-109 kernel: dev[00000000a76b9b60]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:08:30 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 5 01:08:30 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:08:30 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:08:30 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 5 01:08:30 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 5 01:08:30 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:08:30 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 5 01:08:30 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 5 01:08:30 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:08:30 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:30 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 5 01:08:30 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 5 01:08:30 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:08:30 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:08:30 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 5 01:08:30 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 5 01:08:30 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:08:30 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:30 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 5 01:08:30 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 5 01:08:30 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 5 01:08:30 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:08:30 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:30 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 5 01:08:30 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 5 01:08:30 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:08:31 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:31 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:08:31 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 5 01:08:31 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 5 01:08:31 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:08:31 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 5 01:08:31 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 5 01:08:31 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 5 01:08:31 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:08:31 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:31 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 5 01:08:31 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 5 01:08:31 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:08:31 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:08:31 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:31 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 5 01:08:31 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:08:31 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 5 01:08:31 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 5 01:08:31 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:08:31 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:31 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 5 01:08:31 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 5 01:08:31 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 5 01:08:31 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:31 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 5 01:08:31 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 5 01:08:41 storageqe-109 INFO: Verifying iSCSI target setup... Oct 5 01:08:41 storageqe-109 INFO: Found 4 LIO target(s) Oct 5 01:08:41 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 5 01:08:42 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:08:42 storageqe-109 iscsid[1934616]: iscsid shutting down. Oct 5 01:08:42 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:08:42 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:08:42 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:08:42 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:08:42 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 01:08:42 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:08:42 storageqe-109 iscsid[1935652]: iscsid shutting down. Oct 5 01:08:42 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:08:42 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:08:42 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:08:42 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:08:42 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 01:08:42 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 5 01:08:42 storageqe-109 iscsid[1935658]: iscsid: Login authentication failed with target iqn.2003-01.udisks.test:iscsi-test-noauth, T bit set on response, but authenticaton not complete Oct 5 01:08:42 storageqe-109 iscsid[1935658]: iscsid: connection9:0 Login error (Login status 5) Oct 5 01:08:42 storageqe-109 kernel: iSCSI Login negotiation failed. Oct 5 01:08:42 storageqe-109 iscsid[1935658]: iscsid: Connection9:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 5 01:08:43 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:08:43 storageqe-109 iscsid[1935658]: iscsid shutting down. Oct 5 01:08:43 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:08:43 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:08:43 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:08:43 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:08:43 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 01:08:43 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:08:43 storageqe-109 iscsid[1935671]: iscsid shutting down. Oct 5 01:08:43 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:08:43 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:08:43 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:08:43 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:08:43 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 01:08:43 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 5 01:08:43 storageqe-109 iscsid[1935676]: iscsid: Connection10:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 5 01:08:43 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 5 01:08:43 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 5 01:08:43 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:08:43 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 5 01:08:43 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk Oct 5 01:08:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 5 01:08:43 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 5 01:08:43 storageqe-109 iscsid[1935676]: iscsid: Connection10:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 5 01:08:44 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 5 01:08:44 storageqe-109 INFO: Clearing targetcli configuration... Oct 5 01:08:44 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 5 01:08:44 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 5 01:08:45 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 5 01:08:45 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 5 01:08:45 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 5 01:08:45 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 5 01:08:45 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 5 01:08:45 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 5 01:08:45 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 5 01:08:45 storageqe-109 INFO: Removing test disk files... Oct 5 01:08:45 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 5 01:08:45 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 5 01:08:45 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 5 01:08:45 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 5 01:08:45 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 5 01:08:45 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 5 01:08:45 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 5 01:08:45 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1983602_iscsi_login_failed #### INFO: #### will start test_bz2136557_iscsi_chap ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:08:51 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:08:51 storageqe-109 INFO: #### END test_bz1983602_iscsi_login_failed #### Oct 5 01:08:51 storageqe-109 INFO: #### will start test_bz2136557_iscsi_chap ##### Oct 5 01:08:51 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 Oct 5 01:08:57 storageqe-109 INFO: Setting up local iSCSI target... Oct 5 01:08:57 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 5 01:08:57 storageqe-109 INFO: Creating test disk files... Oct 5 01:08:57 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 5 01:08:58 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 5 01:08:58 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 5 01:08:58 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 5 01:08:58 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 5 01:08:58 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 5 01:08:58 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 5 01:08:58 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 5 01:09:00 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 5 01:09:01 storageqe-109 kernel: dev[00000000bf852954]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:09:01 storageqe-109 kernel: dev[000000009f51c177]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:09:01 storageqe-109 kernel: dev[00000000c2460924]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:09:01 storageqe-109 kernel: dev[000000001be7c8ba]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:09:01 storageqe-109 kernel: dev[000000005799707d]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:09:01 storageqe-109 kernel: dev[00000000a76b9b60]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:09:01 storageqe-109 kernel: dev[0000000039965492]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:09:01 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 5 01:09:01 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:09:01 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:09:01 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 5 01:09:01 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 5 01:09:01 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:09:01 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 5 01:09:01 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 5 01:09:01 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 5 01:09:01 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 5 01:09:01 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:09:01 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 5 01:09:01 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 5 01:09:01 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:09:01 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 5 01:09:01 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 5 01:09:01 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 5 01:09:01 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 5 01:09:01 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:09:01 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:09:01 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 5 01:09:01 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 5 01:09:01 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:09:01 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 5 01:09:01 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 5 01:09:01 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 5 01:09:01 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 5 01:09:01 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:09:01 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:09:01 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 5 01:09:01 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 5 01:09:01 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 5 01:09:01 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:09:01 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 5 01:09:01 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 5 01:09:01 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 5 01:09:01 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 5 01:09:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:01 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 5 01:09:01 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 5 01:09:11 storageqe-109 INFO: Verifying iSCSI target setup... Oct 5 01:09:11 storageqe-109 INFO: Found 4 LIO target(s) Oct 5 01:09:11 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 5 01:09:11 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:09:11 storageqe-109 iscsid[1935676]: iscsid shutting down. Oct 5 01:09:11 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:09:11 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:09:11 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:09:11 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:09:11 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 01:09:11 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 5 01:09:11 storageqe-109 iscsid[1936159]: iscsid: Connection11:0 to [target: iqn.2003-01.udisks.test:iscsi-test-chap, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 5 01:09:11 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 5 01:09:11 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 5 01:09:11 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 2 Oct 5 01:09:11 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 5 01:09:11 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) INFO: initfw_name None Oct 5 01:09:11 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 5 01:09:11 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:09:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:11 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 5 01:09:11 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 5 01:09:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:11 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk Oct 5 01:09:11 storageqe-109 INFO: initfw_name None INFO: init_name iqn.1994-05.com.redhat:iscsi-test INFO: init_name_raw iqn.1994-05.com.redhat:iscsi-test Oct 5 01:09:11 storageqe-109 INFO: init_name iqn.1994-05.com.redhat:iscsi-test Oct 5 01:09:11 storageqe-109 INFO: init_name_raw iqn.1994-05.com.redhat:iscsi-test INFO: target_name iqn.2003-01.udisks.test:iscsi-test-chap Oct 5 01:09:13 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-chap INFO: tpgt 1 Oct 5 01:09:14 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 5 01:09:15 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 5 01:09:16 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 5 01:09:17 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 5 01:09:18 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 5 01:09:19 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 5 01:09:20 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 5 01:09:21 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 Oct 5 01:09:22 storageqe-109 INFO: tgt_reset_timeout 30 Oct 5 01:09:22 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 5 01:09:23 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 5 01:09:23 storageqe-109 iscsid[1936159]: iscsid: Connection11:0 to [target: iqn.2003-01.udisks.test:iscsi-test-chap, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 5 01:09:23 storageqe-109 iscsid[1936159]: iscsid shutting down. Oct 5 01:09:23 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:09:23 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:09:23 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:09:23 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:09:23 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:09:23 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 01:09:23 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 5 01:09:23 storageqe-109 iscsid[1936252]: iscsid: Connection12:0 to [target: iqn.2003-01.udisks.test:iscsi-test-mutual, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 5 01:09:23 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 5 01:09:23 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 5 01:09:23 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 3 Oct 5 01:09:23 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:09:23 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 5 01:09:23 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 5 01:09:23 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:09:23 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:23 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 5 01:09:23 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 5 01:09:23 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:09:23 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: target_name iqn.2003-01.udisks.test:iscsi-test-mutual Oct 5 01:09:25 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-mutual INFO: tpgt 1 Oct 5 01:09:26 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 5 01:09:27 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 5 01:09:28 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 5 01:09:29 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 5 01:09:30 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 5 01:09:31 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 5 01:09:32 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 5 01:09:33 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 5 01:09:34 storageqe-109 INFO: tgt_reset_timeout 30 Oct 5 01:09:34 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 5 01:09:34 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 5 01:09:34 storageqe-109 iscsid[1936252]: iscsid: Connection12:0 to [target: iqn.2003-01.udisks.test:iscsi-test-mutual, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 5 01:09:34 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 5 01:09:34 storageqe-109 INFO: Clearing targetcli configuration... Oct 5 01:09:34 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 5 01:09:34 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 5 01:09:34 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 5 01:09:34 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 5 01:09:34 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 5 01:09:34 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 5 01:09:35 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 5 01:09:35 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 5 01:09:35 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 5 01:09:35 storageqe-109 INFO: Removing test disk files... Oct 5 01:09:35 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 5 01:09:35 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 5 01:09:35 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 5 01:09:35 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 5 01:09:35 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 5 01:09:35 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 5 01:09:35 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 5 01:09:35 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz2136557_iscsi_chap #### INFO: #### will start test_md_stop ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:09:41 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:09:41 storageqe-109 INFO: #### END test_bz2136557_iscsi_chap #### Oct 5 01:09:41 storageqe-109 INFO: #### will start test_md_stop ##### Oct 5 01:09:41 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:09:48 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:09:48 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_stop_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_stop INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:09:48 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:09:48 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_stop_1.img) Oct 5 01:09:48 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:09:48 storageqe-109 INFO: raid level raid1 Oct 5 01:09:48 storageqe-109 INFO: raid name test_md_stop Oct 5 01:09:48 storageqe-109 INFO: raid chunk 0 Oct 5 01:09:48 storageqe-109 INFO: raid bitmap None Oct 5 01:09:48 storageqe-109 INFO: raid version 1.2 Oct 5 01:09:48 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:09:48 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:09:48 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:09:48 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:09:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:09:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:09:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:09:54 storageqe-109 kernel: md: md127: resync done. Oct 5 01:09:57 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:09:57 storageqe-109 kernel: md: md127 stopped. Oct 5 01:09:57 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:10:01 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_stop_0.img) Oct 5 01:10:01 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:10:01 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_stop_1.img) Oct 5 01:10:01 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_md_stop #### INFO: #### will start test_fs_label_and_resize ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:08 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:08 storageqe-109 INFO: #### END test_md_stop #### Oct 5 01:10:08 storageqe-109 INFO: #### will start test_fs_label_and_resize ##### Oct 5 01:10:08 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:14 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:10:14 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_fs.img) Oct 5 01:10:14 storageqe-109 kernel: loop0: Oct 5 01:10:28 storageqe-109 kernel: loop0: Oct 5 01:10:28 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_fs.img) Oct 5 01:10:28 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fs_label_and_resize #### INFO: #### will start test_fstab_handling ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:34 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:34 storageqe-109 INFO: #### END test_fs_label_and_resize #### Oct 5 01:10:34 storageqe-109 INFO: #### will start test_fstab_handling ##### Oct 5 01:10:34 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:41 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:10:41 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_fstab.img) Oct 5 01:10:41 storageqe-109 kernel: loop0: Oct 5 01:10:52 storageqe-109 kernel: loop0: Oct 5 01:10:52 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_fstab.img) Oct 5 01:10:52 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fstab_handling #### INFO: #### will start test_manager_device_listing_and_resolving ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:59 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:10:59 storageqe-109 INFO: #### END test_fstab_handling #### Oct 5 01:10:59 storageqe-109 INFO: #### will start test_manager_device_listing_and_resolving ##### Oct 5 01:10:59 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:11:05 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:11:05 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_manager.img) Oct 5 01:11:05 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_manager.img) Oct 5 01:11:05 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_manager_device_listing_and_resolving #### INFO: #### will start test_luks_change_password ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:11:11 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:11:11 storageqe-109 INFO: #### END test_manager_device_listing_and_resolving #### Oct 5 01:11:11 storageqe-109 INFO: #### will start test_luks_change_password ##### Oct 5 01:11:11 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:11:18 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:11:18 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_luks_passwd.img) Oct 5 01:11:18 storageqe-109 kernel: loop0: INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'initial_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2i', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 5 01:11:19 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'initial_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2i', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 5 01:11:26 storageqe-109 stratisd[1277]: [2025-10-05T05:11:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:26 storageqe-109 stratisd[1277]: [2025-10-05T05:11:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:29 storageqe-109 stratisd[1277]: [2025-10-05T05:11:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:29 storageqe-109 stratisd[1277]: [2025-10-05T05:11:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 5 01:11:30 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 5 01:11:31 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 5 01:11:32 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to argon2i Oct 5 01:11:33 storageqe-109 INFO: foramt to luks2 Oct 5 01:11:33 storageqe-109 INFO: foramt to argon2i INFO: changed passwd to redhatredhat Oct 5 01:11:41 storageqe-109 stratisd[1277]: [2025-10-05T05:11:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:41 storageqe-109 stratisd[1277]: [2025-10-05T05:11:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:41 storageqe-109 INFO: changed passwd to redhatredhat Oct 5 01:11:41 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:11:41 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:11:42 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:11:44 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:11:46 storageqe-109 stratisd[1277]: [2025-10-05T05:11:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:46 storageqe-109 stratisd[1277]: [2025-10-05T05:11:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:46 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 INFO: changed passwd to initial_password Oct 5 01:11:54 storageqe-109 stratisd[1277]: [2025-10-05T05:11:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:54 storageqe-109 stratisd[1277]: [2025-10-05T05:11:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:54 storageqe-109 INFO: changed passwd to initial_password Oct 5 01:11:54 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:11:54 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:11:54 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:11:56 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:11:58 storageqe-109 stratisd[1277]: [2025-10-05T05:11:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:58 storageqe-109 stratisd[1277]: [2025-10-05T05:11:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:11:58 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 01:12:07 storageqe-109 stratisd[1277]: [2025-10-05T05:12:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:07 storageqe-109 stratisd[1277]: [2025-10-05T05:12:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:07 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 01:12:07 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:12:09 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:12:11 storageqe-109 stratisd[1277]: [2025-10-05T05:12:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:11 storageqe-109 stratisd[1277]: [2025-10-05T05:12:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:11 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 01:12:20 storageqe-109 stratisd[1277]: [2025-10-05T05:12:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:20 storageqe-109 stratisd[1277]: [2025-10-05T05:12:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:20 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 01:12:20 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:12:22 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 5 01:12:24 storageqe-109 stratisd[1277]: [2025-10-05T05:12:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:24 storageqe-109 stratisd[1277]: [2025-10-05T05:12:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:24 storageqe-109 udisksd[1947]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 5 01:12:32 storageqe-109 stratisd[1277]: [2025-10-05T05:12:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:32 storageqe-109 stratisd[1277]: [2025-10-05T05:12:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:12:32 storageqe-109 udisksd[1947]: LUKS device 253:3 was manually removed Oct 5 01:12:33 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 5 01:12:38 storageqe-109 kernel: loop0: Oct 5 01:12:38 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_luks_passwd.img) Oct 5 01:12:38 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_change_password #### INFO: #### will start test_manager_properties ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:12:44 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:12:44 storageqe-109 INFO: #### END test_luks_change_password #### Oct 5 01:12:44 storageqe-109 INFO: #### will start test_manager_properties ##### Oct 5 01:12:44 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_manager_properties #### INFO: #### will start test_nvme_manager_properties ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:12:59 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:12:59 storageqe-109 INFO: #### END test_manager_properties #### Oct 5 01:12:59 storageqe-109 INFO: #### will start test_nvme_manager_properties ##### Oct 5 01:12:59 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_manager_properties #### INFO: #### will start test_nvme_smart_update ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:19 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:19 storageqe-109 INFO: #### END test_nvme_manager_properties #### Oct 5 01:13:19 storageqe-109 INFO: #### will start test_nvme_smart_update ##### Oct 5 01:13:19 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_update #### INFO: #### will start test_nvme_smart_get_attributes ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:32 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:32 storageqe-109 INFO: #### END test_nvme_smart_update #### Oct 5 01:13:32 storageqe-109 INFO: #### will start test_nvme_smart_get_attributes ##### Oct 5 01:13:32 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_get_attributes #### INFO: #### will start test_nvme_smart_self_test ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:45 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:45 storageqe-109 INFO: #### END test_nvme_smart_get_attributes #### Oct 5 01:13:45 storageqe-109 INFO: #### will start test_nvme_smart_self_test ##### Oct 5 01:13:45 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_self_test #### INFO: #### will start test_nvme_properties_validation ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:59 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:13:59 storageqe-109 INFO: #### END test_nvme_smart_self_test #### Oct 5 01:13:59 storageqe-109 INFO: #### will start test_nvme_properties_validation ##### Oct 5 01:13:59 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_properties_validation #### INFO: #### will start test_iscsi_session_logout_no_interface ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:14:12 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:14:12 storageqe-109 INFO: #### END test_nvme_properties_validation #### Oct 5 01:14:12 storageqe-109 INFO: #### will start test_iscsi_session_logout_no_interface ##### Oct 5 01:14:12 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 5 01:14:18 storageqe-109 INFO: Setting up local iSCSI target... Oct 5 01:14:18 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 5 01:14:18 storageqe-109 INFO: Creating test disk files... Oct 5 01:14:18 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 5 01:14:18 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 5 01:14:18 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 5 01:14:19 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 5 01:14:19 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 5 01:14:19 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 5 01:14:19 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 5 01:14:19 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 5 01:14:21 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 5 01:14:21 storageqe-109 kernel: dev[00000000c2460924]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:14:21 storageqe-109 kernel: dev[00000000bf852954]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:14:21 storageqe-109 kernel: dev[00000000ef0cf0b5]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:14:21 storageqe-109 kernel: dev[000000003ca0c13f]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:14:21 storageqe-109 kernel: dev[000000003a5a18c0]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:14:21 storageqe-109 kernel: dev[000000000bc39720]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:14:21 storageqe-109 kernel: dev[000000001be7c8ba]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 5 01:14:21 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 5 01:14:21 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:14:21 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:14:21 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 5 01:14:21 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 5 01:14:21 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:14:21 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 5 01:14:21 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 5 01:14:21 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:14:21 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:21 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 5 01:14:21 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 5 01:14:21 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:14:22 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:14:22 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:22 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 5 01:14:22 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 5 01:14:22 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:14:22 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 5 01:14:22 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 5 01:14:22 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:14:22 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 5 01:14:22 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:22 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 5 01:14:22 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 5 01:14:22 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:14:22 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:22 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:14:22 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 5 01:14:22 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 5 01:14:22 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:14:22 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 5 01:14:22 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 5 01:14:22 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:14:22 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 5 01:14:22 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:22 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 5 01:14:22 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 5 01:14:22 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 5 01:14:22 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 5 01:14:22 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 5 01:14:22 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 5 01:14:22 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:14:22 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 5 01:14:22 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:22 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:14:22 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:22 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 5 01:14:22 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 5 01:14:22 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 5 01:14:22 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:22 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 5 01:14:22 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 5 01:14:32 storageqe-109 INFO: Verifying iSCSI target setup... Oct 5 01:14:32 storageqe-109 INFO: Found 4 LIO target(s) Oct 5 01:14:32 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 5 01:14:32 storageqe-109 iscsid[1936252]: iscsid shutting down. Oct 5 01:14:32 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 01:14:32 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 01:14:32 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 01:14:32 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 01:14:32 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 01:14:32 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 01:14:32 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 5 01:14:32 storageqe-109 iscsid[1946906]: iscsid: Connection13:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 5 01:14:32 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 5 01:14:32 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 5 01:14:32 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 5 01:14:32 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 5 01:14:32 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 5 01:14:32 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 5 01:14:32 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 5 01:14:32 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:32 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 5 01:14:32 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 5 01:14:32 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 5 01:14:32 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: target_name iqn.2003-01.udisks.test:iscsi-test-noauth Oct 5 01:14:34 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-noauth INFO: tpgt 1 Oct 5 01:14:35 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 5 01:14:36 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 5 01:14:37 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 5 01:14:38 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 5 01:14:39 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 5 01:14:40 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 5 01:14:41 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 5 01:14:42 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 5 01:14:43 storageqe-109 INFO: tgt_reset_timeout 30 Oct 5 01:14:43 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 5 01:14:43 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 5 01:14:43 storageqe-109 iscsid[1946906]: iscsid: Connection13:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 5 01:14:43 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 5 01:14:43 storageqe-109 INFO: Clearing targetcli configuration... Oct 5 01:14:43 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 5 01:14:44 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 5 01:14:44 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 5 01:14:44 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 5 01:14:44 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 5 01:14:44 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 5 01:14:44 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 5 01:14:44 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 5 01:14:44 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 5 01:14:44 storageqe-109 INFO: Removing test disk files... Oct 5 01:14:44 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 5 01:14:44 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 5 01:14:44 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 5 01:14:44 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 5 01:14:44 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 5 01:14:44 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 5 01:14:44 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 5 01:14:44 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_iscsi_session_logout_no_interface #### INFO: #### will start test_iscsi_discover_invalid_target ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:14:50 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:14:50 storageqe-109 INFO: #### END test_iscsi_session_logout_no_interface #### Oct 5 01:14:50 storageqe-109 INFO: #### will start test_iscsi_discover_invalid_target ##### Oct 5 01:14:50 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_iscsi_discover_invalid_target #### INFO: #### will start test_vdo_deduplication_and_compression ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:15:03 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:15:03 storageqe-109 INFO: #### END test_iscsi_discover_invalid_target #### Oct 5 01:15:03 storageqe-109 INFO: #### will start test_vdo_deduplication_and_compression ##### Oct 5 01:15:03 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:15:19 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 5 01:15:19 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_vdo_dedup.img) Oct 5 01:15:19 storageqe-109 lvm[1947537]: PV /dev/loop0 not used. Oct 5 01:15:19 storageqe-109 lvm[1947540]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:19 storageqe-109 systemd[1]: Started lvm-activate-test_vdo_vg.service - [systemd-run] /usr/sbin/lvm vgchange -aay --autoactivation event test_vdo_vg. Oct 5 01:15:19 storageqe-109 lvm[1947544]: 0 logical volume(s) in volume group "test_vdo_vg" now active Oct 5 01:15:19 storageqe-109 systemd[1]: lvm-activate-test_vdo_vg.service: Deactivated successfully. Oct 5 01:15:20 storageqe-109 UDS/vdoformat[1947562]: INFO (vdoformat/1947562) Using 2 indexing zones for concurrency. Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo24:lvm: loading device '253:4' Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo24:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo24:lvm: starting device '253:4' Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:physQ0: VDO commencing normal operation Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:journa: Setting UDS index target state to online Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: creating index: 253:3 Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' started Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: Using 2 indexing zones for concurrency. Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:20 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:20 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:20 storageqe-109 lvm[1947604]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:20 storageqe-109 lvm[1947604]: VG test_vdo_vg finished INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_vg/udisks_test_vdopool Oct 5 01:15:22 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_vg/udisks_test_vdopool INFO: OperatingMode normal Oct 5 01:15:23 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 5 01:15:24 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 5 01:15:25 storageqe-109 INFO: IndexState online INFO: UsedSize 3219931136 Oct 5 01:15:26 storageqe-109 INFO: UsedSize 3219931136 INFO: Compression 1 Oct 5 01:15:27 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 5 01:15:28 storageqe-109 INFO: Deduplication 1 Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:28 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: beginning save (vcn 18446744073709551615) Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:28 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: finished save (vcn 18446744073709551615) Oct 5 01:15:28 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:28 storageqe-109 lvm[1947668]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:28 storageqe-109 lvm[1947668]: VG test_vdo_vg finished Oct 5 01:15:29 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:29 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:29 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:29 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:29 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:29 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:29 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 5 01:15:29 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:29 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:29 storageqe-109 lvm[1947688]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:29 storageqe-109 lvm[1947688]: VG test_vdo_vg finished Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:30 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loading or rebuilding index: 253:3 Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: Using 2 indexing zones for concurrency. Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:30 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:30 storageqe-109 lvm[1947713]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:30 storageqe-109 lvm[1947713]: VG test_vdo_vg finished Oct 5 01:15:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loaded index from chapter 0 through chapter 0 Oct 5 01:15:31 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:31 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:31 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:31 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:31 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:31 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 5 01:15:31 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:31 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:31 storageqe-109 lvm[1947733]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:31 storageqe-109 lvm[1947733]: VG test_vdo_vg finished Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: Preparing to resize physical to 2358272 Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: Done preparing to resize physical Oct 5 01:15:35 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: Physical block count was 1833984, now 2358272 Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 5 01:15:35 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:35 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:35 storageqe-109 lvm[1947760]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:35 storageqe-109 lvm[1947760]: VG test_vdo_vg finished INFO: the 9659482112 8589934592 Oct 5 01:15:38 storageqe-109 INFO: the 9659482112 8589934592 INFO:before lv vdo 80509665280 Oct 5 01:15:39 storageqe-109 journal: INFO:before lv vdo 80509665280 Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: Preparing to resize logical to 98278656 Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: Done preparing to resize logical Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: Resizing logical to 98278656 Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: Logical blocks now 98278656 Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:39 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 5 01:15:39 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:39 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:39 storageqe-109 lvm[1947795]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:39 storageqe-109 lvm[1947795]: VG test_vdo_vg finished INFO: after lv vdo 402548326400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 5 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 90 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 Oct 5 01:15:41 storageqe-109 INFO: after lv vdo 402548326400 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 5 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics maxVIOs 90 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 24 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 98278656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9433088 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics instance 24 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics biosInFua 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 5 01:15:41 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 98278656 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9433088 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 5 INFO: vdo.GetStatistics overheadBlocksUsed 786470 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 34 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 5 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 786470 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics usedPercent 34 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2358272 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2358272 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 3 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 3 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 5 01:15:42 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:45 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:45 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:45 storageqe-109 lvm[1948477]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:45 storageqe-109 lvm[1948477]: VG test_vdo_vg finished Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:45 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 5 01:15:45 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:45 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:45 storageqe-109 lvm[1948492]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:45 storageqe-109 lvm[1948492]: VG test_vdo_vg finished Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:47 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loading or rebuilding index: 253:3 Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: Using 2 indexing zones for concurrency. Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:47 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loaded index from chapter 0 through chapter 0 Oct 5 01:15:47 storageqe-109 lvm[1948522]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:47 storageqe-109 lvm[1948522]: VG test_vdo_vg finished Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 5 01:15:47 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 5 01:15:47 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 5 01:15:47 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:47 storageqe-109 lvm[1948537]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 5 01:15:47 storageqe-109 lvm[1948537]: VG test_vdo_vg finished Oct 5 01:15:50 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 5 01:15:50 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 5 01:15:50 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 5 01:15:50 storageqe-109 kernel: device-mapper: vdo24:lvm: stopping device '253:4' Oct 5 01:15:50 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' stopped Oct 5 01:15:50 storageqe-109 lvm[1948559]: PV /dev/loop0 not used. Oct 5 01:15:51 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_vdo_dedup.img) Oct 5 01:15:51 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_vdo_deduplication_and_compression #### INFO: #### will start test_partition_resize ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:15:57 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:15:57 storageqe-109 INFO: #### END test_vdo_deduplication_and_compression #### Oct 5 01:15:57 storageqe-109 INFO: #### will start test_partition_resize ##### Oct 5 01:15:57 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:16:03 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:16:03 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_resize.img) Oct 5 01:16:03 storageqe-109 kernel: loop0: Oct 5 01:16:04 storageqe-109 udisksd[1947]: Could not open /dev/loop0p1 to query new partition size Oct 5 01:16:04 storageqe-109 kernel: loop0: p1 Oct 5 01:16:28 storageqe-109 udisksd[1947]: Could not open /dev/loop0p1 to query new partition size Oct 5 01:16:28 storageqe-109 kernel: loop0: p1 Oct 5 01:16:57 storageqe-109 kernel: loop0: Oct 5 01:16:57 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_resize.img) Oct 5 01:16:57 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_partition_resize #### INFO: #### will start test_nvme_size_properties ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:04 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:04 storageqe-109 INFO: #### END test_partition_resize #### Oct 5 01:17:04 storageqe-109 INFO: #### will start test_nvme_size_properties ##### Oct 5 01:17:04 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_size_properties #### INFO: #### will start test_iscsi_get_firmware_initiator_name_failure ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:20 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:20 storageqe-109 INFO: #### END test_nvme_size_properties #### Oct 5 01:17:20 storageqe-109 INFO: #### will start test_iscsi_get_firmware_initiator_name_failure ##### Oct 5 01:17:20 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_iscsi_get_firmware_initiator_name_failure #### INFO: #### will start test_mdraid_basic_properties ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:32 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:32 storageqe-109 INFO: #### END test_iscsi_get_firmware_initiator_name_failure #### Oct 5 01:17:32 storageqe-109 INFO: #### will start test_mdraid_basic_properties ##### Oct 5 01:17:32 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:39 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:17:39 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_props1.img) Oct 5 01:17:39 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:17:39 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_props2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_props INFO: raid chunk 524288 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:17:40 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 5 01:17:40 storageqe-109 udisksd[1947]: Set up loop device /dev/loop2 (backed by /home/loop_md_props3.img) Oct 5 01:17:40 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 5 01:17:40 storageqe-109 INFO: raid level raid5 Oct 5 01:17:40 storageqe-109 INFO: raid name test_md_props Oct 5 01:17:40 storageqe-109 INFO: raid chunk 524288 Oct 5 01:17:40 storageqe-109 INFO: raid bitmap None Oct 5 01:17:40 storageqe-109 INFO: raid version 1.2 Oct 5 01:17:40 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 5 01:17:40 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 5 01:17:40 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 01:17:40 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 5 01:17:40 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 01:17:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:17:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:17:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:17:45 storageqe-109 kernel: md: md127: recover done. Oct 5 01:17:48 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 5 01:17:48 storageqe-109 kernel: md: md127 stopped. Oct 5 01:17:48 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:17:51 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_props1.img) Oct 5 01:17:51 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:17:51 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_props2.img) Oct 5 01:17:51 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:17:51 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop2 (was backed by /home/loop_md_props3.img) Oct 5 01:17:51 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_basic_properties #### INFO: #### will start test_mdraid_set_bitmap_location ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:58 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:17:58 storageqe-109 INFO: #### END test_mdraid_basic_properties #### Oct 5 01:17:58 storageqe-109 INFO: #### will start test_mdraid_set_bitmap_location ##### Oct 5 01:17:58 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:18:04 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:18:04 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_set_bitmap1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_set_bitmap INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:18:05 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:18:05 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_set_bitmap2.img) Oct 5 01:18:05 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:18:05 storageqe-109 INFO: raid level raid1 Oct 5 01:18:05 storageqe-109 INFO: raid name test_md_set_bitmap Oct 5 01:18:05 storageqe-109 INFO: raid chunk 0 Oct 5 01:18:05 storageqe-109 INFO: raid bitmap None Oct 5 01:18:05 storageqe-109 INFO: raid version 1.2 Oct 5 01:18:05 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:18:05 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:18:05 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:18:05 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:18:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:18:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:18:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:18:10 storageqe-109 kernel: md: md127: resync done. Oct 5 01:18:13 storageqe-109 kernel: md127: bitmap file is out of date (0 < 17) -- forcing full recovery Oct 5 01:18:13 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery Oct 5 01:18:18 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:18:18 storageqe-109 kernel: md: md127 stopped. Oct 5 01:18:18 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:18:21 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_set_bitmap1.img) Oct 5 01:18:21 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:18:21 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_set_bitmap2.img) Oct 5 01:18:21 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_set_bitmap_location #### INFO: #### will start test_mdraid_with_internal_bitmap ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:18:27 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:18:27 storageqe-109 INFO: #### END test_mdraid_set_bitmap_location #### Oct 5 01:18:27 storageqe-109 INFO: #### will start test_mdraid_with_internal_bitmap ##### Oct 5 01:18:27 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:18:34 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:18:34 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_bitmap1.img) Oct 5 01:18:34 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_bitmap INFO: raid chunk 0 INFO: raid bitmap internal INFO: raid version 1.2 Oct 5 01:18:34 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_bitmap2.img) Oct 5 01:18:34 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:18:34 storageqe-109 INFO: raid level raid1 Oct 5 01:18:34 storageqe-109 INFO: raid name test_md_bitmap Oct 5 01:18:34 storageqe-109 INFO: raid chunk 0 Oct 5 01:18:34 storageqe-109 INFO: raid bitmap internal Oct 5 01:18:34 storageqe-109 INFO: raid version 1.2 Oct 5 01:18:34 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:18:34 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:18:34 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:18:34 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:18:34 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:18:34 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:18:35 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:18:40 storageqe-109 kernel: md: md127: resync done. Oct 5 01:18:44 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:18:44 storageqe-109 kernel: md: md127 stopped. Oct 5 01:18:44 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:18:47 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_bitmap1.img) Oct 5 01:18:47 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:18:47 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_bitmap2.img) Oct 5 01:18:47 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:18:47 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 01:18:47 storageqe-109 dnf[1950469]: Updating Subscription Management repositories. Oct 5 01:18:47 storageqe-109 dnf[1950469]: Unable to read consumer identity Oct 5 01:18:47 storageqe-109 dnf[1950469]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 01:18:47 storageqe-109 dnf[1950469]: Metadata cache refreshed recently. Oct 5 01:18:47 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 01:18:47 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_with_internal_bitmap #### INFO: #### will start test_mdraid_sync_progress_properties ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:18:53 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:18:53 storageqe-109 INFO: #### END test_mdraid_with_internal_bitmap #### Oct 5 01:18:53 storageqe-109 INFO: #### will start test_mdraid_sync_progress_properties ##### Oct 5 01:18:53 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:18:59 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:18:59 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_progress1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_progress INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:19:00 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:19:00 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_progress2.img) Oct 5 01:19:00 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:19:00 storageqe-109 INFO: raid level raid1 Oct 5 01:19:00 storageqe-109 INFO: raid name test_md_progress Oct 5 01:19:00 storageqe-109 INFO: raid chunk 0 Oct 5 01:19:00 storageqe-109 INFO: raid bitmap None Oct 5 01:19:00 storageqe-109 INFO: raid version 1.2 Oct 5 01:19:00 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:19:00 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:19:00 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:19:00 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:19:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:05 storageqe-109 kernel: md: md127: resync done. Oct 5 01:19:17 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:19:17 storageqe-109 kernel: md: md127 stopped. Oct 5 01:19:17 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:19:20 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_progress1.img) Oct 5 01:19:20 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:19:20 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_progress2.img) Oct 5 01:19:20 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_sync_progress_properties #### INFO: #### will start test_mdraid_consistency_policy ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:19:26 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:19:26 storageqe-109 INFO: #### END test_mdraid_sync_progress_properties #### Oct 5 01:19:26 storageqe-109 INFO: #### will start test_mdraid_consistency_policy ##### Oct 5 01:19:26 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:19:33 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:19:33 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_policy1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_policy INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:19:33 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:19:33 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_policy2.img) Oct 5 01:19:33 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:19:33 storageqe-109 INFO: raid level raid1 Oct 5 01:19:33 storageqe-109 INFO: raid name test_md_policy Oct 5 01:19:33 storageqe-109 INFO: raid chunk 0 Oct 5 01:19:33 storageqe-109 INFO: raid bitmap None Oct 5 01:19:33 storageqe-109 INFO: raid version 1.2 Oct 5 01:19:33 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:19:33 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:19:33 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:19:33 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:19:33 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:33 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:33 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:39 storageqe-109 kernel: md: md127: resync done. Oct 5 01:19:42 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:19:42 storageqe-109 kernel: md: md127 stopped. Oct 5 01:19:43 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:19:46 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_policy1.img) Oct 5 01:19:46 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:19:46 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_policy2.img) Oct 5 01:19:46 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_consistency_policy #### INFO: #### will start test_mdraid_sync_actions ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:19:52 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:19:52 storageqe-109 INFO: #### END test_mdraid_consistency_policy #### Oct 5 01:19:52 storageqe-109 INFO: #### will start test_mdraid_sync_actions ##### Oct 5 01:19:52 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:19:58 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:19:58 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_sync1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_sync INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:19:59 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:19:59 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_sync2.img) Oct 5 01:19:59 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:19:59 storageqe-109 INFO: raid level raid1 Oct 5 01:19:59 storageqe-109 INFO: raid name test_md_sync Oct 5 01:19:59 storageqe-109 INFO: raid chunk 0 Oct 5 01:19:59 storageqe-109 INFO: raid bitmap None Oct 5 01:19:59 storageqe-109 INFO: raid version 1.2 Oct 5 01:19:59 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:19:59 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:19:59 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:19:59 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:19:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:19:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:20:04 storageqe-109 kernel: md: md127: resync done. Oct 5 01:20:06 storageqe-109 kernel: md: check of RAID array md127 Oct 5 01:20:11 storageqe-109 kernel: md: md127: check done. Oct 5 01:20:14 storageqe-109 kernel: md: repair of RAID array md127 Oct 5 01:20:16 storageqe-109 kernel: md: md127: repair interrupted. Oct 5 01:20:16 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:20:16 storageqe-109 kernel: md: md127 stopped. Oct 5 01:20:16 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:20:19 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_sync1.img) Oct 5 01:20:19 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:20:19 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_sync2.img) Oct 5 01:20:19 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_sync_actions #### INFO: #### will start test_luks_remove_with_teardown ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:20:25 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:20:25 storageqe-109 INFO: #### END test_mdraid_sync_actions #### Oct 5 01:20:25 storageqe-109 INFO: #### will start test_luks_remove_with_teardown ##### Oct 5 01:20:25 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:20:32 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:20:32 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_luks_teardown.img) Oct 5 01:20:32 storageqe-109 kernel: loop0: INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'teardown_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2id', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 5 01:20:33 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'teardown_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2id', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 5 01:20:42 storageqe-109 stratisd[1277]: [2025-10-05T05:20:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:20:42 storageqe-109 stratisd[1277]: [2025-10-05T05:20:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:20:45 storageqe-109 stratisd[1277]: [2025-10-05T05:20:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:20:45 storageqe-109 stratisd[1277]: [2025-10-05T05:20:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 5 01:20:46 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 5 01:20:47 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 5 01:20:48 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to argon2id Oct 5 01:20:49 storageqe-109 INFO: foramt to luks2 Oct 5 01:20:49 storageqe-109 INFO: foramt to argon2id Oct 5 01:20:51 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:20:51 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:20:51 storageqe-109 udisksd[1947]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 5 01:21:00 storageqe-109 kernel: loop0: Oct 5 01:21:00 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_luks_teardown.img) Oct 5 01:21:00 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_remove_with_teardown #### INFO: #### will start test_vdo_resize ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:21:06 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:21:06 storageqe-109 INFO: #### END test_luks_remove_with_teardown #### Oct 5 01:21:06 storageqe-109 INFO: #### will start test_vdo_resize ##### Oct 5 01:21:06 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:21:22 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 5 01:21:22 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_vdo_resize1.img) Oct 5 01:21:37 storageqe-109 kernel: loop1: detected capacity change from 0 to 31457280 Oct 5 01:21:37 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_vdo_resize2.img) Oct 5 01:21:37 storageqe-109 lvm[1953336]: PV /dev/loop0 not used. Oct 5 01:21:37 storageqe-109 lvm[1953339]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:37 storageqe-109 systemd[1]: Started lvm-activate-test_vdo_resize_vg.service - [systemd-run] /usr/sbin/lvm vgchange -aay --autoactivation event test_vdo_resize_vg. Oct 5 01:21:37 storageqe-109 lvm[1953342]: 0 logical volume(s) in volume group "test_vdo_resize_vg" now active Oct 5 01:21:37 storageqe-109 systemd[1]: lvm-activate-test_vdo_resize_vg.service: Deactivated successfully. Oct 5 01:21:38 storageqe-109 UDS/vdoformat[1953361]: INFO (vdoformat/1953361) Using 2 indexing zones for concurrency. Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo25:lvm: loading device '253:4' Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo25:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo25:lvm: starting device '253:4' Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:physQ0: VDO commencing normal operation Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:journa: Setting UDS index target state to online Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: creating index: 253:3 Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' started Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: Using 2 indexing zones for concurrency. Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:38 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:38 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:38 storageqe-109 lvm[1953401]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:38 storageqe-109 lvm[1953401]: VG test_vdo_resize_vg finished INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_resize_vg/udisks_test_vdopool Oct 5 01:21:40 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_resize_vg/udisks_test_vdopool INFO: OperatingMode normal Oct 5 01:21:41 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 5 01:21:42 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 5 01:21:43 storageqe-109 INFO: IndexState online INFO: UsedSize 3219931136 Oct 5 01:21:44 storageqe-109 INFO: UsedSize 3219931136 INFO: Compression 1 Oct 5 01:21:45 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 5 01:21:46 storageqe-109 INFO: Deduplication 1 Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:21:46 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: beginning save (vcn 18446744073709551615) Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: finished save (vcn 18446744073709551615) Oct 5 01:21:46 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:46 storageqe-109 lvm[1953466]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:46 storageqe-109 lvm[1953466]: VG test_vdo_resize_vg finished Oct 5 01:21:47 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:21:47 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:21:47 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:47 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:21:47 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:21:47 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is disabled Oct 5 01:21:47 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:47 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:47 storageqe-109 lvm[1953486]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:47 storageqe-109 lvm[1953486]: VG test_vdo_resize_vg finished Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:21:48 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: loading or rebuilding index: 253:3 Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is disabled Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: Using 2 indexing zones for concurrency. Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:48 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:48 storageqe-109 lvm[1953511]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:48 storageqe-109 lvm[1953511]: VG test_vdo_resize_vg finished Oct 5 01:21:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: loaded index from chapter 0 through chapter 0 Oct 5 01:21:49 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:21:49 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:21:49 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:49 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:21:49 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:21:49 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:49 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:21:49 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:50 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:50 storageqe-109 lvm[1953531]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:50 storageqe-109 lvm[1953531]: VG test_vdo_resize_vg finished Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize physical to 2358272 Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize physical Oct 5 01:21:53 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: Physical block count was 1833984, now 2358272 Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:21:53 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:53 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:53 storageqe-109 lvm[1953558]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:53 storageqe-109 lvm[1953558]: VG test_vdo_resize_vg finished INFO: the 9659482112 8589934592 Oct 5 01:21:56 storageqe-109 INFO: the 9659482112 8589934592 INFO:before lv vdo 80509665280 Oct 5 01:21:57 storageqe-109 journal: INFO:before lv vdo 80509665280 Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize logical to 98278656 Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize logical Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: Resizing logical to 98278656 Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: Logical blocks now 98278656 Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:57 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:21:57 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:21:57 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:21:57 storageqe-109 lvm[1953592]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:21:57 storageqe-109 lvm[1953592]: VG test_vdo_resize_vg finished INFO: after lv vdo 402548326400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 5 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 64 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 5 01:21:59 storageqe-109 INFO: after lv vdo 402548326400 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 5 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics maxVIOs 64 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 25 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 98278656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9433088 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosInFua 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics instance 25 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 5 01:21:59 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 98278656 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9433088 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 5 INFO: vdo.GetStatistics overheadBlocksUsed 786470 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 34 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 5 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 786470 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics usedPercent 34 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2358272 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2358272 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 3 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 3 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 5 01:22:00 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 5 01:22:01 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 5 01:22:01 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 5 01:22:01 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 5 01:22:01 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize logical to 196557056 Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize logical Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: Resizing logical to 196557056 Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: Logical blocks now 196557056 Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:22:02 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:22:02 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:22:02 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:22:02 storageqe-109 lvm[1954278]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:22:02 storageqe-109 lvm[1954278]: VG test_vdo_resize_vg finished Oct 5 01:22:05 storageqe-109 lvm[1954288]: PV /dev/loop1 not used. Oct 5 01:22:05 storageqe-109 lvm[1954290]: PV /dev/loop1 online, VG test_vdo_resize_vg is complete. Oct 5 01:22:05 storageqe-109 lvm[1954290]: VG test_vdo_resize_vg finished Oct 5 01:22:05 storageqe-109 lvm[1954291]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:22:05 storageqe-109 lvm[1954291]: VG test_vdo_resize_vg finished Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 3668992 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize physical to 3668992 Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize physical Oct 5 01:22:05 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: Physical block count was 2358272, now 3668992 Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 5 01:22:05 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 5 01:22:05 storageqe-109 dmeventd[1921687]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:22:05 storageqe-109 lvm[1954312]: PV /dev/loop1 online, VG test_vdo_resize_vg is complete. Oct 5 01:22:05 storageqe-109 lvm[1954311]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 5 01:22:05 storageqe-109 lvm[1954312]: VG test_vdo_resize_vg finished Oct 5 01:22:05 storageqe-109 lvm[1954311]: VG test_vdo_resize_vg finished Oct 5 01:22:07 storageqe-109 dmeventd[1921687]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 5 01:22:07 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 5 01:22:07 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 5 01:22:07 storageqe-109 kernel: device-mapper: vdo25:lvm: stopping device '253:4' Oct 5 01:22:07 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' stopped Oct 5 01:22:07 storageqe-109 lvm[1954332]: PV /dev/loop0 not used. Oct 5 01:22:07 storageqe-109 lvm[1954333]: PV /dev/loop1 not used. Oct 5 01:22:08 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_vdo_resize1.img) Oct 5 01:22:08 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:22:08 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_vdo_resize2.img) Oct 5 01:22:08 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_vdo_resize #### INFO: #### will start test_mdraid_chunk_size_property ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:22:14 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:22:14 storageqe-109 INFO: #### END test_vdo_resize #### Oct 5 01:22:14 storageqe-109 INFO: #### will start test_mdraid_chunk_size_property ##### Oct 5 01:22:14 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:22:20 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:22:20 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_chunk1.img) Oct 5 01:22:21 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:22:21 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_chunk2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_chunk INFO: raid chunk 262144 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:22:21 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 5 01:22:21 storageqe-109 udisksd[1947]: Set up loop device /dev/loop2 (backed by /home/loop_md_chunk3.img) Oct 5 01:22:21 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 5 01:22:21 storageqe-109 INFO: raid level raid5 Oct 5 01:22:21 storageqe-109 INFO: raid name test_md_chunk Oct 5 01:22:21 storageqe-109 INFO: raid chunk 262144 Oct 5 01:22:21 storageqe-109 INFO: raid bitmap None Oct 5 01:22:21 storageqe-109 INFO: raid version 1.2 Oct 5 01:22:21 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 5 01:22:21 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 5 01:22:21 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 01:22:21 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 5 01:22:21 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 01:22:21 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:22:21 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:22:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:22:27 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 01:22:27 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 5 01:22:27 storageqe-109 kernel: md: md127 stopped. Oct 5 01:22:27 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:22:30 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_chunk1.img) Oct 5 01:22:30 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:22:30 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_chunk2.img) Oct 5 01:22:30 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:22:30 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop2 (was backed by /home/loop_md_chunk3.img) Oct 5 01:22:30 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_chunk_size_property #### INFO: #### will start test_mdraid_add_and_remove_spare ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:22:36 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:22:36 storageqe-109 INFO: #### END test_mdraid_chunk_size_property #### Oct 5 01:22:36 storageqe-109 INFO: #### will start test_mdraid_add_and_remove_spare ##### Oct 5 01:22:36 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:22:43 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:22:43 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_add_spare1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_add_spare INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:22:43 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:22:43 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_add_spare2.img) Oct 5 01:22:43 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:22:43 storageqe-109 INFO: raid level raid1 Oct 5 01:22:43 storageqe-109 INFO: raid name test_md_add_spare Oct 5 01:22:43 storageqe-109 INFO: raid chunk 0 Oct 5 01:22:43 storageqe-109 INFO: raid bitmap None Oct 5 01:22:43 storageqe-109 INFO: raid version 1.2 Oct 5 01:22:43 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:22:43 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:22:43 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:22:43 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:22:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:22:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:22:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:22:49 storageqe-109 kernel: md: md127: resync done. Oct 5 01:22:51 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 5 01:22:51 storageqe-109 udisksd[1947]: Set up loop device /dev/loop2 (backed by /home/loop_md_spare.img) Oct 5 01:22:58 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:22:58 storageqe-109 kernel: md: md127 stopped. Oct 5 01:22:58 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:23:02 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:23:02 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:23:02 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_add_and_remove_spare #### INFO: #### will start test_mdraid_degraded_state ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:23:07 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:23:07 storageqe-109 INFO: #### END test_mdraid_add_and_remove_spare #### Oct 5 01:23:07 storageqe-109 INFO: #### will start test_mdraid_degraded_state ##### Oct 5 01:23:07 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:23:14 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:23:14 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_degraded1.img) Oct 5 01:23:14 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 5 01:23:14 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_degraded2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_degraded INFO: raid chunk 524288 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:23:15 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 5 01:23:15 storageqe-109 udisksd[1947]: Set up loop device /dev/loop2 (backed by /home/loop_md_degraded3.img) Oct 5 01:23:15 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 5 01:23:15 storageqe-109 INFO: raid level raid5 Oct 5 01:23:15 storageqe-109 INFO: raid name test_md_degraded Oct 5 01:23:15 storageqe-109 INFO: raid chunk 524288 Oct 5 01:23:15 storageqe-109 INFO: raid bitmap None Oct 5 01:23:15 storageqe-109 INFO: raid version 1.2 Oct 5 01:23:15 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 5 01:23:15 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 5 01:23:15 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 01:23:15 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 5 01:23:15 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 01:23:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:23:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:23:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:23:20 storageqe-109 kernel: md: md127: recover done. Oct 5 01:23:23 storageqe-109 kernel: md/raid:md127: Disk failure on loop1, disabling device. Oct 5 01:23:23 storageqe-109 kernel: md/raid:md127: Operation continuing on 2 devices. Oct 5 01:23:28 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 5 01:23:28 storageqe-109 kernel: md: md127 stopped. Oct 5 01:23:28 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:23:32 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:23:32 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:23:32 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_degraded_state #### INFO: #### will start test_mdraid_delete_method ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:23:37 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:23:37 storageqe-109 INFO: #### END test_mdraid_degraded_state #### Oct 5 01:23:37 storageqe-109 INFO: #### will start test_mdraid_delete_method ##### Oct 5 01:23:37 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:23:44 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:23:44 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_delete1.img) Oct 5 01:23:44 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_delete INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:23:44 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_delete2.img) Oct 5 01:23:44 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:23:44 storageqe-109 INFO: raid level raid1 Oct 5 01:23:44 storageqe-109 INFO: raid name test_md_delete Oct 5 01:23:44 storageqe-109 INFO: raid chunk 0 Oct 5 01:23:44 storageqe-109 INFO: raid bitmap None Oct 5 01:23:44 storageqe-109 INFO: raid version 1.2 Oct 5 01:23:45 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:23:45 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:23:45 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:23:45 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:23:45 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:23:45 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:23:45 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:23:50 storageqe-109 kernel: md: md127: resync done. Oct 5 01:23:53 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:23:53 storageqe-109 kernel: md: md127 stopped. Oct 5 01:23:53 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:23:57 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 Oct 5 01:23:57 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_delete_method #### INFO: #### will start test_mdraid_activedevices_property_structure ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:24:02 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:24:02 storageqe-109 INFO: #### END test_mdraid_delete_method #### Oct 5 01:24:02 storageqe-109 INFO: #### will start test_mdraid_activedevices_property_structure ##### Oct 5 01:24:02 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:24:09 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:24:09 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_active1.img) Oct 5 01:24:09 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_active INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:24:09 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_active2.img) Oct 5 01:24:09 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:24:09 storageqe-109 INFO: raid level raid1 Oct 5 01:24:09 storageqe-109 INFO: raid name test_md_active Oct 5 01:24:09 storageqe-109 INFO: raid chunk 0 Oct 5 01:24:09 storageqe-109 INFO: raid bitmap None Oct 5 01:24:09 storageqe-109 INFO: raid version 1.2 Oct 5 01:24:09 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:24:09 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:24:09 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:24:09 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:24:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:24:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:24:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:24:14 storageqe-109 kernel: md: md127: resync done. Oct 5 01:24:19 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:24:19 storageqe-109 kernel: md: md127 stopped. Oct 5 01:24:19 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:24:22 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_active1.img) Oct 5 01:24:22 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:24:22 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_active2.img) Oct 5 01:24:22 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_activedevices_property_structure #### INFO: #### will start test_mdraid_size_property_verification ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:24:28 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:24:28 storageqe-109 INFO: #### END test_mdraid_activedevices_property_structure #### Oct 5 01:24:28 storageqe-109 INFO: #### will start test_mdraid_size_property_verification ##### Oct 5 01:24:28 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:24:35 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 5 01:24:35 storageqe-109 udisksd[1947]: Set up loop device /dev/loop0 (backed by /home/loop_md_size1.img) Oct 5 01:24:35 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_size1 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:24:35 storageqe-109 udisksd[1947]: Set up loop device /dev/loop1 (backed by /home/loop_md_size2.img) Oct 5 01:24:35 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:24:35 storageqe-109 INFO: raid level raid1 Oct 5 01:24:35 storageqe-109 INFO: raid name test_md_size1 Oct 5 01:24:35 storageqe-109 INFO: raid chunk 0 Oct 5 01:24:35 storageqe-109 INFO: raid bitmap None Oct 5 01:24:35 storageqe-109 INFO: raid version 1.2 Oct 5 01:24:36 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 01:24:36 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 01:24:36 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 5 01:24:36 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 01:24:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:24:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:24:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 01:24:41 storageqe-109 kernel: md: md127: resync done. Oct 5 01:24:45 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 5 01:24:45 storageqe-109 kernel: md: md127 stopped. Oct 5 01:24:45 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_md_size0 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 5 01:24:50 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 5 01:24:50 storageqe-109 INFO: raid level raid0 Oct 5 01:24:50 storageqe-109 INFO: raid name test_md_size0 Oct 5 01:24:50 storageqe-109 INFO: raid chunk 0 Oct 5 01:24:50 storageqe-109 INFO: raid bitmap None Oct 5 01:24:50 storageqe-109 INFO: raid version 1.2 Oct 5 01:24:50 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 5 01:24:55 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 5 01:24:55 storageqe-109 kernel: md: md127 stopped. Oct 5 01:24:55 storageqe-109 udisksd[1947]: No longer watching mdraid device 9:127 Oct 5 01:24:58 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_size1.img) Oct 5 01:24:58 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop0 Oct 5 01:24:58 storageqe-109 udisksd[1947]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_size2.img) Oct 5 01:24:58 storageqe-109 udisksd[1947]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_size_property_verification #### INFO: #### will start test_nvme_smart_properties_validation ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:04 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:04 storageqe-109 INFO: #### END test_mdraid_size_property_verification #### Oct 5 01:25:04 storageqe-109 INFO: #### will start test_nvme_smart_properties_validation ##### Oct 5 01:25:04 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_properties_validation #### INFO: #### will start test_nvme_drive_properties ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:17 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:17 storageqe-109 INFO: #### END test_nvme_smart_properties_validation #### Oct 5 01:25:17 storageqe-109 INFO: #### will start test_nvme_drive_properties ##### Oct 5 01:25:17 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_drive_properties #### INFO: #### will start test_nvme_controller_static_properties ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:31 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:31 storageqe-109 INFO: #### END test_nvme_drive_properties #### Oct 5 01:25:31 storageqe-109 INFO: #### will start test_nvme_controller_static_properties ##### Oct 5 01:25:31 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_controller_static_properties #### INFO: #### will start test_nvme_namespace_size_property ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:44 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:44 storageqe-109 INFO: #### END test_nvme_controller_static_properties #### Oct 5 01:25:44 storageqe-109 INFO: #### will start test_nvme_namespace_size_property ##### Oct 5 01:25:44 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_size_property #### INFO: #### will start test_nvme_namespace_properties_detailed ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:57 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:25:57 storageqe-109 INFO: #### END test_nvme_namespace_size_property #### Oct 5 01:25:57 storageqe-109 INFO: #### will start test_nvme_namespace_properties_detailed ##### Oct 5 01:25:57 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_properties_detailed #### INFO: #### will start test_nvme_namespace_format ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:26:20 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:26:20 storageqe-109 INFO: #### END test_nvme_namespace_properties_detailed #### Oct 5 01:26:20 storageqe-109 INFO: #### will start test_nvme_namespace_format ##### Oct 5 01:26:20 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:26:28 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 01:28:30 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format #### INFO: #### will start test_nvme_namespace_format_invalid_lba ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:30:38 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:30:38 storageqe-109 INFO: #### END test_nvme_namespace_format #### Oct 5 01:30:38 storageqe-109 INFO: #### will start test_nvme_namespace_format_invalid_lba ##### Oct 5 01:30:38 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:30:44 storageqe-109 udisksd[1947]: Error formatting namespace /org/freedesktop/UDisks2/block_devices/nvme0n1: Couldn't match desired LBA data block size in a device supported LBA format data sizes (g-bd-nvme-error-quark, 3) INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_invalid_lba #### INFO: #### will start test_nvme_namespace_format_invalid_secure_erase ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:30:50 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:30:50 storageqe-109 INFO: #### END test_nvme_namespace_format_invalid_lba #### Oct 5 01:30:50 storageqe-109 INFO: #### will start test_nvme_namespace_format_invalid_secure_erase ##### Oct 5 01:30:50 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_invalid_secure_erase #### INFO: #### will start test_nvme_block_size_consistency_after_format ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:31:03 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:31:03 storageqe-109 INFO: #### END test_nvme_namespace_format_invalid_secure_erase #### Oct 5 01:31:03 storageqe-109 INFO: #### will start test_nvme_block_size_consistency_after_format ##### Oct 5 01:31:03 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:31:13 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 01:33:16 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_block_size_consistency_after_format #### INFO: #### will start test_nvme_namespace_wwn_property ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:35:23 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:35:23 storageqe-109 INFO: #### END test_nvme_block_size_consistency_after_format #### Oct 5 01:35:23 storageqe-109 INFO: #### will start test_nvme_namespace_wwn_property ##### Oct 5 01:35:23 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_wwn_property #### INFO: #### will start test_nvme_namespace_utilization ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:35:36 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:35:36 storageqe-109 INFO: #### END test_nvme_namespace_wwn_property #### Oct 5 01:35:36 storageqe-109 INFO: #### will start test_nvme_namespace_utilization ##### Oct 5 01:35:36 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:35:55 storageqe-109 kernel: XFS (nvme0n1): Mounting V5 Filesystem d7eeb6e3-0c0e-493c-8c06-8ade82f91a8d Oct 5 01:35:55 storageqe-109 kernel: XFS (nvme0n1): Ending clean mount Oct 5 01:35:55 storageqe-109 udisksd[1947]: Mounted /dev/nvme0n1 at /run/media/root/d7eeb6e3-0c0e-493c-8c06-8ade82f91a8d on behalf of uid 0 Oct 5 01:35:55 storageqe-109 systemd[1]: run-media-root-d7eeb6e3\x2d0c0e\x2d493c\x2d8c06\x2d8ade82f91a8d.mount: Deactivated successfully. Oct 5 01:35:55 storageqe-109 kernel: XFS (nvme0n1): Unmounting Filesystem d7eeb6e3-0c0e-493c-8c06-8ade82f91a8d Oct 5 01:35:55 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/d7eeb6e3-0c0e-493c-8c06-8ade82f91a8d (device 259:1 is not mounted) Oct 5 01:35:55 storageqe-109 udisksd[1947]: Unmounted /dev/nvme0n1 on behalf of uid 0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_utilization #### INFO: #### will start test_luks_on_4k_nvme_namespace ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:36:02 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:36:02 storageqe-109 INFO: #### END test_nvme_namespace_utilization #### Oct 5 01:36:02 storageqe-109 INFO: #### will start test_luks_on_4k_nvme_namespace ##### Oct 5 01:36:02 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:36:10 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 01:38:18 storageqe-109 stratisd[1277]: [2025-10-05T05:38:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:38:18 storageqe-109 stratisd[1277]: [2025-10-05T05:38:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:38:20 storageqe-109 stratisd[1277]: [2025-10-05T05:38:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:38:20 storageqe-109 stratisd[1277]: [2025-10-05T05:38:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 01:38:25 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:38:25 storageqe-109 udisksd[1947]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 5 01:38:25 storageqe-109 udisksd[1947]: Locked device /dev/nvme0n1 (was unlocked as /dev/dm-3) Oct 5 01:38:25 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_on_4k_nvme_namespace #### INFO: #### will start test_nvme_namespace_format_on_mounted_device ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:40:32 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:40:32 storageqe-109 INFO: #### END test_luks_on_4k_nvme_namespace #### Oct 5 01:40:32 storageqe-109 INFO: #### will start test_nvme_namespace_format_on_mounted_device ##### Oct 5 01:40:32 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:40:44 storageqe-109 kernel: XFS (nvme0n1): Mounting V5 Filesystem fc63408b-3510-4b5c-ad11-766ecf07b4ec Oct 5 01:40:44 storageqe-109 udisksd[1947]: Mounted /dev/nvme0n1 at /run/media/root/fc63408b-3510-4b5c-ad11-766ecf07b4ec on behalf of uid 0 Oct 5 01:40:44 storageqe-109 kernel: XFS (nvme0n1): Ending clean mount Oct 5 01:40:44 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 01:40:46 storageqe-109 udisksd[1947]: Error re-reading partition table (BLKRRPART ioctl) on /dev/nvme0n1: Device or resource busy Oct 5 01:40:47 storageqe-109 systemd[1]: run-media-root-fc63408b\x2d3510\x2d4b5c\x2dad11\x2d766ecf07b4ec.mount: Deactivated successfully. Oct 5 01:40:47 storageqe-109 kernel: XFS (nvme0n1): Unmounting Filesystem fc63408b-3510-4b5c-ad11-766ecf07b4ec Oct 5 01:40:47 storageqe-109 udisksd[1947]: Cleaning up mount point /run/media/root/fc63408b-3510-4b5c-ad11-766ecf07b4ec (device 259:1 is not mounted) Oct 5 01:40:47 storageqe-109 udisksd[1947]: Unmounted /dev/nvme0n1 on behalf of uid 0 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_on_mounted_device #### INFO: #### will start test_nvme_namespace_format_with_metadata ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:40:53 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:40:53 storageqe-109 INFO: #### END test_nvme_namespace_format_on_mounted_device #### Oct 5 01:40:53 storageqe-109 INFO: #### will start test_nvme_namespace_format_with_metadata ##### Oct 5 01:40:53 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:41:01 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 01:43:03 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_with_metadata #### INFO: #### will start test_nvme_namespace_format_with_extra_options ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:45:10 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:45:10 storageqe-109 INFO: #### END test_nvme_namespace_format_with_metadata #### Oct 5 01:45:10 storageqe-109 INFO: #### will start test_nvme_namespace_format_with_extra_options ##### Oct 5 01:45:10 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:45:17 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 01:47:19 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_with_extra_options #### INFO: #### will start test_lvm_on_nvme_namespace ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:49:26 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:49:26 storageqe-109 INFO: #### END test_nvme_namespace_format_with_extra_options #### Oct 5 01:49:26 storageqe-109 INFO: #### will start test_lvm_on_nvme_namespace ##### Oct 5 01:49:26 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_on_nvme_namespace #### Oct 5 01:49:53 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 01:49:53 storageqe-109 INFO: #### END test_lvm_on_nvme_namespace #### Oct 5 01:57:46 storageqe-109 systemd[1]: session-7.scope: Deactivated successfully. Oct 5 01:57:46 storageqe-109 systemd-logind[995]: Session 7 logged out. Waiting for processes to exit. Oct 5 01:57:46 storageqe-109 systemd-logind[995]: Removed session 7. Oct 5 01:57:47 storageqe-109 systemd-logind[995]: New session 12 of user root. Oct 5 01:57:47 storageqe-109 systemd[1]: Started session-12.scope - Session 12 of User root. Oct 5 01:57:47 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 01:57:47 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 01:58:55 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:00:49 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:00:49 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:00:53 storageqe-109 udisksd[1947]: Loading module lsm ... Oct 5 02:00:53 storageqe-109 udisksd[1947]: Error loading module: LSM: Failed to connect plugin via URI 'hpsa://', error code: -1, error message: (null) Oct 5 02:00:55 storageqe-109 systemd[1]: Reload requested from client PID 1963249 ('systemctl') (unit session-12.scope)... Oct 5 02:00:55 storageqe-109 systemd[1]: Reloading... Oct 5 02:00:55 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 5 02:00:55 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 02:00:55 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 02:00:55 storageqe-109 systemd[1]: Reloading finished in 143 ms. Oct 5 02:00:55 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 02:00:55 storageqe-109 iscsid[1946906]: iscsid shutting down. Oct 5 02:00:55 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 02:00:55 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 02:00:55 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 02:00:55 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 02:00:55 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 02:00:55 storageqe-109 multipathd[770]: Multipath configuration updated. Oct 5 02:00:55 storageqe-109 multipathd[770]: Reload multipathd for changes to take effect Oct 5 02:00:55 storageqe-109 systemd[1]: Reloading multipathd.service - Device-Mapper Multipath Device Controller... Oct 5 02:00:55 storageqe-109 multipathd[770]: reconfigure (operator) Oct 5 02:00:55 storageqe-109 multipathd[770]: reconfigure: setting up paths and maps Oct 5 02:00:55 storageqe-109 multipathd[1963349]: ok Oct 5 02:00:55 storageqe-109 systemd[1]: Reloaded multipathd.service - Device-Mapper Multipath Device Controller. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 02:00:57 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 02:01:09 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 02:01:19 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_init_nvme ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 02:01:20 storageqe-109 INFO: #### will start test_init_nvme ##### Oct 5 02:01:20 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: Namespace object for /dev/nvme0n1: :1.26 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7f7246a936b0> Oct 5 02:01:26 storageqe-109 INFO: Namespace object for /dev/nvme0n1: :1.26 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7f7246a936b0> INFO: Drive path for /dev/nvme0n1: / INFO: NVMe controller object: None INFO: NVMe manager interface: :1.26 /org/freedesktop/UDisks2/Manager at 0x7f7246a92060> implementing 'org.freedesktop.UDisks2.Manager.NVMe' at 0x7f724662f830> Oct 5 02:01:27 storageqe-109 INFO: Drive path for /dev/nvme0n1: / Oct 5 02:01:27 storageqe-109 INFO: NVMe controller object: None Oct 5 02:01:27 storageqe-109 INFO: NVMe manager interface: :1.26 /org/freedesktop/UDisks2/Manager at 0x7f7246a92060> implementing 'org.freedesktop.UDisks2.Manager.NVMe' at 0x7f724662f830> INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_init_nvme #### Oct 5 02:01:33 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 02:01:33 storageqe-109 INFO: #### END test_init_nvme #### Oct 5 02:01:39 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:01:56 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:01:56 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:02:44 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:02:58 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:02:58 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:03:02 storageqe-109 udisksd[1947]: Loading module lsm ... Oct 5 02:03:02 storageqe-109 udisksd[1947]: Error loading module: LSM: Failed to connect plugin via URI 'hpsa://', error code: -1, error message: (null) Oct 5 02:03:04 storageqe-109 systemd[1]: Reload requested from client PID 1965110 ('systemctl') (unit session-12.scope)... Oct 5 02:03:04 storageqe-109 systemd[1]: Reloading... Oct 5 02:03:04 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 5 02:03:04 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 02:03:04 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 02:03:04 storageqe-109 systemd[1]: Reloading finished in 143 ms. Oct 5 02:03:04 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 02:03:04 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 5 02:03:04 storageqe-109 iscsid[1963306]: iscsid shutting down. Oct 5 02:03:04 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 5 02:03:04 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 5 02:03:04 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 02:03:04 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 02:03:04 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 02:03:04 storageqe-109 multipathd[770]: Multipath configuration updated. Oct 5 02:03:04 storageqe-109 multipathd[770]: Reload multipathd for changes to take effect Oct 5 02:03:04 storageqe-109 systemd[1]: Reloading multipathd.service - Device-Mapper Multipath Device Controller... Oct 5 02:03:04 storageqe-109 multipathd[770]: reconfigure (operator) Oct 5 02:03:04 storageqe-109 multipathd[1965218]: ok Oct 5 02:03:04 storageqe-109 multipathd[770]: reconfigure: setting up paths and maps Oct 5 02:03:04 storageqe-109 systemd[1]: Reloaded multipathd.service - Device-Mapper Multipath Device Controller. Oct 5 02:03:04 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 02:03:04 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 02:03:06 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 02:03:18 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 02:03:28 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_init_nvme ##### INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 02:03:28 storageqe-109 INFO: #### will start test_init_nvme ##### Oct 5 02:03:28 storageqe-109 INFO: #### before available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: Namespace object for /dev/nvme0n1: :1.26 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7f5157450dd0> Oct 5 02:03:35 storageqe-109 INFO: Namespace object for /dev/nvme0n1: :1.26 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7f5157450dd0> INFO: Drive path for /dev/nvme0n1: / INFO: Device /dev/nvme0n1 has no associated drive controller (Drive path is '/'), skipping NVMe controller tests Oct 5 02:03:36 storageqe-109 INFO: Drive path for /dev/nvme0n1: / Oct 5 02:03:36 storageqe-109 INFO: Device /dev/nvme0n1 has no associated drive controller (Drive path is '/'), skipping NVMe controller tests INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_init_nvme #### Oct 5 02:03:42 storageqe-109 INFO: #### after available_disks ['/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 02:03:42 storageqe-109 INFO: #### END test_init_nvme #### Oct 5 02:03:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:04:55 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:04:55 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:05:26 storageqe-109 kernel: __vm_enough_memory: pid: 1962636, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 5 02:05:26 storageqe-109 kernel: __vm_enough_memory: pid: 1962636, comm: claude, bytes: 34355400704 not enough memory for the allocation Oct 5 02:05:26 storageqe-109 kernel: __vm_enough_memory: pid: 1962636, comm: claude, bytes: 34359873536 not enough memory for the allocation Oct 5 02:05:26 storageqe-109 kernel: __vm_enough_memory: pid: 1962636, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 5 02:05:26 storageqe-109 systemd-coredump[1966620]: Process 1962636 (claude) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 5 02:05:26 storageqe-109 systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump. Oct 5 02:05:26 storageqe-109 systemd[1]: Started systemd-coredump@0-1966620-0.service - Process Core Dump (PID 1966620/UID 0). Oct 5 02:05:28 storageqe-109 systemd-coredump[1966621]: Process 1962636 (claude) of user 0 dumped core.#012#012Module /usr/bin/node-22 from rpm nodejs22-22.19.0-2.el10_0.x86_64#012Stack trace of thread 1962636:#012#0 0x00007f08f44bdfcc n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 5 02:05:28 storageqe-109 systemd[1]: systemd-coredump@0-1966620-0.service: Deactivated successfully. Oct 5 02:05:28 storageqe-109 systemd[1]: systemd-coredump@0-1966620-0.service: Consumed 1.063s CPU time, 1G memory peak. Oct 5 02:05:32 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:05:41 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:05:41 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:06:11 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:10:59 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:10:59 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:11:43 storageqe-109 kernel: __vm_enough_memory: pid: 1966630, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 5 02:11:43 storageqe-109 kernel: __vm_enough_memory: pid: 1966630, comm: claude, bytes: 34354864128 not enough memory for the allocation Oct 5 02:11:43 storageqe-109 kernel: __vm_enough_memory: pid: 1966630, comm: claude, bytes: 34359873536 not enough memory for the allocation Oct 5 02:11:43 storageqe-109 kernel: __vm_enough_memory: pid: 1966630, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 5 02:11:43 storageqe-109 systemd-coredump[1967136]: Process 1966630 (claude) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 5 02:11:43 storageqe-109 systemd[1]: Started systemd-coredump@1-1967136-0.service - Process Core Dump (PID 1967136/UID 0). Oct 5 02:11:44 storageqe-109 systemd-coredump[1967137]: Process 1966630 (claude) of user 0 dumped core.#012#012Module /usr/bin/node-22 from rpm nodejs22-22.19.0-2.el10_0.x86_64#012Stack trace of thread 1966630:#012#0 0x00007f5ad0ebdfcc n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 5 02:11:44 storageqe-109 systemd[1]: systemd-coredump@1-1967136-0.service: Deactivated successfully. Oct 5 02:11:44 storageqe-109 systemd[1]: systemd-coredump@1-1967136-0.service: Consumed 1.088s CPU time, 1G memory peak. Oct 5 02:11:52 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:11:55 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:11:55 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:12:25 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:22:08 storageqe-109 dmeventd[1921687]: dmeventd was idle for 3600 second(s), exiting. Oct 5 02:22:08 storageqe-109 dmeventd[1921687]: dmeventd shutting down. Oct 5 02:22:08 storageqe-109 systemd[1]: dm-event.service: Deactivated successfully. Oct 5 02:27:05 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:27:05 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:28:53 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:30:10 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:30:10 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:30:40 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:30:43 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:30:44 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:31:02 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 02:31:02 storageqe-109 dnf[1968134]: Updating Subscription Management repositories. Oct 5 02:31:02 storageqe-109 dnf[1968134]: Unable to read consumer identity Oct 5 02:31:02 storageqe-109 dnf[1968134]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 02:31:02 storageqe-109 dnf[1968134]: Metadata cache refreshed recently. Oct 5 02:31:03 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 02:31:03 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 02:31:03 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 227ms CPU time, 65.3M memory peak. Oct 5 02:32:01 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 02:32:03 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 02:32:03 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 02:34:12 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 03:51:47 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 03:51:47 storageqe-109 dnf[1969269]: Updating Subscription Management repositories. Oct 5 03:51:47 storageqe-109 dnf[1969269]: Unable to read consumer identity Oct 5 03:51:47 storageqe-109 dnf[1969269]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-AppStream 445 kB/s | 2.8 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-AppStream-debuginfo 500 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-BaseOS 715 kB/s | 2.7 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-BaseOS-debuginfo 417 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-CRB 688 kB/s | 2.7 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-CRB-debuginfo 780 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-HighAvailability 1.1 MB/s | 2.8 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-HighAvailability-debuginfo 528 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-NFV 713 kB/s | 2.7 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-NFV-debuginfo 402 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-RT 703 kB/s | 2.7 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-RT-debuginfo 295 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-SAP 603 kB/s | 2.7 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-SAP-debuginfo 413 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-SAPHANA 846 kB/s | 2.7 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: beaker-SAPHANA-debuginfo 575 kB/s | 1.5 kB 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 5 03:51:47 storageqe-109 dnf[1969269]: Errors during downloading metadata for repository 'beaker-client': Oct 5 03:51:47 storageqe-109 dnf[1969269]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 03:51:47 storageqe-109 dnf[1969269]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 03:51:48 storageqe-109 dnf[1969269]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 5 03:51:48 storageqe-109 dnf[1969269]: Google Cloud CLI 4.2 kB/s | 1.4 kB 00:00 Oct 5 03:51:49 storageqe-109 dnf[1969269]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 5 03:51:50 storageqe-109 dnf[1969269]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 5 03:51:50 storageqe-109 dnf[1969269]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 5 03:51:50 storageqe-109 dnf[1969269]: Ignoring repositories: beaker-client Oct 5 03:51:50 storageqe-109 dnf[1969269]: Metadata cache created. Oct 5 03:51:51 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 03:51:51 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 03:51:51 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 330ms CPU time, 75.1M memory peak. Oct 5 03:53:22 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 03:53:23 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 03:53:23 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 04:26:19 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 04:26:19 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 04:26:19 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 05:17:22 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 05:17:22 storageqe-109 dnf[1969469]: Updating Subscription Management repositories. Oct 5 05:17:22 storageqe-109 dnf[1969469]: Unable to read consumer identity Oct 5 05:17:22 storageqe-109 dnf[1969469]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 05:17:22 storageqe-109 dnf[1969469]: Metadata cache refreshed recently. Oct 5 05:17:22 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 05:17:22 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 05:23:43 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 05:23:43 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 05:23:43 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 06:23:16 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 06:23:16 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 06:23:16 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 06:41:34 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 06:41:35 storageqe-109 dnf[1969614]: Updating Subscription Management repositories. Oct 5 06:41:35 storageqe-109 dnf[1969614]: Unable to read consumer identity Oct 5 06:41:35 storageqe-109 dnf[1969614]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 06:41:35 storageqe-109 dnf[1969614]: Metadata cache refreshed recently. Oct 5 06:41:35 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 06:41:35 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 07:21:22 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 07:21:23 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 07:21:23 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 07:44:01 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 07:44:01 storageqe-109 dnf[1969713]: Updating Subscription Management repositories. Oct 5 07:44:01 storageqe-109 dnf[1969713]: Unable to read consumer identity Oct 5 07:44:01 storageqe-109 dnf[1969713]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-AppStream 487 kB/s | 2.8 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-AppStream-debuginfo 371 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-BaseOS 489 kB/s | 2.7 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-BaseOS-debuginfo 340 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-CRB 553 kB/s | 2.7 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-CRB-debuginfo 436 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-HighAvailability 768 kB/s | 2.8 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-HighAvailability-debuginfo 419 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-NFV 574 kB/s | 2.7 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-NFV-debuginfo 517 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-RT 733 kB/s | 2.7 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-RT-debuginfo 482 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-SAP 663 kB/s | 2.7 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-SAP-debuginfo 391 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-SAPHANA 697 kB/s | 2.7 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: beaker-SAPHANA-debuginfo 499 kB/s | 1.5 kB 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 5 07:44:01 storageqe-109 dnf[1969713]: Errors during downloading metadata for repository 'beaker-client': Oct 5 07:44:01 storageqe-109 dnf[1969713]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 07:44:01 storageqe-109 dnf[1969713]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 07:44:02 storageqe-109 dnf[1969713]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 5 07:44:02 storageqe-109 dnf[1969713]: Google Cloud CLI 4.1 kB/s | 1.4 kB 00:00 Oct 5 07:44:03 storageqe-109 dnf[1969713]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 5 07:44:04 storageqe-109 dnf[1969713]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 5 07:44:04 storageqe-109 dnf[1969713]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 5 07:44:04 storageqe-109 dnf[1969713]: Ignoring repositories: beaker-client Oct 5 07:44:04 storageqe-109 dnf[1969713]: Metadata cache created. Oct 5 07:44:04 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 07:44:04 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 07:44:04 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 334ms CPU time, 70.2M memory peak. Oct 5 08:41:45 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 08:41:45 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 08:42:30 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 08:42:51 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 08:42:51 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 08:43:21 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 08:50:05 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 08:50:05 storageqe-109 dnf[1970245]: Updating Subscription Management repositories. Oct 5 08:50:05 storageqe-109 dnf[1970245]: Unable to read consumer identity Oct 5 08:50:05 storageqe-109 dnf[1970245]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 08:50:05 storageqe-109 dnf[1970245]: Metadata cache refreshed recently. Oct 5 08:50:05 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 08:50:05 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 08:53:55 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 08:53:55 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 08:53:55 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 09:28:47 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 09:28:47 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 09:28:47 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 09:55:28 storageqe-109 NetworkManager[979]: [1759672528.7914] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 5 09:55:28 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 5 09:55:28 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 5 09:55:38 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 5 10:02:34 storageqe-109 systemd[1058]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories... Oct 5 10:02:34 storageqe-109 systemd[1058]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories. Oct 5 10:05:49 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 10:05:49 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 10:05:49 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 10:10:40 storageqe-109 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Oct 5 10:10:40 storageqe-109 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Oct 5 10:10:40 storageqe-109 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Oct 5 10:19:50 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 10:19:50 storageqe-109 dnf[1970619]: Updating Subscription Management repositories. Oct 5 10:19:50 storageqe-109 dnf[1970619]: Unable to read consumer identity Oct 5 10:19:50 storageqe-109 dnf[1970619]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 10:19:50 storageqe-109 dnf[1970619]: Metadata cache refreshed recently. Oct 5 10:19:50 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 10:19:50 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 11:07:13 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 11:07:13 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 11:07:13 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 11:33:25 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 11:33:25 storageqe-109 dnf[1970734]: Updating Subscription Management repositories. Oct 5 11:33:25 storageqe-109 dnf[1970734]: Unable to read consumer identity Oct 5 11:33:25 storageqe-109 dnf[1970734]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-AppStream 417 kB/s | 2.8 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-AppStream-debuginfo 374 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-BaseOS 782 kB/s | 2.7 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-BaseOS-debuginfo 365 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-CRB 553 kB/s | 2.7 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-CRB-debuginfo 480 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-HighAvailability 800 kB/s | 2.8 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-HighAvailability-debuginfo 561 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-NFV 283 kB/s | 2.7 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-NFV-debuginfo 454 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-RT 638 kB/s | 2.7 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-RT-debuginfo 458 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-SAP 764 kB/s | 2.7 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-SAP-debuginfo 377 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-SAPHANA 664 kB/s | 2.7 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-SAPHANA-debuginfo 363 kB/s | 1.5 kB 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 5 11:33:25 storageqe-109 dnf[1970734]: Errors during downloading metadata for repository 'beaker-client': Oct 5 11:33:25 storageqe-109 dnf[1970734]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 11:33:25 storageqe-109 dnf[1970734]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 11:33:25 storageqe-109 dnf[1970734]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 5 11:33:26 storageqe-109 dnf[1970734]: Google Cloud CLI 3.3 kB/s | 1.4 kB 00:00 Oct 5 11:33:27 storageqe-109 dnf[1970734]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 5 11:33:27 storageqe-109 dnf[1970734]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 5 11:33:28 storageqe-109 dnf[1970734]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 5 11:33:28 storageqe-109 dnf[1970734]: Ignoring repositories: beaker-client Oct 5 11:33:28 storageqe-109 dnf[1970734]: Metadata cache created. Oct 5 11:33:28 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 11:33:28 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 12:18:07 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 12:18:07 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 12:18:07 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 13:21:11 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 13:21:11 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 13:21:11 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 13:31:22 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 13:31:22 storageqe-109 dnf[1970979]: Updating Subscription Management repositories. Oct 5 13:31:22 storageqe-109 dnf[1970979]: Unable to read consumer identity Oct 5 13:31:22 storageqe-109 dnf[1970979]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 13:31:22 storageqe-109 dnf[1970979]: Metadata cache refreshed recently. Oct 5 13:31:22 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 13:31:22 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 14:50:56 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 14:50:57 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 14:50:57 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 15:14:28 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 15:14:28 storageqe-109 dnf[1971144]: Updating Subscription Management repositories. Oct 5 15:14:28 storageqe-109 dnf[1971144]: Unable to read consumer identity Oct 5 15:14:28 storageqe-109 dnf[1971144]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-AppStream 145 kB/s | 2.8 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-AppStream-debuginfo 176 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-BaseOS 919 kB/s | 2.7 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-BaseOS-debuginfo 517 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-CRB 680 kB/s | 2.7 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-CRB-debuginfo 70 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-HighAvailability 203 kB/s | 2.8 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-HighAvailability-debuginfo 639 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-NFV 232 kB/s | 2.7 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-NFV-debuginfo 160 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-RT 787 kB/s | 2.7 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-RT-debuginfo 577 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-SAP 149 kB/s | 2.7 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-SAP-debuginfo 192 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-SAPHANA 636 kB/s | 2.7 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: beaker-SAPHANA-debuginfo 484 kB/s | 1.5 kB 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 5 15:14:28 storageqe-109 dnf[1971144]: Errors during downloading metadata for repository 'beaker-client': Oct 5 15:14:28 storageqe-109 dnf[1971144]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 15:14:28 storageqe-109 dnf[1971144]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 15:14:29 storageqe-109 dnf[1971144]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 5 15:14:29 storageqe-109 dnf[1971144]: Google Cloud CLI 3.4 kB/s | 1.4 kB 00:00 Oct 5 15:14:30 storageqe-109 dnf[1971144]: Copr repo for python-ssh2-python312 owned by mh 2.0 kB/s | 1.5 kB 00:00 Oct 5 15:14:31 storageqe-109 dnf[1971144]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 5 15:14:31 storageqe-109 dnf[1971144]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 5 15:14:31 storageqe-109 dnf[1971144]: Ignoring repositories: beaker-client Oct 5 15:14:31 storageqe-109 dnf[1971144]: Metadata cache created. Oct 5 15:14:31 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 15:14:31 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 15:49:20 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 15:49:20 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 15:49:20 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 16:29:32 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 16:29:33 storageqe-109 dnf[1971300]: Updating Subscription Management repositories. Oct 5 16:29:33 storageqe-109 dnf[1971300]: Unable to read consumer identity Oct 5 16:29:33 storageqe-109 dnf[1971300]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 16:29:33 storageqe-109 dnf[1971300]: Metadata cache refreshed recently. Oct 5 16:29:33 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 16:29:33 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 16:50:54 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 16:50:54 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 16:50:54 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 17:03:34 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 17:03:34 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 17:03:34 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 18:25:49 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 18:25:50 storageqe-109 dnf[1971493]: Updating Subscription Management repositories. Oct 5 18:25:50 storageqe-109 dnf[1971493]: Unable to read consumer identity Oct 5 18:25:50 storageqe-109 dnf[1971493]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-AppStream 637 kB/s | 2.8 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-AppStream-debuginfo 474 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-BaseOS 854 kB/s | 2.7 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-BaseOS-debuginfo 565 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-CRB 728 kB/s | 2.7 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-CRB-debuginfo 629 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-HighAvailability 940 kB/s | 2.8 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-HighAvailability-debuginfo 666 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-NFV 999 kB/s | 2.7 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-NFV-debuginfo 549 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-RT 335 kB/s | 2.7 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-RT-debuginfo 573 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-SAP 792 kB/s | 2.7 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-SAP-debuginfo 567 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-SAPHANA 777 kB/s | 2.7 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-SAPHANA-debuginfo 632 kB/s | 1.5 kB 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 5 18:25:50 storageqe-109 dnf[1971493]: Errors during downloading metadata for repository 'beaker-client': Oct 5 18:25:50 storageqe-109 dnf[1971493]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 18:25:50 storageqe-109 dnf[1971493]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 18:25:50 storageqe-109 dnf[1971493]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 5 18:25:51 storageqe-109 dnf[1971493]: Google Cloud CLI 3.5 kB/s | 1.4 kB 00:00 Oct 5 18:25:51 storageqe-109 dnf[1971493]: Copr repo for python-ssh2-python312 owned by mh 2.0 kB/s | 1.5 kB 00:00 Oct 5 18:25:52 storageqe-109 dnf[1971493]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 5 18:25:52 storageqe-109 dnf[1971493]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 5 18:25:52 storageqe-109 dnf[1971493]: Ignoring repositories: beaker-client Oct 5 18:25:52 storageqe-109 dnf[1971493]: Metadata cache created. Oct 5 18:25:52 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 18:25:52 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 18:55:01 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 18:55:01 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 18:55:01 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 19:37:40 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 19:37:40 storageqe-109 dnf[1971650]: Updating Subscription Management repositories. Oct 5 19:37:40 storageqe-109 dnf[1971650]: Unable to read consumer identity Oct 5 19:37:40 storageqe-109 dnf[1971650]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 19:37:40 storageqe-109 dnf[1971650]: Metadata cache refreshed recently. Oct 5 19:37:40 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 19:37:40 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 19:54:22 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 19:54:23 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 19:54:23 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 20:14:06 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 20:14:06 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 20:14:06 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 5 20:31:00 storageqe-109 root[1971762]: efibootmgr -n 0001 Oct 5 20:31:00 storageqe-109 root[1971764]: NEXTBOOT_VALID_TIME is zero. BootNext setting will persist. Oct 5 20:37:21 storageqe-109 systemd: RTC configured in localtime, applying delta of -240 minutes to system time. Oct 5 20:37:21 storageqe-109 systemd: systemd 257-13.el10-g833aa52 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +IPE +SMACK +SECCOMP -GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 +PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +BTF +XKBCOMMON +UTMP +SYSVINIT +LIBARCHIVE) Oct 5 20:37:21 storageqe-109 systemd: Detected architecture x86-64. Oct 5 20:37:21 storageqe-109 systemd: bpf-restrict-fs: LSM BPF program attached Oct 5 20:37:21 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 5 20:37:21 storageqe-109 systemd: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 20:37:21 storageqe-109 systemd: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 20:37:21 storageqe-109 systemd: initrd-switch-root.service: Deactivated successfully. Oct 5 20:37:21 storageqe-109 systemd: Stopped initrd-switch-root.service - Switch Root. Oct 5 20:37:21 storageqe-109 systemd: systemd-journald.service: Scheduled restart job, restart counter is at 1. Oct 5 20:37:21 storageqe-109 systemd: Created slice system-getty.slice - Slice /system/getty. Oct 5 20:37:21 storageqe-109 systemd: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty. Oct 5 20:37:21 storageqe-109 systemd: Created slice system-sshd\x2dkeygen.slice - Slice /system/sshd-keygen. Oct 5 20:37:21 storageqe-109 systemd: Created slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck. Oct 5 20:37:21 storageqe-109 systemd: Created slice user.slice - User and Session Slice. Oct 5 20:37:21 storageqe-109 systemd: Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch. Oct 5 20:37:21 storageqe-109 systemd: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch. Oct 5 20:37:21 storageqe-109 systemd: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point. Oct 5 20:37:21 storageqe-109 systemd: Expecting device dev-disk-by\x2duuid-1DB2\x2d7C4E.device - /dev/disk/by-uuid/1DB2-7C4E... Oct 5 20:37:21 storageqe-109 systemd: Expecting device dev-disk-by\x2duuid-3dcfa39e\x2d4494\x2d4145\x2da4a0\x2dec3f64d1f9c4.device - /dev/disk/by-uuid/3dcfa39e-4494-4145-a4a0-ec3f64d1f9c4... Oct 5 20:37:21 storageqe-109 systemd: Expecting device dev-disk-by\x2duuid-a353de39\x2dbab8\x2d4701\x2da7a6\x2d575e3e4eb6f5.device - /dev/disk/by-uuid/a353de39-bab8-4701-a7a6-575e3e4eb6f5... Oct 5 20:37:21 storageqe-109 systemd: Expecting device dev-ttyS0.device - /dev/ttyS0... Oct 5 20:37:21 storageqe-109 systemd: Reached target cryptsetup.target - Local Encrypted Volumes. Oct 5 20:37:21 storageqe-109 systemd: Stopped target initrd-switch-root.target - Switch Root. Oct 5 20:37:21 storageqe-109 systemd: Stopped target initrd-fs.target - Initrd File Systems. Oct 5 20:37:21 storageqe-109 systemd: Stopped target initrd-root-fs.target - Initrd Root File System. Oct 5 20:37:21 storageqe-109 systemd: Reached target integritysetup.target - Local Integrity Protected Volumes. Oct 5 20:37:21 storageqe-109 systemd: Reached target paths.target - Path Units. Oct 5 20:37:21 storageqe-109 systemd: Reached target slices.target - Slice Units. Oct 5 20:37:21 storageqe-109 systemd: Reached target time-set.target - System Time Set. Oct 5 20:37:21 storageqe-109 systemd: Reached target veritysetup.target - Local Verity Protected Volumes. Oct 5 20:37:21 storageqe-109 systemd: Listening on dm-event.socket - Device-mapper event daemon FIFOs. Oct 5 20:37:21 storageqe-109 systemd: Listening on lvm2-lvmpolld.socket - LVM2 poll daemon socket. Oct 5 20:37:21 storageqe-109 systemd: Listening on systemd-coredump.socket - Process Core Dump Socket. Oct 5 20:37:21 storageqe-109 systemd: Listening on systemd-creds.socket - Credential Encryption/Decryption. Oct 5 20:37:21 storageqe-109 systemd: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe. Oct 5 20:37:21 storageqe-109 systemd: systemd-pcrextend.socket - TPM PCR Measurements was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:21 storageqe-109 systemd: systemd-pcrlock.socket - Make TPM PCR Policy was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:21 storageqe-109 systemd: Listening on systemd-udevd-control.socket - udev Control Socket. Oct 5 20:37:21 storageqe-109 systemd: Listening on systemd-udevd-kernel.socket - udev Kernel Socket. Oct 5 20:37:21 storageqe-109 systemd: Listening on systemd-userdbd.socket - User Database Manager Socket. Oct 5 20:37:21 storageqe-109 systemd: Activating swap dev-disk-by\x2duuid-4936f7ee\x2ddc93\x2d48f9\x2da95b\x2dd627a3523b69.swap - /dev/disk/by-uuid/4936f7ee-dc93-48f9-a95b-d627a3523b69... Oct 5 20:37:21 storageqe-109 systemd: Mounting dev-hugepages.mount - Huge Pages File System... Oct 5 20:37:21 storageqe-109 systemd: Mounting dev-mqueue.mount - POSIX Message Queue File System... Oct 5 20:37:21 storageqe-109 kernel: Adding 8163324k swap on /dev/mapper/rhel_storageqe--109-swap. Priority:-2 extents:1 across:8163324k SS Oct 5 20:37:21 storageqe-109 systemd: Mounting sys-kernel-debug.mount - Kernel Debug File System... Oct 5 20:37:21 storageqe-109 systemd: Mounting sys-kernel-tracing.mount - Kernel Trace File System... Oct 5 20:37:21 storageqe-109 systemd: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). Oct 5 20:37:21 storageqe-109 systemd: fips-crypto-policy-overlay.service - Bind-mount FIPS crypto-policy in FIPS mode was skipped because of an unmet condition check (ConditionKernelCommandLine=fips=1). Oct 5 20:37:21 storageqe-109 systemd: Starting iscsi-starter.service... Oct 5 20:37:21 storageqe-109 systemd: Starting kmod-static-nodes.service - Create List of Static Device Nodes... Oct 5 20:37:21 storageqe-109 systemd: Starting lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... Oct 5 20:37:21 storageqe-109 systemd: Starting modprobe@configfs.service - Load Kernel Module configfs... Oct 5 20:37:21 storageqe-109 systemd: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... Oct 5 20:37:21 storageqe-109 systemd: Starting modprobe@dm_multipath.service - Load Kernel Module dm_multipath... Oct 5 20:37:21 storageqe-109 systemd: Starting modprobe@drm.service - Load Kernel Module drm... Oct 5 20:37:21 storageqe-109 systemd: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore... Oct 5 20:37:21 storageqe-109 systemd: Starting modprobe@fuse.service - Load Kernel Module fuse... Oct 5 20:37:21 storageqe-109 kernel: fuse: init (API version 7.41) Oct 5 20:37:21 storageqe-109 systemd: Starting modprobe@loop.service - Load Kernel Module loop... Oct 5 20:37:21 storageqe-109 kernel: loop: module loaded Oct 5 20:37:21 storageqe-109 systemd: systemd-fsck-root.service: Deactivated successfully. Oct 5 20:37:21 storageqe-109 systemd: Stopped systemd-fsck-root.service - File System Check on Root Device. Oct 5 20:37:21 storageqe-109 systemd: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67). Oct 5 20:37:21 storageqe-109 systemd: Starting systemd-journald.service - Journal Service... Oct 5 20:37:21 storageqe-109 systemd: Starting systemd-modules-load.service - Load Kernel Modules... Oct 5 20:37:21 storageqe-109 systemd: Starting systemd-network-generator.service - Generate network units from Kernel command line... Oct 5 20:37:21 storageqe-109 systemd-journald[737]: Collecting audit messages is disabled. Oct 5 20:37:21 storageqe-109 systemd-journald[737]: Journal started Oct 5 20:37:21 storageqe-109 systemd-journald[737]: Runtime Journal (/run/log/journal/7f339974107e491c9e42a18c8fe3fb7d) is 8M, max 300.9M, 292.9M free. Oct 5 20:37:21 storageqe-109 systemd[1]: Queued start job for default target multi-user.target. Oct 5 20:37:21 storageqe-109 systemd[1]: systemd-journald.service: Deactivated successfully. Oct 5 20:37:21 storageqe-109 systemd-modules-load[738]: Module 'msr' is built in Oct 5 20:37:21 storageqe-109 systemd-modules-load[738]: Module 'scsi_dh_alua' is built in Oct 5 20:37:21 storageqe-109 systemd-modules-load[738]: Module 'scsi_dh_emc' is built in Oct 5 20:37:21 storageqe-109 systemd-modules-load[738]: Module 'scsi_dh_rdac' is built in Oct 5 20:37:21 storageqe-109 lvm[727]: 2 logical volume(s) in volume group "rhel_storageqe-109" monitored Oct 5 20:37:21 storageqe-109 systemd: systemd-pcrmachine.service - TPM PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:21 storageqe-109 systemd: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems... Oct 5 20:37:22 storageqe-109 systemd: systemd-tpm2-setup-early.service - Early TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:22 storageqe-109 systemd: Starting systemd-udev-load-credentials.service - Load udev Rules from Credentials... Oct 5 20:37:22 storageqe-109 systemd: Starting systemd-udev-trigger.service - Coldplug All udev Devices... Oct 5 20:37:22 storageqe-109 systemd: Activated swap dev-disk-by\x2duuid-4936f7ee\x2ddc93\x2d48f9\x2da95b\x2dd627a3523b69.swap - /dev/disk/by-uuid/4936f7ee-dc93-48f9-a95b-d627a3523b69. Oct 5 20:37:22 storageqe-109 systemd: Started systemd-journald.service - Journal Service. Oct 5 20:37:22 storageqe-109 systemd[1]: Mounted dev-hugepages.mount - Huge Pages File System. Oct 5 20:37:22 storageqe-109 systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System. Oct 5 20:37:22 storageqe-109 systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System. Oct 5 20:37:22 storageqe-109 systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@configfs.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@dm_mod.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@dm_multipath.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@dm_multipath.service - Load Kernel Module dm_multipath. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@drm.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@fuse.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@loop.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-network-generator.service - Generate network units from Kernel command line. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-udev-load-credentials.service - Load udev Rules from Credentials. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-udev-trigger.service - Coldplug All udev Devices. Oct 5 20:37:22 storageqe-109 systemd[1]: Reached target network-pre.target - Preparation for Network. Oct 5 20:37:22 storageqe-109 systemd[1]: Reached target swap.target - Swaps. Oct 5 20:37:22 storageqe-109 systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System... Oct 5 20:37:22 storageqe-109 systemd[1]: Starting multipathd.service - Device-Mapper Multipath Device Controller... Oct 5 20:37:22 storageqe-109 systemd[1]: iscsi-onboot.service - Special handling of early boot iSCSI sessions was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/class/iscsi_session). Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). Oct 5 20:37:22 storageqe-109 systemd[1]: Starting systemd-journal-flush.service - Flush Journal to Persistent Storage... Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). Oct 5 20:37:22 storageqe-109 systemd[1]: Starting systemd-random-seed.service - Load/Save OS Random Seed... Oct 5 20:37:22 storageqe-109 systemd-journald[737]: Runtime Journal (/run/log/journal/7f339974107e491c9e42a18c8fe3fb7d) is 8M, max 300.9M, 292.9M free. Oct 5 20:37:22 storageqe-109 systemd-journald[737]: Received client request to flush runtime journal. Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. Oct 5 20:37:22 storageqe-109 systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables... Oct 5 20:37:22 storageqe-109 systemd[1]: Starting systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully... Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:22 storageqe-109 systemd[1]: Mounted sys-fs-fuse-connections.mount - FUSE Control File System. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-journal-flush.service - Flush Journal to Persistent Storage. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-random-seed.service - Load/Save OS Random Seed. Oct 5 20:37:22 storageqe-109 multipathd[775]: multipathd v0.9.9: start up Oct 5 20:37:22 storageqe-109 multipathd[775]: reconfigure: setting up paths and maps Oct 5 20:37:22 storageqe-109 systemd[1]: Started multipathd.service - Device-Mapper Multipath Device Controller. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-sysctl.service - Apply Kernel Variables. Oct 5 20:37:22 storageqe-109 systemd[1]: fips-crypto-policy-overlay.service - Bind-mount FIPS crypto-policy in FIPS mode was skipped because of an unmet condition check (ConditionKernelCommandLine=fips=1). Oct 5 20:37:22 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 20:37:22 storageqe-109 systemd[1]: iscsi-onboot.service - Special handling of early boot iSCSI sessions was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/class/iscsi_session). Oct 5 20:37:22 storageqe-109 systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod... Oct 5 20:37:22 storageqe-109 systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore... Oct 5 20:37:22 storageqe-109 systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop... Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-hibernate-clear.service - Clear Stale Hibernate Storage Info was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/HibernateLocation-8cf2644b-4b0b-428f-9387-6d876050dc67). Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-hwdb-update.service - Rebuild Hardware Database was skipped because of an unmet condition check (ConditionNeedsUpdate=/etc). Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-pcrmachine.service - TPM PCR Machine ID Measurement was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-tpm2-setup-early.service - Early TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-tpm2-setup.service - TPM SRK Setup was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:22 storageqe-109 systemd[1]: Starting systemd-userdbd.service - User Database Manager... Oct 5 20:37:22 storageqe-109 systemd[1]: Finished iscsi-starter.service. Oct 5 20:37:22 storageqe-109 systemd[1]: Started systemd-userdbd.service - User Database Manager. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@dm_mod.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@efi_pstore.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore. Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@loop.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop. Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully. Oct 5 20:37:22 storageqe-109 systemd[1]: systemd-sysusers.service - Create System Users was skipped because no trigger condition checks were met. Oct 5 20:37:22 storageqe-109 systemd[1]: Starting systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev... Oct 5 20:37:22 storageqe-109 systemd[1]: Finished systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev. Oct 5 20:37:22 storageqe-109 systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files... Oct 5 20:37:22 storageqe-109 systemd-udevd[803]: Using default interface naming scheme 'rhel-10.0'. Oct 5 20:37:22 storageqe-109 systemd[1]: Started systemd-udevd.service - Rule-based Manager for Device Events and Files. Oct 5 20:37:22 storageqe-109 systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs... Oct 5 20:37:22 storageqe-109 systemd[1]: nvmefc-boot-connections.service - Auto-connect to subsystems on FC-NVME devices found during boot was skipped because of an unmet condition check (ConditionPathExists=/sys/class/fc/fc_udev_device/nvme_discovery). Oct 5 20:37:22 storageqe-109 systemd[1]: Reached target local-fs-pre.target - Preparation for Local File Systems. Oct 5 20:37:22 storageqe-109 kernel: sd 0:3:107:0: Attached scsi generic sg0 type 0 Oct 5 20:37:22 storageqe-109 kernel: sd 0:3:108:0: Attached scsi generic sg1 type 0 Oct 5 20:37:22 storageqe-109 kernel: sd 0:3:109:0: Attached scsi generic sg2 type 0 Oct 5 20:37:22 storageqe-109 kernel: sd 0:3:110:0: Attached scsi generic sg3 type 0 Oct 5 20:37:22 storageqe-109 kernel: IPMI message handler: version 39.2 Oct 5 20:37:22 storageqe-109 kernel: sd 0:3:111:0: Attached scsi generic sg4 type 0 Oct 5 20:37:22 storageqe-109 systemd[1]: Condition check resulted in dev-ttyS0.device - /dev/ttyS0 being skipped. Oct 5 20:37:22 storageqe-109 systemd[1]: Condition check resulted in dev-tpmrm0.device - /dev/tpmrm0 being skipped. Oct 5 20:37:22 storageqe-109 kernel: ipmi device interface Oct 5 20:37:22 storageqe-109 systemd[1]: Reached target tpm2.target - Trusted Platform Module. Oct 5 20:37:22 storageqe-109 kernel: mei_me 0000:00:16.0: Device doesn't have valid ME Interface Oct 5 20:37:22 storageqe-109 kernel: ACPI: \_SB_.PR00: _PSS evaluation failed: AE_NOT_FOUND Oct 5 20:37:22 storageqe-109 systemd[1]: modprobe@configfs.service: Deactivated successfully. Oct 5 20:37:22 storageqe-109 systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs. Oct 5 20:37:22 storageqe-109 kernel: i801_smbus 0000:00:1f.4: SPD Write Disable is set Oct 5 20:37:22 storageqe-109 kernel: ipmi_si: IPMI System Interface driver Oct 5 20:37:22 storageqe-109 kernel: i801_smbus 0000:00:1f.4: SMBus using PCI interrupt Oct 5 20:37:22 storageqe-109 kernel: ipmi_si dmi-ipmi-si.0: ipmi_platform: probing via SMBIOS Oct 5 20:37:22 storageqe-109 kernel: ipmi_platform: ipmi_si: SMBIOS: io 0xca8 regsize 1 spacing 4 irq 10 Oct 5 20:37:22 storageqe-109 kernel: input: PC Speaker as /devices/platform/pcspkr/input/input2 Oct 5 20:37:22 storageqe-109 kernel: Console: switching to colour dummy device 80x25 Oct 5 20:37:22 storageqe-109 kernel: ipmi_si: Adding SMBIOS-specified kcs state machine Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.0 eth0: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address d0:46:0c:64:a6:2c Oct 5 20:37:22 storageqe-109 kernel: ipmi_si IPI0001:00: ipmi_platform: probing via ACPI Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) Oct 5 20:37:22 storageqe-109 kernel: ipmi_si IPI0001:00: ipmi_platform: [io 0x0ca8] regsize 1 spacing 4 irq 10 Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] Oct 5 20:37:22 storageqe-109 kernel: ipmi_si dmi-ipmi-si.0: Removing SMBIOS-specified kcs state machine in favor of ACPI Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit] Oct 5 20:37:22 storageqe-109 kernel: ipmi_si: Adding ACPI-specified kcs state machine Oct 5 20:37:22 storageqe-109 kernel: ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca8, slave address 0x20, irq 10 Oct 5 20:37:22 storageqe-109 lvm[881]: PV /dev/sda3 online, VG rhel_storageqe-109 is complete. Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.1 eth1: Tigon3 [partno(BCM95720) rev 5720000] (PCI Express) MAC address d0:46:0c:64:a6:2d Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.1 eth1: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] Oct 5 20:37:22 storageqe-109 kernel: tg3 0000:07:00.1 eth1: dma_rwctrl[00000001] dma_mask[64-bit] Oct 5 20:37:22 storageqe-109 kernel: dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.4) Oct 5 20:37:22 storageqe-109 kernel: mgag200 0000:06:00.0: vgaarb: deactivate vga console Oct 5 20:37:23 storageqe-109 kernel: RAPL PMU: API unit is 2^-32 Joules, 2 fixed counters, 655360 ms ovfl timer Oct 5 20:37:23 storageqe-109 kernel: RAPL PMU: hw unit of domain pp0-core 2^-14 Joules Oct 5 20:37:23 storageqe-109 kernel: RAPL PMU: hw unit of domain package 2^-14 Joules Oct 5 20:37:23 storageqe-109 kernel: iTCO_vendor_support: vendor-support=0 Oct 5 20:37:23 storageqe-109 kernel: [drm] Initialized mgag200 1.0.0 for 0000:06:00.0 on minor 0 Oct 5 20:37:23 storageqe-109 kernel: tg3 0000:07:00.0 eno8303: renamed from eth0 Oct 5 20:37:23 storageqe-109 kernel: iTCO_wdt iTCO_wdt: unable to reset NO_REBOOT flag, device disabled by hardware/BIOS Oct 5 20:37:23 storageqe-109 kernel: tg3 0000:07:00.1 eno8403: renamed from eth1 Oct 5 20:37:23 storageqe-109 kernel: fbcon: mgag200drmfb (fb0) is primary device Oct 5 20:37:23 storageqe-109 kernel: ipmi_si IPI0001:00: The BMC does not support setting the recv irq bit, compensating, but the BMC needs to be fixed. Oct 5 20:37:23 storageqe-109 kernel: ipmi_si IPI0001:00: Using irq 10 Oct 5 20:37:23 storageqe-109 kernel: Console: switching to colour frame buffer device 128x48 Oct 5 20:37:23 storageqe-109 kernel: mgag200 0000:06:00.0: [drm] fb0: mgag200drmfb frame buffer device Oct 5 20:37:23 storageqe-109 kernel: intel_tcc_cooling: TCC Offset locked Oct 5 20:37:23 storageqe-109 systemd[1]: Condition check resulted in dev-disk-by\x2duuid-1DB2\x2d7C4E.device - PERC_H755_Adp EFI\x20System\x20Partition being skipped. Oct 5 20:37:23 storageqe-109 systemd[1]: Condition check resulted in dev-disk-by\x2duuid-3dcfa39e\x2d4494\x2d4145\x2da4a0\x2dec3f64d1f9c4.device - PERC_H755_Adp 2 being skipped. Oct 5 20:37:23 storageqe-109 systemd[1]: Starting systemd-fsck@dev-disk-by\x2duuid-1DB2\x2d7C4E.service - File System Check on /dev/disk/by-uuid/1DB2-7C4E... Oct 5 20:37:23 storageqe-109 systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup... Oct 5 20:37:23 storageqe-109 systemd[1]: Mounting boot.mount - /boot... Oct 5 20:37:23 storageqe-109 systemd[1]: Started lvm-activate-rhel_storageqe-109.service - [systemd-run] /usr/sbin/lvm vgchange -aay --autoactivation event rhel_storageqe-109. Oct 5 20:37:23 storageqe-109 kernel: XFS (sda2): Mounting V5 Filesystem 3dcfa39e-4494-4145-a4a0-ec3f64d1f9c4 Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-vconsole-setup.service: Deactivated successfully. Oct 5 20:37:23 storageqe-109 systemd[1]: Stopped systemd-vconsole-setup.service - Virtual Console Setup. Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: fsck.fat 4.2 (2021-01-31) Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: There are differences between boot sector and its backup. Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: This is mostly harmless. Differences: (offset:original/backup) Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: 65:01/00 Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: Not automatically fixing this. Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: Automatically removing dirty bit. Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: *** Filesystem was changed *** Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: Writing changes. Oct 5 20:37:23 storageqe-109 systemd-fsck[909]: /dev/sda1: 15 files, 2149/153290 clusters Oct 5 20:37:23 storageqe-109 systemd[1]: Starting systemd-vconsole-setup.service - Virtual Console Setup... Oct 5 20:37:23 storageqe-109 kernel: XFS (sda2): Starting recovery (logdev: internal) Oct 5 20:37:23 storageqe-109 lvm[902]: 3 logical volume(s) in volume group "rhel_storageqe-109" now active Oct 5 20:37:23 storageqe-109 kernel: XFS (sda2): Ending recovery (logdev: internal) Oct 5 20:37:23 storageqe-109 kernel: intel_rapl_msr: PL4 support detected. Oct 5 20:37:23 storageqe-109 kernel: intel_rapl_common: Found RAPL domain package Oct 5 20:37:23 storageqe-109 kernel: intel_rapl_common: Found RAPL domain core Oct 5 20:37:23 storageqe-109 systemd[1]: Finished systemd-fsck@dev-disk-by\x2duuid-1DB2\x2d7C4E.service - File System Check on /dev/disk/by-uuid/1DB2-7C4E. Oct 5 20:37:23 storageqe-109 systemd[1]: Mounted boot.mount - /boot. Oct 5 20:37:23 storageqe-109 systemd[1]: lvm-activate-rhel_storageqe-109.service: Deactivated successfully. Oct 5 20:37:23 storageqe-109 systemd[1]: Found device dev-disk-by\x2duuid-a353de39\x2dbab8\x2d4701\x2da7a6\x2d575e3e4eb6f5.device - /dev/disk/by-uuid/a353de39-bab8-4701-a7a6-575e3e4eb6f5. Oct 5 20:37:23 storageqe-109 systemd[1]: Mounting boot-efi.mount - /boot/efi... Oct 5 20:37:23 storageqe-109 systemd[1]: Mounting home.mount - /home... Oct 5 20:37:23 storageqe-109 kernel: XFS (dm-2): Mounting V5 Filesystem a353de39-bab8-4701-a7a6-575e3e4eb6f5 Oct 5 20:37:23 storageqe-109 systemd[1]: Mounted boot-efi.mount - /boot/efi. Oct 5 20:37:23 storageqe-109 kernel: XFS (dm-2): Starting recovery (logdev: internal) Oct 5 20:37:23 storageqe-109 kernel: XFS (dm-2): Ending recovery (logdev: internal) Oct 5 20:37:23 storageqe-109 systemd[1]: Finished systemd-vconsole-setup.service - Virtual Console Setup. Oct 5 20:37:23 storageqe-109 systemd[1]: Mounted home.mount - /home. Oct 5 20:37:23 storageqe-109 systemd[1]: Reached target local-fs.target - Local File Systems. Oct 5 20:37:23 storageqe-109 kernel: ipmi_si IPI0001:00: IPMI message handler: Found new BMC (man_id: 0x0002a2, prod_id: 0x0100, dev_id: 0x20) Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on systemd-bootctl.socket - Boot Entries Service Socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on systemd-sysext.socket - System Extension Image Management. Oct 5 20:37:23 storageqe-109 systemd[1]: selinux-autorelabel-mark.service - Mark the need to relabel after reboot was skipped because of an unmet condition check (ConditionPathExists=!/.autorelabel). Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-binfmt.service - Set Up Additional Binary Formats was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-boot-random-seed.service - Update Boot Loader Random Seed was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-confext.service - Merge System Configuration Images into /etc/ was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-sysext.service - Merge System Extension Images into /usr/ and /opt/ was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: Starting systemd-tmpfiles-setup.service - Create System Files and Directories... Oct 5 20:37:23 storageqe-109 kernel: ipmi_si IPI0001:00: IPMI kcs interface initialized Oct 5 20:37:23 storageqe-109 kernel: power_meter ACPI000D:00: Found ACPI power meter. Oct 5 20:37:23 storageqe-109 kernel: ipmi_ssif: IPMI SSIF Interface driver Oct 5 20:37:23 storageqe-109 systemd[1]: Finished systemd-tmpfiles-setup.service - Create System Files and Directories. Oct 5 20:37:23 storageqe-109 systemd[1]: Starting auditd.service - Security Audit Logging Service... Oct 5 20:37:23 storageqe-109 systemd[1]: ldconfig.service - Rebuild Dynamic Linker Cache was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes). Oct 5 20:37:23 storageqe-109 systemd[1]: first-boot-complete.target - First Boot Complete was skipped because of an unmet condition check (ConditionFirstBoot=yes). Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-journal-catalog-update.service - Rebuild Journal Catalog was skipped because of an unmet condition check (ConditionNeedsUpdate=/var). Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-machine-id-commit.service - Save Transient machine-id to Disk was skipped because of an unmet condition check (ConditionPathIsMountPoint=/etc/machine-id). Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-update-done.service - Update is Completed was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 auditd[957]: audit dispatcher initialized with q_depth=2000 and 1 active plugins Oct 5 20:37:23 storageqe-109 auditd[957]: Init complete, auditd 4.0.3 listening for events (startup state enable) Oct 5 20:37:23 storageqe-109 systemd[1]: Started auditd.service - Security Audit Logging Service. Oct 5 20:37:23 storageqe-109 systemd[1]: Starting audit-rules.service - Load Audit Rules... Oct 5 20:37:23 storageqe-109 systemd[1]: Starting systemd-update-utmp.service - Record System Boot/Shutdown in UTMP... Oct 5 20:37:23 storageqe-109 augenrules[963]: /usr/sbin/augenrules: No change Oct 5 20:37:23 storageqe-109 augenrules[979]: No rules Oct 5 20:37:23 storageqe-109 augenrules[979]: enabled 1 Oct 5 20:37:23 storageqe-109 augenrules[979]: failure 1 Oct 5 20:37:23 storageqe-109 augenrules[979]: pid 957 Oct 5 20:37:23 storageqe-109 augenrules[979]: rate_limit 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_limit 8192 Oct 5 20:37:23 storageqe-109 augenrules[979]: lost 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_wait_time 60000 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_wait_time_actual 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: enabled 1 Oct 5 20:37:23 storageqe-109 augenrules[979]: failure 1 Oct 5 20:37:23 storageqe-109 augenrules[979]: pid 957 Oct 5 20:37:23 storageqe-109 augenrules[979]: rate_limit 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_limit 8192 Oct 5 20:37:23 storageqe-109 augenrules[979]: lost 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_wait_time 60000 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_wait_time_actual 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: enabled 1 Oct 5 20:37:23 storageqe-109 augenrules[979]: failure 1 Oct 5 20:37:23 storageqe-109 augenrules[979]: pid 957 Oct 5 20:37:23 storageqe-109 augenrules[979]: rate_limit 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_limit 8192 Oct 5 20:37:23 storageqe-109 augenrules[979]: lost 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog 0 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_wait_time 60000 Oct 5 20:37:23 storageqe-109 augenrules[979]: backlog_wait_time_actual 0 Oct 5 20:37:23 storageqe-109 systemd[1]: audit-rules.service: Deactivated successfully. Oct 5 20:37:23 storageqe-109 systemd[1]: Finished audit-rules.service - Load Audit Rules. Oct 5 20:37:23 storageqe-109 systemd[1]: Finished systemd-update-utmp.service - Record System Boot/Shutdown in UTMP. Oct 5 20:37:23 storageqe-109 systemd[1]: Reached target sysinit.target - System Initialization. Oct 5 20:37:23 storageqe-109 systemd[1]: Started dnf-makecache.timer - dnf makecache --timer. Oct 5 20:37:23 storageqe-109 systemd[1]: Started systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on dbus.socket - D-Bus System Message Bus Socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on iscsid.socket - Open-iSCSI iscsid Socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on iscsiuio.socket - Open-iSCSI iscsiuio Socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on pcscd.socket - PC/SC Smart Card Daemon Activation Socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on sshd-unix-local.socket - OpenSSH Server Socket (systemd-ssh-generator, AF_UNIX Local). Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on sssd-kcm.socket - SSSD Kerberos Cache Manager responder socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on systemd-hostnamed.socket - Hostname Service Socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Starting tangd.socket - Tang Server socket... Oct 5 20:37:23 storageqe-109 systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus... Oct 5 20:37:23 storageqe-109 systemd[1]: systemd-pcrphase-sysinit.service - TPM PCR Barrier (Initialization) was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:23 storageqe-109 systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. Oct 5 20:37:23 storageqe-109 dbus-broker-launch[989]: Ready Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on tangd.socket - Tang Server socket. Oct 5 20:37:23 storageqe-109 systemd[1]: Reached target sockets.target - Socket Units. Oct 5 20:37:23 storageqe-109 systemd[1]: Reached target basic.target - Basic System. Oct 5 20:37:23 storageqe-109 systemd[1]: Starting NetworkManager.service - Network Manager... Oct 5 20:37:23 storageqe-109 systemd[1]: Starting chronyd.service - NTP client/server... Oct 5 20:37:23 storageqe-109 systemd[1]: Starting dracut-shutdown.service - Restore /run/initramfs on shutdown... Oct 5 20:37:23 storageqe-109 chronyd[999]: chronyd version 4.6.1 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +NTS +SECHASH +IPV6 +DEBUG) Oct 5 20:37:23 storageqe-109 chronyd[999]: Could not open command socket on [::1]:323 Oct 5 20:37:23 storageqe-109 chronyd[999]: Frequency -33.661 +/- 0.003 ppm read from /var/lib/chrony/drift Oct 5 20:37:23 storageqe-109 chronyd[999]: Loaded seccomp filter (level 2) Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.7791] NetworkManager (version 1.55.4-1.el10) is starting... (boot:7f1eabbe-fb6f-41f6-829f-6247606b64b7) Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.7791] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/99-nvme-nbft-no-ignore-carrier.conf Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.7820] manager[0x55df4a526e60]: monitoring kernel firmware directory '/lib/firmware'. Oct 5 20:37:23 storageqe-109 systemd[1]: Started irqbalance.service - irqbalance daemon. Oct 5 20:37:23 storageqe-109 systemd[1]: Started libstoragemgmt.service - libstoragemgmt plug-in server daemon. Oct 5 20:37:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 20:37:23 storageqe-109 systemd[1]: Starting smartd.service - Self Monitoring and Reporting Technology (SMART) Daemon... Oct 5 20:37:23 storageqe-109 systemd[1]: ssh-host-keys-migration.service - Update OpenSSH host key permissions was skipped because of an unmet condition check (ConditionPathExists=!/var/lib/.ssh-host-keys-migration). Oct 5 20:37:23 storageqe-109 systemd[1]: sshd-keygen@ecdsa.service - OpenSSH ecdsa Server Key Generation was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: sshd-keygen@ed25519.service - OpenSSH ed25519 Server Key Generation was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: sshd-keygen@rsa.service - OpenSSH rsa Server Key Generation was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: Reached target sshd-keygen.target. Oct 5 20:37:23 storageqe-109 systemd[1]: sssd.service - System Security Services Daemon was skipped because no trigger condition checks were met. Oct 5 20:37:23 storageqe-109 systemd[1]: Reached target nss-user-lookup.target - User and Group Name Lookups. Oct 5 20:37:23 storageqe-109 smartd[1008]: smartd 7.4 2023-08-01 r5530 [x86_64-linux-6.12.0-134.el10.x86_64] (local build) Oct 5 20:37:23 storageqe-109 smartd[1008]: Opened configuration file /etc/smartmontools/smartd.conf Oct 5 20:37:23 storageqe-109 smartd[1008]: Configuration file /etc/smartmontools/smartd.conf was parsed, found DEVICESCAN, scanning devices Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_00], type changed from 'megaraid,0' to 'sat+megaraid,0' Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], opened Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], HFS480G3H2X069N, S/N:ESC7N4719I0807E39, WWN:5-ace42e-375012e69, FW:DZ02, 480 GB Oct 5 20:37:23 storageqe-109 systemd[1]: Starting systemd-logind.service - User Login Management... Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], found in smartd database 7.3/5610: SK hynix SATA SSDs Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], not capable of SMART Health Status check Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], can't monitor Current_Pending_Sector count - no Attribute 197 Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_00] [SAT], no ATA CHECK POWER STATUS support, ignoring -n Directive Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_01], opened Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_01], [KIOXIA KPM7WVUG800G C40A], lu id: 0x58ce38ee22ffc92d, S/N: 2470A0EFTP1J, 800 GB Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_01], is SMART capable. Adding to "monitor" list. Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_02], opened Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_02], [KIOXIA KPM7WVUG800G C40A], lu id: 0x58ce38ee22ffc931, S/N: 2470A0EGTP1J, 800 GB Oct 5 20:37:23 storageqe-109 systemd[1]: Started chronyd.service - NTP client/server. Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_02], is SMART capable. Adding to "monitor" list. Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_03], opened Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_03], [KIOXIA KPM7WVUG800G C40A], lu id: 0x58ce38ee22ffc935, S/N: 2470A0EHTP1J, 800 GB Oct 5 20:37:23 storageqe-109 systemd[1]: Finished dracut-shutdown.service - Restore /run/initramfs on shutdown. Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_03], is SMART capable. Adding to "monitor" list. Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_04], opened Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_04], [KIOXIA KPM7WVUG800G C40A], lu id: 0x58ce38ee22ffc93d, S/N: 2470A0EKTP1J, 800 GB Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/bus/0 [megaraid_disk_04], is SMART capable. Adding to "monitor" list. Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/nvme0, opened Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/nvme0, SAMSUNG MZPLJ1T6HBJR-00007, S/N:S55JNC0T900418, FW:EPK9CB5Q, 1.60 TB Oct 5 20:37:23 storageqe-109 smartd[1008]: Device: /dev/nvme0, is SMART capable. Adding to "monitor" list. Oct 5 20:37:23 storageqe-109 smartd[1008]: Monitoring 0 ATA/SATA, 4 SCSI/SAS and 1 NVMe devices Oct 5 20:37:23 storageqe-109 systemd-logind[1011]: New seat seat0. Oct 5 20:37:23 storageqe-109 systemd-logind[1011]: Watching system buttons on /dev/input/event1 (Power Button) Oct 5 20:37:23 storageqe-109 systemd-logind[1011]: Watching system buttons on /dev/input/event0 (Sleep Button) Oct 5 20:37:23 storageqe-109 systemd[1]: Starting chrony-wait.service - Wait for chrony to synchronize system clock... Oct 5 20:37:23 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 20:37:23 storageqe-109 systemd[1]: Started smartd.service - Self Monitoring and Reporting Technology (SMART) Daemon. Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.8993] hostname: hostname: using hostnamed Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.8993] hostname: static hostname changed from (none) to "storageqe-109.rhts.eng.pek2.redhat.com" Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.8996] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto) Oct 5 20:37:23 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9027] manager[0x55df4a526e60]: rfkill: Wi-Fi hardware radio set enabled Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9028] manager[0x55df4a526e60]: rfkill: WWAN hardware radio set enabled Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9069] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9069] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9069] manager: Networking is enabled by state file Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9071] settings: Loaded settings plugin: keyfile (internal) Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9090] dhcp: init: Using DHCP client 'internal' Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9091] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1) Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9095] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9097] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9099] device (lo): Activation: starting connection 'lo' (8a6d3414-f0c6-4c4c-bcfd-a668a0804e90) Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9103] manager: (eno8303): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Oct 5 20:37:23 storageqe-109 NetworkManager[995]: [1759711043.9104] device (eno8303): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external') Oct 5 20:37:23 storageqe-109 systemd[1]: Started systemd-logind.service - User Login Management. Oct 5 20:37:23 storageqe-109 systemd[1]: Created slice user-0.slice - User Slice of UID 0. Oct 5 20:37:23 storageqe-109 systemd[1]: Listening on systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch. Oct 5 20:37:23 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.0382] manager: (eno8403): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3) Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.0384] device (eno8403): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external') Oct 5 20:37:24 storageqe-109 systemd[1]: Starting user-runtime-dir@0.service - User Runtime Directory /run/user/0... Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1671] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1672] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1673] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1674] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1676] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1719] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1720] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 5 20:37:24 storageqe-109 NetworkManager[995]: [1759711044.1722] device (lo): Activation: successful, device activated. Oct 5 20:37:24 storageqe-109 systemd[1]: Started NetworkManager.service - Network Manager. Oct 5 20:37:24 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 5 20:37:24 storageqe-109 systemd[1]: Reached target network.target - Network. Oct 5 20:37:24 storageqe-109 systemd[1]: Mounting var-lib-nfs-rpc_pipefs.mount - RPC Pipe File System... Oct 5 20:37:24 storageqe-109 systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online... Oct 5 20:37:24 storageqe-109 systemd[1]: Starting gssproxy.service - GSSAPI Proxy Daemon... Oct 5 20:37:24 storageqe-109 systemd[1]: Starting rhsmcertd.service - Enable periodic update of entitlement certificates.... Oct 5 20:37:24 storageqe-109 kernel: RPC: Registered named UNIX socket transport module. Oct 5 20:37:24 storageqe-109 kernel: RPC: Registered udp transport module. Oct 5 20:37:24 storageqe-109 kernel: RPC: Registered tcp transport module. Oct 5 20:37:24 storageqe-109 kernel: RPC: Registered tcp-with-tls transport module. Oct 5 20:37:24 storageqe-109 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Oct 5 20:37:24 storageqe-109 systemd[1]: Starting sshd.service - OpenSSH server daemon... Oct 5 20:37:24 storageqe-109 systemd[1]: Started gssproxy.service - GSSAPI Proxy Daemon. Oct 5 20:37:24 storageqe-109 systemd[1]: Mounted var-lib-nfs-rpc_pipefs.mount - RPC Pipe File System. Oct 5 20:37:24 storageqe-109 systemd[1]: Started sshd.service - OpenSSH server daemon. Oct 5 20:37:24 storageqe-109 systemd[1]: Started rhsmcertd.service - Enable periodic update of entitlement certificates.. Oct 5 20:37:24 storageqe-109 systemd[1]: Reached target rpc_pipefs.target. Oct 5 20:37:24 storageqe-109 systemd[1]: rpc-gssd.service - RPC security service for NFS client and server was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab). Oct 5 20:37:24 storageqe-109 systemd[1]: Reached target nfs-client.target - NFS client services. Oct 5 20:37:24 storageqe-109 systemd[1]: Reached target remote-fs-pre.target - Preparation for Remote File Systems. Oct 5 20:37:24 storageqe-109 systemd[1]: Reached target remote-cryptsetup.target - Remote Encrypted Volumes. Oct 5 20:37:24 storageqe-109 systemd[1]: Finished user-runtime-dir@0.service - User Runtime Directory /run/user/0. Oct 5 20:37:24 storageqe-109 systemd[1]: Starting user@0.service - User Manager for UID 0... Oct 5 20:37:24 storageqe-109 systemd-logind[1011]: New session 1 of user root. Oct 5 20:37:24 storageqe-109 systemd[1078]: Queued start job for default target default.target. Oct 5 20:37:24 storageqe-109 systemd[1078]: Created slice app.slice - User Application Slice. Oct 5 20:37:24 storageqe-109 systemd[1078]: grub-boot-success.timer - Mark boot as successful after the user session has run 2 minutes was skipped because of an unmet condition check (ConditionUser=!@system). Oct 5 20:37:24 storageqe-109 systemd[1078]: Started systemd-tmpfiles-clean.timer - Daily Cleanup of User's Temporary Directories. Oct 5 20:37:24 storageqe-109 systemd[1078]: Reached target paths.target - Paths. Oct 5 20:37:24 storageqe-109 systemd[1078]: Reached target timers.target - Timers. Oct 5 20:37:24 storageqe-109 systemd[1078]: Starting dbus.socket - D-Bus User Message Bus Socket... Oct 5 20:37:24 storageqe-109 systemd[1078]: pipewire-pulse.socket - PipeWire PulseAudio was skipped because of an unmet condition check (ConditionUser=!root). Oct 5 20:37:24 storageqe-109 systemd[1078]: pipewire.socket - PipeWire Multimedia System Sockets was skipped because of an unmet condition check (ConditionUser=!root). Oct 5 20:37:24 storageqe-109 systemd[1078]: Starting systemd-tmpfiles-setup.service - Create User Files and Directories... Oct 5 20:37:24 storageqe-109 systemd[1078]: Finished systemd-tmpfiles-setup.service - Create User Files and Directories. Oct 5 20:37:24 storageqe-109 systemd[1078]: Listening on dbus.socket - D-Bus User Message Bus Socket. Oct 5 20:37:24 storageqe-109 systemd[1078]: Reached target sockets.target - Sockets. Oct 5 20:37:24 storageqe-109 systemd[1078]: Reached target basic.target - Basic System. Oct 5 20:37:24 storageqe-109 systemd[1078]: Reached target default.target - Main User Target. Oct 5 20:37:24 storageqe-109 systemd[1078]: Startup finished in 101ms. Oct 5 20:37:24 storageqe-109 systemd[1]: Started user@0.service - User Manager for UID 0. Oct 5 20:37:27 storageqe-109 kernel: tg3 0000:07:00.0 eno8303: Link is up at 1000 Mbps, full duplex Oct 5 20:37:27 storageqe-109 kernel: tg3 0000:07:00.0 eno8303: Flow control is on for TX and on for RX Oct 5 20:37:27 storageqe-109 kernel: tg3 0000:07:00.0 eno8303: EEE is disabled Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2007] device (eno8303): carrier: link connected Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2008] device (eno8303): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full') Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2009] policy: auto-activating connection 'eno8303' (61a49902-271c-4fa4-b4d5-7eacebe644a6) Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2011] device (eno8303): Activation: starting connection 'eno8303' (61a49902-271c-4fa4-b4d5-7eacebe644a6) Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2011] device (eno8303): state change: disconnected -> prepare (reason 'none', managed-type: 'full') Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2012] manager: NetworkManager state is now CONNECTING Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2013] device (eno8303): state change: prepare -> config (reason 'none', managed-type: 'full') Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2015] device (eno8303): state change: config -> ip-config (reason 'none', managed-type: 'full') Oct 5 20:37:27 storageqe-109 NetworkManager[995]: [1759711047.2019] dhcp4 (eno8303): activation: beginning transaction (timeout in 90 seconds) Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.0242] dhcp4 (eno8303): state changed new lease, address=10.73.194.89, acd pending Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1608] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1611] policy: set 'eno8303' (eno8303) as default for IPv4 routing and DNS Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1619] device (eno8303): state change: ip-config -> ip-check (reason 'none', managed-type: 'full') Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1627] device (eno8303): state change: ip-check -> secondaries (reason 'none', managed-type: 'full') Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1628] device (eno8303): state change: secondaries -> activated (reason 'none', managed-type: 'full') Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1629] manager: NetworkManager state is now CONNECTED_SITE Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1630] device (eno8303): Activation: successful, device activated. Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1632] manager: NetworkManager state is now CONNECTED_GLOBAL Oct 5 20:37:32 storageqe-109 NetworkManager[995]: [1759711052.1633] manager: startup complete Oct 5 20:37:32 storageqe-109 systemd[1]: Finished NetworkManager-wait-online.service - Network Manager Wait Online. Oct 5 20:37:32 storageqe-109 systemd[1]: Reached target network-online.target - Network is Online. Oct 5 20:37:32 storageqe-109 systemd[1]: Started anamon.service - Anaconda Monitoring (anamon) post-boot notification program. Oct 5 20:37:32 storageqe-109 systemd[1]: insights-client-boot.service - Run Insights Client at boot was skipped because of an unmet condition check (ConditionPathExists=/etc/insights-client/.run_insights_client_next_boot). Oct 5 20:37:32 storageqe-109 systemd[1]: Starting iscsi.service - Login and scanning of iSCSI devices... Oct 5 20:37:32 storageqe-109 systemd[1]: Starting rpc-statd-notify.service - Notify NFS peers of a restart... Oct 5 20:37:32 storageqe-109 iscsiadm[1101]: iscsiadm: No records found Oct 5 20:37:32 storageqe-109 systemd[1]: Starting rsyslog.service - System Logging Service... Oct 5 20:37:32 storageqe-109 sm-notify[1102]: Version 2.8.3 starting Oct 5 20:37:32 storageqe-109 systemd[1]: Finished iscsi.service - Login and scanning of iSCSI devices. Oct 5 20:37:32 storageqe-109 rsyslogd[1103]: [origin software="rsyslogd" swVersion="8.2506.0-2.el10" x-pid="1103" x-info="https://www.rsyslog.com"] start Oct 5 20:37:32 storageqe-109 systemd[1]: Started rsyslog.service - System Logging Service. Oct 5 20:37:32 storageqe-109 rsyslogd[1103]: imjournal: journal files changed, reloading... [v8.2506.0-2.el10 try https://www.rsyslog.com/e/0 ] Oct 5 20:37:32 storageqe-109 systemd[1]: anamon.service: Deactivated successfully. Oct 5 20:37:32 storageqe-109 systemd[1]: anamon.service: Unit process 1107 (anamon) remains running after unit stopped. Oct 5 20:37:32 storageqe-109 systemd[1]: anamon.service: Unit process 1109 (journalctl) remains running after unit stopped. Oct 5 20:37:32 storageqe-109 systemd[1]: Started rpc-statd-notify.service - Notify NFS peers of a restart. Oct 5 20:37:32 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 5 20:37:32 storageqe-109 chronyd[999]: Added source 10.11.160.238 Oct 5 20:37:32 storageqe-109 chronyd[999]: Added source 10.2.32.37 Oct 5 20:37:32 storageqe-109 chronyd[999]: Added source 10.2.32.38 Oct 5 20:37:32 storageqe-109 iscsiadm[1113]: iscsiadm: No records found Oct 5 20:37:32 storageqe-109 systemd[1]: Reloaded iscsi.service - Login and scanning of iSCSI devices. Oct 5 20:37:32 storageqe-109 systemd[1]: Reached target remote-fs.target - Remote File Systems. Oct 5 20:37:32 storageqe-109 systemd[1]: Starting kdump.service - Crash recovery kernel arming... Oct 5 20:37:32 storageqe-109 systemd[1]: systemd-pcrphase.service - TPM PCR Barrier (User) was skipped because of an unmet condition check (ConditionSecurity=measured-uki). Oct 5 20:37:32 storageqe-109 systemd[1]: Starting systemd-user-sessions.service - Permit User Sessions... Oct 5 20:37:32 storageqe-109 systemd[1]: Finished systemd-user-sessions.service - Permit User Sessions. Oct 5 20:37:32 storageqe-109 kdumpctl[1156]: kdump: WARNING: Option 'default' was renamed 'failure_action' and will be removed in the future. Oct 5 20:37:32 storageqe-109 kdumpctl[1156]: kdump: Please update /etc/kdump.conf to use option 'failure_action' instead. Oct 5 20:37:32 storageqe-109 systemd[1]: Started getty@tty1.service - Getty on tty1. Oct 5 20:37:32 storageqe-109 systemd[1]: Started serial-getty@ttyS0.service - Serial Getty on ttyS0. Oct 5 20:37:32 storageqe-109 systemd[1]: Reached target getty.target - Login Prompts. Oct 5 20:37:32 storageqe-109 kdumpctl[1156]: kdump: Detected change(s) in the following file(s): /etc/fstab Oct 5 20:37:32 storageqe-109 kdumpctl[1156]: kdump: Rebuilding /boot/initramfs-6.12.0-134.el10.x86_64kdump.img Oct 5 20:37:32 storageqe-109 kernel: netfs: FS-Cache loaded Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 134 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 134 affinity is now unmanaged Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 132 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 132 affinity is now unmanaged Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 135 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 135 affinity is now unmanaged Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 133 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 133 affinity is now unmanaged Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 140 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 140 affinity is now unmanaged Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 139 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 139 affinity is now unmanaged Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 137 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 137 affinity is now unmanaged Oct 5 20:37:33 storageqe-109 irqbalance[1005]: Cannot change IRQ 138 affinity: Permission denied Oct 5 20:37:33 storageqe-109 irqbalance[1005]: IRQ 138 affinity is now unmanaged Oct 5 20:37:37 storageqe-109 chronyd[999]: Selected source 10.2.32.37 Oct 5 20:37:37 storageqe-109 kernel: Key type dns_resolver registered Oct 5 20:37:37 storageqe-109 kernel: NFS: Registering the id_resolver key type Oct 5 20:37:37 storageqe-109 kernel: Key type id_resolver registered Oct 5 20:37:37 storageqe-109 kernel: Key type id_legacy registered Oct 5 20:37:37 storageqe-109 nfsrahead[1301]: setting /tmp/mkdumprd.XhXtGW/target readahead to 128 Oct 5 20:37:37 storageqe-109 dracut[1370]: dracut-107-3.el10 Oct 5 20:37:37 storageqe-109 dracut[1373]: Executing: /usr/bin/dracut --list-modules Oct 5 20:37:37 storageqe-109 dracut[1436]: dracut-107-3.el10 Oct 5 20:37:37 storageqe-109 dracut[1439]: Executing: /usr/bin/dracut --list-modules Oct 5 20:37:37 storageqe-109 dracut[1508]: dracut-107-3.el10 Oct 5 20:37:38 storageqe-109 dracut[1511]: Executing: /usr/bin/dracut --quiet --hostonly --hostonly-cmdline --hostonly-i18n --hostonly-mode strict --hostonly-nics --aggressive-strip --mount "vmcore.usersys.redhat.com:/data/vmcore /kdumproot nfs defaults" --add squash-erofs --squash-compressor lzma --no-hostonly-default-device --add-confdir /lib/kdump/dracut.conf.d -f /boot/initramfs-6.12.0-134.el10.x86_64kdump.img 6.12.0-134.el10.x86_64 Oct 5 20:37:38 storageqe-109 dracut[1511]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'! Oct 5 20:37:38 storageqe-109 dracut[1511]: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'! Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: bash *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: fips *** Oct 5 20:37:38 storageqe-109 systemd[1]: tmp-mkdumprd.XhXtGW-target.mount: Deactivated successfully. Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: fips-crypto-policies *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-ask-password *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-battery-check *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-initrd *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-journald *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-modules-load *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-pcrphase *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-sysctl *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-sysusers *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-tmpfiles *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: systemd-udevd *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: dbus-broker *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: dbus *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: i18n *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: network-manager *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: network *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: drm *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: net-lib *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: prefixdevname *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: kernel-modules *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: kernel-modules-extra *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: kernel-network-modules *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: tpm2-tss *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: fstab-sys *** Oct 5 20:37:38 storageqe-109 dracut[1511]: *** Including module: nfs *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: rootfs-block *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: squash-erofs *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: terminfo *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: udev-rules *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: dracut-systemd *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: usrmount *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: base *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: fs-lib *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: kdumpbase *** Oct 5 20:37:39 storageqe-109 NetworkManager[995]: [1759711059.4794] audit: op="connection-add" uuid="334008b5-4cd7-4e22-9219-34c8d31703fd" name="eno8303" pid=3410 uid=0 result="success" Oct 5 20:37:39 storageqe-109 NetworkManager[995]: [1759711059.4868] audit: op="connection-update" uuid="334008b5-4cd7-4e22-9219-34c8d31703fd" name="eno8303" args="ipv4.may-fail,connection.timestamp" pid=3416 uid=0 result="success" Oct 5 20:37:39 storageqe-109 NetworkManager[995]: [1759711059.4928] audit: op="connection-update" uuid="334008b5-4cd7-4e22-9219-34c8d31703fd" name="eno8303" args="ipv6.method" pid=3423 uid=0 result="success" Oct 5 20:37:39 storageqe-109 NetworkManager[995]: [1759711059.4989] audit: op="connection-update" uuid="334008b5-4cd7-4e22-9219-34c8d31703fd" name="eno8303" args="connection.wait-device-timeout" pid=3431 uid=0 result="success" Oct 5 20:37:39 storageqe-109 NetworkManager[995]: [1759711059.5116] audit: op="connection-update" uuid="334008b5-4cd7-4e22-9219-34c8d31703fd" name="eno8303" args="802-3-ethernet.mac-address" pid=3449 uid=0 result="success" Oct 5 20:37:39 storageqe-109 NetworkManager[995]: [1759711059.5179] audit: op="connection-update" uuid="334008b5-4cd7-4e22-9219-34c8d31703fd" name="eno8303" args="connection.interface-name" pid=3456 uid=0 result="success" Oct 5 20:37:39 storageqe-109 NetworkManager[995]: [1759711059.5311] audit: op="connection-delete" uuid="334008b5-4cd7-4e22-9219-34c8d31703fd" name="eno8303" pid=3475 uid=0 result="success" Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: memstrack *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: microcode_ctl-fw_dir_override *** Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl module: mangling fw_dir Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: reset fw_dir to "/lib/firmware/updates /lib/firmware" Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel"... Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: intel: caveats check for kernel version "6.12.0-134.el10.x86_64" passed, adding "/usr/share/microcode_ctl/ucode_with_caveats/intel" to fw_dir variable Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-4f-01"... Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: configuration "intel-06-4f-01" is ignored Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: processing data directory "/usr/share/microcode_ctl/ucode_with_caveats/intel-06-8f-08"... Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: configuration "intel-06-8f-08" is ignored Oct 5 20:37:39 storageqe-109 dracut[1511]: microcode_ctl: final fw_dir: "/usr/share/microcode_ctl/ucode_with_caveats/intel /lib/firmware/updates /lib/firmware" Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: openssl *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: shell-interpreter *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: shutdown *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including module: squash-lib *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Including modules done *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Installing kernel module dependencies *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Installing kernel module dependencies done *** Oct 5 20:37:39 storageqe-109 dracut[1511]: *** Resolving executable dependencies *** Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Resolving executable dependencies done *** Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Hardlinking files *** Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Hardlinking files done *** Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Generating early-microcode cpio image *** Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Constructing GenuineIntel.bin *** Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Constructing GenuineIntel.bin *** Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Store current command line parameters *** Oct 5 20:37:40 storageqe-109 dracut[1511]: Stored kernel commandline: Oct 5 20:37:40 storageqe-109 dracut[1511]: rd.neednet Oct 5 20:37:40 storageqe-109 dracut[1511]: kdump_remote_ip=10.73.194.122 Oct 5 20:37:40 storageqe-109 dracut[1511]: *** Squashing the files inside the initramfs *** Oct 5 20:37:41 storageqe-109 systemd[1]: Finished chrony-wait.service - Wait for chrony to synchronize system clock. Oct 5 20:37:41 storageqe-109 systemd[1]: Reached target time-sync.target - System Time Synchronized. Oct 5 20:37:41 storageqe-109 systemd[1]: Started fstrim.timer - Discard unused filesystem blocks once a week. Oct 5 20:37:41 storageqe-109 systemd[1]: Started fwupd-refresh.timer - Refresh fwupd metadata regularly. Oct 5 20:37:41 storageqe-109 systemd[1]: Started logrotate.timer - Daily rotation of log files. Oct 5 20:37:41 storageqe-109 systemd[1]: Started raid-check.timer - Weekly RAID setup health check. Oct 5 20:37:41 storageqe-109 systemd[1]: Reached target timers.target - Timer Units. Oct 5 20:37:41 storageqe-109 systemd[1]: Started crond.service - Command Scheduler. Oct 5 20:37:41 storageqe-109 systemd[1]: Starting restraintd.service - The restraint harness.... Oct 5 20:37:41 storageqe-109 systemd[1]: Started restraintd.service - The restraint harness.. Oct 5 20:37:41 storageqe-109 systemd[1]: Reached target multi-user.target - Multi-User System. Oct 5 20:37:41 storageqe-109 systemd[1]: Starting stratisd.service - Stratis daemon... Oct 5 20:37:41 storageqe-109 systemd[1]: Starting systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP... Oct 5 20:37:41 storageqe-109 systemd[1]: systemd-update-utmp-runlevel.service: Deactivated successfully. Oct 5 20:37:41 storageqe-109 systemd[1]: Finished systemd-update-utmp-runlevel.service - Record Runlevel Change in UTMP. Oct 5 20:37:41 storageqe-109 stratisd[4947]: [2025-10-06T00:37:41Z INFO stratisd::stratis::run] stratis daemon version 3.8.1 started Oct 5 20:37:41 storageqe-109 stratisd[4947]: [2025-10-06T00:37:41Z INFO stratisd::stratis::run] Using StratEngine Oct 5 20:37:41 storageqe-109 stratisd[4947]: [2025-10-06T00:37:41Z INFO stratisd::engine::strat_engine::liminal::identify] Beginning initial search for Stratis block devices Oct 5 20:37:41 storageqe-109 restraintd[4944]: Unable to listen on local IPv6 address: Could not listen on address ::1, port 8081 Oct 5 20:37:41 storageqe-109 restraintd[4944]: Listening on http://localhost:8081 Oct 5 20:37:41 storageqe-109 systemd[1]: Started stratisd.service - Stratis daemon. Oct 5 20:37:41 storageqe-109 stratisd[4947]: [2025-10-06T00:37:41Z INFO stratisd::stratis::ipc_support::dbus_support] D-Bus API is available Oct 5 20:37:42 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 5 20:37:45 storageqe-109 restraintd[4944]: * Fetching recipe: http://lab-01.rhts.eng.pek2.redhat.com:8000//recipes/19660839/ Oct 5 20:37:46 storageqe-109 dracut[1511]: *** Squashing the files inside the initramfs done *** Oct 5 20:37:46 storageqe-109 dracut[1511]: *** Creating image file '/boot/initramfs-6.12.0-134.el10.x86_64kdump.img.tmp' *** Oct 5 20:37:46 storageqe-109 dracut[1511]: *** Creating initramfs image file '/boot/initramfs-6.12.0-134.el10.x86_64kdump.img.tmp' done *** Oct 5 20:37:46 storageqe-109 dracut[1511]: *** Moving image file '/boot/initramfs-6.12.0-134.el10.x86_64kdump.img.tmp' to '/boot/initramfs-6.12.0-134.el10.x86_64kdump.img' *** Oct 5 20:37:46 storageqe-109 dracut[1511]: *** Moving image file '/boot/initramfs-6.12.0-134.el10.x86_64kdump.img.tmp' to '/boot/initramfs-6.12.0-134.el10.x86_64kdump.img' done *** Oct 5 20:37:46 storageqe-109 kdumpctl[1156]: kdump: kexec: loaded kdump kernel Oct 5 20:37:46 storageqe-109 kdumpctl[1156]: kdump: Starting kdump: [OK] Oct 5 20:37:46 storageqe-109 systemd[1]: Finished kdump.service - Crash recovery kernel arming. Oct 5 20:37:46 storageqe-109 systemd[1]: Startup finished in 3.148s (kernel) + 4.429s (initrd) + 25.850s (userspace) = 33.428s. Oct 5 20:37:48 storageqe-109 restraintd[4944]: * Parsing recipe Oct 5 20:37:48 storageqe-109 restraintd[4944]: * Running recipe Oct 5 20:37:48 storageqe-109 restraintd[4944]: * Finished recipe Oct 5 20:37:53 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 20:37:58 storageqe-109 systemd-logind[1011]: New session 2 of user root. Oct 5 20:37:58 storageqe-109 systemd[1]: Started session-2.scope - Session 2 of User root. Oct 5 20:37:58 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 20:37:58 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 20:38:09 storageqe-109 systemd-logind[1011]: New session 3 of user root. Oct 5 20:38:09 storageqe-109 systemd[1]: Started session-3.scope - Session 3 of User root. Oct 5 20:38:23 storageqe-109 systemd[1]: Starting udisks2.service - Disk Manager... Oct 5 20:38:23 storageqe-109 udisksd[5174]: udisks daemon version 2.10.90 starting Oct 5 20:38:23 storageqe-109 systemd[1]: Starting polkit.service - Authorization Manager... Oct 5 20:38:23 storageqe-109 polkitd[5179]: Started polkitd version 125 Oct 5 20:38:23 storageqe-109 systemd[1]: Started polkit.service - Authorization Manager. Oct 5 20:38:23 storageqe-109 kernel: block nvme0n1: No UUID available providing old NGUID Oct 5 20:38:23 storageqe-109 systemd[1]: Started udisks2.service - Disk Manager. Oct 5 20:38:23 storageqe-109 udisksd[5174]: Acquired the name org.freedesktop.UDisks2 on the system message bus Oct 5 20:38:39 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 20:39:39 storageqe-109 kernel: sched: DL replenish lagged too much Oct 5 20:40:18 storageqe-109 systemd-logind[1011]: New session 4 of user root. Oct 5 20:40:18 storageqe-109 systemd[1]: Started session-4.scope - Session 4 of User root. Oct 5 20:40:18 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 20:40:18 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 20:40:20 storageqe-109 systemd-logind[1011]: New session 5 of user root. Oct 5 20:40:20 storageqe-109 systemd[1]: Started session-5.scope - Session 5 of User root. Oct 5 20:40:51 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 20:42:53 storageqe-109 systemd[1078]: Created slice background.slice - User Background Tasks Slice. Oct 5 20:42:53 storageqe-109 systemd[1078]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories... Oct 5 20:42:53 storageqe-109 systemd[1078]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories. Oct 5 20:50:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 20:50:54 storageqe-109 dnf[5285]: Updating Subscription Management repositories. Oct 5 20:50:54 storageqe-109 dnf[5285]: Unable to read consumer identity Oct 5 20:50:54 storageqe-109 dnf[5285]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 20:50:54 storageqe-109 dnf[5285]: Metadata cache refreshed recently. Oct 5 20:50:54 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 20:50:54 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 20:52:28 storageqe-109 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Oct 5 20:52:28 storageqe-109 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Oct 5 20:52:28 storageqe-109 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Oct 5 21:07:33 storageqe-109 udisksd[5174]: Loading module iscsi ... Oct 5 21:07:33 storageqe-109 udisksd[5174]: Loading module lsm ... Oct 5 21:07:33 storageqe-109 udisksd[5174]: Error loading module: LSM: Failed to connect plugin via URI 'hpsa://', error code: -1, error message: (null) Oct 5 21:07:33 storageqe-109 udisksd[5174]: Loading module lvm2 ... Oct 5 21:07:35 storageqe-109 systemd[1]: Reload requested from client PID 5563 ('systemctl') (unit session-4.scope)... Oct 5 21:07:35 storageqe-109 systemd[1]: Reloading... Oct 5 21:07:35 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 5 21:07:35 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 21:07:35 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 5 21:07:35 storageqe-109 systemd[1]: Reloading finished in 126 ms. Oct 5 21:07:35 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 5 21:07:35 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 5 21:07:35 storageqe-109 kernel: Loading iSCSI transport class v2.0-870. Oct 5 21:07:35 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 5 21:07:35 storageqe-109 systemd[1]: Starting iscsi-shutdown.service - Logout off all iSCSI sessions on shutdown... Oct 5 21:07:35 storageqe-109 systemd[1]: Finished iscsi-shutdown.service - Logout off all iSCSI sessions on shutdown. Oct 5 21:07:35 storageqe-109 multipathd[775]: Multipath configuration updated. Oct 5 21:07:35 storageqe-109 multipathd[775]: Reload multipathd for changes to take effect Oct 5 21:07:35 storageqe-109 systemd[1]: Reloading multipathd.service - Device-Mapper Multipath Device Controller... Oct 5 21:07:35 storageqe-109 multipathd[775]: reconfigure (operator) Oct 5 21:07:35 storageqe-109 multipathd[5662]: ok Oct 5 21:07:35 storageqe-109 multipathd[775]: reconfigure: setting up paths and maps Oct 5 21:07:35 storageqe-109 systemd[1]: Reloaded multipathd.service - Device-Mapper Multipath Device Controller. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 21:07:37 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 21:07:37 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 21:07:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### will start test_generate_backup_passphrase ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:07:47 storageqe-109 INFO: #### will start test_generate_backup_passphrase ##### Oct 5 21:07:47 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_generate_backup_passphrase #### Oct 5 21:07:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:07:57 storageqe-109 INFO: #### END test_generate_backup_passphrase #### Oct 5 21:07:58 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 21:08:08 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_luks_suspend_resume[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:14 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:14 storageqe-109 INFO: #### will start test_luks_suspend_resume[npo2_linear] ##### Oct 5 21:08:14 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:28 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 21:08:31 storageqe-109 stratisd[4947]: [2025-10-06T01:08:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:08:31 storageqe-109 stratisd[4947]: [2025-10-06T01:08:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:08:33 storageqe-109 stratisd[4947]: [2025-10-06T01:08:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:08:33 storageqe-109 stratisd[4947]: [2025-10-06T01:08:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_suspend_resume[npo2_linear] #### INFO: #### will start test_luks1_convert_to_luks2[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:43 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:43 storageqe-109 INFO: #### END test_luks_suspend_resume[npo2_linear] #### Oct 5 21:08:43 storageqe-109 INFO: #### will start test_luks1_convert_to_luks2[npo2_linear] ##### Oct 5 21:08:43 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:52 storageqe-109 stratisd[4947]: [2025-10-06T01:08:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:08:52 storageqe-109 stratisd[4947]: [2025-10-06T01:08:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks1_convert_to_luks2[npo2_linear] #### INFO: #### will start test_bitlocker_info_on_luks_device[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:08:57 storageqe-109 INFO: #### END test_luks1_convert_to_luks2[npo2_linear] #### Oct 5 21:08:57 storageqe-109 INFO: #### will start test_bitlocker_info_on_luks_device[npo2_linear] ##### Oct 5 21:08:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:15 storageqe-109 stratisd[4947]: [2025-10-06T01:09:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:09:15 storageqe-109 stratisd[4947]: [2025-10-06T01:09:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bitlocker_info_on_luks_device[npo2_linear] #### INFO: #### will start test_crypto_luks_info[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:20 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:20 storageqe-109 INFO: #### END test_bitlocker_info_on_luks_device[npo2_linear] #### Oct 5 21:09:20 storageqe-109 INFO: #### will start test_crypto_luks_info[npo2_linear] ##### Oct 5 21:09:20 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:37 storageqe-109 stratisd[4947]: [2025-10-06T01:09:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:09:37 storageqe-109 stratisd[4947]: [2025-10-06T01:09:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_info[npo2_linear] #### INFO: #### will start test_crypto_integrity_info[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:42 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:42 storageqe-109 INFO: #### END test_crypto_luks_info[npo2_linear] #### Oct 5 21:09:42 storageqe-109 INFO: #### will start test_crypto_integrity_info[npo2_linear] ##### Oct 5 21:09:42 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:47 storageqe-109 kernel: async_tx: api initialized (async) Oct 5 21:09:47 storageqe-109 kernel: xor: automatically using best checksumming function avx INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_integrity_info[npo2_linear] #### INFO: #### will start test_crypto_bitlk_info[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:55 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:09:55 storageqe-109 INFO: #### END test_crypto_integrity_info[npo2_linear] #### Oct 5 21:09:55 storageqe-109 INFO: #### will start test_crypto_bitlk_info[npo2_linear] ##### Oct 5 21:09:55 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:13 storageqe-109 stratisd[4947]: [2025-10-06T01:10:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:10:13 storageqe-109 stratisd[4947]: [2025-10-06T01:10:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_bitlk_info[npo2_linear] #### INFO: #### will start test_crypto_luks_token_info[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:18 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:18 storageqe-109 INFO: #### END test_crypto_bitlk_info[npo2_linear] #### Oct 5 21:10:18 storageqe-109 INFO: #### will start test_crypto_luks_token_info[npo2_linear] ##### Oct 5 21:10:18 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:30 storageqe-109 udisksd[5174]: Error getting '/dev/dm-3' metadata_size: Unknown or unsupported LUKS version (g-bd-crypto-error-quark, 0) INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_token_info[npo2_linear] #### INFO: #### will start test_crypto_luks_open_keyring[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:35 storageqe-109 INFO: #### END test_crypto_luks_token_info[npo2_linear] #### Oct 5 21:10:35 storageqe-109 INFO: #### will start test_crypto_luks_open_keyring[npo2_linear] ##### Oct 5 21:10:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:53 storageqe-109 stratisd[4947]: [2025-10-06T01:10:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:10:53 storageqe-109 stratisd[4947]: [2025-10-06T01:10:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_open_keyring[npo2_linear] #### INFO: #### will start test_crypto_tc_open_with_invalid_data[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:10:58 storageqe-109 INFO: #### END test_crypto_luks_open_keyring[npo2_linear] #### Oct 5 21:10:58 storageqe-109 INFO: #### will start test_crypto_tc_open_with_invalid_data[npo2_linear] ##### Oct 5 21:10:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_tc_open_with_invalid_data[npo2_linear] #### INFO: #### will start test_crypto_tc_with_different_parameters[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:08 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:08 storageqe-109 INFO: #### END test_crypto_tc_open_with_invalid_data[npo2_linear] #### Oct 5 21:11:08 storageqe-109 INFO: #### will start test_crypto_tc_with_different_parameters[npo2_linear] ##### Oct 5 21:11:08 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_tc_with_different_parameters[npo2_linear] #### INFO: #### will start test_crypto_tc_edge_cases[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:18 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:18 storageqe-109 INFO: #### END test_crypto_tc_with_different_parameters[npo2_linear] #### Oct 5 21:11:18 storageqe-109 INFO: #### will start test_crypto_tc_edge_cases[npo2_linear] ##### Oct 5 21:11:18 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_tc_edge_cases[npo2_linear] #### INFO: #### will start test_crypto_module_initialization ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:28 storageqe-109 INFO: #### END test_crypto_tc_edge_cases[npo2_linear] #### Oct 5 21:11:28 storageqe-109 INFO: #### will start test_crypto_module_initialization ##### Oct 5 21:11:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_module_initialization #### INFO: #### will start test_crypto_keyring_functions ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:38 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:38 storageqe-109 INFO: #### END test_crypto_module_initialization #### Oct 5 21:11:38 storageqe-109 INFO: #### will start test_crypto_keyring_functions ##### Oct 5 21:11:38 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_keyring_functions #### INFO: #### will start test_crypto_escrow_packet_info ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:48 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:48 storageqe-109 INFO: #### END test_crypto_keyring_functions #### Oct 5 21:11:48 storageqe-109 INFO: #### will start test_crypto_escrow_packet_info ##### Oct 5 21:11:48 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_escrow_packet_info #### INFO: #### will start test_crypto_tc_functions_availability ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:11:58 storageqe-109 INFO: #### END test_crypto_escrow_packet_info #### Oct 5 21:11:58 storageqe-109 INFO: #### will start test_crypto_tc_functions_availability ##### Oct 5 21:11:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_tc_functions_availability #### INFO: #### will start test_crypto_tc_close_nonexistent ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:12:09 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:12:09 storageqe-109 INFO: #### END test_crypto_tc_functions_availability #### Oct 5 21:12:09 storageqe-109 INFO: #### will start test_crypto_tc_close_nonexistent ##### Oct 5 21:12:09 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_tc_close_nonexistent #### INFO: #### will start test_crypto_tc_technology_availability ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:12:19 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:12:19 storageqe-109 INFO: #### END test_crypto_tc_close_nonexistent #### Oct 5 21:12:19 storageqe-109 INFO: #### will start test_crypto_tc_technology_availability ##### Oct 5 21:12:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_tc_technology_availability #### Oct 5 21:12:29 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:12:29 storageqe-109 INFO: #### END test_crypto_tc_technology_availability #### Oct 5 21:12:30 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### will start test_dm_is_available ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:12:30 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:12:30 storageqe-109 INFO: #### will start test_dm_is_available ##### Oct 5 21:12:30 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_dm_is_available #### INFO: #### will start test_dm_create_linear_mapping ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:12:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:12:41 storageqe-109 INFO: #### END test_dm_is_available #### Oct 5 21:12:41 storageqe-109 INFO: #### will start test_dm_create_linear_mapping ##### Oct 5 21:12:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_dm_create_linear_mapping #### INFO: #### will start test_dm_create_and_remove ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:12:51 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:12:51 storageqe-109 INFO: #### END test_dm_create_linear_mapping #### Oct 5 21:12:51 storageqe-109 INFO: #### will start test_dm_create_and_remove ##### Oct 5 21:12:51 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_dm_create_and_remove #### INFO: #### will start test_dm_map_exists ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:13:01 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:13:01 storageqe-109 INFO: #### END test_dm_create_and_remove #### Oct 5 21:13:01 storageqe-109 INFO: #### will start test_dm_map_exists ##### Oct 5 21:13:01 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_dm_map_exists #### INFO: #### will start test_dm_create_with_uuid ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:13:11 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:13:11 storageqe-109 INFO: #### END test_dm_map_exists #### Oct 5 21:13:11 storageqe-109 INFO: #### will start test_dm_create_with_uuid ##### Oct 5 21:13:11 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_create_with_uuid #### INFO: #### will start test_dm_name_from_node ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:13:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:13:21 storageqe-109 INFO: #### END test_dm_create_with_uuid #### Oct 5 21:13:21 storageqe-109 INFO: #### will start test_dm_name_from_node ##### Oct 5 21:13:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_dm_name_from_node #### INFO: #### will start test_dm_node_from_name ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:13:31 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:13:31 storageqe-109 INFO: #### END test_dm_name_from_node #### Oct 5 21:13:31 storageqe-109 INFO: #### will start test_dm_node_from_name ##### Oct 5 21:13:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_dm_node_from_name #### INFO: #### will start test_dm_get_subsystem_from_name ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:13:41 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:13:41 storageqe-109 INFO: #### END test_dm_node_from_name #### Oct 5 21:13:41 storageqe-109 INFO: #### will start test_dm_get_subsystem_from_name ##### Oct 5 21:13:41 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_dm_get_subsystem_from_name #### INFO: #### will start test_dm_multiple_linear_mappings ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:13:51 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:13:51 storageqe-109 INFO: #### END test_dm_get_subsystem_from_name #### Oct 5 21:13:51 storageqe-109 INFO: #### will start test_dm_multiple_linear_mappings ##### Oct 5 21:13:51 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_multiple_linear_mappings #### INFO: #### will start test_dm_device_io_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:14:01 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:14:01 storageqe-109 INFO: #### END test_dm_multiple_linear_mappings #### Oct 5 21:14:01 storageqe-109 INFO: #### will start test_dm_device_io_operations ##### Oct 5 21:14:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_dm_device_io_operations #### INFO: #### will start test_dm_device_write_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:14:12 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:14:12 storageqe-109 INFO: #### END test_dm_device_io_operations #### Oct 5 21:14:12 storageqe-109 INFO: #### will start test_dm_device_write_operations ##### Oct 5 21:14:12 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_dm_device_write_operations #### INFO: #### will start test_dm_invalid_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:14:22 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:14:22 storageqe-109 INFO: #### END test_dm_device_write_operations #### Oct 5 21:14:22 storageqe-109 INFO: #### will start test_dm_invalid_operations ##### Oct 5 21:14:22 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_dm_invalid_operations #### INFO: #### will start test_dm_name_validation ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:14:32 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:14:32 storageqe-109 INFO: #### END test_dm_invalid_operations #### Oct 5 21:14:32 storageqe-109 INFO: #### will start test_dm_name_validation ##### Oct 5 21:14:32 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_dm_name_validation #### INFO: #### will start test_dm_device_size_verification ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:14:42 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:14:42 storageqe-109 INFO: #### END test_dm_name_validation #### Oct 5 21:14:42 storageqe-109 INFO: #### will start test_dm_device_size_verification ##### Oct 5 21:14:42 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_dm_device_size_verification #### INFO: #### will start test_dm_device_concurrent_access ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:14:52 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:14:52 storageqe-109 INFO: #### END test_dm_device_size_verification #### Oct 5 21:14:52 storageqe-109 INFO: #### will start test_dm_device_concurrent_access ##### Oct 5 21:14:52 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_device_concurrent_access #### INFO: #### will start test_dm_device_persistence ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:15:02 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:15:02 storageqe-109 INFO: #### END test_dm_device_concurrent_access #### Oct 5 21:15:02 storageqe-109 INFO: #### will start test_dm_device_persistence ##### Oct 5 21:15:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_dm_device_persistence #### INFO: #### will start test_dm_device_removal_cleanup ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:15:12 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:15:12 storageqe-109 INFO: #### END test_dm_device_persistence #### Oct 5 21:15:12 storageqe-109 INFO: #### will start test_dm_device_removal_cleanup ##### Oct 5 21:15:12 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_dm_device_removal_cleanup #### INFO: #### will start test_fs_is_available ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:15:22 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:15:22 storageqe-109 INFO: #### END test_dm_device_removal_cleanup #### Oct 5 21:15:22 storageqe-109 INFO: #### will start test_fs_is_available ##### Oct 5 21:15:22 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_fs_is_available #### INFO: #### will start test_fs_technology_availability ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:15:32 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:15:32 storageqe-109 INFO: #### END test_fs_is_available #### Oct 5 21:15:32 storageqe-109 INFO: #### will start test_fs_technology_availability ##### Oct 5 21:15:32 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_fs_technology_availability #### INFO: #### will start test_fs_ext4_basic_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:15:42 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:15:43 storageqe-109 INFO: #### END test_fs_technology_availability #### Oct 5 21:15:43 storageqe-109 INFO: #### will start test_fs_ext4_basic_operations ##### Oct 5 21:15:43 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_fs_ext4_basic_operations #### INFO: #### will start test_fs_xfs_basic_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:15:53 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:15:53 storageqe-109 INFO: #### END test_fs_ext4_basic_operations #### Oct 5 21:15:53 storageqe-109 INFO: #### will start test_fs_xfs_basic_operations ##### Oct 5 21:15:53 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_fs_xfs_basic_operations #### INFO: #### will start test_fs_vfat_basic_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:16:03 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:16:03 storageqe-109 INFO: #### END test_fs_xfs_basic_operations #### Oct 5 21:16:03 storageqe-109 INFO: #### will start test_fs_vfat_basic_operations ##### Oct 5 21:16:03 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:16:09 storageqe-109 kernel: sde: sde1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fs_vfat_basic_operations #### INFO: #### will start test_fs_mount_unmount_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:16:14 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:16:14 storageqe-109 INFO: #### END test_fs_vfat_basic_operations #### Oct 5 21:16:14 storageqe-109 INFO: #### will start test_fs_mount_unmount_operations ##### Oct 5 21:16:14 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:16:20 storageqe-109 kernel: EXT4-fs (nvme0n1): mounted filesystem edff8306-c8bf-4fdb-914b-6b7d9e03ecc9 r/w with ordered data mode. Quota mode: none. Oct 5 21:16:20 storageqe-109 systemd[1]: tmp-test_fs_mount_pqmucg9t.mount: Deactivated successfully. Oct 5 21:16:20 storageqe-109 kernel: EXT4-fs (nvme0n1): unmounting filesystem edff8306-c8bf-4fdb-914b-6b7d9e03ecc9. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fs_mount_unmount_operations #### INFO: #### will start test_fs_label_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:16:25 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:16:25 storageqe-109 INFO: #### END test_fs_mount_unmount_operations #### Oct 5 21:16:25 storageqe-109 INFO: #### will start test_fs_label_operations ##### Oct 5 21:16:25 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_fs_label_operations #### INFO: #### will start test_fs_uuid_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:16:35 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:16:35 storageqe-109 INFO: #### END test_fs_label_operations #### Oct 5 21:16:35 storageqe-109 INFO: #### will start test_fs_uuid_operations ##### Oct 5 21:16:35 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_fs_uuid_operations #### INFO: #### will start test_fs_resize_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:16:46 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:16:46 storageqe-109 INFO: #### END test_fs_uuid_operations #### Oct 5 21:16:46 storageqe-109 INFO: #### will start test_fs_resize_operations ##### Oct 5 21:16:46 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_fs_resize_operations #### INFO: #### will start test_fs_check_repair_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:16:59 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:16:59 storageqe-109 INFO: #### END test_fs_resize_operations #### Oct 5 21:16:59 storageqe-109 INFO: #### will start test_fs_check_repair_operations ##### Oct 5 21:16:59 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fs_check_repair_operations #### INFO: #### will start test_fs_free_space_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:17:10 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:17:10 storageqe-109 INFO: #### END test_fs_check_repair_operations #### Oct 5 21:17:10 storageqe-109 INFO: #### will start test_fs_free_space_operations ##### Oct 5 21:17:10 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:17:16 storageqe-109 kernel: EXT4-fs (nvme0n1): mounted filesystem ac821a66-0ba2-4891-b226-46b073e85d2d r/w with ordered data mode. Quota mode: none. Oct 5 21:17:16 storageqe-109 systemd[1]: tmp-test_fs_free_20tal0m6.mount: Deactivated successfully. Oct 5 21:17:16 storageqe-109 kernel: EXT4-fs (nvme0n1): unmounting filesystem ac821a66-0ba2-4891-b226-46b073e85d2d. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fs_free_space_operations #### INFO: #### will start test_fs_freeze_unfreeze_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:17:21 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:17:21 storageqe-109 INFO: #### END test_fs_free_space_operations #### Oct 5 21:17:21 storageqe-109 INFO: #### will start test_fs_freeze_unfreeze_operations ##### Oct 5 21:17:21 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:17:26 storageqe-109 kernel: EXT4-fs (sdb): mounted filesystem 1845e44d-9b63-40a7-b3f2-d6c5fe85457d r/w with ordered data mode. Quota mode: none. Oct 5 21:17:26 storageqe-109 systemd[1]: tmp-test_fs_freeze_qnh0gv7t.mount: Deactivated successfully. Oct 5 21:17:26 storageqe-109 kernel: EXT4-fs (sdb): unmounting filesystem 1845e44d-9b63-40a7-b3f2-d6c5fe85457d. INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_fs_freeze_unfreeze_operations #### INFO: #### will start test_fs_wipe_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:17:31 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:17:31 storageqe-109 INFO: #### END test_fs_freeze_unfreeze_operations #### Oct 5 21:17:31 storageqe-109 INFO: #### will start test_fs_wipe_operations ##### Oct 5 21:17:31 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_fs_wipe_operations #### INFO: #### will start test_fs_multiple_filesystem_types ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:17:42 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:17:42 storageqe-109 INFO: #### END test_fs_wipe_operations #### Oct 5 21:17:42 storageqe-109 INFO: #### will start test_fs_multiple_filesystem_types ##### Oct 5 21:17:42 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_fs_multiple_filesystem_types #### INFO: #### will start test_fs_label_validation ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:18:11 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:18:11 storageqe-109 INFO: #### END test_fs_multiple_filesystem_types #### Oct 5 21:18:11 storageqe-109 INFO: #### will start test_fs_label_validation ##### Oct 5 21:18:11 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fs_label_validation #### INFO: #### will start test_fs_uuid_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:18:22 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:18:22 storageqe-109 INFO: #### END test_fs_label_validation #### Oct 5 21:18:22 storageqe-109 INFO: #### will start test_fs_uuid_validation ##### Oct 5 21:18:22 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fs_uuid_validation #### INFO: #### will start test_fs_mount_options ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:18:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:18:33 storageqe-109 INFO: #### END test_fs_uuid_validation #### Oct 5 21:18:33 storageqe-109 INFO: #### will start test_fs_mount_options ##### Oct 5 21:18:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): mounted filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995 r/w with ordered data mode. Quota mode: none. Oct 5 21:18:38 storageqe-109 systemd[1]: tmp-test_fs_mount_defaults_x8gmegvw.mount: Deactivated successfully. Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): unmounting filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995. Oct 5 21:18:38 storageqe-109 systemd[1]: tmp-test_fs_mount_ro_17r28mja.mount: Deactivated successfully. Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): mounted filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995 ro with ordered data mode. Quota mode: none. Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): unmounting filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995. Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): mounted filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995 r/w with ordered data mode. Quota mode: none. Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): unmounting filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995. Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): mounted filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995 r/w with ordered data mode. Quota mode: none. Oct 5 21:18:38 storageqe-109 kernel: EXT4-fs (sdb): unmounting filesystem 3378538f-158b-4cbb-b9f7-dae32f8d1995. Oct 5 21:18:39 storageqe-109 systemd[1]: tmp-test_fs_mount_noatime_o_h_yb0q.mount: Deactivated successfully. INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_fs_mount_options #### INFO: #### will start test_fs_error_handling ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:18:44 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:18:44 storageqe-109 INFO: #### END test_fs_mount_options #### Oct 5 21:18:44 storageqe-109 INFO: #### will start test_fs_error_handling ##### Oct 5 21:18:44 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_fs_error_handling #### INFO: #### will start test_fs_concurrent_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:18:54 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:18:54 storageqe-109 INFO: #### END test_fs_error_handling #### Oct 5 21:18:54 storageqe-109 INFO: #### will start test_fs_concurrent_operations ##### Oct 5 21:18:54 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:18:59 storageqe-109 kernel: EXT4-fs (sdd): mounted filesystem 5a913633-1268-4ff0-89e4-bebad83ab6ca r/w with ordered data mode. Quota mode: none. Oct 5 21:18:59 storageqe-109 kernel: XFS (sde): Mounting V5 Filesystem 8c8ad5b6-3633-4cbc-8e98-81a38997f872 Oct 5 21:18:59 storageqe-109 kernel: XFS (sde): Ending clean mount Oct 5 21:18:59 storageqe-109 systemd[1]: tmp-test_fs_concurrent_0_i7yzp7qe.mount: Deactivated successfully. Oct 5 21:18:59 storageqe-109 kernel: EXT4-fs (sdd): unmounting filesystem 5a913633-1268-4ff0-89e4-bebad83ab6ca. Oct 5 21:18:59 storageqe-109 systemd[1]: tmp-test_fs_concurrent_1_wco_xagj.mount: Deactivated successfully. Oct 5 21:18:59 storageqe-109 kernel: XFS (sde): Unmounting Filesystem 8c8ad5b6-3633-4cbc-8e98-81a38997f872 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fs_concurrent_operations #### INFO: #### will start test_fs_large_filesystem_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:19:04 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:19:04 storageqe-109 INFO: #### END test_fs_concurrent_operations #### Oct 5 21:19:04 storageqe-109 INFO: #### will start test_fs_large_filesystem_operations ##### Oct 5 21:19:04 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:19:10 storageqe-109 kernel: EXT4-fs (nvme0n1): mounted filesystem 0b90466c-8bf3-4364-8ccb-5ea9b2d41efd r/w with ordered data mode. Quota mode: none. Oct 5 21:19:11 storageqe-109 systemd[1]: tmp-test_fs_large_myc_s563.mount: Deactivated successfully. Oct 5 21:19:11 storageqe-109 kernel: EXT4-fs (nvme0n1): unmounting filesystem 0b90466c-8bf3-4364-8ccb-5ea9b2d41efd. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fs_large_filesystem_operations #### INFO: #### will start test_fs_capability_checks ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:19:16 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:19:16 storageqe-109 INFO: #### END test_fs_large_filesystem_operations #### Oct 5 21:19:16 storageqe-109 INFO: #### will start test_fs_capability_checks ##### Oct 5 21:19:16 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_fs_capability_checks #### INFO: #### will start test_fs_performance_basic ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:19:26 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:19:26 storageqe-109 INFO: #### END test_fs_capability_checks #### Oct 5 21:19:26 storageqe-109 INFO: #### will start test_fs_performance_basic ##### Oct 5 21:19:26 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:19:31 storageqe-109 kernel: EXT4-fs (sdc): mounted filesystem ccbeb9fb-27f1-4d9f-ac73-029059923408 r/w with ordered data mode. Quota mode: none. Oct 5 21:19:31 storageqe-109 systemd[1]: tmp-test_fs_perf_932ogwvw.mount: Deactivated successfully. Oct 5 21:19:31 storageqe-109 kernel: EXT4-fs (sdc): unmounting filesystem ccbeb9fb-27f1-4d9f-ac73-029059923408. INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_fs_performance_basic #### INFO: #### will start test_fs_clean_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:19:36 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:19:36 storageqe-109 INFO: #### END test_fs_performance_basic #### Oct 5 21:19:36 storageqe-109 INFO: #### will start test_fs_clean_operations ##### Oct 5 21:19:36 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_fs_clean_operations #### INFO: #### will start test_fs_generic_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:19:46 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:19:46 storageqe-109 INFO: #### END test_fs_clean_operations #### Oct 5 21:19:46 storageqe-109 INFO: #### will start test_fs_generic_operations ##### Oct 5 21:19:46 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fs_generic_operations #### INFO: #### will start test_fuzz_loop_device_paths ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:19:57 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:19:57 storageqe-109 INFO: #### END test_fs_generic_operations #### Oct 5 21:19:57 storageqe-109 INFO: #### will start test_fuzz_loop_device_paths ##### Oct 5 21:19:57 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_loop_device_paths #### INFO: #### will start test_fuzz_crypto_passphrases ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:07 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:07 storageqe-109 INFO: #### END test_fuzz_loop_device_paths #### Oct 5 21:20:07 storageqe-109 INFO: #### will start test_fuzz_crypto_passphrases ##### Oct 5 21:20:07 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:12 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 21:20:12 storageqe-109 systemd[1]: Starting fwupd.service - Firmware update daemon... Oct 5 21:20:12 storageqe-109 systemd[1]: Starting upower.service - Daemon for power management... Oct 5 21:20:12 storageqe-109 systemd-logind[1011]: /boot/loader/entries/7f339974107e491c9e42a18c8fe3fb7d-6.12.0-134.el10.x86_64.conf:6: Unknown line 'grub_users', ignoring. Oct 5 21:20:12 storageqe-109 systemd-logind[1011]: /boot/loader/entries/7f339974107e491c9e42a18c8fe3fb7d-6.12.0-134.el10.x86_64.conf:7: Unknown line 'grub_arg', ignoring. Oct 5 21:20:12 storageqe-109 systemd-logind[1011]: /boot/loader/entries/7f339974107e491c9e42a18c8fe3fb7d-6.12.0-134.el10.x86_64.conf:8: Unknown line 'grub_class', ignoring. Oct 5 21:20:12 storageqe-109 systemd-logind[1011]: /boot/loader/entries/7f339974107e491c9e42a18c8fe3fb7d-0-rescue.conf:6: Unknown line 'grub_users', ignoring. Oct 5 21:20:12 storageqe-109 systemd-logind[1011]: /boot/loader/entries/7f339974107e491c9e42a18c8fe3fb7d-0-rescue.conf:7: Unknown line 'grub_arg', ignoring. Oct 5 21:20:12 storageqe-109 systemd-logind[1011]: /boot/loader/entries/7f339974107e491c9e42a18c8fe3fb7d-0-rescue.conf:8: Unknown line 'grub_class', ignoring. Oct 5 21:20:12 storageqe-109 systemd[1]: Started upower.service - Daemon for power management. Oct 5 21:20:12 storageqe-109 fwupd[15484]: 01:20:12.936 FuMain fwupd 1.9.31 ready for requests (locale en_US.UTF-8) Oct 5 21:20:12 storageqe-109 systemd[1]: Started fwupd.service - Firmware update daemon. Oct 5 21:20:12 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 21:20:12 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_crypto_passphrases #### INFO: #### will start test_fuzz_filesystem_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:17 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:17 storageqe-109 INFO: #### END test_fuzz_crypto_passphrases #### Oct 5 21:20:17 storageqe-109 INFO: #### will start test_fuzz_filesystem_operations ##### Oct 5 21:20:17 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_filesystem_operations #### INFO: #### will start test_fuzz_partition_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:27 storageqe-109 INFO: #### END test_fuzz_filesystem_operations #### Oct 5 21:20:27 storageqe-109 INFO: #### will start test_fuzz_partition_operations ##### Oct 5 21:20:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_partition_operations #### INFO: #### will start test_fuzz_lvm_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:37 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:37 storageqe-109 INFO: #### END test_fuzz_partition_operations #### Oct 5 21:20:37 storageqe-109 INFO: #### will start test_fuzz_lvm_operations ##### Oct 5 21:20:37 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: the malicious_name for vg volumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroup INFO: the malicious_name for lv volumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroupvolumegroup INFO: the malicious_name for vg vg INFO: the malicious_name for lv vg INFO: the malicious_name for vg -vg INFO: the malicious_name for lv -vg INFO: the malicious_name for vg vg- INFO: the malicious_name for lv vg- INFO: the malicious_name for vg .vg INFO: the malicious_name for lv .vg INFO: the malicious_name for vg vg. INFO: the malicious_name for lv vg. INFO: the malicious_name for vg 卷组 INFO: the malicious_name for lv 卷组 INFO: the malicious_name for vg ボリューム INFO: the malicious_name for lv ボリューム Oct 5 21:20:43 storageqe-109 systemd[1]: Starting lvm2-lvmdbusd.service - LVM2 D-Bus service... Oct 5 21:20:43 storageqe-109 systemd[1]: Started lvm2-lvmdbusd.service - LVM2 D-Bus service. Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg vg Oct 5 21:20:43 storageqe-109 journal: #015#011 Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv vg Oct 5 21:20:43 storageqe-109 journal: #015#011 Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg -vg Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv -vg Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg vg- Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv vg- Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg .vg Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv .vg INFO: the malicious_name for vg том Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg vg. Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv vg. Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg 卷组 Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv 卷组 Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg ボリューム Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv ボリューム Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg том INFO: the malicious_name for lv том INFO: the malicious_name for vg %s_%s_%s INFO: the malicious_name for lv %s_%s_%s INFO: the malicious_name for vg %n_%n_%n INFO: the malicious_name for lv %n_%n_%n INFO: the malicious_name for vg INFO: the malicious_name for lv INFO: the malicious_name for vg INFO: the malicious_name for lv INFO: the malicious_name for vg INFO: the malicious_name for lv Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv том Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg %s_%s_%s Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv %s_%s_%s Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg %n_%n_%n Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv %n_%n_%n Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for vg #011 Oct 5 21:20:43 storageqe-109 journal: #015 Oct 5 21:20:43 storageqe-109 INFO: the malicious_name for lv #011 Oct 5 21:20:43 storageqe-109 journal: #015 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_lvm_operations #### INFO: #### will start test_fuzz_raid_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:48 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:48 storageqe-109 INFO: #### END test_fuzz_lvm_operations #### Oct 5 21:20:48 storageqe-109 INFO: #### will start test_fuzz_raid_operations ##### Oct 5 21:20:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:58 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_raid_operations #### INFO: #### will start test_fuzz_memory_exhaustion ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:20:58 storageqe-109 INFO: #### END test_fuzz_raid_operations #### Oct 5 21:20:58 storageqe-109 INFO: #### will start test_fuzz_memory_exhaustion ##### Oct 5 21:20:58 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:03 storageqe-109 kernel: loop0: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop1: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop2: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop3: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop4: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop5: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop6: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop7: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop8: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop9: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop10: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop11: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop12: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop13: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop14: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop15: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop16: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop17: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop18: detected capacity change from 0 to 2048 Oct 5 21:21:03 storageqe-109 kernel: loop19: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop20: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop21: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop22: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop23: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop24: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop25: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop26: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop27: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop28: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop29: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop30: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop31: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop32: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop33: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop34: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop35: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop36: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop37: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop38: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop39: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop40: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop41: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop42: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop43: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop44: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop45: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop46: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop47: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop48: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop49: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop50: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop51: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop52: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop53: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop54: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop55: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop56: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop57: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop58: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop59: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop60: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop61: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop62: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop63: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop64: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop65: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop66: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop67: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop68: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop69: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop70: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop71: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop72: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop73: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop74: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop75: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop76: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop77: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop78: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop79: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop80: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop81: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop82: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop83: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop84: detected capacity change from 0 to 2048 Oct 5 21:21:04 storageqe-109 kernel: loop85: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop86: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop87: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop88: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop89: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop90: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop91: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop92: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop93: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop94: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop95: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop96: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop97: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop98: detected capacity change from 0 to 2048 Oct 5 21:21:05 storageqe-109 kernel: loop99: detected capacity change from 0 to 2048 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_memory_exhaustion #### INFO: #### will start test_fuzz_concurrent_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:10 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:10 storageqe-109 INFO: #### END test_fuzz_memory_exhaustion #### Oct 5 21:21:10 storageqe-109 INFO: #### will start test_fuzz_concurrent_operations ##### Oct 5 21:21:10 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:15 storageqe-109 kernel: loop100: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop101: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop102: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop103: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop104: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop105: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop106: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop107: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop108: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop109: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop110: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop111: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop112: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop113: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop114: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop115: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop116: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop117: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop118: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop119: detected capacity change from 0 to 20480 Oct 5 21:21:15 storageqe-109 kernel: loop120: detected capacity change from 0 to 20480 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_concurrent_operations #### INFO: #### will start test_fuzz_unicode_edge_cases ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:21 storageqe-109 INFO: #### END test_fuzz_concurrent_operations #### Oct 5 21:21:21 storageqe-109 INFO: #### will start test_fuzz_unicode_edge_cases ##### Oct 5 21:21:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_unicode_edge_cases #### INFO: #### will start test_fuzz_buffer_boundaries ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:31 storageqe-109 INFO: #### END test_fuzz_unicode_edge_cases #### Oct 5 21:21:31 storageqe-109 INFO: #### will start test_fuzz_buffer_boundaries ##### Oct 5 21:21:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:36 storageqe-109 kernel: loop121: detected capacity change from 0 to 1 Oct 5 21:21:36 storageqe-109 kernel: loop122: detected capacity change from 0 to 2 Oct 5 21:21:36 storageqe-109 kernel: loop123: detected capacity change from 0 to 8 Oct 5 21:21:36 storageqe-109 kernel: loop124: detected capacity change from 0 to 16 Oct 5 21:21:36 storageqe-109 kernel: loop125: detected capacity change from 0 to 128 Oct 5 21:21:36 storageqe-109 kernel: loop127: detected capacity change from 0 to 1 Oct 5 21:21:36 storageqe-109 kernel: loop128: detected capacity change from 0 to 7 Oct 5 21:21:36 storageqe-109 kernel: loop129: detected capacity change from 0 to 8 Oct 5 21:21:36 storageqe-109 kernel: loop130: detected capacity change from 0 to 127 Oct 5 21:21:36 storageqe-109 kernel: loop131: detected capacity change from 0 to 128 Oct 5 21:21:36 storageqe-109 kernel: loop132: detected capacity change from 0 to 2047 Oct 5 21:21:36 storageqe-109 kernel: loop133: detected capacity change from 0 to 2048 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_buffer_boundaries #### INFO: #### will start test_fuzz_integer_boundaries_32bit ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:41 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:41 storageqe-109 INFO: #### END test_fuzz_buffer_boundaries #### Oct 5 21:21:41 storageqe-109 INFO: #### will start test_fuzz_integer_boundaries_32bit ##### Oct 5 21:21:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_integer_boundaries_32bit #### INFO: #### will start test_fuzz_buffer_size_boundaries ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:51 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:51 storageqe-109 INFO: #### END test_fuzz_integer_boundaries_32bit #### Oct 5 21:21:51 storageqe-109 INFO: #### will start test_fuzz_buffer_size_boundaries ##### Oct 5 21:21:51 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:21:56 storageqe-109 kernel: loop134: detected capacity change from 0 to 1 Oct 5 21:21:56 storageqe-109 kernel: loop135: detected capacity change from 0 to 2 Oct 5 21:21:56 storageqe-109 kernel: loop136: detected capacity change from 0 to 4 Oct 5 21:21:56 storageqe-109 kernel: loop137: detected capacity change from 0 to 8 Oct 5 21:21:56 storageqe-109 kernel: loop138: detected capacity change from 0 to 16 Oct 5 21:21:56 storageqe-109 kernel: loop139: detected capacity change from 0 to 32 Oct 5 21:21:56 storageqe-109 kernel: loop140: detected capacity change from 0 to 128 Oct 5 21:21:56 storageqe-109 kernel: loop141: detected capacity change from 0 to 256 Oct 5 21:21:56 storageqe-109 kernel: loop142: detected capacity change from 0 to 2048 Oct 5 21:21:56 storageqe-109 kernel: loop143: detected capacity change from 0 to 1 Oct 5 21:21:56 storageqe-109 kernel: loop144: detected capacity change from 0 to 1 Oct 5 21:21:56 storageqe-109 kernel: loop145: detected capacity change from 0 to 2 Oct 5 21:21:56 storageqe-109 kernel: loop146: detected capacity change from 0 to 7 Oct 5 21:21:56 storageqe-109 kernel: loop147: detected capacity change from 0 to 8 Oct 5 21:21:56 storageqe-109 kernel: loop148: detected capacity change from 0 to 127 Oct 5 21:21:56 storageqe-109 kernel: loop149: detected capacity change from 0 to 128 Oct 5 21:21:56 storageqe-109 kernel: loop150: detected capacity change from 0 to 2047 Oct 5 21:21:56 storageqe-109 kernel: loop151: detected capacity change from 0 to 2048 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_buffer_size_boundaries #### INFO: #### will start test_fuzz_string_length_boundaries ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:01 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:01 storageqe-109 INFO: #### END test_fuzz_buffer_size_boundaries #### Oct 5 21:22:01 storageqe-109 INFO: #### will start test_fuzz_string_length_boundaries ##### Oct 5 21:22:01 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_string_length_boundaries #### INFO: #### will start test_fuzz_alignment_boundaries ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:11 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:12 storageqe-109 INFO: #### END test_fuzz_string_length_boundaries #### Oct 5 21:22:12 storageqe-109 INFO: #### will start test_fuzz_alignment_boundaries ##### Oct 5 21:22:12 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_alignment_boundaries #### INFO: #### will start test_fuzz_memory_pattern_boundaries ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:22 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:22 storageqe-109 INFO: #### END test_fuzz_alignment_boundaries #### Oct 5 21:22:22 storageqe-109 INFO: #### will start test_fuzz_memory_pattern_boundaries ##### Oct 5 21:22:22 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:27 storageqe-109 kernel: loop152: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop153: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop154: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop155: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop156: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop157: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop158: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop159: detected capacity change from 0 to 2 Oct 5 21:22:27 storageqe-109 kernel: loop160: detected capacity change from 0 to 2 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_memory_pattern_boundaries #### INFO: #### will start test_fuzz_path_traversal_attacks ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:32 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:32 storageqe-109 INFO: #### END test_fuzz_memory_pattern_boundaries #### Oct 5 21:22:32 storageqe-109 INFO: #### will start test_fuzz_path_traversal_attacks ##### Oct 5 21:22:32 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_path_traversal_attacks #### INFO: #### will start test_fuzz_command_injection_attacks ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:42 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:42 storageqe-109 INFO: #### END test_fuzz_path_traversal_attacks #### Oct 5 21:22:42 storageqe-109 INFO: #### will start test_fuzz_command_injection_attacks ##### Oct 5 21:22:42 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_command_injection_attacks #### INFO: #### will start test_fuzz_format_string_attacks ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:52 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:22:52 storageqe-109 INFO: #### END test_fuzz_command_injection_attacks #### Oct 5 21:22:52 storageqe-109 INFO: #### will start test_fuzz_format_string_attacks ##### Oct 5 21:22:52 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_format_string_attacks #### INFO: #### will start test_fuzz_buffer_overflow_attempts ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:02 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:02 storageqe-109 INFO: #### END test_fuzz_format_string_attacks #### Oct 5 21:23:02 storageqe-109 INFO: #### will start test_fuzz_buffer_overflow_attempts ##### Oct 5 21:23:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_buffer_overflow_attempts #### INFO: #### will start test_fuzz_privilege_escalation_attempts ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:12 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:12 storageqe-109 INFO: #### END test_fuzz_buffer_overflow_attempts #### Oct 5 21:23:12 storageqe-109 INFO: #### will start test_fuzz_privilege_escalation_attempts ##### Oct 5 21:23:12 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_privilege_escalation_attempts #### INFO: #### will start test_fuzz_symlink_attacks ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:22 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:22 storageqe-109 INFO: #### END test_fuzz_privilege_escalation_attempts #### Oct 5 21:23:22 storageqe-109 INFO: #### will start test_fuzz_symlink_attacks ##### Oct 5 21:23:22 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_symlink_attacks #### INFO: #### will start test_fuzz_race_condition_attempts ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:32 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:32 storageqe-109 INFO: #### END test_fuzz_symlink_attacks #### Oct 5 21:23:32 storageqe-109 INFO: #### will start test_fuzz_race_condition_attempts ##### Oct 5 21:23:32 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:37 storageqe-109 kernel: loop162: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop163: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop164: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop165: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop166: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop167: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop168: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop169: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop170: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop171: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop172: detected capacity change from 0 to 20480 Oct 5 21:23:37 storageqe-109 kernel: loop173: detected capacity change from 0 to 20480 Oct 5 21:23:38 storageqe-109 kernel: loop174: detected capacity change from 0 to 20480 Oct 5 21:23:38 storageqe-109 kernel: loop175: detected capacity change from 0 to 20480 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_race_condition_attempts #### INFO: #### will start test_fuzz_memory_corruption_attempts ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:43 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:43 storageqe-109 INFO: #### END test_fuzz_race_condition_attempts #### Oct 5 21:23:43 storageqe-109 INFO: #### will start test_fuzz_memory_corruption_attempts ##### Oct 5 21:23:43 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:48 storageqe-109 kernel: loop176: detected capacity change from 0 to 200 Oct 5 21:23:48 storageqe-109 kernel: loop177: detected capacity change from 0 to 800 Oct 5 21:23:48 storageqe-109 kernel: loop178: detected capacity change from 0 to 200 Oct 5 21:23:48 storageqe-109 kernel: loop179: detected capacity change from 0 to 200 Oct 5 21:23:48 storageqe-109 kernel: loop180: detected capacity change from 0 to 200 Oct 5 21:23:48 storageqe-109 kernel: loop181: detected capacity change from 0 to 200 Oct 5 21:23:48 storageqe-109 kernel: loop182: detected capacity change from 0 to 1 Oct 5 21:23:48 storageqe-109 kernel: loop183: detected capacity change from 0 to 1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fuzz_memory_corruption_attempts #### INFO: #### will start test_loop_device_availability ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:53 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:53 storageqe-109 INFO: #### END test_fuzz_memory_corruption_attempts #### Oct 5 21:23:53 storageqe-109 INFO: #### will start test_loop_device_availability ##### Oct 5 21:23:53 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:23:58 storageqe-109 kernel: loop186: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_availability #### INFO: #### will start test_loop_device_creation_and_cleanup ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:03 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:03 storageqe-109 INFO: #### END test_loop_device_availability #### Oct 5 21:24:03 storageqe-109 INFO: #### will start test_loop_device_creation_and_cleanup ##### Oct 5 21:24:03 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:08 storageqe-109 kernel: loop187: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_creation_and_cleanup #### INFO: #### will start test_multiple_loop_devices ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:13 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:13 storageqe-109 INFO: #### END test_loop_device_creation_and_cleanup #### Oct 5 21:24:13 storageqe-109 INFO: #### will start test_multiple_loop_devices ##### Oct 5 21:24:13 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:18 storageqe-109 kernel: loop188: detected capacity change from 0 to 2097152 Oct 5 21:24:18 storageqe-109 kernel: loop189: detected capacity change from 0 to 2097152 Oct 5 21:24:18 storageqe-109 kernel: loop190: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_multiple_loop_devices #### INFO: #### will start test_loop_device_io_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:23 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:23 storageqe-109 INFO: #### END test_multiple_loop_devices #### Oct 5 21:24:23 storageqe-109 INFO: #### will start test_loop_device_io_operations ##### Oct 5 21:24:23 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:28 storageqe-109 kernel: loop191: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_io_operations #### INFO: #### will start test_loop_device_size ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:33 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:33 storageqe-109 INFO: #### END test_loop_device_io_operations #### Oct 5 21:24:33 storageqe-109 INFO: #### will start test_loop_device_size ##### Oct 5 21:24:33 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:38 storageqe-109 kernel: loop192: detected capacity change from 0 to 4194304 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_size #### INFO: #### will start test_loop_device_status_query ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:43 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:43 storageqe-109 INFO: #### END test_loop_device_size #### Oct 5 21:24:43 storageqe-109 INFO: #### will start test_loop_device_status_query ##### Oct 5 21:24:43 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:48 storageqe-109 kernel: loop193: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_status_query #### INFO: #### will start test_loop_device_with_filesystem ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:53 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:54 storageqe-109 INFO: #### END test_loop_device_status_query #### Oct 5 21:24:54 storageqe-109 INFO: #### will start test_loop_device_with_filesystem ##### Oct 5 21:24:54 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:24:59 storageqe-109 kernel: loop194: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_with_filesystem #### INFO: #### will start test_loop_device_mount_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:04 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:04 storageqe-109 INFO: #### END test_loop_device_with_filesystem #### Oct 5 21:25:04 storageqe-109 INFO: #### will start test_loop_device_mount_operations ##### Oct 5 21:25:04 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:09 storageqe-109 kernel: loop195: detected capacity change from 0 to 2097152 Oct 5 21:25:09 storageqe-109 kernel: EXT4-fs (loop195): mounted filesystem e6619523-e59d-456a-b45c-66b1257f6389 r/w with ordered data mode. Quota mode: none. Oct 5 21:25:09 storageqe-109 systemd[1]: tmp-loop_mount_gpt9aogv.mount: Deactivated successfully. Oct 5 21:25:09 storageqe-109 kernel: EXT4-fs (loop195): unmounting filesystem e6619523-e59d-456a-b45c-66b1257f6389. Oct 5 21:25:12 storageqe-109 systemd[1]: fwupd.service: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_mount_operations #### INFO: #### will start test_loop_device_error_conditions ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:14 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:14 storageqe-109 INFO: #### END test_loop_device_mount_operations #### Oct 5 21:25:14 storageqe-109 INFO: #### will start test_loop_device_error_conditions ##### Oct 5 21:25:14 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_error_conditions #### INFO: #### will start test_loop_device_backing_file_access ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:24 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:24 storageqe-109 INFO: #### END test_loop_device_error_conditions #### Oct 5 21:25:24 storageqe-109 INFO: #### will start test_loop_device_backing_file_access ##### Oct 5 21:25:24 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:29 storageqe-109 kernel: loop197: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_backing_file_access #### INFO: #### will start test_loop_device_large_size ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:34 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:34 storageqe-109 INFO: #### END test_loop_device_backing_file_access #### Oct 5 21:25:34 storageqe-109 INFO: #### will start test_loop_device_large_size ##### Oct 5 21:25:34 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:39 storageqe-109 kernel: loop198: detected capacity change from 0 to 10485760 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_large_size #### INFO: #### will start test_loop_device_concurrent_access ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:44 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:44 storageqe-109 INFO: #### END test_loop_device_large_size #### Oct 5 21:25:44 storageqe-109 INFO: #### will start test_loop_device_concurrent_access ##### Oct 5 21:25:44 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:49 storageqe-109 kernel: loop199: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_concurrent_access #### INFO: #### will start test_loop_device_zero_fill ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:54 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:54 storageqe-109 INFO: #### END test_loop_device_concurrent_access #### Oct 5 21:25:54 storageqe-109 INFO: #### will start test_loop_device_zero_fill ##### Oct 5 21:25:54 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:25:59 storageqe-109 kernel: loop200: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_zero_fill #### INFO: #### will start test_loop_device_partial_write_read ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:04 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:04 storageqe-109 INFO: #### END test_loop_device_zero_fill #### Oct 5 21:26:04 storageqe-109 INFO: #### will start test_loop_device_partial_write_read ##### Oct 5 21:26:04 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:09 storageqe-109 kernel: loop201: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_partial_write_read #### INFO: #### will start test_loop_device_performance_basic ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:15 storageqe-109 INFO: #### END test_loop_device_partial_write_read #### Oct 5 21:26:15 storageqe-109 INFO: #### will start test_loop_device_performance_basic ##### Oct 5 21:26:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:20 storageqe-109 kernel: loop202: detected capacity change from 0 to 2097152 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_loop_device_performance_basic #### Oct 5 21:26:25 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:25 storageqe-109 INFO: #### END test_loop_device_performance_basic #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 21:26:25 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 21:26:25 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 21:26:25 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 21:26:36 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_integrity_format[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:42 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:42 storageqe-109 INFO: #### will start test_integrity_format[npo2_linear] ##### Oct 5 21:26:42 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:47 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbd0380 Oct 5 21:26:47 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbd0380 Oct 5 21:26:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1548400, async page read INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_format[npo2_linear] #### INFO: #### will start test_luks_format[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:52 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:52 storageqe-109 INFO: #### END test_integrity_format[npo2_linear] #### Oct 5 21:26:52 storageqe-109 INFO: #### will start test_luks_format[npo2_linear] ##### Oct 5 21:26:52 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:26:55 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 21:27:02 storageqe-109 stratisd[4947]: [2025-10-06T01:27:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:02 storageqe-109 stratisd[4947]: [2025-10-06T01:27:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:02 storageqe-109 stratisd[4947]: [2025-10-06T01:27:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:02 storageqe-109 stratisd[4947]: [2025-10-06T01:27:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:03 storageqe-109 stratisd[4947]: [2025-10-06T01:27:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:03 storageqe-109 stratisd[4947]: [2025-10-06T01:27:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:08 storageqe-109 stratisd[4947]: [2025-10-06T01:27:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:08 storageqe-109 stratisd[4947]: [2025-10-06T01:27:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:08 storageqe-109 stratisd[4947]: [2025-10-06T01:27:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:08 storageqe-109 stratisd[4947]: [2025-10-06T01:27:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:09 storageqe-109 stratisd[4947]: [2025-10-06T01:27:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:09 storageqe-109 stratisd[4947]: [2025-10-06T01:27:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_format[npo2_linear] #### INFO: #### will start test_luks_key_management[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:27:14 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:27:14 storageqe-109 INFO: #### END test_luks_format[npo2_linear] #### Oct 5 21:27:14 storageqe-109 INFO: #### will start test_luks_key_management[npo2_linear] ##### Oct 5 21:27:14 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:27:19 storageqe-109 stratisd[4947]: [2025-10-06T01:27:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:19 storageqe-109 stratisd[4947]: [2025-10-06T01:27:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:26 storageqe-109 stratisd[4947]: [2025-10-06T01:27:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:26 storageqe-109 stratisd[4947]: [2025-10-06T01:27:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:34 storageqe-109 stratisd[4947]: [2025-10-06T01:27:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:34 storageqe-109 stratisd[4947]: [2025-10-06T01:27:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:38 storageqe-109 stratisd[4947]: [2025-10-06T01:27:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:38 storageqe-109 stratisd[4947]: [2025-10-06T01:27:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:47 storageqe-109 stratisd[4947]: [2025-10-06T01:27:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:47 storageqe-109 stratisd[4947]: [2025-10-06T01:27:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:55 storageqe-109 stratisd[4947]: [2025-10-06T01:27:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:55 storageqe-109 stratisd[4947]: [2025-10-06T01:27:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:57 storageqe-109 stratisd[4947]: [2025-10-06T01:27:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:27:57 storageqe-109 stratisd[4947]: [2025-10-06T01:27:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_key_management[npo2_linear] #### INFO: #### will start test_luks_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:04 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:04 storageqe-109 INFO: #### END test_luks_key_management[npo2_linear] #### Oct 5 21:28:04 storageqe-109 INFO: #### will start test_luks_operations[npo2_linear] ##### Oct 5 21:28:04 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:09 storageqe-109 stratisd[4947]: [2025-10-06T01:28:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:09 storageqe-109 stratisd[4947]: [2025-10-06T01:28:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:16 storageqe-109 stratisd[4947]: [2025-10-06T01:28:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:16 storageqe-109 stratisd[4947]: [2025-10-06T01:28:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:18 storageqe-109 stratisd[4947]: [2025-10-06T01:28:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:18 storageqe-109 stratisd[4947]: [2025-10-06T01:28:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:24 storageqe-109 stratisd[4947]: [2025-10-06T01:28:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:24 storageqe-109 stratisd[4947]: [2025-10-06T01:28:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:24 storageqe-109 stratisd[4947]: [2025-10-06T01:28:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:24 storageqe-109 stratisd[4947]: [2025-10-06T01:28:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:26 storageqe-109 stratisd[4947]: [2025-10-06T01:28:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:26 storageqe-109 stratisd[4947]: [2025-10-06T01:28:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_operations[npo2_linear] #### INFO: #### will start test_luks_metadata_and_keyslots[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:31 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:32 storageqe-109 INFO: #### END test_luks_operations[npo2_linear] #### Oct 5 21:28:32 storageqe-109 INFO: #### will start test_luks_metadata_and_keyslots[npo2_linear] ##### Oct 5 21:28:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:37 storageqe-109 stratisd[4947]: [2025-10-06T01:28:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:37 storageqe-109 stratisd[4947]: [2025-10-06T01:28:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:44 storageqe-109 stratisd[4947]: [2025-10-06T01:28:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:44 storageqe-109 stratisd[4947]: [2025-10-06T01:28:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:44 storageqe-109 stratisd[4947]: [2025-10-06T01:28:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:44 storageqe-109 stratisd[4947]: [2025-10-06T01:28:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:44 storageqe-109 stratisd[4947]: [2025-10-06T01:28:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:44 storageqe-109 stratisd[4947]: [2025-10-06T01:28:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:52 storageqe-109 stratisd[4947]: [2025-10-06T01:28:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:28:52 storageqe-109 stratisd[4947]: [2025-10-06T01:28:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_metadata_and_keyslots[npo2_linear] #### INFO: #### will start test_luks_token_info[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:28:57 storageqe-109 INFO: #### END test_luks_metadata_and_keyslots[npo2_linear] #### Oct 5 21:28:57 storageqe-109 INFO: #### will start test_luks_token_info[npo2_linear] ##### Oct 5 21:28:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:29:02 storageqe-109 stratisd[4947]: [2025-10-06T01:29:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:02 storageqe-109 stratisd[4947]: [2025-10-06T01:29:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:10 storageqe-109 stratisd[4947]: [2025-10-06T01:29:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:10 storageqe-109 stratisd[4947]: [2025-10-06T01:29:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_token_info[npo2_linear] #### INFO: #### will start test_luks_kill_slot[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:29:15 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:29:15 storageqe-109 INFO: #### END test_luks_token_info[npo2_linear] #### Oct 5 21:29:15 storageqe-109 INFO: #### will start test_luks_kill_slot[npo2_linear] ##### Oct 5 21:29:15 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:29:20 storageqe-109 stratisd[4947]: [2025-10-06T01:29:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:20 storageqe-109 stratisd[4947]: [2025-10-06T01:29:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:27 storageqe-109 stratisd[4947]: [2025-10-06T01:29:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:27 storageqe-109 stratisd[4947]: [2025-10-06T01:29:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:36 storageqe-109 stratisd[4947]: [2025-10-06T01:29:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:36 storageqe-109 stratisd[4947]: [2025-10-06T01:29:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:36 storageqe-109 stratisd[4947]: [2025-10-06T01:29:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:36 storageqe-109 stratisd[4947]: [2025-10-06T01:29:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_kill_slot[npo2_linear] #### INFO: #### will start test_crypto_device_seems_encrypted[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:29:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:29:41 storageqe-109 INFO: #### END test_luks_kill_slot[npo2_linear] #### Oct 5 21:29:41 storageqe-109 INFO: #### will start test_crypto_device_seems_encrypted[npo2_linear] ##### Oct 5 21:29:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:29:51 storageqe-109 stratisd[4947]: [2025-10-06T01:29:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:51 storageqe-109 stratisd[4947]: [2025-10-06T01:29:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:58 storageqe-109 stratisd[4947]: [2025-10-06T01:29:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:29:58 storageqe-109 stratisd[4947]: [2025-10-06T01:29:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_device_seems_encrypted[npo2_linear] #### INFO: #### will start test_crypto_luks_different_ciphers[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:30:03 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:30:03 storageqe-109 INFO: #### END test_crypto_device_seems_encrypted[npo2_linear] #### Oct 5 21:30:03 storageqe-109 INFO: #### will start test_crypto_luks_different_ciphers[npo2_linear] ##### Oct 5 21:30:03 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:30:13 storageqe-109 stratisd[4947]: [2025-10-06T01:30:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:13 storageqe-109 stratisd[4947]: [2025-10-06T01:30:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:21 storageqe-109 stratisd[4947]: [2025-10-06T01:30:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:21 storageqe-109 stratisd[4947]: [2025-10-06T01:30:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:23 storageqe-109 stratisd[4947]: [2025-10-06T01:30:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:23 storageqe-109 stratisd[4947]: [2025-10-06T01:30:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:35 storageqe-109 stratisd[4947]: [2025-10-06T01:30:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:35 storageqe-109 stratisd[4947]: [2025-10-06T01:30:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:38 storageqe-109 stratisd[4947]: [2025-10-06T01:30:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:38 storageqe-109 stratisd[4947]: [2025-10-06T01:30:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:50 storageqe-109 stratisd[4947]: [2025-10-06T01:30:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:50 storageqe-109 stratisd[4947]: [2025-10-06T01:30:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:52 storageqe-109 stratisd[4947]: [2025-10-06T01:30:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:30:52 storageqe-109 stratisd[4947]: [2025-10-06T01:30:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:05 storageqe-109 stratisd[4947]: [2025-10-06T01:31:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:05 storageqe-109 stratisd[4947]: [2025-10-06T01:31:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:07 storageqe-109 stratisd[4947]: [2025-10-06T01:31:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:07 storageqe-109 stratisd[4947]: [2025-10-06T01:31:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_different_ciphers[npo2_linear] #### INFO: #### will start test_crypto_luks_different_sector_sizes[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:12 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:12 storageqe-109 INFO: #### END test_crypto_luks_different_ciphers[npo2_linear] #### Oct 5 21:31:12 storageqe-109 INFO: #### will start test_crypto_luks_different_sector_sizes[npo2_linear] ##### Oct 5 21:31:12 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:30 storageqe-109 stratisd[4947]: [2025-10-06T01:31:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:30 storageqe-109 stratisd[4947]: [2025-10-06T01:31:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:32 storageqe-109 stratisd[4947]: [2025-10-06T01:31:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:32 storageqe-109 stratisd[4947]: [2025-10-06T01:31:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_different_sector_sizes[npo2_linear] #### INFO: #### will start test_crypto_luks_persistent_flags_comprehensive[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:37 storageqe-109 INFO: #### END test_crypto_luks_different_sector_sizes[npo2_linear] #### Oct 5 21:31:37 storageqe-109 INFO: #### will start test_crypto_luks_persistent_flags_comprehensive[npo2_linear] ##### Oct 5 21:31:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:31:49 storageqe-109 stratisd[4947]: [2025-10-06T01:31:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_persistent_flags_comprehensive[npo2_linear] #### INFO: #### will start test_crypto_keyring_comprehensive[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:31:54 storageqe-109 INFO: #### END test_crypto_luks_persistent_flags_comprehensive[npo2_linear] #### Oct 5 21:31:54 storageqe-109 INFO: #### will start test_crypto_keyring_comprehensive[npo2_linear] ##### Oct 5 21:31:54 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:32:04 storageqe-109 stratisd[4947]: [2025-10-06T01:32:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:04 storageqe-109 stratisd[4947]: [2025-10-06T01:32:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:12 storageqe-109 stratisd[4947]: [2025-10-06T01:32:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:12 storageqe-109 stratisd[4947]: [2025-10-06T01:32:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:26 storageqe-109 stratisd[4947]: [2025-10-06T01:32:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:26 storageqe-109 stratisd[4947]: [2025-10-06T01:32:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:41 storageqe-109 stratisd[4947]: [2025-10-06T01:32:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:41 storageqe-109 stratisd[4947]: [2025-10-06T01:32:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:43 storageqe-109 stratisd[4947]: [2025-10-06T01:32:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:32:43 storageqe-109 stratisd[4947]: [2025-10-06T01:32:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_keyring_comprehensive[npo2_linear] #### INFO: #### will start test_crypto_integrity_different_algorithms[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:32:48 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:32:48 storageqe-109 INFO: #### END test_crypto_keyring_comprehensive[npo2_linear] #### Oct 5 21:32:48 storageqe-109 INFO: #### will start test_crypto_integrity_different_algorithms[npo2_linear] ##### Oct 5 21:32:48 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:32:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbe5100 Oct 5 21:32:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbe5100 Oct 5 21:32:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1559072, async page read Oct 5 21:32:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbe5100 Oct 5 21:32:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbe5100 Oct 5 21:32:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1559072, async page read Oct 5 21:32:53 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Invalid tag size (-EINVAL) Oct 5 21:32:53 storageqe-109 kernel: device-mapper: ioctl: error adding target to table Oct 5 21:32:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbd9280 Oct 5 21:32:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbd9280 Oct 5 21:32:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1552976, async page read Oct 5 21:32:54 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbd0480 Oct 5 21:32:54 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbd0480 Oct 5 21:32:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1548432, async page read Oct 5 21:32:54 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbb8f80 Oct 5 21:32:54 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0xbb8f80 Oct 5 21:32:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1536496, async page read Oct 5 21:32:54 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Invalid tag size (-EINVAL) Oct 5 21:32:54 storageqe-109 kernel: device-mapper: ioctl: error adding target to table Oct 5 21:32:54 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Invalid tag size (-EINVAL) Oct 5 21:32:54 storageqe-109 kernel: device-mapper: ioctl: error adding target to table INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_integrity_different_algorithms[npo2_linear] #### INFO: #### will start test_crypto_bitlocker_detection[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:32:59 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:32:59 storageqe-109 INFO: #### END test_crypto_integrity_different_algorithms[npo2_linear] #### Oct 5 21:32:59 storageqe-109 INFO: #### will start test_crypto_bitlocker_detection[npo2_linear] ##### Oct 5 21:32:59 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:33:17 storageqe-109 stratisd[4947]: [2025-10-06T01:33:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:33:17 storageqe-109 stratisd[4947]: [2025-10-06T01:33:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_bitlocker_detection[npo2_linear] #### INFO: #### will start test_crypto_luks_error_conditions[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:33:22 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:33:22 storageqe-109 INFO: #### END test_crypto_bitlocker_detection[npo2_linear] #### Oct 5 21:33:22 storageqe-109 INFO: #### will start test_crypto_luks_error_conditions[npo2_linear] ##### Oct 5 21:33:22 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:33:39 storageqe-109 stratisd[4947]: [2025-10-06T01:33:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:33:39 storageqe-109 stratisd[4947]: [2025-10-06T01:33:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:33:43 storageqe-109 stratisd[4947]: [2025-10-06T01:33:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:33:43 storageqe-109 stratisd[4947]: [2025-10-06T01:33:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_error_conditions[npo2_linear] #### INFO: #### will start test_crypto_escrow_device[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:33:48 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:33:48 storageqe-109 INFO: #### END test_crypto_luks_error_conditions[npo2_linear] #### Oct 5 21:33:48 storageqe-109 INFO: #### will start test_crypto_escrow_device[npo2_linear] ##### Oct 5 21:33:48 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:33:58 storageqe-109 stratisd[4947]: [2025-10-06T01:33:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:33:58 storageqe-109 stratisd[4947]: [2025-10-06T01:33:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:06 storageqe-109 stratisd[4947]: [2025-10-06T01:34:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:06 storageqe-109 stratisd[4947]: [2025-10-06T01:34:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_escrow_device[npo2_linear] #### INFO: #### will start test_crypto_luks_multiple_keyslots[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:34:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:34:11 storageqe-109 INFO: #### END test_crypto_escrow_device[npo2_linear] #### Oct 5 21:34:11 storageqe-109 INFO: #### will start test_crypto_luks_multiple_keyslots[npo2_linear] ##### Oct 5 21:34:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:34:16 storageqe-109 stratisd[4947]: [2025-10-06T01:34:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:16 storageqe-109 stratisd[4947]: [2025-10-06T01:34:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:23 storageqe-109 stratisd[4947]: [2025-10-06T01:34:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:23 storageqe-109 stratisd[4947]: [2025-10-06T01:34:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:31 storageqe-109 stratisd[4947]: [2025-10-06T01:34:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:31 storageqe-109 stratisd[4947]: [2025-10-06T01:34:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:40 storageqe-109 stratisd[4947]: [2025-10-06T01:34:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:40 storageqe-109 stratisd[4947]: [2025-10-06T01:34:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:48 storageqe-109 stratisd[4947]: [2025-10-06T01:34:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:48 storageqe-109 stratisd[4947]: [2025-10-06T01:34:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:50 storageqe-109 stratisd[4947]: [2025-10-06T01:34:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:50 storageqe-109 stratisd[4947]: [2025-10-06T01:34:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:54 storageqe-109 stratisd[4947]: [2025-10-06T01:34:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:34:54 storageqe-109 stratisd[4947]: [2025-10-06T01:34:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:00 storageqe-109 stratisd[4947]: [2025-10-06T01:35:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:00 storageqe-109 stratisd[4947]: [2025-10-06T01:35:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:08 storageqe-109 stratisd[4947]: [2025-10-06T01:35:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:08 storageqe-109 stratisd[4947]: [2025-10-06T01:35:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:08 storageqe-109 stratisd[4947]: [2025-10-06T01:35:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:08 storageqe-109 stratisd[4947]: [2025-10-06T01:35:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_luks_multiple_keyslots[npo2_linear] #### INFO: #### will start test_luks_with_detached_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:35:13 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:35:13 storageqe-109 INFO: #### END test_crypto_luks_multiple_keyslots[npo2_linear] #### Oct 5 21:35:13 storageqe-109 INFO: #### will start test_luks_with_detached_header[npo2_linear] ##### Oct 5 21:35:13 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_with_detached_header[npo2_linear] #### INFO: #### will start test_luks_benchmark_and_iteration_time[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:35:23 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:35:23 storageqe-109 INFO: #### END test_luks_with_detached_header[npo2_linear] #### Oct 5 21:35:23 storageqe-109 INFO: #### will start test_luks_benchmark_and_iteration_time[npo2_linear] ##### Oct 5 21:35:23 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:35:33 storageqe-109 stratisd[4947]: [2025-10-06T01:35:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:33 storageqe-109 stratisd[4947]: [2025-10-06T01:35:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:33 storageqe-109 stratisd[4947]: [2025-10-06T01:35:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:33 storageqe-109 stratisd[4947]: [2025-10-06T01:35:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:38 storageqe-109 stratisd[4947]: [2025-10-06T01:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:38 storageqe-109 stratisd[4947]: [2025-10-06T01:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:38 storageqe-109 stratisd[4947]: [2025-10-06T01:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:38 storageqe-109 stratisd[4947]: [2025-10-06T01:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:43 storageqe-109 stratisd[4947]: [2025-10-06T01:35:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:43 storageqe-109 stratisd[4947]: [2025-10-06T01:35:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:43 storageqe-109 stratisd[4947]: [2025-10-06T01:35:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:43 storageqe-109 stratisd[4947]: [2025-10-06T01:35:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:48 storageqe-109 stratisd[4947]: [2025-10-06T01:35:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:48 storageqe-109 stratisd[4947]: [2025-10-06T01:35:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:48 storageqe-109 stratisd[4947]: [2025-10-06T01:35:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:35:48 storageqe-109 stratisd[4947]: [2025-10-06T01:35:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_benchmark_and_iteration_time[npo2_linear] #### INFO: #### will start test_luks_with_custom_uuid_and_label[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:35:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:35:54 storageqe-109 INFO: #### END test_luks_benchmark_and_iteration_time[npo2_linear] #### Oct 5 21:35:54 storageqe-109 INFO: #### will start test_luks_with_custom_uuid_and_label[npo2_linear] ##### Oct 5 21:35:54 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:36:06 storageqe-109 stratisd[4947]: [2025-10-06T01:36:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:06 storageqe-109 stratisd[4947]: [2025-10-06T01:36:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:06 storageqe-109 stratisd[4947]: [2025-10-06T01:36:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:06 storageqe-109 stratisd[4947]: [2025-10-06T01:36:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:06 storageqe-109 stratisd[4947]: [2025-10-06T01:36:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:06 storageqe-109 stratisd[4947]: [2025-10-06T01:36:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_with_custom_uuid_and_label[npo2_linear] #### INFO: #### will start test_luks_backup_restore_workflow[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:36:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:36:11 storageqe-109 INFO: #### END test_luks_with_custom_uuid_and_label[npo2_linear] #### Oct 5 21:36:11 storageqe-109 INFO: #### will start test_luks_backup_restore_workflow[npo2_linear] ##### Oct 5 21:36:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:36:16 storageqe-109 stratisd[4947]: [2025-10-06T01:36:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:16 storageqe-109 stratisd[4947]: [2025-10-06T01:36:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:24 storageqe-109 stratisd[4947]: [2025-10-06T01:36:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:24 storageqe-109 stratisd[4947]: [2025-10-06T01:36:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:24 storageqe-109 stratisd[4947]: [2025-10-06T01:36:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:24 storageqe-109 stratisd[4947]: [2025-10-06T01:36:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:26 storageqe-109 stratisd[4947]: [2025-10-06T01:36:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:26 storageqe-109 stratisd[4947]: [2025-10-06T01:36:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:26 storageqe-109 stratisd[4947]: [2025-10-06T01:36:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:26 storageqe-109 stratisd[4947]: [2025-10-06T01:36:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:28 storageqe-109 stratisd[4947]: [2025-10-06T01:36:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:28 storageqe-109 stratisd[4947]: [2025-10-06T01:36:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_backup_restore_workflow[npo2_linear] #### INFO: #### will start test_luks_resize_scenarios[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:36:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:36:33 storageqe-109 INFO: #### END test_luks_backup_restore_workflow[npo2_linear] #### Oct 5 21:36:33 storageqe-109 INFO: #### will start test_luks_resize_scenarios[npo2_linear] ##### Oct 5 21:36:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:36:43 storageqe-109 stratisd[4947]: [2025-10-06T01:36:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:43 storageqe-109 stratisd[4947]: [2025-10-06T01:36:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:51 storageqe-109 stratisd[4947]: [2025-10-06T01:36:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:51 storageqe-109 stratisd[4947]: [2025-10-06T01:36:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:53 storageqe-109 stratisd[4947]: [2025-10-06T01:36:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:53 storageqe-109 stratisd[4947]: [2025-10-06T01:36:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:55 storageqe-109 stratisd[4947]: [2025-10-06T01:36:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:55 storageqe-109 stratisd[4947]: [2025-10-06T01:36:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:57 storageqe-109 stratisd[4947]: [2025-10-06T01:36:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:57 storageqe-109 stratisd[4947]: [2025-10-06T01:36:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:57 storageqe-109 stratisd[4947]: [2025-10-06T01:36:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:36:57 storageqe-109 stratisd[4947]: [2025-10-06T01:36:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_resize_scenarios[npo2_linear] #### INFO: #### will start test_luks_suspend_resume_with_io[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:02 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:02 storageqe-109 INFO: #### END test_luks_resize_scenarios[npo2_linear] #### Oct 5 21:37:02 storageqe-109 INFO: #### will start test_luks_suspend_resume_with_io[npo2_linear] ##### Oct 5 21:37:02 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:12 storageqe-109 stratisd[4947]: [2025-10-06T01:37:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:37:12 storageqe-109 stratisd[4947]: [2025-10-06T01:37:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:37:19 storageqe-109 stratisd[4947]: [2025-10-06T01:37:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:37:19 storageqe-109 stratisd[4947]: [2025-10-06T01:37:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:37:21 storageqe-109 stratisd[4947]: [2025-10-06T01:37:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:37:21 storageqe-109 stratisd[4947]: [2025-10-06T01:37:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_suspend_resume_with_io[npo2_linear] #### INFO: #### will start test_luks_with_integrity_combined[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:34 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:34 storageqe-109 INFO: #### END test_luks_suspend_resume_with_io[npo2_linear] #### Oct 5 21:37:34 storageqe-109 INFO: #### will start test_luks_with_integrity_combined[npo2_linear] ##### Oct 5 21:37:34 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:39 storageqe-109 stratisd[4947]: [2025-10-06T01:37:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:37:39 storageqe-109 stratisd[4947]: [2025-10-06T01:37:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_with_integrity_combined[npo2_linear] #### INFO: #### will start test_crypto_performance_comparison[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:44 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:44 storageqe-109 INFO: #### END test_luks_with_integrity_combined[npo2_linear] #### Oct 5 21:37:44 storageqe-109 INFO: #### will start test_crypto_performance_comparison[npo2_linear] ##### Oct 5 21:37:44 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:37:54 storageqe-109 stratisd[4947]: [2025-10-06T01:37:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:37:54 storageqe-109 stratisd[4947]: [2025-10-06T01:37:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:01 storageqe-109 stratisd[4947]: [2025-10-06T01:38:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:01 storageqe-109 stratisd[4947]: [2025-10-06T01:38:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:03 storageqe-109 stratisd[4947]: [2025-10-06T01:38:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:03 storageqe-109 stratisd[4947]: [2025-10-06T01:38:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:16 storageqe-109 stratisd[4947]: [2025-10-06T01:38:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:16 storageqe-109 stratisd[4947]: [2025-10-06T01:38:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:18 storageqe-109 stratisd[4947]: [2025-10-06T01:38:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:18 storageqe-109 stratisd[4947]: [2025-10-06T01:38:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:31 storageqe-109 stratisd[4947]: [2025-10-06T01:38:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:31 storageqe-109 stratisd[4947]: [2025-10-06T01:38:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:33 storageqe-109 stratisd[4947]: [2025-10-06T01:38:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:33 storageqe-109 stratisd[4947]: [2025-10-06T01:38:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:46 storageqe-109 stratisd[4947]: [2025-10-06T01:38:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:46 storageqe-109 stratisd[4947]: [2025-10-06T01:38:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:48 storageqe-109 stratisd[4947]: [2025-10-06T01:38:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:38:48 storageqe-109 stratisd[4947]: [2025-10-06T01:38:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_performance_comparison[npo2_linear] #### INFO: #### will start test_luks_token_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:38:53 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:38:53 storageqe-109 INFO: #### END test_crypto_performance_comparison[npo2_linear] #### Oct 5 21:38:53 storageqe-109 INFO: #### will start test_luks_token_operations[npo2_linear] ##### Oct 5 21:38:53 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:06 storageqe-109 stratisd[4947]: [2025-10-06T01:39:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:39:06 storageqe-109 stratisd[4947]: [2025-10-06T01:39:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_token_operations[npo2_linear] #### INFO: #### will start test_truecrypt_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:11 storageqe-109 INFO: #### END test_luks_token_operations[npo2_linear] #### Oct 5 21:39:11 storageqe-109 INFO: #### will start test_truecrypt_operations[npo2_linear] ##### Oct 5 21:39:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_truecrypt_operations[npo2_linear] #### INFO: #### will start test_bitlocker_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:21 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:21 storageqe-109 INFO: #### END test_truecrypt_operations[npo2_linear] #### Oct 5 21:39:21 storageqe-109 INFO: #### will start test_bitlocker_operations[npo2_linear] ##### Oct 5 21:39:21 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bitlocker_operations[npo2_linear] #### INFO: #### will start test_filevault2_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:31 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:31 storageqe-109 INFO: #### END test_bitlocker_operations[npo2_linear] #### Oct 5 21:39:31 storageqe-109 INFO: #### will start test_filevault2_operations[npo2_linear] ##### Oct 5 21:39:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_filevault2_operations[npo2_linear] #### INFO: #### will start test_crypto_format_detection[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:41 storageqe-109 INFO: #### END test_filevault2_operations[npo2_linear] #### Oct 5 21:39:41 storageqe-109 INFO: #### will start test_crypto_format_detection[npo2_linear] ##### Oct 5 21:39:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:39:59 storageqe-109 stratisd[4947]: [2025-10-06T01:39:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:39:59 storageqe-109 stratisd[4947]: [2025-10-06T01:39:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_format_detection[npo2_linear] #### INFO: #### will start test_crypto_with_keyfiles[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:40:04 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:40:04 storageqe-109 INFO: #### END test_crypto_format_detection[npo2_linear] #### Oct 5 21:40:04 storageqe-109 INFO: #### will start test_crypto_with_keyfiles[npo2_linear] ##### Oct 5 21:40:04 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:40:14 storageqe-109 stratisd[4947]: [2025-10-06T01:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:14 storageqe-109 stratisd[4947]: [2025-10-06T01:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:21 storageqe-109 stratisd[4947]: [2025-10-06T01:40:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:21 storageqe-109 stratisd[4947]: [2025-10-06T01:40:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:23 storageqe-109 stratisd[4947]: [2025-10-06T01:40:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:23 storageqe-109 stratisd[4947]: [2025-10-06T01:40:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:32 storageqe-109 stratisd[4947]: [2025-10-06T01:40:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:32 storageqe-109 stratisd[4947]: [2025-10-06T01:40:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:36 storageqe-109 stratisd[4947]: [2025-10-06T01:40:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:36 storageqe-109 stratisd[4947]: [2025-10-06T01:40:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:48 storageqe-109 stratisd[4947]: [2025-10-06T01:40:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:48 storageqe-109 stratisd[4947]: [2025-10-06T01:40:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:50 storageqe-109 stratisd[4947]: [2025-10-06T01:40:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:50 storageqe-109 stratisd[4947]: [2025-10-06T01:40:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:59 storageqe-109 stratisd[4947]: [2025-10-06T01:40:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:40:59 storageqe-109 stratisd[4947]: [2025-10-06T01:40:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:03 storageqe-109 stratisd[4947]: [2025-10-06T01:41:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:03 storageqe-109 stratisd[4947]: [2025-10-06T01:41:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:15 storageqe-109 stratisd[4947]: [2025-10-06T01:41:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:15 storageqe-109 stratisd[4947]: [2025-10-06T01:41:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:17 storageqe-109 stratisd[4947]: [2025-10-06T01:41:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:17 storageqe-109 stratisd[4947]: [2025-10-06T01:41:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:26 storageqe-109 stratisd[4947]: [2025-10-06T01:41:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:26 storageqe-109 stratisd[4947]: [2025-10-06T01:41:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:30 storageqe-109 stratisd[4947]: [2025-10-06T01:41:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:30 storageqe-109 stratisd[4947]: [2025-10-06T01:41:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_with_keyfiles[npo2_linear] #### INFO: #### will start test_crypto_error_handling[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:41:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:41:35 storageqe-109 INFO: #### END test_crypto_with_keyfiles[npo2_linear] #### Oct 5 21:41:35 storageqe-109 INFO: #### will start test_crypto_error_handling[npo2_linear] ##### Oct 5 21:41:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:41:45 storageqe-109 kernel: device-mapper: table: 253:4: crypt: Error allocating crypto tfm (-ENOENT) Oct 5 21:41:45 storageqe-109 kernel: device-mapper: ioctl: error adding target to table Oct 5 21:41:57 storageqe-109 stratisd[4947]: [2025-10-06T01:41:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:41:57 storageqe-109 stratisd[4947]: [2025-10-06T01:41:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_error_handling[npo2_linear] #### INFO: #### will start test_crypto_boundary_conditions[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:42:02 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:42:02 storageqe-109 INFO: #### END test_crypto_error_handling[npo2_linear] #### Oct 5 21:42:02 storageqe-109 INFO: #### will start test_crypto_boundary_conditions[npo2_linear] ##### Oct 5 21:42:03 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:42:08 storageqe-109 stratisd[4947]: [2025-10-06T01:42:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:08 storageqe-109 stratisd[4947]: [2025-10-06T01:42:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:15 storageqe-109 kernel: perf: interrupt took too long (2531 > 2500), lowering kernel.perf_event_max_sample_rate to 79000 Oct 5 21:42:15 storageqe-109 stratisd[4947]: [2025-10-06T01:42:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:15 storageqe-109 stratisd[4947]: [2025-10-06T01:42:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:15 storageqe-109 stratisd[4947]: [2025-10-06T01:42:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:15 storageqe-109 stratisd[4947]: [2025-10-06T01:42:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:28 storageqe-109 stratisd[4947]: [2025-10-06T01:42:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:28 storageqe-109 stratisd[4947]: [2025-10-06T01:42:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:30 storageqe-109 stratisd[4947]: [2025-10-06T01:42:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:30 storageqe-109 stratisd[4947]: [2025-10-06T01:42:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:42 storageqe-109 stratisd[4947]: [2025-10-06T01:42:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:42 storageqe-109 stratisd[4947]: [2025-10-06T01:42:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:44 storageqe-109 stratisd[4947]: [2025-10-06T01:42:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:42:44 storageqe-109 stratisd[4947]: [2025-10-06T01:42:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_boundary_conditions[npo2_linear] #### INFO: #### will start test_crypto_concurrent_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:42:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:42:54 storageqe-109 INFO: #### END test_crypto_boundary_conditions[npo2_linear] #### Oct 5 21:42:54 storageqe-109 INFO: #### will start test_crypto_concurrent_operations[npo2_linear] ##### Oct 5 21:42:54 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:43:12 storageqe-109 stratisd[4947]: [2025-10-06T01:43:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:12 storageqe-109 stratisd[4947]: [2025-10-06T01:43:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:14 storageqe-109 stratisd[4947]: [2025-10-06T01:43:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:14 storageqe-109 stratisd[4947]: [2025-10-06T01:43:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_concurrent_operations[npo2_linear] #### INFO: #### will start test_luks_status_api_comparison[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:43:22 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:43:22 storageqe-109 INFO: #### END test_crypto_concurrent_operations[npo2_linear] #### Oct 5 21:43:22 storageqe-109 INFO: #### will start test_luks_status_api_comparison[npo2_linear] ##### Oct 5 21:43:22 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:43:32 storageqe-109 stratisd[4947]: [2025-10-06T01:43:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:32 storageqe-109 stratisd[4947]: [2025-10-06T01:43:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:40 storageqe-109 stratisd[4947]: [2025-10-06T01:43:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:40 storageqe-109 stratisd[4947]: [2025-10-06T01:43:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:42 storageqe-109 stratisd[4947]: [2025-10-06T01:43:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:43:42 storageqe-109 stratisd[4947]: [2025-10-06T01:43:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:43:53 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_status_api_comparison[npo2_linear] #### INFO: #### will start test_luks_persistent_flags[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:43:53 storageqe-109 INFO: #### END test_luks_status_api_comparison[npo2_linear] #### Oct 5 21:43:53 storageqe-109 INFO: #### will start test_luks_persistent_flags[npo2_linear] ##### Oct 5 21:43:53 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_persistent_flags[npo2_linear] #### INFO: #### will start test_generate_backup_passphrase ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:44:03 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:44:03 storageqe-109 INFO: #### END test_luks_persistent_flags[npo2_linear] #### Oct 5 21:44:03 storageqe-109 INFO: #### will start test_generate_backup_passphrase ##### Oct 5 21:44:03 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_generate_backup_passphrase #### INFO: #### will start test_crypto_is_tech_avail ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:44:13 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:44:13 storageqe-109 INFO: #### END test_generate_backup_passphrase #### Oct 5 21:44:13 storageqe-109 INFO: #### will start test_crypto_is_tech_avail ##### Oct 5 21:44:13 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_crypto_is_tech_avail #### Oct 5 21:44:23 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:44:23 storageqe-109 INFO: #### END test_crypto_is_tech_avail #### Oct 5 21:44:24 storageqe-109 stratisd[4947]: [2025-10-06T01:44:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:44:24 storageqe-109 stratisd[4947]: [2025-10-06T01:44:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:44:24 storageqe-109 stratisd[4947]: [2025-10-06T01:44:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:44:24 storageqe-109 stratisd[4947]: [2025-10-06T01:44:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 21:44:25 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_lvm_pv_basic_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:44:27 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:44:27 storageqe-109 INFO: #### will start test_lvm_pv_basic_operations ##### Oct 5 21:44:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_pv_basic_operations #### INFO: #### will start test_lvm_pv_resize ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:44:38 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:44:38 storageqe-109 INFO: #### END test_lvm_pv_basic_operations #### Oct 5 21:44:38 storageqe-109 INFO: #### will start test_lvm_pv_resize ##### Oct 5 21:44:38 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_lvm_pv_resize #### INFO: #### will start test_lvm_pv_tags ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:44:49 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:44:49 storageqe-109 INFO: #### END test_lvm_pv_resize #### Oct 5 21:44:49 storageqe-109 INFO: #### will start test_lvm_pv_tags ##### Oct 5 21:44:49 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:44:54 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_pv_tags: Process reported exit code 5: Volume group "test_vg_pv_tags" not found#012 Cannot process volume group test_vg_pv_tags INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_lvm_pv_tags #### INFO: #### will start test_lvm_vg_basic_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:45:00 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:45:00 storageqe-109 INFO: #### END test_lvm_pv_tags #### Oct 5 21:45:00 storageqe-109 INFO: #### will start test_lvm_vg_basic_operations ##### Oct 5 21:45:00 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:45:05 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_basic: Process reported exit code 5: Volume group "test_vg_basic" not found#012 Cannot process volume group test_vg_basic INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_vg_basic_operations #### INFO: #### will start test_lvm_vg_extend_reduce ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:45:11 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:45:11 storageqe-109 INFO: #### END test_lvm_vg_basic_operations #### Oct 5 21:45:11 storageqe-109 INFO: #### will start test_lvm_vg_extend_reduce ##### Oct 5 21:45:11 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:45:16 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_extend: Process reported exit code 5: Volume group "test_vg_extend" not found#012 Cannot process volume group test_vg_extend INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_vg_extend_reduce #### INFO: #### will start test_lvm_vg_rename ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:45:22 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:45:22 storageqe-109 INFO: #### END test_lvm_vg_extend_reduce #### Oct 5 21:45:22 storageqe-109 INFO: #### will start test_lvm_vg_rename ##### Oct 5 21:45:22 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:45:27 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_old: Process reported exit code 5: Volume group "test_vg_old" not found#012 Cannot process volume group test_vg_old INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_lvm_vg_rename #### INFO: #### will start test_lvm_vg_tags ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:45:32 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:45:32 storageqe-109 INFO: #### END test_lvm_vg_rename #### Oct 5 21:45:32 storageqe-109 INFO: #### will start test_lvm_vg_tags ##### Oct 5 21:45:32 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:45:38 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_tags: Process reported exit code 5: Volume group "test_vg_tags" not found#012 Cannot process volume group test_vg_tags INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_lvm_vg_tags #### INFO: #### will start test_lvm_lv_basic_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:45:43 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:45:43 storageqe-109 INFO: #### END test_lvm_vg_tags #### Oct 5 21:45:43 storageqe-109 INFO: #### will start test_lvm_lv_basic_operations ##### Oct 5 21:45:43 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:45:49 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_lv: Process reported exit code 5: Volume group "test_vg_lv" not found#012 Cannot process volume group test_vg_lv INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_lv_basic_operations #### INFO: #### will start test_lvm_lv_resize ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:45:54 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:45:54 storageqe-109 INFO: #### END test_lvm_lv_basic_operations #### Oct 5 21:45:54 storageqe-109 INFO: #### will start test_lvm_lv_resize ##### Oct 5 21:45:54 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:46:00 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_resize: Process reported exit code 5: Volume group "test_vg_resize" not found#012 Cannot process volume group test_vg_resize INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_lv_resize #### INFO: #### will start test_lvm_lv_rename ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:46:05 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:46:05 storageqe-109 INFO: #### END test_lvm_lv_resize #### Oct 5 21:46:05 storageqe-109 INFO: #### will start test_lvm_lv_rename ##### Oct 5 21:46:05 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:46:11 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_rename_lv: Process reported exit code 5: Volume group "test_vg_rename_lv" not found#012 Cannot process volume group test_vg_rename_lv INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_lv_rename #### INFO: #### will start test_lvm_lv_tags ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:46:16 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:46:16 storageqe-109 INFO: #### END test_lvm_lv_rename #### Oct 5 21:46:16 storageqe-109 INFO: #### will start test_lvm_lv_tags ##### Oct 5 21:46:16 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:46:22 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_lv_tags: Process reported exit code 5: Volume group "test_vg_lv_tags" not found#012 Cannot process volume group test_vg_lv_tags INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_lvm_lv_tags #### INFO: #### will start test_lvm_lv_snapshots ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:46:27 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:46:27 storageqe-109 INFO: #### END test_lvm_lv_tags #### Oct 5 21:46:27 storageqe-109 INFO: #### will start test_lvm_lv_snapshots ##### Oct 5 21:46:27 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:46:33 storageqe-109 systemd[1]: Started dm-event.service - Device-mapper event daemon. Oct 5 21:46:33 storageqe-109 dmeventd[73612]: dmeventd ready for processing. Oct 5 21:46:33 storageqe-109 dmeventd[73612]: Monitoring snapshot test_vg_snap-test_lv_snap. Oct 5 21:46:33 storageqe-109 dmeventd[73612]: No longer monitoring snapshot test_vg_snap-test_lv_snap. Oct 5 21:46:33 storageqe-109 systemd[1]: Started lvm2-lvmpolld.service - LVM2 poll daemon. Oct 5 21:46:33 storageqe-109 lvmpolld[73650]: W: #011LVPOLL: PID 73653: STDERR: ' WARNING: This metadata update is NOT backed up.' INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_lvm_lv_snapshots #### INFO: #### will start test_lvm_thin_pool_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:46:40 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:46:40 storageqe-109 INFO: #### END test_lvm_lv_snapshots #### Oct 5 21:46:40 storageqe-109 INFO: #### will start test_lvm_thin_pool_operations ##### Oct 5 21:46:40 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:46:45 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 5 21:46:45 storageqe-109 dmeventd[73612]: Monitoring thin pool test_vg_thin-test_thin_pool. Oct 5 21:46:46 storageqe-109 dmeventd[73612]: No longer monitoring thin pool test_vg_thin-test_thin_pool. Oct 5 21:46:46 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_thin: Process reported exit code 5: Volume group "test_vg_thin" not found#012 Cannot process volume group test_vg_thin INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_thin_pool_operations #### INFO: #### will start test_lvm_thin_lv_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:46:51 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:46:51 storageqe-109 INFO: #### END test_lvm_thin_pool_operations #### Oct 5 21:46:51 storageqe-109 INFO: #### will start test_lvm_thin_lv_operations ##### Oct 5 21:46:51 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:46:56 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 5 21:46:56 storageqe-109 dmeventd[73612]: Monitoring thin pool test_vg_thin_lv-test_thin_pool. Oct 5 21:46:56 storageqe-109 dmeventd[73612]: No longer monitoring thin pool test_vg_thin_lv-test_thin_pool. Oct 5 21:46:58 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 5 21:46:58 storageqe-109 dmeventd[73612]: Monitoring thin pool test_vg_thin_lv-test_thin_pool-tpool. Oct 5 21:46:58 storageqe-109 dmeventd[73612]: No longer monitoring thin pool test_vg_thin_lv-test_thin_pool-tpool. Oct 5 21:46:58 storageqe-109 dmeventd[73612]: Monitoring thin pool test_vg_thin_lv-test_thin_pool-tpool. Oct 5 21:46:58 storageqe-109 dmeventd[73612]: No longer monitoring thin pool test_vg_thin_lv-test_thin_pool-tpool. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_thin_lv_operations #### INFO: #### will start test_lvm_thin_pool_convert ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:47:04 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:47:04 storageqe-109 INFO: #### END test_lvm_thin_lv_operations #### Oct 5 21:47:04 storageqe-109 INFO: #### will start test_lvm_thin_pool_convert ##### Oct 5 21:47:04 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:47:09 storageqe-109 dmeventd[73612]: Monitoring thin pool test_vg_convert-test_data_lv. Oct 5 21:47:09 storageqe-109 dmeventd[73612]: No longer monitoring thin pool test_vg_convert-test_data_lv. Oct 5 21:47:10 storageqe-109 dmeventd[73612]: Monitoring thin pool test_vg_convert-converted_pool. Oct 5 21:47:10 storageqe-109 dmeventd[73612]: No longer monitoring thin pool test_vg_convert-converted_pool. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_thin_pool_convert #### INFO: #### will start test_lvm_cache_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:47:15 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:47:15 storageqe-109 INFO: #### END test_lvm_thin_pool_convert #### Oct 5 21:47:15 storageqe-109 INFO: #### will start test_lvm_cache_operations ##### Oct 5 21:47:15 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:47:21 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_cache: Process reported exit code 5: Volume group "test_vg_cache" not found#012 Cannot process volume group test_vg_cache INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_lvm_cache_operations #### INFO: #### will start test_lvm_cache_create_cached_lv ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:47:26 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:47:26 storageqe-109 INFO: #### END test_lvm_cache_operations #### Oct 5 21:47:26 storageqe-109 INFO: #### will start test_lvm_cache_create_cached_lv ##### Oct 5 21:47:26 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:47:32 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_cached_lv: Process reported exit code 5: Volume group "test_vg_cached_lv" not found#012 Cannot process volume group test_vg_cached_lv Oct 5 21:47:34 storageqe-109 systemd[1]: lvm2-lvmpolld.service: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_cache_create_cached_lv #### INFO: #### will start test_lvm_vdo_pool_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:47:37 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:47:37 storageqe-109 INFO: #### END test_lvm_cache_create_cached_lv #### Oct 5 21:47:37 storageqe-109 INFO: #### will start test_lvm_vdo_pool_operations ##### Oct 5 21:47:37 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:47:42 storageqe-109 UDS/vdoformat[75318]: INFO (vdoformat/75318) Using 2 indexing zones for concurrency. Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: loading device '253:4' Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: starting device '253:4' Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo0:physQ0: VDO commencing normal operation Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo0:journal: Setting UDS index target state to online Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo0:dedupeQ: creating index: 253:3 Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: device '253:4' started Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo0:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: resuming device '253:4' Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: device '253:4' resumed Oct 5 21:47:43 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo-test_vdo_pool-vpool. Oct 5 21:47:43 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo-test_vdo_pool-vpool. Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: suspending device '253:4' Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo0:journal: beginning save (vcn 18446744073709551615) Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo0:journal: finished save (vcn 18446744073709551615) Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: device '253:4' suspended Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: stopping device '253:4' Oct 5 21:47:43 storageqe-109 kernel: device-mapper: vdo0:lvm: device '253:4' stopped Oct 5 21:47:43 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_vdo: Process reported exit code 5: Volume group "test_vg_vdo" not found#012 Cannot process volume group test_vg_vdo INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_vdo_pool_operations #### INFO: #### will start test_lvm_vdo_resize ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:47:49 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:47:49 storageqe-109 INFO: #### END test_lvm_vdo_pool_operations #### Oct 5 21:47:49 storageqe-109 INFO: #### will start test_lvm_vdo_resize ##### Oct 5 21:47:49 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:47:54 storageqe-109 UDS/vdoformat[75563]: INFO (vdoformat/75563) Using 2 indexing zones for concurrency. Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: loading device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: starting device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:physQ0: VDO commencing normal operation Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:journal: Setting UDS index target state to online Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:dedupeQ: creating index: 253:3 Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' started Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: resuming device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' resumed Oct 5 21:47:54 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_resize-test_vdo_pool_resize-vpool. Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: preparing to modify device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: Preparing to resize logical to 10486016 Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: Done preparing to resize logical Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: suspending device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:journal: beginning save (vcn 18446744073709551615) Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:journal: finished save (vcn 18446744073709551615) Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' suspended Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: resuming device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: Resizing logical to 10486016 Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: Logical blocks now 10486016 Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:packerQ: compression is enabled Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' resumed Oct 5 21:47:54 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_resize-test_vdo_pool_resize-vpool. Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: suspending device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' suspended Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo1:lvm: resuming device '253:4' Oct 5 21:47:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:packerQ: compression is enabled Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' resumed Oct 5 21:47:55 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_resize-test_vdo_pool_resize-vpool. Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: table line: V4 /dev/dm-3 1835008 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: preparing to modify device '253:4' Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: Preparing to resize physical to 1835008 Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: Done preparing to resize physical Oct 5 21:47:55 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_resize-test_vdo_pool_resize-vpool. Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: suspending device '253:4' Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' suspended Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: resuming device '253:4' Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: Physical block count was 1310720, now 1835008 Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo: dm_vdo1:packerQ: compression is enabled Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' resumed Oct 5 21:47:55 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_resize-test_vdo_pool_resize-vpool. Oct 5 21:47:55 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_resize-test_vdo_pool_resize-vpool. Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: suspending device '253:4' Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' suspended Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: stopping device '253:4' Oct 5 21:47:55 storageqe-109 kernel: device-mapper: vdo1:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_lvm_vdo_resize #### INFO: #### will start test_lvm_vdo_minimum_size_boundary ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:48:01 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:48:01 storageqe-109 INFO: #### END test_lvm_vdo_resize #### Oct 5 21:48:01 storageqe-109 INFO: #### will start test_lvm_vdo_minimum_size_boundary ##### Oct 5 21:48:01 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:48:06 storageqe-109 UDS/vdoformat[75888]: INFO (vdoformat/75888) Using 2 indexing zones for concurrency. Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: table line: V4 /dev/dm-3 1236992 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: loading device '253:4' Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: starting device '253:4' Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo2:physQ0: VDO commencing normal operation Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo2:journal: Setting UDS index target state to online Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo2:dedupeQ: creating index: 253:3 Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: device '253:4' started Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo2:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: resuming device '253:4' Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: device '253:4' resumed Oct 5 21:48:06 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_min-test_vdo_pool_min-vpool. Oct 5 21:48:06 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_min-test_vdo_pool_min-vpool. Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: suspending device '253:4' Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo2:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo2:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: device '253:4' suspended Oct 5 21:48:06 storageqe-109 kernel: device-mapper: vdo2:lvm: stopping device '253:4' Oct 5 21:48:07 storageqe-109 kernel: device-mapper: vdo2:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_lvm_vdo_minimum_size_boundary #### INFO: #### will start test_lvm_vdo_maximum_compression_ratio ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:48:12 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:48:12 storageqe-109 INFO: #### END test_lvm_vdo_minimum_size_boundary #### Oct 5 21:48:12 storageqe-109 INFO: #### will start test_lvm_vdo_maximum_compression_ratio ##### Oct 5 21:48:12 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:48:17 storageqe-109 UDS/vdoformat[76154]: INFO (vdoformat/76154) Using 2 indexing zones for concurrency. Oct 5 21:48:17 storageqe-109 kernel: device-mapper: vdo3:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:17 storageqe-109 kernel: device-mapper: vdo3:lvm: loading device '253:4' Oct 5 21:48:17 storageqe-109 kernel: device-mapper: vdo3:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: starting device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo3:physQ0: VDO commencing normal operation Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo3:journal: Setting UDS index target state to online Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo3:dedupeQ: creating index: 253:3 Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo3:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: device '253:4' started Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: resuming device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: device '253:4' resumed Oct 5 21:48:18 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_10x-vpool. Oct 5 21:48:18 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_10x-vpool. Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: suspending device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo3:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo3:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: device '253:4' suspended Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: stopping device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo3:lvm: device '253:4' stopped Oct 5 21:48:18 storageqe-109 UDS/vdoformat[76231]: INFO (vdoformat/76231) Using 2 indexing zones for concurrency. Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: loading device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: starting device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo4:physQ0: VDO commencing normal operation Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo4:journal: Setting UDS index target state to online Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo4:dedupeQ: creating index: 253:3 Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo4:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: device '253:4' started Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: resuming device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: device '253:4' resumed Oct 5 21:48:18 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_50x-vpool. Oct 5 21:48:18 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_50x-vpool. Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: suspending device '253:4' Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo4:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo4:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: device '253:4' suspended Oct 5 21:48:18 storageqe-109 kernel: device-mapper: vdo4:lvm: stopping device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo4:lvm: device '253:4' stopped Oct 5 21:48:19 storageqe-109 UDS/vdoformat[76307]: INFO (vdoformat/76307) Using 2 indexing zones for concurrency. Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: loading device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: starting device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo5:physQ0: VDO commencing normal operation Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo5:journal: Setting UDS index target state to online Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo5:dedupeQ: creating index: 253:3 Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: device '253:4' started Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo5:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: resuming device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: device '253:4' resumed Oct 5 21:48:19 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_100x-vpool. Oct 5 21:48:19 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_100x-vpool. Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: suspending device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo5:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo5:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: device '253:4' suspended Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: stopping device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo5:lvm: device '253:4' stopped Oct 5 21:48:19 storageqe-109 UDS/vdoformat[76383]: INFO (vdoformat/76383) Using 2 indexing zones for concurrency. Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo6:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo6:lvm: loading device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo6:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo6:lvm: starting device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo6:physQ0: VDO commencing normal operation Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo6:journal: Setting UDS index target state to online Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo6:dedupeQ: creating index: 253:3 Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo6:lvm: device '253:4' started Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo6:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo6:lvm: resuming device '253:4' Oct 5 21:48:19 storageqe-109 kernel: device-mapper: vdo6:lvm: device '253:4' resumed Oct 5 21:48:19 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_255x-vpool. Oct 5 21:48:20 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_max_compression-test_vdo_pool_max_comp_255x-vpool. Oct 5 21:48:20 storageqe-109 kernel: device-mapper: vdo6:lvm: suspending device '253:4' Oct 5 21:48:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo6:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo6:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:20 storageqe-109 kernel: device-mapper: vdo6:lvm: device '253:4' suspended Oct 5 21:48:20 storageqe-109 kernel: device-mapper: vdo6:lvm: stopping device '253:4' Oct 5 21:48:20 storageqe-109 kernel: device-mapper: vdo6:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_vdo_maximum_compression_ratio #### INFO: #### will start test_lvm_vdo_extreme_resize_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:48:25 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:48:25 storageqe-109 INFO: #### END test_lvm_vdo_maximum_compression_ratio #### Oct 5 21:48:25 storageqe-109 INFO: #### will start test_lvm_vdo_extreme_resize_operations ##### Oct 5 21:48:25 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:48:31 storageqe-109 UDS/vdoformat[76639]: INFO (vdoformat/76639) Using 2 indexing zones for concurrency. Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: loading device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: starting device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:physQ0: VDO commencing normal operation Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:journal: Setting UDS index target state to online Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:dedupeQ: creating index: 253:3 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' started Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:31 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: preparing to modify device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Preparing to resize logical to 13107456 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Done preparing to resize logical Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Resizing logical to 13107456 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Logical blocks now 13107456 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:packerQ: compression is enabled Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:31 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:packerQ: compression is enabled Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:31 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: preparing to modify device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Preparing to resize logical to 26214656 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Done preparing to resize logical Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Resizing logical to 26214656 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: Logical blocks now 26214656 Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:packerQ: compression is enabled Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:31 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:packerQ: compression is enabled Oct 5 21:48:31 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:31 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: preparing to modify device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: Preparing to resize logical to 131072256 Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: Done preparing to resize logical Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: Resizing logical to 131072256 Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: Logical blocks now 131072256 Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:packerQ: compression is enabled Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:32 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:packerQ: compression is enabled Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:32 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: table line: V4 /dev/dm-3 3407872 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: preparing to modify device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: Preparing to resize physical to 3407872 Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: Done preparing to resize physical Oct 5 21:48:32 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: resuming device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: Physical block count was 1310720, now 3407872 Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo: dm_vdo7:packerQ: compression is enabled Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' resumed Oct 5 21:48:32 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:32 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_extreme_resize-test_vdo_pool_extreme-vpool. Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: suspending device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' suspended Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: stopping device '253:4' Oct 5 21:48:32 storageqe-109 kernel: device-mapper: vdo7:lvm: device '253:4' stopped Oct 5 21:48:33 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_vdo_extreme_resize: Process reported exit code 5: Volume group "test_vg_vdo_extreme_resize" not found#012 Cannot process volume group test_vg_vdo_extreme_resize INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_vdo_extreme_resize_operations #### INFO: #### will start test_lvm_vdo_stress_and_boundary_conditions ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:48:38 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:48:38 storageqe-109 INFO: #### END test_lvm_vdo_extreme_resize_operations #### Oct 5 21:48:38 storageqe-109 INFO: #### will start test_lvm_vdo_stress_and_boundary_conditions ##### Oct 5 21:48:38 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:48:43 storageqe-109 UDS/vdoformat[77021]: INFO (vdoformat/77021) Using 2 indexing zones for concurrency. Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo8:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo8:lvm: loading device '253:4' Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo8:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo8:lvm: starting device '253:4' Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo8:physQ0: VDO commencing normal operation Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo8:journal: Setting UDS index target state to online Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo8:dedupeQ: creating index: 253:3 Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo8:lvm: device '253:4' started Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo: dm_vdo8:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:43 storageqe-109 kernel: device-mapper: vdo8:lvm: resuming device '253:4' Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo8:lvm: device '253:4' resumed Oct 5 21:48:44 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_0-vpool. Oct 5 21:48:44 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_0-vpool. Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo8:lvm: suspending device '253:4' Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo8:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo8:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo8:lvm: device '253:4' suspended Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo8:lvm: stopping device '253:4' Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo8:lvm: device '253:4' stopped Oct 5 21:48:44 storageqe-109 udisksd[5174]: Failed to get information about VDO volume test_vdo_lv_stress_0: Process reported exit code 5: Failed to find logical volume "test_vg_vdo_stress/test_vdo_pool_stress_0" Oct 5 21:48:44 storageqe-109 UDS/vdoformat[77085]: INFO (vdoformat/77085) Using 2 indexing zones for concurrency. Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: loading device '253:4' Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: starting device '253:4' Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo9:physQ0: VDO commencing normal operation Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo9:journal: Setting UDS index target state to online Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo9:dedupeQ: creating index: 253:3 Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo9:dedupeQ: Using 2 indexing zones for concurrency. Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: device '253:4' started Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: resuming device '253:4' Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: device '253:4' resumed Oct 5 21:48:44 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_1-vpool. Oct 5 21:48:44 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_1-vpool. Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: suspending device '253:4' Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo9:journal: beginning save (vcn 18446744073709551615) Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo9:journal: finished save (vcn 18446744073709551615) Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: device '253:4' suspended Oct 5 21:48:44 storageqe-109 kernel: device-mapper: vdo9:lvm: stopping device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo9:lvm: device '253:4' stopped Oct 5 21:48:45 storageqe-109 UDS/vdoformat[77146]: INFO (vdoformat/77146) Using 2 indexing zones for concurrency. Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: loading device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: starting device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo10:physQ0: VDO commencing normal operation Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo10:journa: Setting UDS index target state to online Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo10:dedupe: creating index: 253:3 Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: device '253:4' started Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo10:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: resuming device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: device '253:4' resumed Oct 5 21:48:45 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_2-vpool. Oct 5 21:48:45 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_2-vpool. Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: suspending device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo10:journa: beginning save (vcn 18446744073709551615) Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo10:journa: finished save (vcn 18446744073709551615) Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: device '253:4' suspended Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: stopping device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo10:lvm: device '253:4' stopped Oct 5 21:48:45 storageqe-109 UDS/vdoformat[77204]: INFO (vdoformat/77204) Using 2 indexing zones for concurrency. Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo11:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo11:lvm: loading device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo11:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo11:lvm: starting device '253:4' Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo11:physQ0: VDO commencing normal operation Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo11:dedupe: creating index: 253:3 Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo11:journa: Setting UDS index target state to online Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo11:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:48:45 storageqe-109 kernel: device-mapper: vdo11:lvm: device '253:4' started Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo11:lvm: resuming device '253:4' Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo11:lvm: device '253:4' resumed Oct 5 21:48:46 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_3-vpool. Oct 5 21:48:46 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_3-vpool. Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo11:lvm: suspending device '253:4' Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo11:journa: beginning save (vcn 18446744073709551615) Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo11:journa: finished save (vcn 18446744073709551615) Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo11:lvm: device '253:4' suspended Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo11:lvm: stopping device '253:4' Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo11:lvm: device '253:4' stopped Oct 5 21:48:46 storageqe-109 UDS/vdoformat[77264]: INFO (vdoformat/77264) Using 2 indexing zones for concurrency. Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: loading device '253:4' Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: starting device '253:4' Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo12:physQ0: VDO commencing normal operation Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo12:journa: Setting UDS index target state to online Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo12:dedupe: creating index: 253:3 Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: device '253:4' started Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo12:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: resuming device '253:4' Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: device '253:4' resumed Oct 5 21:48:46 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_4-vpool. Oct 5 21:48:46 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_4-vpool. Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: suspending device '253:4' Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo12:journa: beginning save (vcn 18446744073709551615) Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo: dm_vdo12:journa: finished save (vcn 18446744073709551615) Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: device '253:4' suspended Oct 5 21:48:46 storageqe-109 kernel: device-mapper: vdo12:lvm: stopping device '253:4' Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo12:lvm: device '253:4' stopped Oct 5 21:48:47 storageqe-109 UDS/vdoformat[77328]: INFO (vdoformat/77328) Using 2 indexing zones for concurrency. Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo13:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo13:lvm: loading device '253:4' Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo13:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo13:lvm: starting device '253:4' Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:physQ0: VDO commencing normal operation Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:journa: Setting UDS index target state to online Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:dedupe: creating index: 253:3 Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' started Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo13:lvm: resuming device '253:4' Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' resumed Oct 5 21:48:47 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_0-vpool. Oct 5 21:48:47 storageqe-109 UDS/vdoformat[77381]: INFO (vdoformat/77381) Using 2 indexing zones for concurrency. Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo14:lvm: table line: V4 /dev/dm-6 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo14:lvm: loading device '253:7' Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo14:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo14:lvm: starting device '253:7' Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:physQ0: VDO commencing normal operation Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:journa: Setting UDS index target state to online Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:dedupe: creating index: 253:6 Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' started Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo14:lvm: resuming device '253:7' Oct 5 21:48:47 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' resumed Oct 5 21:48:47 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_1-vpool. Oct 5 21:48:47 storageqe-109 UDS/vdoformat[77432]: INFO (vdoformat/77432) Using 2 indexing zones for concurrency. Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo15:lvm: table line: V4 /dev/dm-9 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo15:lvm: loading device '253:10' Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo15:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo15:lvm: starting device '253:10' Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:physQ0: VDO commencing normal operation Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:journa: Setting UDS index target state to online Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:dedupe: creating index: 253:9 Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' started Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo15:lvm: resuming device '253:10' Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' resumed Oct 5 21:48:48 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_2-vpool. Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: preparing to modify device '253:4' Oct 5 21:48:48 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_0-vpool. Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: suspending device '253:4' Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' suspended Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: resuming device '253:4' Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:packer: compression is disabled Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' resumed Oct 5 21:48:48 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_0-vpool. Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: preparing to modify device '253:4' Oct 5 21:48:48 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_0-vpool. Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: suspending device '253:4' Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' suspended Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: resuming device '253:4' Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:packer: compression is enabled Oct 5 21:48:48 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' resumed Oct 5 21:48:48 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_0-vpool. Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: table line: V4 /dev/dm-6 1310720 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: preparing to modify device '253:7' Oct 5 21:48:49 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_1-vpool. Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: suspending device '253:7' Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' suspended Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: resuming device '253:7' Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:packer: compression is disabled Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' resumed Oct 5 21:48:49 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_1-vpool. Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: table line: V4 /dev/dm-6 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: preparing to modify device '253:7' Oct 5 21:48:49 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_1-vpool. Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: suspending device '253:7' Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' suspended Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: resuming device '253:7' Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:packer: compression is enabled Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' resumed Oct 5 21:48:49 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_1-vpool. Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo15:lvm: table line: V4 /dev/dm-9 1310720 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo15:lvm: preparing to modify device '253:10' Oct 5 21:48:49 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_2-vpool. Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo15:lvm: suspending device '253:10' Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' suspended Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo15:lvm: resuming device '253:10' Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:packer: compression is disabled Oct 5 21:48:49 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' resumed Oct 5 21:48:49 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_2-vpool. Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo15:lvm: table line: V4 /dev/dm-9 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo15:lvm: preparing to modify device '253:10' Oct 5 21:48:50 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_2-vpool. Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo15:lvm: suspending device '253:10' Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' suspended Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo15:lvm: resuming device '253:10' Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:packer: compression is enabled Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' resumed Oct 5 21:48:50 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_2-vpool. Oct 5 21:48:50 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_0-vpool. Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo13:lvm: suspending device '253:4' Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:journa: beginning save (vcn 18446744073709551615) Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo: dm_vdo13:journa: finished save (vcn 18446744073709551615) Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' suspended Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo13:lvm: stopping device '253:4' Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo13:lvm: device '253:4' stopped Oct 5 21:48:50 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_1-vpool. Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo14:lvm: suspending device '253:7' Oct 5 21:48:50 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:journa: beginning save (vcn 18446744073709551615) Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo14:journa: finished save (vcn 18446744073709551615) Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' suspended Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo14:lvm: stopping device '253:7' Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo14:lvm: device '253:7' stopped Oct 5 21:48:51 storageqe-109 udisksd[5174]: Failed to get information about VDO volume test_vdo_lv_stress_concurrent_1: Process reported exit code 5: Failed to find logical volume "test_vg_vdo_stress/test_vdo_pool_stress_concurrent_1" Oct 5 21:48:51 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-test_vdo_pool_stress_concurrent_2-vpool. Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo15:lvm: suspending device '253:10' Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:journa: beginning save (vcn 18446744073709551615) Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo15:journa: finished save (vcn 18446744073709551615) Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' suspended Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo15:lvm: stopping device '253:10' Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo15:lvm: device '253:10' stopped Oct 5 21:48:51 storageqe-109 udisksd[5174]: Failed to get information about VDO volume test_vdo_lv_stress_concurrent_2: Process reported exit code 5: Failed to find logical volume "test_vg_vdo_stress/test_vdo_pool_stress_concurrent_2" Oct 5 21:48:51 storageqe-109 UDS/vdoformat[77651]: INFO (vdoformat/77651) Using 2 indexing zones for concurrency. Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: loading device '253:4' Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: starting device '253:4' Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo16:physQ0: VDO commencing normal operation Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo16:journa: Setting UDS index target state to online Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo16:dedupe: creating index: 253:3 Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo16:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: device '253:4' started Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: resuming device '253:4' Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: device '253:4' resumed Oct 5 21:48:51 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_stress-aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa-vpool. Oct 5 21:48:51 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_stress-aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa-vpool. Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo16:lvm: suspending device '253:4' Oct 5 21:48:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo16:journa: beginning save (vcn 18446744073709551615) Oct 5 21:48:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo16:journa: finished save (vcn 18446744073709551615) Oct 5 21:48:52 storageqe-109 kernel: device-mapper: vdo16:lvm: device '253:4' suspended Oct 5 21:48:52 storageqe-109 kernel: device-mapper: vdo16:lvm: stopping device '253:4' Oct 5 21:48:52 storageqe-109 kernel: device-mapper: vdo16:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_vdo_stress_and_boundary_conditions #### INFO: #### will start test_lvm_vdo_error_conditions_and_recovery ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:48:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:48:57 storageqe-109 INFO: #### END test_lvm_vdo_stress_and_boundary_conditions #### Oct 5 21:48:57 storageqe-109 INFO: #### will start test_lvm_vdo_error_conditions_and_recovery ##### Oct 5 21:48:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:49:03 storageqe-109 UDS/vdoformat[77890]: INFO (vdoformat/77890) Using 2 indexing zones for concurrency. Oct 5 21:49:03 storageqe-109 UDS/vdoformat[77890]: ERROR (vdoformat/77890) Not enough space to make a VDO: VDO Status: Out of space (1467) Oct 5 21:49:03 storageqe-109 UDS/vdoformat[77890]: INFO (vdoformat/77890) Using 2 indexing zones for concurrency. Oct 5 21:49:03 storageqe-109 UDS/vdoformat[77906]: INFO (vdoformat/77906) Using 2 indexing zones for concurrency. Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: table line: V4 /dev/dm-3 1310720 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: loading device '253:4' Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: starting device '253:4' Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo17:physQ0: VDO commencing normal operation Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo17:journa: Setting UDS index target state to online Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo17:dedupe: creating index: 253:3 Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo17:dedupe: Using 2 indexing zones for concurrency. Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: device '253:4' started Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: resuming device '253:4' Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: device '253:4' resumed Oct 5 21:49:03 storageqe-109 dmeventd[73612]: Monitoring VDO pool test_vg_vdo_error-test_vdo_pool_error-vpool. Oct 5 21:49:03 storageqe-109 dmeventd[73612]: No longer monitoring VDO pool test_vg_vdo_error-test_vdo_pool_error-vpool. Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: suspending device '253:4' Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo17:journa: beginning save (vcn 18446744073709551615) Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo17:journa: finished save (vcn 18446744073709551615) Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: device '253:4' suspended Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: stopping device '253:4' Oct 5 21:49:03 storageqe-109 kernel: device-mapper: vdo17:lvm: device '253:4' stopped Oct 5 21:49:03 storageqe-109 udisksd[5174]: Failed to get information about VDO volume test_vdo_lv_error: Process reported exit code 5: Failed to find logical volume "test_vg_vdo_error/test_vdo_pool_error" Oct 5 21:49:03 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_vdo_error: Process reported exit code 5: Volume group "test_vg_vdo_error" not found#012 Cannot process volume group test_vg_vdo_error INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_lvm_vdo_error_conditions_and_recovery #### INFO: #### will start test_lvm_writecache_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:49:09 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:49:09 storageqe-109 INFO: #### END test_lvm_vdo_error_conditions_and_recovery #### Oct 5 21:49:09 storageqe-109 INFO: #### will start test_lvm_writecache_operations ##### Oct 5 21:49:09 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_writecache_operations #### INFO: #### will start test_lvm_cache_pool_convert ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:49:20 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:49:20 storageqe-109 INFO: #### END test_lvm_writecache_operations #### Oct 5 21:49:20 storageqe-109 INFO: #### will start test_lvm_cache_pool_convert ##### Oct 5 21:49:20 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_cache_pool_convert #### INFO: #### will start test_lvm_lv_tree_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:49:31 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:49:31 storageqe-109 INFO: #### END test_lvm_cache_pool_convert #### Oct 5 21:49:31 storageqe-109 INFO: #### will start test_lvm_lv_tree_operations ##### Oct 5 21:49:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:49:36 storageqe-109 dmeventd[73612]: Monitoring snapshot test_vg_tree-test_snap_tree. Oct 5 21:49:36 storageqe-109 dmeventd[73612]: No longer monitoring snapshot test_vg_tree-test_snap_tree. Oct 5 21:49:37 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_tree: Process reported exit code 5: Volume group "test_vg_tree" not found#012 Cannot process volume group test_vg_tree INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_lvm_lv_tree_operations #### INFO: #### will start test_lvm_pv_move ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:49:42 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:49:42 storageqe-109 INFO: #### END test_lvm_lv_tree_operations #### Oct 5 21:49:42 storageqe-109 INFO: #### will start test_lvm_pv_move ##### Oct 5 21:49:42 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:49:48 storageqe-109 systemd[1]: Started lvm2-lvmpolld.service - LVM2 poll daemon. Oct 5 21:49:49 storageqe-109 lvmpolld[79103]: W: #011LVPOLL: PID 79106: STDERR: ' WARNING: This metadata update is NOT backed up.' INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_pv_move #### INFO: #### will start test_lvm_utility_functions ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:49:55 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:49:55 storageqe-109 INFO: #### END test_lvm_pv_move #### Oct 5 21:49:55 storageqe-109 INFO: #### will start test_lvm_utility_functions ##### Oct 5 21:49:55 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_utility_functions #### INFO: #### will start test_lvm_error_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:50:06 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:50:06 storageqe-109 INFO: #### END test_lvm_utility_functions #### Oct 5 21:50:06 storageqe-109 INFO: #### will start test_lvm_error_handling ##### Oct 5 21:50:06 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_error_handling #### INFO: #### will start test_lvm_boundary_conditions ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:50:17 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:50:17 storageqe-109 INFO: #### END test_lvm_error_handling #### Oct 5 21:50:17 storageqe-109 INFO: #### will start test_lvm_boundary_conditions ##### Oct 5 21:50:17 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:50:23 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_boundary: Process reported exit code 5: Volume group "test_vg_boundary" not found#012 Cannot process volume group test_vg_boundary INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_boundary_conditions #### INFO: #### will start test_lvm_concurrent_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:50:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:50:28 storageqe-109 INFO: #### END test_lvm_boundary_conditions #### Oct 5 21:50:28 storageqe-109 INFO: #### will start test_lvm_concurrent_operations ##### Oct 5 21:50:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:50:34 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_concurrent: Process reported exit code 5: Volume group "test_vg_concurrent" not found#012 Cannot process volume group test_vg_concurrent INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_lvm_concurrent_operations #### INFO: #### will start test_lvm_config_get ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:50:39 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:50:39 storageqe-109 INFO: #### END test_lvm_concurrent_operations #### Oct 5 21:50:39 storageqe-109 INFO: #### will start test_lvm_config_get ##### Oct 5 21:50:39 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_lvm_config_get #### INFO: #### will start test_lvm_vgcfgbackup_restore ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:50:50 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:50:50 storageqe-109 INFO: #### END test_lvm_config_get #### Oct 5 21:50:50 storageqe-109 systemd[1]: lvm2-lvmpolld.service: Deactivated successfully. Oct 5 21:50:50 storageqe-109 INFO: #### will start test_lvm_vgcfgbackup_restore ##### Oct 5 21:50:50 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_lvm_vgcfgbackup_restore #### INFO: #### will start test_lvm_performance_and_stress ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:51:02 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:51:02 storageqe-109 INFO: #### END test_lvm_vgcfgbackup_restore #### Oct 5 21:51:02 storageqe-109 INFO: #### will start test_lvm_performance_and_stress ##### Oct 5 21:51:02 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:51:09 storageqe-109 udisksd[5174]: Failed to update LVM volume group test_vg_performance: Process reported exit code 5: Volume group "test_vg_performance" not found#012 Cannot process volume group test_vg_performance INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_performance_and_stress #### INFO: #### will start test_lvm_error_quark ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:51:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:51:15 storageqe-109 INFO: #### END test_lvm_performance_and_stress #### Oct 5 21:51:15 storageqe-109 INFO: #### will start test_lvm_error_quark ##### Oct 5 21:51:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_error_quark #### INFO: #### will start test_lvm_comprehensive_cleanup_verification ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:51:25 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:51:25 storageqe-109 INFO: #### END test_lvm_error_quark #### Oct 5 21:51:25 storageqe-109 INFO: #### will start test_lvm_comprehensive_cleanup_verification ##### Oct 5 21:51:25 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_comprehensive_cleanup_verification #### INFO: #### will start test_raid_create_options ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:51:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:51:36 storageqe-109 INFO: #### END test_lvm_comprehensive_cleanup_verification #### Oct 5 21:51:36 storageqe-109 INFO: #### will start test_raid_create_options ##### Oct 5 21:51:36 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Testing RAID creation with chunk_size=65536, bitmap=internal, version=1.2, size=6G INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdb', '/dev/sdc', '/dev/sdd'], version 1.2, bitmap internal, chunk_size 64.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:51:41 storageqe-109 INFO: Testing RAID creation with chunk_size=65536, bitmap=internal, version=1.2, size=6G Oct 5 21:51:42 storageqe-109 INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdb', '/dev/sdc', '/dev/sdd'], version 1.2, bitmap internal, chunk_size 64.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:51:42 storageqe-109 kernel: raid6: skipped pq benchmark and selected avx2x4 Oct 5 21:51:42 storageqe-109 kernel: raid6: using avx2x2 recovery algorithm Oct 5 21:51:42 storageqe-109 kernel: md/raid:md127: device sdc operational as raid disk 1 Oct 5 21:51:42 storageqe-109 kernel: md/raid:md127: device sdb operational as raid disk 0 Oct 5 21:51:42 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 21:51:42 storageqe-109 kernel: md127: detected capacity change from 0 to 25165824 Oct 5 21:51:42 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 21:51:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:51:44 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 21:51:44 storageqe-109 kernel: md127: detected capacity change from 25165824 to 0 Oct 5 21:51:44 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested and removed RAID with options {'chunk_size': 65536, 'bitmap': 'internal', 'version': '1.2', 'size': '6G'} INFO: Testing RAID creation with chunk_size=131072, bitmap=None, version=1.1, size=6G INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdb', '/dev/sdc', '/dev/sdd'], version 1.1, bitmap None, chunk_size 128.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:51:46 storageqe-109 INFO: Successfully tested and removed RAID with options {'chunk_size': 65536, 'bitmap': 'internal', 'version': '1.2', 'size': '6G'} Oct 5 21:51:46 storageqe-109 INFO: Testing RAID creation with chunk_size=131072, bitmap=None, version=1.1, size=6G Oct 5 21:51:46 storageqe-109 INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdb', '/dev/sdc', '/dev/sdd'], version 1.1, bitmap None, chunk_size 128.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:51:47 storageqe-109 kernel: md/raid:md127: device sdc operational as raid disk 1 Oct 5 21:51:47 storageqe-109 kernel: md/raid:md127: device sdb operational as raid disk 0 Oct 5 21:51:47 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 21:51:47 storageqe-109 kernel: md127: detected capacity change from 0 to 25165824 Oct 5 21:51:47 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 21:51:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:51:49 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 21:51:49 storageqe-109 kernel: md127: detected capacity change from 25165824 to 0 Oct 5 21:51:49 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested and removed RAID with options {'chunk_size': 131072, 'bitmap': None, 'version': '1.1', 'size': '6G'} INFO: Testing RAID creation with chunk_size=262144, bitmap=internal, version=1.0, size=6G INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdb', '/dev/sdc', '/dev/sdd'], version 1.0, bitmap internal, chunk_size 256.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:51:51 storageqe-109 INFO: Successfully tested and removed RAID with options {'chunk_size': 131072, 'bitmap': None, 'version': '1.1', 'size': '6G'} Oct 5 21:51:51 storageqe-109 INFO: Testing RAID creation with chunk_size=262144, bitmap=internal, version=1.0, size=6G Oct 5 21:51:51 storageqe-109 INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdb', '/dev/sdc', '/dev/sdd'], version 1.0, bitmap internal, chunk_size 256.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:51:51 storageqe-109 kernel: md/raid:md127: device sdc operational as raid disk 1 Oct 5 21:51:51 storageqe-109 kernel: md/raid:md127: device sdb operational as raid disk 0 Oct 5 21:51:51 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 21:51:51 storageqe-109 kernel: md127: detected capacity change from 0 to 25165824 Oct 5 21:51:52 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 21:51:52 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:51:54 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 21:51:54 storageqe-109 kernel: md127: detected capacity change from 25165824 to 0 Oct 5 21:51:54 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested and removed RAID with options {'chunk_size': 262144, 'bitmap': 'internal', 'version': '1.0', 'size': '6G'} Oct 5 21:51:56 storageqe-109 INFO: Successfully tested and removed RAID with options {'chunk_size': 262144, 'bitmap': 'internal', 'version': '1.0', 'size': '6G'} INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_raid_create_options #### INFO: #### will start test_raid_stop_start ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:52:02 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:52:02 storageqe-109 INFO: #### END test_raid_create_options #### Oct 5 21:52:02 storageqe-109 INFO: #### will start test_raid_stop_start ##### Oct 5 21:52:02 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:52:07 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:52:08 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:52:08 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:52:08 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:52:08 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:52:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:52:39 storageqe-109 kernel: md: md127: resync done. INFO: Stopping RAID device /dev/md/testraid_stop_start Oct 5 21:52:40 storageqe-109 INFO: Stopping RAID device /dev/md/testraid_stop_start Oct 5 21:52:40 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:52:40 storageqe-109 kernel: md: md127 stopped. INFO: Assembling RAID device testraid_stop_start Oct 5 21:52:42 storageqe-109 INFO: Assembling RAID device testraid_stop_start Oct 5 21:52:42 storageqe-109 kernel: md: md127 stopped. Oct 5 21:52:42 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:52:42 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:52:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:52:42 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:52:42 storageqe-109 kernel: md: md127 stopped. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_raid_stop_start #### INFO: #### will start test_raid_level_creation[raid1-2] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:52:50 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:52:50 storageqe-109 INFO: #### END test_raid_stop_start #### Oct 5 21:52:51 storageqe-109 INFO: #### will start test_raid_level_creation[raid1-2] ##### Oct 5 21:52:51 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Creating raid1 array 'testraid_raid1' with 2 devices INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:52:56 storageqe-109 INFO: Creating raid1 array 'testraid_raid1' with 2 devices Oct 5 21:52:56 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:52:56 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:52:56 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:52:56 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:52:56 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:52:56 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:53:27 storageqe-109 kernel: md: md127: resync done. Oct 5 21:53:28 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:53:28 storageqe-109 kernel: md: md127 stopped. INFO: Successfully created and removed raid1 array Oct 5 21:53:30 storageqe-109 INFO: Successfully created and removed raid1 array INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_raid_level_creation[raid1-2] #### INFO: #### will start test_raid_level_creation[raid5-3] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:53:36 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:53:36 storageqe-109 INFO: #### END test_raid_level_creation[raid1-2] #### Oct 5 21:53:36 storageqe-109 INFO: #### will start test_raid_level_creation[raid5-3] ##### Oct 5 21:53:36 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: Creating raid5 array 'testraid_raid5' with 3 devices INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdd', '/dev/sde', '/dev/nvme0n1'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:53:41 storageqe-109 INFO: Creating raid5 array 'testraid_raid5' with 3 devices Oct 5 21:53:41 storageqe-109 INFO: raid parameter raid_level raid5, raid_mem ['/dev/sdd', '/dev/sde', '/dev/nvme0n1'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:53:41 storageqe-109 kernel: md/raid:md127: device sde operational as raid disk 1 Oct 5 21:53:41 storageqe-109 kernel: md/raid:md127: device sdd operational as raid disk 0 Oct 5 21:53:41 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 21:53:41 storageqe-109 kernel: md127: detected capacity change from 0 to 25165824 Oct 5 21:53:41 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 21:53:41 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:53:43 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 21:53:44 storageqe-109 kernel: md127: detected capacity change from 25165824 to 0 Oct 5 21:53:44 storageqe-109 kernel: md: md127 stopped. INFO: Successfully created and removed raid5 array Oct 5 21:53:46 storageqe-109 INFO: Successfully created and removed raid5 array INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_raid_level_creation[raid5-3] #### INFO: #### will start test_raid_add_remove_spare ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:53:52 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:53:52 storageqe-109 INFO: #### END test_raid_level_creation[raid5-3] #### Oct 5 21:53:52 storageqe-109 INFO: #### will start test_raid_add_remove_spare ##### Oct 5 21:53:52 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:53:57 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:53:57 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:53:57 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:53:57 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:53:57 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:53:57 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:54:29 storageqe-109 kernel: md: md127: resync done. INFO: Adding spare device /dev/sdd to /dev/md/testraid_spare INFO: Removing spare device /dev/sdd from /dev/md/testraid_spare Oct 5 21:54:29 storageqe-109 INFO: Adding spare device /dev/sdd to /dev/md/testraid_spare Oct 5 21:54:29 storageqe-109 INFO: Removing spare device /dev/sdd from /dev/md/testraid_spare Oct 5 21:54:29 storageqe-109 kernel: md/raid1:md127: Disk failure on sdd, disabling device.#012md/raid1:md127: Operation continuing on 2 devices. Oct 5 21:54:29 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:54:29 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested adding and removing a spare device Oct 5 21:54:32 storageqe-109 INFO: Successfully tested adding and removing a spare device INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_raid_add_remove_spare #### INFO: #### will start test_raid_sync_action ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:54:38 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 21:54:38 storageqe-109 INFO: #### END test_raid_add_remove_spare #### Oct 5 21:54:38 storageqe-109 INFO: #### will start test_raid_sync_action ##### Oct 5 21:54:38 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:54:43 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:54:43 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:54:43 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:54:43 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:54:43 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:54:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:55:14 storageqe-109 kernel: md: md127: resync done. INFO: Requesting 'check' sync action on /dev/md/testraid_sync Oct 5 21:55:15 storageqe-109 INFO: Requesting 'check' sync action on /dev/md/testraid_sync Oct 5 21:55:15 storageqe-109 kernel: md: check of RAID array md127 Oct 5 21:55:46 storageqe-109 kernel: md: md127: check done. INFO: Requesting 'repair' sync action on /dev/md/testraid_sync Oct 5 21:55:47 storageqe-109 INFO: Requesting 'repair' sync action on /dev/md/testraid_sync Oct 5 21:55:47 storageqe-109 kernel: md: repair of RAID array md127 Oct 5 21:55:49 storageqe-109 kernel: md: md127: repair interrupted. Oct 5 21:55:49 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:55:49 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested sync actions Oct 5 21:55:51 storageqe-109 INFO: Successfully tested sync actions INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_raid_sync_action #### INFO: #### will start test_raid_examine_member ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:55:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 21:55:58 storageqe-109 INFO: #### END test_raid_sync_action #### Oct 5 21:55:58 storageqe-109 INFO: #### will start test_raid_examine_member ##### Oct 5 21:55:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:56:03 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:56:03 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:56:03 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:56:03 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:56:03 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:56:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:56:34 storageqe-109 kernel: md: md127: resync done. INFO: Examining RAID member /dev/sdb Oct 5 21:56:35 storageqe-109 INFO: Examining RAID member /dev/sdb INFO: Examining RAID member /dev/sdc Oct 5 21:56:35 storageqe-109 INFO: Examining RAID member /dev/sdc Oct 5 21:56:36 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:56:36 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested RAID member examination Oct 5 21:56:38 storageqe-109 INFO: Successfully tested RAID member examination INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_raid_examine_member #### INFO: #### will start test_raid_bitmap_location ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:56:44 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 21:56:44 storageqe-109 INFO: #### END test_raid_examine_member #### Oct 5 21:56:44 storageqe-109 INFO: #### will start test_raid_bitmap_location ##### Oct 5 21:56:44 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdd', '/dev/sde'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:56:49 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdd', '/dev/sde'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:56:49 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:56:49 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:56:49 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:56:49 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:56:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:57:21 storageqe-109 kernel: md: md127: resync done. INFO: Setting internal bitmap for /dev/md/testraid_bitmap_location INFO: Removing bitmap from /dev/md/testraid_bitmap_location Oct 5 21:57:21 storageqe-109 INFO: Setting internal bitmap for /dev/md/testraid_bitmap_location Oct 5 21:57:21 storageqe-109 kernel: md127: bitmap file is out of date (0 < 17) -- forcing full recovery Oct 5 21:57:21 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery Oct 5 21:57:21 storageqe-109 INFO: Removing bitmap from /dev/md/testraid_bitmap_location Oct 5 21:57:21 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:57:21 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested setting and removing a bitmap Oct 5 21:57:24 storageqe-109 INFO: Successfully tested setting and removing a bitmap INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_raid_bitmap_location #### INFO: #### will start test_raid_activate_run ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:57:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:57:30 storageqe-109 INFO: #### END test_raid_bitmap_location #### Oct 5 21:57:30 storageqe-109 INFO: #### will start test_raid_activate_run ##### Oct 5 21:57:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: Starting RAID activation test with member devices: ['/dev/nvme0n1', '/dev/sdb'] INFO: raid parameter raid_level raid1, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:57:35 storageqe-109 INFO: Starting RAID activation test with member devices: ['/dev/nvme0n1', '/dev/sdb'] Oct 5 21:57:35 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:57:35 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:57:35 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:57:35 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:57:35 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:57:35 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:58:07 storageqe-109 kernel: md: md127: resync done. INFO: RAID created successfully: /dev/md/testraid_activate Oct 5 21:58:07 storageqe-109 INFO: RAID created successfully: /dev/md/testraid_activate INFO: UUID from bd.md_examine: 844460a1-6636-1ac4-c417-b37e968f89ad INFO: examine_info details - metadata: None, level: raid1 INFO: UUID from bd.md_detail: 844460a1-6636-1ac4-c417-b37e968f89ad INFO: Starting RAID deactivation and activation test INFO: Pre-deactivation check - device exists: True Oct 5 21:58:08 storageqe-109 INFO: UUID from bd.md_examine: 844460a1-6636-1ac4-c417-b37e968f89ad Oct 5 21:58:08 storageqe-109 INFO: examine_info details - metadata: None, level: raid1 Oct 5 21:58:08 storageqe-109 INFO: UUID from bd.md_detail: 844460a1-6636-1ac4-c417-b37e968f89ad Oct 5 21:58:08 storageqe-109 INFO: Starting RAID deactivation and activation test Oct 5 21:58:08 storageqe-109 INFO: Pre-deactivation check - device exists: True INFO: bd.md_deactivate returned: True Oct 5 21:58:08 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:58:08 storageqe-109 kernel: md: md127 stopped. Oct 5 21:58:08 storageqe-109 INFO: bd.md_deactivate returned: True INFO: Post-deactivation check - device exists: False INFO: Attempting to activate RAID using bd.md_activate INFO: Activation parameters: Device: /dev/md/testraid_activate Members: ['/dev/nvme0n1', '/dev/sdb'] UUID: 844460a1-6636-1ac4-c417-b37e968f89ad Oct 5 21:58:09 storageqe-109 INFO: Post-deactivation check - device exists: False Oct 5 21:58:09 storageqe-109 INFO: Attempting to activate RAID using bd.md_activate Oct 5 21:58:09 storageqe-109 INFO: Activation parameters: Oct 5 21:58:09 storageqe-109 Device: /dev/md/testraid_activate Oct 5 21:58:09 storageqe-109 Members: ['/dev/nvme0n1', '/dev/sdb'] Oct 5 21:58:09 storageqe-109 UUID: 844460a1-6636-1ac4-c417-b37e968f89ad Oct 5 21:58:09 storageqe-109 kernel: md: md127 stopped. Oct 5 21:58:09 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:58:09 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:58:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: bd.md_activate returned: True INFO: RAID activation successful, continuing verification... Oct 5 21:58:09 storageqe-109 INFO: bd.md_activate returned: True Oct 5 21:58:09 storageqe-109 INFO: RAID activation successful, continuing verification... INFO: Scanning activated array: return code=1, output= INFO: Original device still exists: /dev/md/testraid_activate INFO: Testing second deactivation and run INFO: Second deactivation successful Oct 5 21:58:10 storageqe-109 INFO: Scanning activated array: return code=1, output= Oct 5 21:58:10 storageqe-109 INFO: Original device still exists: /dev/md/testraid_activate Oct 5 21:58:10 storageqe-109 INFO: Testing second deactivation and run Oct 5 21:58:10 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:58:10 storageqe-109 kernel: md: md127 stopped. Oct 5 21:58:10 storageqe-109 INFO: Second deactivation successful INFO: Testing bd.md_run INFO: Re-activating array for md_run test... Oct 5 21:58:11 storageqe-109 INFO: Testing bd.md_run Oct 5 21:58:11 storageqe-109 INFO: Re-activating array for md_run test... INFO: Re-activation result: True INFO: bd.md_run(/dev/md/testraid_activate) returned: True Oct 5 21:58:11 storageqe-109 kernel: md: md127 stopped. Oct 5 21:58:11 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:58:11 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:58:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:58:11 storageqe-109 INFO: Re-activation result: True Oct 5 21:58:12 storageqe-109 INFO: bd.md_run(/dev/md/testraid_activate) returned: True INFO: Device exists after run: True Oct 5 21:58:13 storageqe-109 INFO: Device exists after run: True Oct 5 21:58:13 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:58:13 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested activate and run functions Oct 5 21:58:15 storageqe-109 INFO: Successfully tested activate and run functions INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_raid_activate_run #### INFO: #### will start test_raid_failure_and_recovery[raid1-2] ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:58:21 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 21:58:21 storageqe-109 INFO: #### END test_raid_activate_run #### Oct 5 21:58:21 storageqe-109 INFO: #### will start test_raid_failure_and_recovery[raid1-2] ##### Oct 5 21:58:21 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:58:26 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:58:26 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 21:58:26 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 21:58:26 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 21:58:26 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 21:58:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 21:58:58 storageqe-109 kernel: md: md127: resync done. INFO: Waiting for initial RAID sync to complete... Oct 5 21:58:58 storageqe-109 INFO: Waiting for initial RAID sync to complete... INFO: Initial RAID state - clean: True, working_devices: 2 INFO: Failing disk /dev/sdd in /dev/md/testraid_recovery_raid1 INFO: Waiting for RAID operations to settle before removing failed device... Oct 5 21:59:00 storageqe-109 INFO: Initial RAID state - clean: True, working_devices: 2 Oct 5 21:59:00 storageqe-109 INFO: Failing disk /dev/sdd in /dev/md/testraid_recovery_raid1 Oct 5 21:59:00 storageqe-109 kernel: md/raid1:md127: Disk failure on sdd, disabling device.#012md/raid1:md127: Operation continuing on 1 devices. Oct 5 21:59:00 storageqe-109 INFO: Waiting for RAID operations to settle before removing failed device... INFO: Removing failed disk /dev/sdd from /dev/md/testraid_recovery_raid1 INFO: Adding new disk /dev/sde (size: 7GB) to trigger rebuild Oct 5 21:59:02 storageqe-109 INFO: Removing failed disk /dev/sdd from /dev/md/testraid_recovery_raid1 Oct 5 21:59:02 storageqe-109 INFO: Adding new disk /dev/sde (size: 7GB) to trigger rebuild INFO: Waiting for RAID recovery to complete... Oct 5 21:59:02 storageqe-109 INFO: Waiting for RAID recovery to complete... Oct 5 21:59:02 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 21:59:34 storageqe-109 kernel: md: md127: recover done. Oct 5 21:59:34 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 21:59:34 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested failure and recovery for raid1 Oct 5 21:59:37 storageqe-109 INFO: Successfully tested failure and recovery for raid1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_raid_failure_and_recovery[raid1-2] #### INFO: #### will start test_raid_failure_and_recovery[raid5-3] ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:59:43 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 21:59:43 storageqe-109 INFO: #### END test_raid_failure_and_recovery[raid1-2] #### Oct 5 21:59:43 storageqe-109 INFO: #### will start test_raid_failure_and_recovery[raid5-3] ##### Oct 5 21:59:43 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: raid parameter raid_level raid5, raid_mem ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:59:48 storageqe-109 INFO: raid parameter raid_level raid5, raid_mem ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 21:59:48 storageqe-109 kernel: md/raid:md127: device sdb operational as raid disk 1 Oct 5 21:59:48 storageqe-109 kernel: md/raid:md127: device nvme0n1 operational as raid disk 0 Oct 5 21:59:48 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 21:59:48 storageqe-109 kernel: md127: detected capacity change from 0 to 25165824 Oct 5 21:59:48 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 21:59:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: Waiting for initial RAID sync to complete... Oct 5 21:59:50 storageqe-109 INFO: Waiting for initial RAID sync to complete... INFO: Initial RAID state - clean: False, working_devices: 3 INFO: Failing disk /dev/sdc in /dev/md/testraid_recovery_raid5 INFO: Waiting for RAID operations to settle before removing failed device... Oct 5 21:59:52 storageqe-109 INFO: Initial RAID state - clean: False, working_devices: 3 Oct 5 21:59:52 storageqe-109 INFO: Failing disk /dev/sdc in /dev/md/testraid_recovery_raid5 Oct 5 21:59:52 storageqe-109 kernel: md/raid:md127: Disk failure on sdc, disabling device. Oct 5 21:59:52 storageqe-109 kernel: md/raid:md127: Operation continuing on 2 devices. Oct 5 21:59:52 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 21:59:52 storageqe-109 INFO: Waiting for RAID operations to settle before removing failed device... INFO: Removing failed disk /dev/sdc from /dev/md/testraid_recovery_raid5 INFO: Adding new disk /dev/sdd (size: 7GB) to trigger rebuild Oct 5 21:59:54 storageqe-109 INFO: Removing failed disk /dev/sdc from /dev/md/testraid_recovery_raid5 Oct 5 21:59:54 storageqe-109 INFO: Adding new disk /dev/sdd (size: 7GB) to trigger rebuild INFO: Waiting for RAID recovery to complete... Oct 5 21:59:54 storageqe-109 INFO: Waiting for RAID recovery to complete... Oct 5 21:59:54 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 22:00:26 storageqe-109 kernel: md: md127: recover done. Oct 5 22:00:26 storageqe-109 kernel: md127: detected capacity change from 25165824 to 0 Oct 5 22:00:26 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested failure and recovery for raid5 Oct 5 22:00:29 storageqe-109 INFO: Successfully tested failure and recovery for raid5 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_raid_failure_and_recovery[raid5-3] #### INFO: #### will start test_raid_failure_conditions ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:00:35 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:00:35 storageqe-109 INFO: #### END test_raid_failure_and_recovery[raid5-3] #### Oct 5 22:00:35 storageqe-109 INFO: #### will start test_raid_failure_conditions ##### Oct 5 22:00:35 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: Testing RAID5 creation with insufficient disks INFO: raid parameter raid_level raid5, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:00:40 storageqe-109 INFO: Testing RAID5 creation with insufficient disks Oct 5 22:00:40 storageqe-109 INFO: raid parameter raid_level raid5, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:00:40 storageqe-109 kernel: md/raid:md127: device nvme0n1 operational as raid disk 0 Oct 5 22:00:40 storageqe-109 kernel: md/raid:md127: raid level 5 active with 1 out of 2 devices, algorithm 2 Oct 5 22:00:40 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:00:40 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 22:00:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:00:42 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 22:00:42 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:00:42 storageqe-109 kernel: md: md127 stopped. INFO: Testing adding an invalid path to an array INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:00:44 storageqe-109 INFO: Testing adding an invalid path to an array Oct 5 22:00:45 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:00:45 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:00:45 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:00:45 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:00:45 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:00:45 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:01:11 storageqe-109 kernel: md: md127: resync done. Oct 5 22:01:12 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:01:12 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested failure conditions Oct 5 22:01:14 storageqe-109 INFO: Successfully tested failure conditions INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_raid_failure_conditions #### INFO: #### will start test_raid_metadata_versions[0.90] ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:01:20 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:01:20 storageqe-109 INFO: #### END test_raid_failure_conditions #### Oct 5 22:01:20 storageqe-109 INFO: #### will start test_raid_metadata_versions[0.90] ##### Oct 5 22:01:20 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: Creating RAID1 with metadata version 0.90 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 0.90, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:01:25 storageqe-109 INFO: Creating RAID1 with metadata version 0.90 Oct 5 22:01:25 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 0.90, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:01:25 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:01:25 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:01:25 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:01:25 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:01:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:01:52 storageqe-109 kernel: md: md127: resync done. Oct 5 22:01:52 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:01:52 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested RAID1 with metadata version 0.90 Oct 5 22:01:55 storageqe-109 INFO: Successfully tested RAID1 with metadata version 0.90 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_raid_metadata_versions[0.90] #### INFO: #### will start test_raid_metadata_versions[1.0] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:02:01 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:02:01 storageqe-109 INFO: #### END test_raid_metadata_versions[0.90] #### Oct 5 22:02:01 storageqe-109 INFO: #### will start test_raid_metadata_versions[1.0] ##### Oct 5 22:02:01 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Creating RAID1 with metadata version 1.0 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:02:06 storageqe-109 INFO: Creating RAID1 with metadata version 1.0 Oct 5 22:02:06 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:02:06 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:02:06 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:02:06 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:02:06 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:02:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:02:32 storageqe-109 kernel: md: md127: resync done. Oct 5 22:02:33 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:02:33 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested RAID1 with metadata version 1.0 Oct 5 22:02:35 storageqe-109 INFO: Successfully tested RAID1 with metadata version 1.0 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_raid_metadata_versions[1.0] #### INFO: #### will start test_raid_metadata_versions[1.1] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:02:41 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:02:41 storageqe-109 INFO: #### END test_raid_metadata_versions[1.0] #### Oct 5 22:02:41 storageqe-109 INFO: #### will start test_raid_metadata_versions[1.1] ##### Oct 5 22:02:41 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: Creating RAID1 with metadata version 1.1 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdd', '/dev/sde'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:02:46 storageqe-109 INFO: Creating RAID1 with metadata version 1.1 Oct 5 22:02:46 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdd', '/dev/sde'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:02:47 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:02:47 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:02:47 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:02:47 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:02:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:03:13 storageqe-109 kernel: md: md127: resync done. Oct 5 22:03:14 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:03:14 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested RAID1 with metadata version 1.1 Oct 5 22:03:16 storageqe-109 INFO: Successfully tested RAID1 with metadata version 1.1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_raid_metadata_versions[1.1] #### INFO: #### will start test_raid_metadata_versions[1.2] ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:03:22 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:03:22 storageqe-109 INFO: #### END test_raid_metadata_versions[1.1] #### Oct 5 22:03:22 storageqe-109 INFO: #### will start test_raid_metadata_versions[1.2] ##### Oct 5 22:03:22 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: Creating RAID1 with metadata version 1.2 INFO: raid parameter raid_level raid1, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:03:27 storageqe-109 INFO: Creating RAID1 with metadata version 1.2 Oct 5 22:03:27 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:03:27 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:03:27 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:03:27 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:03:27 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:03:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:03:53 storageqe-109 kernel: md: md127: resync done. Oct 5 22:03:54 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:03:54 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested RAID1 with metadata version 1.2 Oct 5 22:03:56 storageqe-109 INFO: Successfully tested RAID1 with metadata version 1.2 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_raid_metadata_versions[1.2] #### INFO: #### will start test_raid_grow_array ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:04:03 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:04:03 storageqe-109 INFO: #### END test_raid_metadata_versions[1.2] #### Oct 5 22:04:03 storageqe-109 INFO: #### will start test_raid_grow_array ##### Oct 5 22:04:03 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:04:08 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.1, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:04:08 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:04:08 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:04:08 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:04:08 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:04:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:04:34 storageqe-109 kernel: md: md127: resync done. Oct 5 22:04:34 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 22:04:35 storageqe-109 dnf[89514]: Updating Subscription Management repositories. Oct 5 22:04:35 storageqe-109 dnf[89514]: Unable to read consumer identity Oct 5 22:04:35 storageqe-109 dnf[89514]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-AppStream 480 kB/s | 2.8 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-AppStream-debuginfo 469 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-BaseOS 685 kB/s | 2.7 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-BaseOS-debuginfo 484 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-CRB 736 kB/s | 2.7 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-CRB-debuginfo 500 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-HighAvailability 754 kB/s | 2.8 kB 00:00 INFO: Adding /dev/sde as a spare to /dev/md/testraid_grow Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-HighAvailability-debuginfo 560 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-NFV 664 kB/s | 2.7 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-NFV-debuginfo 371 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-RT 711 kB/s | 2.7 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-RT-debuginfo 465 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-SAP 737 kB/s | 2.7 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-SAP-debuginfo 503 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-SAPHANA 669 kB/s | 2.7 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-SAPHANA-debuginfo 430 kB/s | 1.5 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: Errors during downloading metadata for repository 'beaker-client': Oct 5 22:04:35 storageqe-109 dnf[89514]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 22:04:35 storageqe-109 dnf[89514]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 5 22:04:35 storageqe-109 INFO: Adding /dev/sde as a spare to /dev/md/testraid_grow INFO: Growing RAID array /dev/md/testraid_grow to 3 devices INFO: Waiting for RAID reshape to complete... Oct 5 22:04:35 storageqe-109 INFO: Growing RAID array /dev/md/testraid_grow to 3 devices Oct 5 22:04:35 storageqe-109 INFO: Waiting for RAID reshape to complete... Oct 5 22:04:35 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 22:04:35 storageqe-109 dnf[89514]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 5 22:04:35 storageqe-109 dnf[89514]: Google Cloud CLI 5.1 kB/s | 1.4 kB 00:00 Oct 5 22:04:36 storageqe-109 dnf[89514]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 INFO: Waiting for any post-reshape sync operations... Oct 5 22:04:37 storageqe-109 dnf[89514]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 5 22:04:37 storageqe-109 INFO: Waiting for any post-reshape sync operations... Oct 5 22:04:37 storageqe-109 dnf[89514]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 5 22:04:37 storageqe-109 dnf[89514]: Ignoring repositories: beaker-client Oct 5 22:04:37 storageqe-109 dnf[89514]: Metadata cache created. Oct 5 22:04:38 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 22:04:38 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. INFO: RAID array state after grow - clean: False, raid_devices: 3 INFO: Array not clean after reshape, this is acceptable as sync may still be in progress Oct 5 22:04:39 storageqe-109 INFO: RAID array state after grow - clean: False, raid_devices: 3 Oct 5 22:04:39 storageqe-109 INFO: Array not clean after reshape, this is acceptable as sync may still be in progress Oct 5 22:04:39 storageqe-109 kernel: md: md127: recover interrupted. Oct 5 22:04:39 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:04:39 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested growing a RAID1 array Oct 5 22:04:41 storageqe-109 systemd[1]: session-3.scope: Deactivated successfully. Oct 5 22:04:41 storageqe-109 systemd[1]: session-5.scope: Deactivated successfully. Oct 5 22:04:41 storageqe-109 systemd-logind[1011]: Session 2 logged out. Waiting for processes to exit. Oct 5 22:04:41 storageqe-109 systemd-logind[1011]: Session 3 logged out. Waiting for processes to exit. Oct 5 22:04:41 storageqe-109 systemd-logind[1011]: Removed session 3. Oct 5 22:04:41 storageqe-109 systemd-logind[1011]: Session 5 logged out. Waiting for processes to exit. Oct 5 22:04:41 storageqe-109 systemd-logind[1011]: Removed session 5. Oct 5 22:04:41 storageqe-109 systemd[1]: session-2.scope: Deactivated successfully. Oct 5 22:04:41 storageqe-109 systemd-logind[1011]: Removed session 2. Oct 5 22:04:41 storageqe-109 systemd-logind[1011]: Session 4 logged out. Waiting for processes to exit. Oct 5 22:04:41 storageqe-109 INFO: Successfully tested growing a RAID1 array INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_raid_grow_array #### INFO: #### will start test_uuid_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:04:48 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:04:48 storageqe-109 INFO: #### END test_raid_grow_array #### Oct 5 22:04:48 storageqe-109 INFO: #### will start test_uuid_operations ##### Oct 5 22:04:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:04:53 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/nvme0n1', '/dev/sdb'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:04:53 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:04:53 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:04:53 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 22:04:53 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:04:53 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:05:24 storageqe-109 kernel: md: md127: resync done. INFO: Device UUID from md_detail: 857e0c8b-760f-b105-44b0-1e44aa847f2b INFO: Testing md_get_md_uuid with UUID: 857e0c8b-760f-b105-44b0-1e44aa847f2b INFO: Processed UUID: 857e0c8b:760fb105:44b01e44:aa847f2b INFO: Testing md_canonicalize_uuid with UUID: 857e0c8b-760f-b105-44b0-1e44aa847f2b INFO: md_canonicalize_uuid may not support this UUID format: g-bd-md-error-quark: malformed or invalid UUID: 857e0c8b-760f-b105-44b0-1e44aa847f2b (3) Oct 5 22:05:25 storageqe-109 INFO: Device UUID from md_detail: 857e0c8b-760f-b105-44b0-1e44aa847f2b Oct 5 22:05:25 storageqe-109 INFO: Testing md_get_md_uuid with UUID: 857e0c8b-760f-b105-44b0-1e44aa847f2b Oct 5 22:05:25 storageqe-109 INFO: Processed UUID: 857e0c8b:760fb105:44b01e44:aa847f2b Oct 5 22:05:25 storageqe-109 INFO: Testing md_canonicalize_uuid with UUID: 857e0c8b-760f-b105-44b0-1e44aa847f2b Oct 5 22:05:25 storageqe-109 INFO: md_canonicalize_uuid may not support this UUID format: g-bd-md-error-quark: malformed or invalid UUID: 857e0c8b-760f-b105-44b0-1e44aa847f2b (3) Oct 5 22:05:25 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 22:05:25 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested UUID operations Oct 5 22:05:27 storageqe-109 INFO: Successfully tested UUID operations INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_uuid_operations #### INFO: #### will start test_status_and_superblock_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:05:33 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:05:33 storageqe-109 INFO: #### END test_uuid_operations #### Oct 5 22:05:33 storageqe-109 INFO: #### will start test_status_and_superblock_operations ##### Oct 5 22:05:33 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:05:38 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:05:39 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:05:39 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:05:39 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 22:05:39 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:05:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:06:10 storageqe-109 kernel: md: md127: resync done. INFO: Testing md_get_status for /dev/md/testraid_status INFO: RAID status: clean INFO: Testing md_get_superblock_size INFO: Superblock size for version 1.0: 2097152 bytes INFO: Superblock size for version 1.1: 1048576 bytes INFO: Superblock size for version 1.2: 1048576 bytes Oct 5 22:06:11 storageqe-109 INFO: Testing md_get_status for /dev/md/testraid_status Oct 5 22:06:11 storageqe-109 INFO: RAID status: clean Oct 5 22:06:11 storageqe-109 INFO: Testing md_get_superblock_size Oct 5 22:06:11 storageqe-109 INFO: Superblock size for version 1.0: 2097152 bytes Oct 5 22:06:11 storageqe-109 INFO: Superblock size for version 1.1: 1048576 bytes Oct 5 22:06:11 storageqe-109 INFO: Superblock size for version 1.2: 1048576 bytes Oct 5 22:06:11 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 22:06:11 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested status and superblock operations Oct 5 22:06:13 storageqe-109 INFO: Successfully tested status and superblock operations INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_status_and_superblock_operations #### INFO: #### will start test_device_nomination_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:06:19 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:06:19 storageqe-109 INFO: #### END test_status_and_superblock_operations #### Oct 5 22:06:19 storageqe-109 INFO: #### will start test_device_nomination_operations ##### Oct 5 22:06:19 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:06:24 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:06:24 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:06:24 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:06:24 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 22:06:24 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:06:24 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:06:56 storageqe-109 kernel: md: md127: resync done. INFO: Adding spare device /dev/sdb INFO: Testing md_nominate for /dev/sdb INFO: md_nominate not supported or failed: BlockDev.md_nominate() takes exactly 1 argument (2 given) INFO: Testing md_denominate for /dev/sdb INFO: md_denominate not supported or failed: BlockDev.md_denominate() takes exactly 1 argument (2 given) Oct 5 22:06:56 storageqe-109 INFO: Adding spare device /dev/sdb Oct 5 22:06:56 storageqe-109 INFO: Testing md_nominate for /dev/sdb Oct 5 22:06:56 storageqe-109 INFO: md_nominate not supported or failed: BlockDev.md_nominate() takes exactly 1 argument (2 given) Oct 5 22:06:56 storageqe-109 INFO: Testing md_denominate for /dev/sdb Oct 5 22:06:56 storageqe-109 INFO: md_denominate not supported or failed: BlockDev.md_denominate() takes exactly 1 argument (2 given) Oct 5 22:06:57 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 22:06:57 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested device nomination operations Oct 5 22:06:59 storageqe-109 INFO: Successfully tested device nomination operations INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_device_nomination_operations #### INFO: #### will start test_technology_availability ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:07:05 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:07:05 storageqe-109 INFO: #### END test_device_nomination_operations #### Oct 5 22:07:05 storageqe-109 INFO: #### will start test_technology_availability ##### Oct 5 22:07:05 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: Testing md_is_tech_avail INFO: Technology mode available: True INFO: Technology mode available: True INFO: Technology mode available: True INFO: Technology mode available: True INFO: Successfully tested technology availability Oct 5 22:07:10 storageqe-109 INFO: Testing md_is_tech_avail Oct 5 22:07:10 storageqe-109 INFO: Technology mode available: True Oct 5 22:07:10 storageqe-109 INFO: Technology mode available: True Oct 5 22:07:10 storageqe-109 INFO: Technology mode available: True Oct 5 22:07:10 storageqe-109 INFO: Technology mode available: True Oct 5 22:07:10 storageqe-109 INFO: Successfully tested technology availability INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_technology_availability #### INFO: #### will start test_name_node_conversion ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:07:16 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:07:16 storageqe-109 INFO: #### END test_technology_availability #### Oct 5 22:07:16 storageqe-109 INFO: #### will start test_name_node_conversion ##### Oct 5 22:07:16 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:07:21 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '6G'} Oct 5 22:07:21 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:07:21 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:07:21 storageqe-109 kernel: md127: detected capacity change from 0 to 12582912 Oct 5 22:07:22 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:07:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:07:53 storageqe-109 kernel: md: md127: resync done. INFO: Testing md_name_from_node for /dev/md/testraid_namenode INFO: md_name_from_node failed (may not be supported): g-bd-md-error-quark: No name found for the node 'md/testraid_namenode' (4) INFO: Testing md_node_from_name for testraid_namenode INFO: Node from name 'testraid_namenode': md127 Oct 5 22:07:54 storageqe-109 INFO: Testing md_name_from_node for /dev/md/testraid_namenode Oct 5 22:07:54 storageqe-109 INFO: md_name_from_node failed (may not be supported): g-bd-md-error-quark: No name found for the node 'md/testraid_namenode' (4) Oct 5 22:07:54 storageqe-109 INFO: Testing md_node_from_name for testraid_namenode Oct 5 22:07:54 storageqe-109 INFO: Node from name 'testraid_namenode': md127 Oct 5 22:07:54 storageqe-109 kernel: md127: detected capacity change from 12582912 to 0 Oct 5 22:07:54 storageqe-109 kernel: md: md127 stopped. INFO: Successfully tested name/node conversion Oct 5 22:07:56 storageqe-109 INFO: Successfully tested name/node conversion INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_name_node_conversion #### INFO: #### will start test_error_conditions_and_edge_cases ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:08:02 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:08:02 storageqe-109 INFO: #### END test_name_node_conversion #### Oct 5 22:08:02 storageqe-109 INFO: #### will start test_error_conditions_and_edge_cases ##### Oct 5 22:08:02 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: Testing error conditions and edge cases INFO: Testing operations with invalid device paths INFO: Testing UUID operations with invalid input INFO: md_get_superblock_size accepts various parameter values INFO: Testing operations on non-RAID devices INFO: Successfully tested error conditions and edge cases Oct 5 22:08:07 storageqe-109 INFO: Testing error conditions and edge cases Oct 5 22:08:07 storageqe-109 INFO: Testing operations with invalid device paths Oct 5 22:08:07 storageqe-109 INFO: Testing UUID operations with invalid input Oct 5 22:08:07 storageqe-109 INFO: md_get_superblock_size accepts various parameter values Oct 5 22:08:07 storageqe-109 INFO: Testing operations on non-RAID devices Oct 5 22:08:07 storageqe-109 INFO: Successfully tested error conditions and edge cases INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_error_conditions_and_edge_cases #### Oct 5 22:08:13 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:13 storageqe-109 INFO: #### END test_error_conditions_and_edge_cases #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 22:08:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 22:08:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 22:08:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 22:08:25 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_nvme_infos ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:25 storageqe-109 INFO: #### will start test_nvme_infos ##### Oct 5 22:08:25 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:31 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 22:08:31 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 22:08:32 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 22:08:33 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 22:08:33 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 22:08:34 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 22:08:35 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_infos #### INFO: #### will start test_nvm_con_infos ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:40 storageqe-109 INFO: #### END test_nvme_infos #### Oct 5 22:08:40 storageqe-109 INFO: #### will start test_nvm_con_infos ##### Oct 5 22:08:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:45 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvm_con_infos #### INFO: #### will start test_nvme_smart_log ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:50 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:08:50 storageqe-109 INFO: #### END test_nvm_con_infos #### Oct 5 22:08:50 storageqe-109 INFO: #### will start test_nvme_smart_log ##### Oct 5 22:08:50 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_smart_log #### INFO: #### will start test_nvme_get_self_test ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:09:01 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:09:01 storageqe-109 INFO: #### END test_nvme_smart_log #### Oct 5 22:09:01 storageqe-109 INFO: #### will start test_nvme_get_self_test ##### Oct 5 22:09:01 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_get_self_test #### INFO: #### will start test_nvme_host_identifiers ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:09:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:09:15 storageqe-109 INFO: #### END test_nvme_get_self_test #### Oct 5 22:09:15 storageqe-109 INFO: #### will start test_nvme_host_identifiers ##### Oct 5 22:09:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_host_identifiers #### INFO: #### will start test_nvme_sanitize ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:09:25 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:09:25 storageqe-109 INFO: #### END test_nvme_host_identifiers #### Oct 5 22:09:25 storageqe-109 INFO: #### will start test_nvme_sanitize ##### Oct 5 22:09:25 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_sanitize #### INFO: #### will start test_nvme_sanitize_overwrite_params ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:10:35 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:10:35 storageqe-109 INFO: #### END test_nvme_sanitize #### Oct 5 22:10:35 storageqe-109 INFO: #### will start test_nvme_sanitize_overwrite_params ##### Oct 5 22:10:35 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_sanitize_overwrite_params #### INFO: #### will start test_nvme_controller_secure_erase ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:10:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:10:45 storageqe-109 INFO: #### END test_nvme_sanitize_overwrite_params #### Oct 5 22:10:45 storageqe-109 INFO: #### will start test_nvme_controller_secure_erase ##### Oct 5 22:10:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_controller_secure_erase #### INFO: #### will start test_nvme_controller_format ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:10:55 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:10:55 storageqe-109 INFO: #### END test_nvme_controller_secure_erase #### Oct 5 22:10:55 storageqe-109 INFO: #### will start test_nvme_controller_format ##### Oct 5 22:10:55 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:00 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_controller_format #### INFO: #### will start test_nvme_self_test_polling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:06 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:06 storageqe-109 INFO: #### END test_nvme_controller_format #### Oct 5 22:11:06 storageqe-109 INFO: #### will start test_nvme_self_test_polling ##### Oct 5 22:11:06 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_self_test_polling #### INFO: #### will start test_nvme_controller_format_invalid ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:21 storageqe-109 INFO: #### END test_nvme_self_test_polling #### Oct 5 22:11:21 storageqe-109 INFO: #### will start test_nvme_controller_format_invalid ##### Oct 5 22:11:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_controller_format_invalid #### INFO: #### will start test_nvme_error_log ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:31 storageqe-109 INFO: #### END test_nvme_controller_format_invalid #### Oct 5 22:11:31 storageqe-109 INFO: #### will start test_nvme_error_log ##### Oct 5 22:11:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_error_log #### INFO: #### will start test_nvme_find_controllers_for_namespace ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:41 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:41 storageqe-109 INFO: #### END test_nvme_error_log #### Oct 5 22:11:41 storageqe-109 INFO: #### will start test_nvme_find_controllers_for_namespace ##### Oct 5 22:11:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_find_controllers_for_namespace #### INFO: #### will start test_nvme_is_tech_avail ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:51 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:11:51 storageqe-109 INFO: #### END test_nvme_find_controllers_for_namespace #### Oct 5 22:11:51 storageqe-109 INFO: #### will start test_nvme_is_tech_avail ##### Oct 5 22:11:51 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_is_tech_avail #### INFO: #### will start test_nvme_connect_disconnect_loopback ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:01 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:01 storageqe-109 INFO: #### END test_nvme_is_tech_avail #### Oct 5 22:12:01 storageqe-109 kernel: loop0: detected capacity change from 0 to 4194304 Oct 5 22:12:01 storageqe-109 kernel: Key type psk registered Oct 5 22:12:01 storageqe-109 kernel: nvmet: unknown parameter 'nvme_loop' ignored Oct 5 22:12:01 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem libblockdev_nvmeof_subnqn Oct 5 22:12:01 storageqe-109 INFO: #### will start test_nvme_connect_disconnect_loopback ##### Oct 5 22:12:01 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_connect_disconnect_loopback #### INFO: #### will start test_nvme_disconnect_by_path ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:11 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:11 storageqe-109 INFO: #### END test_nvme_connect_disconnect_loopback #### Oct 5 22:12:11 storageqe-109 INFO: #### will start test_nvme_disconnect_by_path ##### Oct 5 22:12:11 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_disconnect_by_path #### INFO: #### will start test_nvme_advanced_namespace_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:22 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:22 storageqe-109 INFO: #### END test_nvme_disconnect_by_path #### Oct 5 22:12:22 storageqe-109 INFO: #### will start test_nvme_advanced_namespace_features ##### Oct 5 22:12:22 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_advanced_namespace_features #### INFO: #### will start test_nvme_advanced_controller_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:32 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:32 storageqe-109 INFO: #### END test_nvme_advanced_namespace_features #### Oct 5 22:12:32 storageqe-109 INFO: #### will start test_nvme_advanced_controller_features ##### Oct 5 22:12:32 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_advanced_controller_features #### INFO: #### will start test_nvme_smart_critical_warnings_comprehensive ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:42 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:42 storageqe-109 INFO: #### END test_nvme_advanced_controller_features #### Oct 5 22:12:42 storageqe-109 INFO: #### will start test_nvme_smart_critical_warnings_comprehensive ##### Oct 5 22:12:42 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_smart_critical_warnings_comprehensive #### INFO: #### will start test_nvme_error_handling_comprehensive ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:52 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:12:52 storageqe-109 INFO: #### END test_nvme_smart_critical_warnings_comprehensive #### Oct 5 22:12:52 storageqe-109 INFO: #### will start test_nvme_error_handling_comprehensive ##### Oct 5 22:12:52 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_error_handling_comprehensive #### INFO: #### will start test_nvme_performance_and_stress ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:02 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:02 storageqe-109 INFO: #### END test_nvme_error_handling_comprehensive #### Oct 5 22:13:02 storageqe-109 INFO: #### will start test_nvme_performance_and_stress ##### Oct 5 22:13:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_performance_and_stress #### INFO: #### will start test_nvme_host_management_comprehensive ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:13 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 22:13:13 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:13 storageqe-109 INFO: #### END test_nvme_performance_and_stress #### Oct 5 22:13:13 storageqe-109 INFO: #### will start test_nvme_host_management_comprehensive ##### Oct 5 22:13:13 storageqe-109 systemd[1]: Starting fwupd.service - Firmware update daemon... Oct 5 22:13:13 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:14 storageqe-109 fwupd[93292]: 02:13:14.146 FuMain fwupd 1.9.31 ready for requests (locale en_US.UTF-8) Oct 5 22:13:14 storageqe-109 systemd[1]: Started fwupd.service - Firmware update daemon. Oct 5 22:13:14 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 22:13:14 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_host_management_comprehensive #### INFO: #### will start test_nvme_version_detection_and_capabilities ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:23 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:23 storageqe-109 INFO: #### END test_nvme_host_management_comprehensive #### Oct 5 22:13:23 storageqe-109 INFO: #### will start test_nvme_version_detection_and_capabilities ##### Oct 5 22:13:23 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_version_detection_and_capabilities #### INFO: #### will start test_nvme_version_specific_command_support ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:33 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:33 storageqe-109 INFO: #### END test_nvme_version_detection_and_capabilities #### Oct 5 22:13:33 storageqe-109 INFO: #### will start test_nvme_version_specific_command_support ##### Oct 5 22:13:33 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_version_specific_command_support #### INFO: #### will start test_nvme_version_compatibility_matrix ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:43 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:43 storageqe-109 INFO: #### END test_nvme_version_specific_command_support #### Oct 5 22:13:43 storageqe-109 INFO: #### will start test_nvme_version_compatibility_matrix ##### Oct 5 22:13:43 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_version_compatibility_matrix #### INFO: #### will start test_nvme_tcp_fio_performance ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:53 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:53 storageqe-109 INFO: #### END test_nvme_version_compatibility_matrix #### Oct 5 22:13:53 storageqe-109 INFO: #### will start test_nvme_tcp_fio_performance ##### Oct 5 22:13:53 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:13:59 storageqe-109 kernel: Warning: Unmaintained driver is detected: nvmet_tcp Oct 5 22:13:59 storageqe-109 kernel: Warning: Unmaintained driver is detected: nvmet_tcp_init Oct 5 22:13:59 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-qrVQgTwN Oct 5 22:13:59 storageqe-109 kernel: nvmet_tcp: enabling port 4420 (127.0.0.1:4420) Oct 5 22:14:04 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-qrVQgTwN for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:14:04 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:14:04 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:14:04 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-qrVQgTwN", addr 127.0.0.1:4420, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:14:07 storageqe-109 kernel: nvme1n1: Oct 5 22:14:07 storageqe-109 kernel: nvme1n1: p1 INFO: Running fio test on /dev/nvme1n1p1 with io_uring Oct 5 22:14:12 storageqe-109 INFO: Running fio test on /dev/nvme1n1p1 with io_uring Oct 5 22:14:12 storageqe-109 kernel: TECH PREVIEW: io_uring may not be fully supported.#012Please review provided documentation for limitations. Oct 5 22:14:12 storageqe-109 kernel: TECH PREVIEW: io_uring may not be fully supported.#012Please review provided documentation for limitations. INFO: Running fio test on /dev/nvme1n1p1 with libaio Oct 5 22:14:13 storageqe-109 INFO: Running fio test on /dev/nvme1n1p1 with libaio Oct 5 22:14:15 storageqe-109 kernel: nvme nvme1: starting error recovery Oct 5 22:14:15 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 5 22:14:15 storageqe-109 kernel: nvme nvme1: queue 1 socket state 11 Oct 5 22:14:15 storageqe-109 kernel: nvme nvme1: Reconnecting in 10 seconds... Oct 5 22:14:15 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-qrVQgTwN" Oct 5 22:14:15 storageqe-109 kernel: nvme nvme1: Property Set error: 880, offset 0x14 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_tcp_fio_performance #### INFO: #### will start test_nvme_tcp_device_lifecycle ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:14:22 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:14:22 storageqe-109 INFO: #### END test_nvme_tcp_fio_performance #### Oct 5 22:14:22 storageqe-109 INFO: #### will start test_nvme_tcp_device_lifecycle ##### Oct 5 22:14:22 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:14:27 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-DVSWdTif Oct 5 22:14:27 storageqe-109 kernel: nvmet_tcp: enabling port 4421 (127.0.0.1:4421) Oct 5 22:14:32 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-DVSWdTif for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:14:32 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:14:32 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:14:32 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-DVSWdTif", addr 127.0.0.1:4421, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:14:36 storageqe-109 kernel: nvme1n1: Oct 5 22:14:36 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:14:36 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-DVSWdTif" Oct 5 22:14:39 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-JUfOLenB Oct 5 22:14:39 storageqe-109 kernel: nvmet_tcp: enabling port 4422 (127.0.0.1:4422) Oct 5 22:14:44 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-JUfOLenB for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:14:44 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:14:44 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:14:44 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-JUfOLenB", addr 127.0.0.1:4422, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:14:47 storageqe-109 kernel: nvme1n1: Oct 5 22:14:47 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:14:47 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-JUfOLenB" Oct 5 22:14:50 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-BkQrtlGg Oct 5 22:14:50 storageqe-109 kernel: nvmet_tcp: enabling port 4423 (127.0.0.1:4423) Oct 5 22:14:56 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-BkQrtlGg for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:14:56 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:14:56 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:14:56 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-BkQrtlGg", addr 127.0.0.1:4423, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:14:59 storageqe-109 kernel: nvme1n1: Oct 5 22:14:59 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:14:59 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-BkQrtlGg" Oct 5 22:15:02 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-YCoMZvXj Oct 5 22:15:02 storageqe-109 kernel: nvmet_tcp: enabling port 4424 (127.0.0.1:4424) Oct 5 22:15:07 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-YCoMZvXj for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:15:07 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:15:07 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:15:07 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-YCoMZvXj", addr 127.0.0.1:4424, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:15:10 storageqe-109 kernel: nvme1n1: Oct 5 22:15:10 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:15:11 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-YCoMZvXj" Oct 5 22:15:14 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-tJGNbYHw Oct 5 22:15:14 storageqe-109 kernel: nvmet_tcp: enabling port 4425 (127.0.0.1:4425) Oct 5 22:15:19 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-tJGNbYHw for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:15:19 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:15:19 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:15:19 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-tJGNbYHw", addr 127.0.0.1:4425, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:15:22 storageqe-109 kernel: nvme1n1: Oct 5 22:15:22 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:15:22 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-tJGNbYHw" Oct 5 22:15:25 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-yPUMDwop Oct 5 22:15:25 storageqe-109 kernel: nvmet_tcp: enabling port 4426 (127.0.0.1:4426) Oct 5 22:15:31 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-yPUMDwop for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:15:31 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:15:31 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:15:31 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-yPUMDwop", addr 127.0.0.1:4426, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:15:34 storageqe-109 kernel: nvme1n1: Oct 5 22:15:34 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:15:34 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-yPUMDwop" Oct 5 22:15:37 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-SCUkxGZM Oct 5 22:15:37 storageqe-109 kernel: nvmet_tcp: enabling port 4427 (127.0.0.1:4427) Oct 5 22:15:42 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-SCUkxGZM for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:15:42 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:15:42 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:15:42 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-SCUkxGZM", addr 127.0.0.1:4427, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:15:45 storageqe-109 kernel: nvme1n1: Oct 5 22:15:45 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:15:45 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-SCUkxGZM" Oct 5 22:15:49 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-HplMwQTG Oct 5 22:15:49 storageqe-109 kernel: nvmet_tcp: enabling port 4428 (127.0.0.1:4428) Oct 5 22:15:54 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-HplMwQTG for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:15:54 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:15:54 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:15:54 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-HplMwQTG", addr 127.0.0.1:4428, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:15:57 storageqe-109 kernel: nvme1n1: Oct 5 22:15:57 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:15:57 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-HplMwQTG" Oct 5 22:16:00 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-uXMAGkxe Oct 5 22:16:00 storageqe-109 kernel: nvmet_tcp: enabling port 4429 (127.0.0.1:4429) Oct 5 22:16:05 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-uXMAGkxe for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:16:05 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:16:05 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:16:05 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-uXMAGkxe", addr 127.0.0.1:4429, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:16:09 storageqe-109 kernel: nvme1n1: Oct 5 22:16:09 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:16:09 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-uXMAGkxe" Oct 5 22:16:12 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-tcp-target-vmNQAcpX Oct 5 22:16:12 storageqe-109 kernel: nvmet_tcp: enabling port 4430 (127.0.0.1:4430) Oct 5 22:16:17 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-tcp-target-vmNQAcpX for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:16:17 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:16:17 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:16:17 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-vmNQAcpX", addr 127.0.0.1:4430, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:16:20 storageqe-109 kernel: nvme1n1: Oct 5 22:16:20 storageqe-109 kernel: nvme1n1: p1 Oct 5 22:16:20 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-tcp-target-vmNQAcpX" INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_tcp_device_lifecycle #### INFO: #### will start test_nvme_tcp_remote_connection ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:16:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:16:30 storageqe-109 INFO: #### END test_nvme_tcp_device_lifecycle #### Oct 5 22:16:31 storageqe-109 INFO: #### will start test_nvme_tcp_remote_connection ##### Oct 5 22:16:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:16:39 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 5 22:16:40 storageqe-109 kernel: nvme nvme1: failed to connect socket: -101 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_tcp_remote_connection #### INFO: #### will start test_nvme_host_management ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:16:46 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:16:46 storageqe-109 INFO: #### END test_nvme_tcp_remote_connection #### Oct 5 22:16:46 storageqe-109 INFO: #### will start test_nvme_host_management ##### Oct 5 22:16:46 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_host_management #### INFO: #### will start test_nvme_connect_comprehensive_parameters ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:16:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:16:56 storageqe-109 INFO: #### END test_nvme_host_management #### Oct 5 22:16:56 storageqe-109 INFO: #### will start test_nvme_connect_comprehensive_parameters ##### Oct 5 22:16:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:01 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO Oct 5 22:17:01 storageqe-109 kernel: nvmet_tcp: enabling port 4431 (127.0.0.1:4431) Oct 5 22:17:03 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:17:03 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:17:03 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:17:03 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO", addr 127.0.0.1:4431, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:17:03 storageqe-109 kernel: nvme_fabrics: found same hostnqn nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 but different hostid aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee Oct 5 22:17:03 storageqe-109 kernel: nvmet: Created nvm controller 2 for subsystem nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:17:03 storageqe-109 kernel: nvme nvme2: creating 4 I/O queues. Oct 5 22:17:03 storageqe-109 kernel: nvme nvme2: mapped 4/0/0 default/read/poll queues. Oct 5 22:17:03 storageqe-109 kernel: nvme nvme2: new ctrl: NQN "nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO", addr 127.0.0.1:4431, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:17:03 storageqe-109 kernel: nvmet: connect request for invalid subsystem nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO! Oct 5 22:17:03 storageqe-109 kernel: nvme nvme3: Connect Invalid Data Parameter, subsysnqn "nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO" Oct 5 22:17:03 storageqe-109 kernel: nvme_fabrics: no handler found for transport invalid. Oct 5 22:17:03 storageqe-109 kernel: nvme_fabrics: no handler found for transport unknown. Oct 5 22:17:03 storageqe-109 kernel: nvme nvme3: rdma_resolve_addr failed (-19). Oct 5 22:17:03 storageqe-109 kernel: nvme_tcp: malformed address passed: 127.0.0.1:99999 Oct 5 22:17:03 storageqe-109 kernel: nvmet: connect request for invalid subsystem invalid-nqn-format! Oct 5 22:17:03 storageqe-109 kernel: nvme nvme3: Connect Invalid Data Parameter, subsysnqn "invalid-nqn-format" Oct 5 22:17:04 storageqe-109 kernel: nvme nvme3: failed to connect queue: 0 ret=16770 Oct 5 22:17:04 storageqe-109 kernel: nvme_fabrics: unknown parameter or missing value 'nqn=' in ctrl creation request Oct 5 22:17:04 storageqe-109 kernel: nvmet: connect request for invalid subsystem nqn.invalid! Oct 5 22:17:04 storageqe-109 kernel: nvme nvme3: Connect Invalid Data Parameter, subsysnqn "nqn.invalid" Oct 5 22:17:04 storageqe-109 kernel: nvme nvme3: failed to connect queue: 0 ret=16770 Oct 5 22:17:04 storageqe-109 kernel: nvmet: connect request for invalid subsystem not-a-nqn-at-all! Oct 5 22:17:04 storageqe-109 kernel: nvme nvme3: Connect Invalid Data Parameter, subsysnqn "not-a-nqn-at-all" Oct 5 22:17:04 storageqe-109 kernel: nvme nvme3: failed to connect queue: 0 ret=16770 Oct 5 22:17:04 storageqe-109 kernel: nvmet: connect request for invalid subsystem nqn.test.nonexistent.subsystem! Oct 5 22:17:04 storageqe-109 kernel: nvme nvme3: Connect Invalid Data Parameter, subsysnqn "nqn.test.nonexistent.subsystem" Oct 5 22:17:04 storageqe-109 kernel: nvme nvme3: failed to connect queue: 0 ret=16770 Oct 5 22:17:04 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO" Oct 5 22:17:04 storageqe-109 kernel: nvme nvme2: Removing ctrl: NQN "nqn.2023-01.local:nvme-connect-comprehensive-VGNQeuFO" INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_connect_comprehensive_parameters #### INFO: #### will start test_nvme_connect_disconnect_functions ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:11 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:11 storageqe-109 INFO: #### END test_nvme_connect_comprehensive_parameters #### Oct 5 22:17:11 storageqe-109 INFO: #### will start test_nvme_connect_disconnect_functions ##### Oct 5 22:17:11 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:16 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-connect-test-rYeEfmKz Oct 5 22:17:16 storageqe-109 kernel: nvmet_tcp: enabling port 4432 (127.0.0.1:4432) Oct 5 22:17:18 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-connect-test-rYeEfmKz for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:17:18 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:17:18 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:17:18 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-connect-test-rYeEfmKz", addr 127.0.0.1:4432, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:17:20 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-connect-test-rYeEfmKz" Oct 5 22:17:22 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_connect_disconnect_functions #### INFO: #### will start test_nvme_find_controllers_for_namespace ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:28 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:28 storageqe-109 INFO: #### END test_nvme_connect_disconnect_functions #### Oct 5 22:17:28 storageqe-109 INFO: #### will start test_nvme_find_controllers_for_namespace ##### Oct 5 22:17:28 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_find_controllers_for_namespace #### INFO: #### will start test_nvme_connection_error_scenarios ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:38 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:38 storageqe-109 INFO: #### END test_nvme_find_controllers_for_namespace #### Oct 5 22:17:38 storageqe-109 INFO: #### will start test_nvme_connection_error_scenarios ##### Oct 5 22:17:38 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_connection_error_scenarios #### INFO: #### will start test_nvme_connect_extra_arguments ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:48 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:48 storageqe-109 INFO: #### END test_nvme_connection_error_scenarios #### Oct 5 22:17:48 storageqe-109 INFO: #### will start test_nvme_connect_extra_arguments ##### Oct 5 22:17:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:17:54 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:nvme-connect-extra-VPhIrFGv Oct 5 22:17:54 storageqe-109 kernel: nvmet_tcp: enabling port 4433 (127.0.0.1:4433) Oct 5 22:17:56 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:nvme-connect-extra-VPhIrFGv for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:17:56 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:17:56 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:17:56 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:nvme-connect-extra-VPhIrFGv", addr 127.0.0.1:4433, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:17:56 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:nvme-connect-extra-VPhIrFGv" INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_connect_extra_arguments #### INFO: #### will start test_nvme_multipath_controller_failover ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:18:03 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:18:03 storageqe-109 INFO: #### END test_nvme_connect_extra_arguments #### Oct 5 22:18:03 storageqe-109 INFO: #### will start test_nvme_multipath_controller_failover ##### Oct 5 22:18:03 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:18:08 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:diag-test-same-ihlSGpJr Oct 5 22:18:08 storageqe-109 kernel: nvmet_tcp: enabling port 5001 (127.0.0.1:5001) Oct 5 22:18:10 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:diag-test-same-ihlSGpJr Oct 5 22:18:10 storageqe-109 kernel: nvmet_tcp: enabling port 5002 (127.0.0.1:5002) Oct 5 22:18:12 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 5 22:18:15 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:diag-test-diff-a-GaAgIoJP Oct 5 22:18:15 storageqe-109 kernel: nvmet_tcp: enabling port 5003 (127.0.0.1:5003) Oct 5 22:18:17 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:diag-test-diff-b-zJXyoLnu Oct 5 22:18:17 storageqe-109 kernel: nvmet_tcp: enabling port 5004 (127.0.0.1:5004) Oct 5 22:18:19 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9660] manager: (nvme_mp1): new Dummy device (/org/freedesktop/NetworkManager/Devices/4) Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9698] device (nvme_mp1): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9701] device (nvme_mp1): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9705] device (nvme_mp1): Activation: starting connection 'nvme_mp1' (b1beb61b-4928-4910-83a2-6cd698db7b1d) Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9706] device (nvme_mp1): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9706] device (nvme_mp1): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9707] device (nvme_mp1): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9708] device (nvme_mp1): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9742] manager: (nvme_mp2): new Dummy device (/org/freedesktop/NetworkManager/Devices/5) Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9779] device (nvme_mp2): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9780] device (nvme_mp2): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9782] device (nvme_mp2): Activation: starting connection 'nvme_mp2' (9d537a08-4893-4d86-84dd-38c6af60b16c) Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9782] device (nvme_mp2): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9783] device (nvme_mp2): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9783] device (nvme_mp2): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9784] device (nvme_mp2): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9810] device (nvme_mp1): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9811] device (nvme_mp2): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9811] device (nvme_mp1): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9813] device (nvme_mp1): Activation: successful, device activated. Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9815] device (nvme_mp2): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 5 22:18:22 storageqe-109 NetworkManager[995]: [1759717102.9817] device (nvme_mp2): Activation: successful, device activated. Oct 5 22:18:22 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 5 22:18:22 storageqe-109 iscsiadm[95409]: iscsiadm: No records found Oct 5 22:18:22 storageqe-109 systemd[1]: Reloaded iscsi.service - Login and scanning of iSCSI devices. Oct 5 22:18:22 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 5 22:18:22 storageqe-109 iscsiadm[95424]: iscsiadm: No records found Oct 5 22:18:23 storageqe-109 systemd[1]: Reloaded iscsi.service - Login and scanning of iSCSI devices. Oct 5 22:18:23 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:multipath-test-1-rxduKmDL Oct 5 22:18:23 storageqe-109 kernel: nvmet_tcp: enabling port 4450 (127.0.0.2:4450) Oct 5 22:18:23 storageqe-109 kernel: nvmet_tcp: enabling port 4451 (127.0.0.3:4451) Oct 5 22:18:28 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:multipath-test-1-rxduKmDL for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:18:28 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:18:28 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:18:28 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:multipath-test-1-rxduKmDL", addr 127.0.0.2:4450, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:18:33 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 5 22:18:33 storageqe-109 kernel: nvmet: Created nvm controller 2 for subsystem nqn.2023-01.local:multipath-test-1-rxduKmDL for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:18:33 storageqe-109 kernel: nvme nvme2: creating 4 I/O queues. Oct 5 22:18:33 storageqe-109 kernel: nvme nvme2: mapped 4/0/0 default/read/poll queues. Oct 5 22:18:33 storageqe-109 kernel: nvme nvme2: new ctrl: NQN "nqn.2023-01.local:multipath-test-1-rxduKmDL", addr 127.0.0.3:4451, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:18:39 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:multipath-test-1-rxduKmDL" Oct 5 22:18:42 storageqe-109 kernel: nvme nvme2: Removing ctrl: NQN "nqn.2023-01.local:multipath-test-1-rxduKmDL" Oct 5 22:18:48 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 5 22:18:48 storageqe-109 NetworkManager[995]: [1759717128.7488] device (nvme_mp1): state change: activated -> unmanaged (reason 'unmanaged', managed-type: 'removed') Oct 5 22:18:48 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 5 22:18:48 storageqe-109 NetworkManager[995]: [1759717128.7602] device (nvme_mp2): state change: activated -> unmanaged (reason 'unmanaged', managed-type: 'removed') Oct 5 22:18:48 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_multipath_controller_failover #### INFO: #### will start test_nvme_multipath_namespace_object_persistence ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:18:55 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:18:55 storageqe-109 INFO: #### END test_nvme_multipath_controller_failover #### Oct 5 22:18:55 storageqe-109 INFO: #### will start test_nvme_multipath_namespace_object_persistence ##### Oct 5 22:18:55 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:18:58 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8630] manager: (nvme_mp1): new Dummy device (/org/freedesktop/NetworkManager/Devices/6) Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8666] device (nvme_mp1): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8668] device (nvme_mp1): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8671] device (nvme_mp1): Activation: starting connection 'nvme_mp1' (b59e0a53-9ff6-4936-b6aa-f8e5f03e46b1) Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8671] device (nvme_mp1): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8672] device (nvme_mp1): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8673] device (nvme_mp1): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8673] device (nvme_mp1): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8707] manager: (nvme_mp2): new Dummy device (/org/freedesktop/NetworkManager/Devices/7) Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8735] device (nvme_mp2): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8736] device (nvme_mp2): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8741] device (nvme_mp2): Activation: starting connection 'nvme_mp2' (4dff87c7-a4c8-4386-abfe-e7fccb3a2d8c) Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8741] device (nvme_mp2): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8742] device (nvme_mp2): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8743] device (nvme_mp2): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8743] device (nvme_mp2): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8789] device (nvme_mp1): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8790] device (nvme_mp1): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8792] device (nvme_mp1): Activation: successful, device activated. Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8794] device (nvme_mp2): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8794] device (nvme_mp2): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 5 22:19:00 storageqe-109 NetworkManager[995]: [1759717140.8796] device (nvme_mp2): Activation: successful, device activated. Oct 5 22:19:00 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 5 22:19:00 storageqe-109 iscsiadm[95741]: iscsiadm: No records found Oct 5 22:19:00 storageqe-109 systemd[1]: Reloaded iscsi.service - Login and scanning of iSCSI devices. Oct 5 22:19:00 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 5 22:19:00 storageqe-109 iscsiadm[95754]: iscsiadm: No records found Oct 5 22:19:00 storageqe-109 systemd[1]: Reloaded iscsi.service - Login and scanning of iSCSI devices. Oct 5 22:19:00 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:multipath-test-2-qGwnLrUI Oct 5 22:19:00 storageqe-109 kernel: nvmet_tcp: enabling port 4460 (127.0.0.2:4460) Oct 5 22:19:00 storageqe-109 kernel: nvmet_tcp: enabling port 4461 (127.0.0.3:4461) Oct 5 22:19:06 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:multipath-test-2-qGwnLrUI for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:19:06 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:19:06 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:19:06 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:multipath-test-2-qGwnLrUI", addr 127.0.0.2:4460, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:19:10 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 5 22:19:11 storageqe-109 kernel: nvmet: Created nvm controller 2 for subsystem nqn.2023-01.local:multipath-test-2-qGwnLrUI for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:19:11 storageqe-109 kernel: nvme nvme2: creating 4 I/O queues. Oct 5 22:19:11 storageqe-109 kernel: nvme nvme2: mapped 4/0/0 default/read/poll queues. Oct 5 22:19:11 storageqe-109 kernel: nvme nvme2: new ctrl: NQN "nqn.2023-01.local:multipath-test-2-qGwnLrUI", addr 127.0.0.3:4461, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:19:17 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:multipath-test-2-qGwnLrUI" Oct 5 22:19:20 storageqe-109 kernel: nvme nvme2: Removing ctrl: NQN "nqn.2023-01.local:multipath-test-2-qGwnLrUI" INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_multipath_namespace_object_persistence #### INFO: #### will start test_nvme_multipath_uevent_hooks ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:19:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:19:27 storageqe-109 INFO: #### END test_nvme_multipath_namespace_object_persistence #### Oct 5 22:19:27 storageqe-109 INFO: #### will start test_nvme_multipath_uevent_hooks ##### Oct 5 22:19:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5772] device (nvme_mp1): state change: activated -> unmanaged (reason 'unmanaged', managed-type: 'removed') Oct 5 22:19:32 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5849] manager: (nvme_mp1): new Dummy device (/org/freedesktop/NetworkManager/Devices/8) Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5880] device (nvme_mp1): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5882] device (nvme_mp1): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5884] device (nvme_mp1): Activation: starting connection 'nvme_mp1' (1eb983a0-714f-47bf-8b60-228e1f153b4a) Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5884] device (nvme_mp1): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5885] device (nvme_mp1): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5886] device (nvme_mp1): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5886] device (nvme_mp1): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5903] device (nvme_mp2): state change: activated -> unmanaged (reason 'unmanaged', managed-type: 'removed') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5911] device (nvme_mp1): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5912] device (nvme_mp1): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5913] device (nvme_mp1): Activation: successful, device activated. Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.5983] manager: (nvme_mp2): new Dummy device (/org/freedesktop/NetworkManager/Devices/9) Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6024] device (nvme_mp2): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6025] device (nvme_mp2): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6027] device (nvme_mp2): Activation: starting connection 'nvme_mp2' (f09d3b87-7412-47f6-876c-8473dbfe22ee) Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6028] device (nvme_mp2): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6030] device (nvme_mp2): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6032] device (nvme_mp2): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6033] device (nvme_mp2): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6039] device (nvme_mp2): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6039] device (nvme_mp2): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 5 22:19:32 storageqe-109 NetworkManager[995]: [1759717172.6041] device (nvme_mp2): Activation: successful, device activated. Oct 5 22:19:32 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 5 22:19:32 storageqe-109 iscsiadm[96000]: iscsiadm: No records found Oct 5 22:19:32 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 5 22:19:32 storageqe-109 iscsiadm[96021]: iscsiadm: No records found Oct 5 22:19:32 storageqe-109 systemd[1]: Reloaded iscsi.service - Login and scanning of iSCSI devices. Oct 5 22:19:32 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2023-01.local:multipath-test-3-EOeWrmDz Oct 5 22:19:32 storageqe-109 kernel: nvmet_tcp: enabling port 4470 (127.0.0.2:4470) Oct 5 22:19:32 storageqe-109 kernel: nvmet_tcp: enabling port 4471 (127.0.0.3:4471) Oct 5 22:19:37 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2023-01.local:multipath-test-3-EOeWrmDz for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:19:37 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 5 22:19:37 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 5 22:19:37 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2023-01.local:multipath-test-3-EOeWrmDz", addr 127.0.0.2:4470, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:19:42 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 5 22:19:42 storageqe-109 kernel: nvmet: Created nvm controller 2 for subsystem nqn.2023-01.local:multipath-test-3-EOeWrmDz for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 5 22:19:42 storageqe-109 kernel: nvme nvme2: creating 4 I/O queues. Oct 5 22:19:42 storageqe-109 kernel: nvme nvme2: mapped 4/0/0 default/read/poll queues. Oct 5 22:19:42 storageqe-109 kernel: nvme nvme2: new ctrl: NQN "nqn.2023-01.local:multipath-test-3-EOeWrmDz", addr 127.0.0.3:4471, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 5 22:19:56 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2023-01.local:multipath-test-3-EOeWrmDz" Oct 5 22:20:02 storageqe-109 kernel: nvme nvme2: Removing ctrl: NQN "nqn.2023-01.local:multipath-test-3-EOeWrmDz" Oct 5 22:20:04 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_multipath_uevent_hooks #### INFO: #### will start test_null_parameter_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:09 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:09 storageqe-109 INFO: #### END test_nvme_multipath_uevent_hooks #### Oct 5 22:20:09 storageqe-109 INFO: #### will start test_null_parameter_handling ##### Oct 5 22:20:09 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_null_parameter_handling #### INFO: #### will start test_empty_string_parameters ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:19 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:19 storageqe-109 INFO: #### END test_null_parameter_handling #### Oct 5 22:20:19 storageqe-109 INFO: #### will start test_empty_string_parameters ##### Oct 5 22:20:19 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_empty_string_parameters #### INFO: #### will start test_boundary_value_parameters ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:29 storageqe-109 INFO: #### END test_empty_string_parameters #### Oct 5 22:20:29 storageqe-109 INFO: #### will start test_boundary_value_parameters ##### Oct 5 22:20:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_boundary_value_parameters #### INFO: #### will start test_string_length_limits ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:39 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:39 storageqe-109 INFO: #### END test_boundary_value_parameters #### Oct 5 22:20:39 storageqe-109 INFO: #### will start test_string_length_limits ##### Oct 5 22:20:39 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_string_length_limits #### INFO: #### will start test_special_character_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:49 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:49 storageqe-109 INFO: #### END test_string_length_limits #### Oct 5 22:20:49 storageqe-109 INFO: #### will start test_special_character_validation ##### Oct 5 22:20:49 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_special_character_validation #### INFO: #### will start test_unicode_parameter_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:59 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:20:59 storageqe-109 INFO: #### END test_special_character_validation #### Oct 5 22:20:59 storageqe-109 INFO: #### will start test_unicode_parameter_handling ##### Oct 5 22:20:59 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_unicode_parameter_handling #### INFO: #### will start test_array_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:09 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:09 storageqe-109 INFO: #### END test_unicode_parameter_handling #### Oct 5 22:21:09 storageqe-109 INFO: #### will start test_array_parameter_validation ##### Oct 5 22:21:09 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_array_parameter_validation #### INFO: #### will start test_concurrent_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:20 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:20 storageqe-109 INFO: #### END test_array_parameter_validation #### Oct 5 22:21:20 storageqe-109 INFO: #### will start test_concurrent_parameter_validation ##### Oct 5 22:21:20 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_parameter_validation #### INFO: #### will start test_type_safety_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:30 storageqe-109 INFO: #### END test_concurrent_parameter_validation #### Oct 5 22:21:30 storageqe-109 INFO: #### will start test_type_safety_validation ##### Oct 5 22:21:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_type_safety_validation #### INFO: #### will start test_format_string_safety ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:40 storageqe-109 INFO: #### END test_type_safety_validation #### Oct 5 22:21:40 storageqe-109 INFO: #### will start test_format_string_safety ##### Oct 5 22:21:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_format_string_safety #### INFO: #### will start test_resource_exhaustion_resistance ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:50 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:21:50 storageqe-109 INFO: #### END test_format_string_safety #### Oct 5 22:21:50 storageqe-109 INFO: #### will start test_resource_exhaustion_resistance ##### Oct 5 22:21:50 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_resource_exhaustion_resistance #### INFO: #### will start test_initialization_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:00 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:00 storageqe-109 INFO: #### END test_resource_exhaustion_resistance #### Oct 5 22:22:00 storageqe-109 INFO: #### will start test_initialization_parameter_validation ##### Oct 5 22:22:00 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_initialization_parameter_validation #### INFO: #### will start test_btrfs_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:10 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:10 storageqe-109 INFO: #### END test_initialization_parameter_validation #### Oct 5 22:22:10 storageqe-109 INFO: #### will start test_btrfs_parameter_validation ##### Oct 5 22:22:10 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_btrfs_parameter_validation #### INFO: #### will start test_dm_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:20 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:20 storageqe-109 INFO: #### END test_btrfs_parameter_validation #### Oct 5 22:22:20 storageqe-109 INFO: #### will start test_dm_parameter_validation ##### Oct 5 22:22:20 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_parameter_validation #### INFO: #### will start test_mdraid_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:30 storageqe-109 INFO: #### END test_dm_parameter_validation #### Oct 5 22:22:30 storageqe-109 INFO: #### will start test_mdraid_parameter_validation ##### Oct 5 22:22:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_parameter_validation #### INFO: #### will start test_nvme_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:40 storageqe-109 INFO: #### END test_mdraid_parameter_validation #### Oct 5 22:22:40 storageqe-109 INFO: #### will start test_nvme_parameter_validation ##### Oct 5 22:22:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_parameter_validation #### INFO: #### will start test_smart_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:50 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:22:50 storageqe-109 INFO: #### END test_nvme_parameter_validation #### Oct 5 22:22:50 storageqe-109 INFO: #### will start test_smart_parameter_validation ##### Oct 5 22:22:50 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_smart_parameter_validation #### INFO: #### will start test_mpath_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:01 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:01 storageqe-109 INFO: #### END test_smart_parameter_validation #### Oct 5 22:23:01 storageqe-109 INFO: #### will start test_mpath_parameter_validation ##### Oct 5 22:23:01 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mpath_parameter_validation #### INFO: #### will start test_nvdimm_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:11 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:11 storageqe-109 INFO: #### END test_mpath_parameter_validation #### Oct 5 22:23:11 storageqe-109 INFO: #### will start test_nvdimm_parameter_validation ##### Oct 5 22:23:11 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvdimm_parameter_validation #### INFO: #### will start test_s390_parameter_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:21 storageqe-109 INFO: #### END test_nvdimm_parameter_validation #### Oct 5 22:23:21 storageqe-109 INFO: #### will start test_s390_parameter_validation ##### Oct 5 22:23:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_s390_parameter_validation #### INFO: #### will start test_comprehensive_module_coverage ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:31 storageqe-109 INFO: #### END test_s390_parameter_validation #### Oct 5 22:23:31 storageqe-109 INFO: #### will start test_comprehensive_module_coverage ##### Oct 5 22:23:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_comprehensive_module_coverage #### INFO: #### will start test_cross_module_parameter_consistency ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:41 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:41 storageqe-109 INFO: #### END test_comprehensive_module_coverage #### Oct 5 22:23:41 storageqe-109 INFO: #### will start test_cross_module_parameter_consistency ##### Oct 5 22:23:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_cross_module_parameter_consistency #### INFO: #### will start test_part_basic_checks ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:51 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:23:51 storageqe-109 INFO: #### END test_cross_module_parameter_consistency #### Oct 5 22:23:51 storageqe-109 INFO: #### will start test_part_basic_checks ##### Oct 5 22:23:51 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_part_basic_checks #### INFO: #### will start test_part_technology_availability ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:24:03 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:24:03 storageqe-109 INFO: #### END test_part_basic_checks #### Oct 5 22:24:03 storageqe-109 INFO: #### will start test_part_technology_availability ##### Oct 5 22:24:03 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_part_technology_availability #### INFO: #### will start test_part_error_quark ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:24:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:24:15 storageqe-109 INFO: #### END test_part_technology_availability #### Oct 5 22:24:15 storageqe-109 INFO: #### will start test_part_error_quark ##### Oct 5 22:24:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_part_error_quark #### INFO: #### will start test_part_create_table_mbr ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:24:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:24:27 storageqe-109 INFO: #### END test_part_error_quark #### Oct 5 22:24:27 storageqe-109 INFO: #### will start test_part_create_table_mbr ##### Oct 5 22:24:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:24:32 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 5 22:24:33 storageqe-109 kernel: nvme0n1: INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_part_create_table_mbr #### INFO: #### will start test_part_create_table_gpt ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:24:40 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:24:40 storageqe-109 INFO: #### END test_part_create_table_mbr #### Oct 5 22:24:40 storageqe-109 INFO: #### will start test_part_create_table_gpt ##### Oct 5 22:24:40 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:24:45 storageqe-109 kernel: sdb: INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_part_create_table_gpt #### INFO: #### will start test_part_create_and_delete_mbr ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:24:52 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:24:52 storageqe-109 INFO: #### END test_part_create_table_gpt #### Oct 5 22:24:52 storageqe-109 INFO: #### will start test_part_create_and_delete_mbr ##### Oct 5 22:24:52 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:24:57 storageqe-109 kernel: sdc: Oct 5 22:24:57 storageqe-109 kernel: sdc: sdc1 Oct 5 22:24:57 storageqe-109 kernel: sdc: INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_part_create_and_delete_mbr #### INFO: #### will start test_part_create_and_delete_gpt ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:25:04 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:25:05 storageqe-109 INFO: #### END test_part_create_and_delete_mbr #### Oct 5 22:25:05 storageqe-109 INFO: #### will start test_part_create_and_delete_gpt ##### Oct 5 22:25:05 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:25:10 storageqe-109 kernel: sdd: Oct 5 22:25:10 storageqe-109 kernel: sdd: sdd1 Oct 5 22:25:10 storageqe-109 kernel: sdd: INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_part_create_and_delete_gpt #### INFO: #### will start test_part_resize ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:25:17 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:25:17 storageqe-109 INFO: #### END test_part_create_and_delete_gpt #### Oct 5 22:25:17 storageqe-109 INFO: #### will start test_part_resize ##### Oct 5 22:25:17 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:25:22 storageqe-109 kernel: sde: Oct 5 22:25:22 storageqe-109 kernel: sde: sde1 Oct 5 22:25:22 storageqe-109 kernel: sde: sde1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_part_resize #### INFO: #### will start test_part_set_properties_gpt ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:25:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:25:29 storageqe-109 INFO: #### END test_part_resize #### Oct 5 22:25:29 storageqe-109 INFO: #### will start test_part_set_properties_gpt ##### Oct 5 22:25:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:25:34 storageqe-109 kernel: nvme0n1: Oct 5 22:25:34 storageqe-109 kernel: nvme0n1: p1 Oct 5 22:25:35 storageqe-109 kernel: nvme0n1: p1 Oct 5 22:25:35 storageqe-109 kernel: nvme0n1: p1 Oct 5 22:25:35 storageqe-109 kernel: nvme0n1: p1 Oct 5 22:25:35 storageqe-109 kernel: nvme0n1: p1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_part_set_properties_gpt #### INFO: #### will start test_part_set_properties_mbr ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:25:42 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:25:42 storageqe-109 INFO: #### END test_part_set_properties_gpt #### Oct 5 22:25:42 storageqe-109 INFO: #### will start test_part_set_properties_mbr ##### Oct 5 22:25:42 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:25:47 storageqe-109 kernel: sdb: Oct 5 22:25:47 storageqe-109 kernel: sdb: sdb1 Oct 5 22:25:47 storageqe-109 kernel: sdb: sdb1 Oct 5 22:25:47 storageqe-109 kernel: sdb: sdb1 Oct 5 22:25:47 storageqe-109 kernel: sdb: sdb1 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_part_set_properties_mbr #### INFO: #### will start test_part_free_regions ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:25:55 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:25:55 storageqe-109 INFO: #### END test_part_set_properties_mbr #### Oct 5 22:25:55 storageqe-109 INFO: #### will start test_part_free_regions ##### Oct 5 22:25:55 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:26:00 storageqe-109 kernel: sdc: Oct 5 22:26:00 storageqe-109 kernel: sdc: sdc1 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_part_free_regions #### INFO: #### will start test_part_spec_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:26:07 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:26:07 storageqe-109 INFO: #### END test_part_free_regions #### Oct 5 22:26:07 storageqe-109 INFO: #### will start test_part_spec_operations ##### Oct 5 22:26:07 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:26:12 storageqe-109 kernel: sdd: Oct 5 22:26:12 storageqe-109 kernel: sdd: sdd1 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_part_spec_operations #### INFO: #### will start test_disk_spec_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:26:19 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:26:19 storageqe-109 INFO: #### END test_part_spec_operations #### Oct 5 22:26:19 storageqe-109 INFO: #### will start test_disk_spec_operations ##### Oct 5 22:26:19 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:26:24 storageqe-109 kernel: sde: INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_disk_spec_operations #### INFO: #### will start test_part_multiple_partitions_workflow ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:26:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:26:31 storageqe-109 INFO: #### END test_disk_spec_operations #### Oct 5 22:26:31 storageqe-109 INFO: #### will start test_part_multiple_partitions_workflow ##### Oct 5 22:26:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:26:36 storageqe-109 kernel: nvme0n1: Oct 5 22:26:36 storageqe-109 kernel: nvme0n1: p1 Oct 5 22:26:37 storageqe-109 kernel: nvme0n1: p1 p2 p3 Oct 5 22:26:37 storageqe-109 kernel: nvme0n1: p1 p2 p3 Oct 5 22:26:37 storageqe-109 kernel: nvme0n1: p1 p2 p3 Oct 5 22:26:37 storageqe-109 kernel: nvme0n1: p1 p3 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_part_multiple_partitions_workflow #### INFO: #### will start test_part_error_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:26:44 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:26:44 storageqe-109 INFO: #### END test_part_multiple_partitions_workflow #### Oct 5 22:26:44 storageqe-109 INFO: #### will start test_part_error_handling ##### Oct 5 22:26:44 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_part_error_handling #### INFO: #### will start test_part_boundary_conditions ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:26:56 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:26:56 storageqe-109 INFO: #### END test_part_error_handling #### Oct 5 22:26:56 storageqe-109 INFO: #### will start test_part_boundary_conditions ##### Oct 5 22:26:56 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:27:01 storageqe-109 kernel: sdb: Oct 5 22:27:01 storageqe-109 kernel: sdb: sdb1 Oct 5 22:27:01 storageqe-109 kernel: sdb: Oct 5 22:27:02 storageqe-109 kernel: sdb: sdb1 Oct 5 22:27:02 storageqe-109 kernel: sdb: INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_part_boundary_conditions #### INFO: #### will start test_raid_info ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:27:09 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:27:09 storageqe-109 INFO: #### END test_part_boundary_conditions #### Oct 5 22:27:09 storageqe-109 INFO: #### will start test_raid_info ##### Oct 5 22:27:09 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:27:14 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:27:14 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:27:14 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:27:14 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:27:14 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:27:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:27:40 storageqe-109 kernel: md: md127: resync done. Oct 5 22:28:00 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:28:00 storageqe-109 kernel: md: md127 stopped. INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_raid_info #### INFO: #### will start test_raid_add_remove ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:28:08 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:28:08 storageqe-109 INFO: #### END test_raid_info #### Oct 5 22:28:08 storageqe-109 INFO: #### will start test_raid_add_remove ##### Oct 5 22:28:08 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:28:14 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sde', '/dev/nvme0n1'], version 1.0, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:28:14 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:28:14 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:28:14 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:28:14 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:28:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:28:40 storageqe-109 kernel: md: md127: resync done. Oct 5 22:28:47 storageqe-109 kernel: md/raid1:md127: Disk failure on sdb, disabling device.#012md/raid1:md127: Operation continuing on 2 devices. Oct 5 22:28:47 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:28:47 storageqe-109 kernel: md: md127 stopped. INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_raid_add_remove #### INFO: #### will start test_bd_raid1_reshape ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:28:55 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:28:55 storageqe-109 INFO: #### END test_raid_add_remove #### Oct 5 22:28:55 storageqe-109 INFO: #### will start test_bd_raid1_reshape ##### Oct 5 22:28:55 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:29:00 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdc', '/dev/sdd'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:29:01 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:29:01 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:29:01 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:29:01 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:29:01 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:29:27 storageqe-109 kernel: md: md127: resync done. Oct 5 22:29:30 storageqe-109 kernel: md/raid:md127: device sdd operational as raid disk 1 Oct 5 22:29:30 storageqe-109 kernel: md/raid:md127: device sdc operational as raid disk 0 Oct 5 22:29:30 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 2 devices, algorithm 2 Oct 5 22:29:34 storageqe-109 kernel: md/raid:md127: Disk failure on sdd, disabling device. Oct 5 22:29:34 storageqe-109 kernel: md/raid:md127: Operation continuing on 1 devices. Oct 5 22:29:34 storageqe-109 udisksd[5174]: Unable to resolve /sys/devices/virtual/block/md127/md/dev-sdd/block symlink Oct 5 22:29:34 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 22:30:00 storageqe-109 kernel: md: md127: recover done. Oct 5 22:30:05 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:30:15 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:30:15 storageqe-109 kernel: md: md127 stopped. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bd_raid1_reshape #### INFO: #### will start test_raid_level_conversions ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:30:23 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:30:23 storageqe-109 INFO: #### END test_bd_raid1_reshape #### Oct 5 22:30:23 storageqe-109 INFO: #### will start test_raid_level_conversions ##### Oct 5 22:30:23 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:30:29 storageqe-109 INFO: raid parameter raid_level raid1, raid_mem ['/dev/sdb', '/dev/sdc'], version 0.9, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:30:29 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 5 22:30:29 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:30:29 storageqe-109 kernel: md127: detected capacity change from 0 to 10485760 Oct 5 22:30:29 storageqe-109 kernel: md: resync of RAID array md127 Oct 5 22:30:29 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:30:55 storageqe-109 kernel: md: md127: resync done. Oct 5 22:30:56 storageqe-109 kernel: md/raid:md127: device sdc operational as raid disk 1 Oct 5 22:30:56 storageqe-109 kernel: md/raid:md127: device sdb operational as raid disk 0 Oct 5 22:30:56 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 2 devices, algorithm 2 Oct 5 22:30:58 storageqe-109 kernel: md: md127: raid6 would not accept array Oct 5 22:31:02 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 5 22:31:06 storageqe-109 kernel: md127: detected capacity change from 10485760 to 0 Oct 5 22:31:06 storageqe-109 kernel: md: md127 stopped. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_raid_level_conversions #### INFO: #### will start test_raid_reshape_size ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:31:14 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:31:14 storageqe-109 INFO: #### END test_raid_level_conversions #### Oct 5 22:31:14 storageqe-109 INFO: #### will start test_raid_reshape_size ##### Oct 5 22:31:14 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: raid parameter raid_level raid5, raid_mem ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:31:19 storageqe-109 INFO: raid parameter raid_level raid5, raid_mem ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc'], version 1.2, bitmap None, chunk_size 0.0K extra, None, kwrags, {'size': '5G'} Oct 5 22:31:20 storageqe-109 kernel: md/raid:md127: device sdb operational as raid disk 1 Oct 5 22:31:20 storageqe-109 kernel: md/raid:md127: device nvme0n1 operational as raid disk 0 Oct 5 22:31:20 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 5 22:31:20 storageqe-109 kernel: md127: detected capacity change from 0 to 20971520 Oct 5 22:31:20 storageqe-109 kernel: md: recover of RAID array md127 Oct 5 22:31:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:31:46 storageqe-109 kernel: md: md127: recover done. Oct 5 22:31:47 storageqe-109 kernel: md127: detected capacity change from 20971520 to 18432 Oct 5 22:31:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:31:49 storageqe-109 kernel: md127: detected capacity change from 18432 to 20480 Oct 5 22:31:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:31:51 storageqe-109 kernel: md127: detected capacity change from 20480 to 20971520 Oct 5 22:31:51 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 5 22:31:53 storageqe-109 kernel: md127: detected capacity change from 20971520 to 0 Oct 5 22:31:53 storageqe-109 kernel: md: md127 stopped. INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_raid_reshape_size #### INFO: #### will start test_ata_disk_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:01 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:01 storageqe-109 INFO: #### END test_raid_reshape_size #### Oct 5 22:32:01 storageqe-109 INFO: #### will start test_ata_disk_info ##### Oct 5 22:32:01 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_ata_disk_info #### INFO: #### will start test_scsi_disks_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:11 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:11 storageqe-109 INFO: #### END test_ata_disk_info #### Oct 5 22:32:11 storageqe-109 INFO: #### will start test_scsi_disks_info ##### Oct 5 22:32:11 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_scsi_disks_info #### INFO: #### will start test_disks_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:22 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:22 storageqe-109 INFO: #### END test_scsi_disks_info #### Oct 5 22:32:22 storageqe-109 INFO: #### will start test_disks_info ##### Oct 5 22:32:22 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_disks_info #### INFO: #### will start test_disks_smart_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:32 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:32 storageqe-109 INFO: #### END test_disks_info #### Oct 5 22:32:32 storageqe-109 INFO: #### will start test_disks_smart_info ##### Oct 5 22:32:32 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_disks_smart_info #### INFO: #### will start test_ata_disk_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:42 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:42 storageqe-109 INFO: #### END test_disks_smart_info #### Oct 5 22:32:42 storageqe-109 INFO: #### will start test_ata_disk_info ##### Oct 5 22:32:42 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_ata_disk_info #### INFO: #### will start test_scsi_disks_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:52 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:32:52 storageqe-109 INFO: #### END test_ata_disk_info #### Oct 5 22:32:52 storageqe-109 INFO: #### will start test_scsi_disks_info ##### Oct 5 22:32:52 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_scsi_disks_info #### INFO: #### will start test_disks_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:03 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:03 storageqe-109 INFO: #### END test_scsi_disks_info #### Oct 5 22:33:03 storageqe-109 INFO: #### will start test_disks_info ##### Oct 5 22:33:03 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_disks_info #### INFO: #### will start test_disks_smart_info ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:13 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:13 storageqe-109 INFO: #### END test_disks_info #### Oct 5 22:33:13 storageqe-109 INFO: #### will start test_disks_smart_info ##### Oct 5 22:33:13 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_disks_smart_info #### INFO: #### will start test_smart_capabilities ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:23 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:23 storageqe-109 INFO: #### END test_disks_smart_info #### Oct 5 22:33:23 storageqe-109 INFO: #### will start test_smart_capabilities ##### Oct 5 22:33:23 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_capabilities #### INFO: #### will start test_smart_enable_disable ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:34 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:34 storageqe-109 INFO: #### END test_smart_capabilities #### Oct 5 22:33:34 storageqe-109 INFO: #### will start test_smart_enable_disable ##### Oct 5 22:33:34 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_enable_disable #### Oct 5 22:33:44 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:44 storageqe-109 INFO: #### END test_smart_enable_disable #### INFO: #### will start test_smart_self_test_abort ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:44 storageqe-109 INFO: #### will start test_smart_self_test_abort ##### Oct 5 22:33:44 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_self_test_abort #### INFO: #### will start test_smart_error_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:54 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:33:54 storageqe-109 INFO: #### END test_smart_self_test_abort #### Oct 5 22:33:54 storageqe-109 INFO: #### will start test_smart_error_handling ##### Oct 5 22:33:54 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_error_handling #### INFO: #### will start test_smart_attribute_details ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:05 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:05 storageqe-109 INFO: #### END test_smart_error_handling #### Oct 5 22:34:05 storageqe-109 INFO: #### will start test_smart_attribute_details ##### Oct 5 22:34:05 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_attribute_details #### INFO: #### will start test_smart_overall_health ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:15 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:15 storageqe-109 INFO: #### END test_smart_attribute_details #### Oct 5 22:34:15 storageqe-109 INFO: #### will start test_smart_overall_health ##### Oct 5 22:34:15 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_overall_health #### INFO: #### will start test_smart_thresholds ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:25 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:25 storageqe-109 INFO: #### END test_smart_overall_health #### Oct 5 22:34:25 storageqe-109 INFO: #### will start test_smart_thresholds ##### Oct 5 22:34:25 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_thresholds #### INFO: #### will start test_smart_benchmark ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:35 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:35 storageqe-109 INFO: #### END test_smart_thresholds #### Oct 5 22:34:35 storageqe-109 INFO: #### will start test_smart_benchmark ##### Oct 5 22:34:36 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_benchmark #### INFO: #### will start test_smart_compatibility ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:46 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:46 storageqe-109 INFO: #### END test_smart_benchmark #### Oct 5 22:34:46 storageqe-109 INFO: #### will start test_smart_compatibility ##### Oct 5 22:34:46 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_smart_compatibility #### INFO: #### will start test_swap_is_available ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:56 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:34:56 storageqe-109 INFO: #### END test_smart_compatibility #### Oct 5 22:34:56 storageqe-109 INFO: #### will start test_swap_is_available ##### Oct 5 22:34:56 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_swap_is_available #### INFO: #### will start test_swap_mkswap_basic ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:35:06 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:35:06 storageqe-109 INFO: #### END test_swap_is_available #### Oct 5 22:35:06 storageqe-109 INFO: #### will start test_swap_mkswap_basic ##### Oct 5 22:35:06 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_swap_mkswap_basic #### INFO: #### will start test_swap_mkswap_with_label ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:35:16 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:35:16 storageqe-109 INFO: #### END test_swap_mkswap_basic #### Oct 5 22:35:16 storageqe-109 INFO: #### will start test_swap_mkswap_with_label ##### Oct 5 22:35:16 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_swap_mkswap_with_label #### INFO: #### will start test_swap_activate_and_deactivate ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:35:26 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:35:26 storageqe-109 INFO: #### END test_swap_mkswap_with_label #### Oct 5 22:35:26 storageqe-109 INFO: #### will start test_swap_activate_and_deactivate ##### Oct 5 22:35:26 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:35:32 storageqe-109 kernel: Adding 1562813780k swap on /dev/nvme0n1. Priority:-3 extents:1 across:1562813780k SS Oct 5 22:35:32 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418.swap: Deactivated successfully. Oct 5 22:35:32 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418_1.swap: Deactivated successfully. Oct 5 22:35:32 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2deui.35354a30549004180025384300000001.swap: Deactivated successfully. Oct 5 22:35:32 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-2.swap: Deactivated successfully. Oct 5 22:35:32 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.swap: Deactivated successfully. Oct 5 22:35:32 storageqe-109 systemd[1]: dev-nvme0n1.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_swap_activate_and_deactivate #### INFO: #### will start test_swap_activate_with_priority ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:35:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:35:37 storageqe-109 INFO: #### END test_swap_activate_and_deactivate #### Oct 5 22:35:37 storageqe-109 INFO: #### will start test_swap_activate_with_priority ##### Oct 5 22:35:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:35:42 storageqe-109 kernel: Adding 780795900k swap on /dev/sdb. Priority:10 extents:1 across:780795900k SS Oct 5 22:35:42 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002eab3460d5de6048.swap: Deactivated successfully. Oct 5 22:35:42 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:108:0.swap: Deactivated successfully. Oct 5 22:35:42 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002eab3460d5de6048.swap: Deactivated successfully. Oct 5 22:35:42 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-4.swap: Deactivated successfully. Oct 5 22:35:42 storageqe-109 systemd[1]: dev-sdb.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_swap_activate_with_priority #### INFO: #### will start test_swap_check_functionality ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:35:47 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:35:47 storageqe-109 INFO: #### END test_swap_activate_with_priority #### Oct 5 22:35:47 storageqe-109 INFO: #### will start test_swap_check_functionality ##### Oct 5 22:35:47 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_swap_check_functionality #### INFO: #### will start test_swap_multiple_devices ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:35:57 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:35:57 storageqe-109 INFO: #### END test_swap_check_functionality #### Oct 5 22:35:57 storageqe-109 INFO: #### will start test_swap_multiple_devices ##### Oct 5 22:35:57 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:36:02 storageqe-109 kernel: Adding 780795900k swap on /dev/sdd. Priority:5 extents:1 across:780795900k SS Oct 5 22:36:02 storageqe-109 kernel: Adding 468320252k swap on /dev/sde. Priority:6 extents:1 across:468320252k SS Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2duuid-5af2623b\x2dc937\x2d4d72\x2daabb\x2d4e8d70b7a2b0.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2duuid-0dd103ca\x2dfe4d\x2d42d8\x2d95e1\x2d75c0fa455894.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2dlabel-swap_label_0.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:110:0.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-6.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-sdd.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2duuid-6ef5f874\x2dedb2\x2d4e58\x2d86a4\x2d69478f0ad7d0.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2dlabel-swap_label_1.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-7.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:111:0.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002e8943977a9fb0b3.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002e8943977a9fb0b3.swap: Deactivated successfully. Oct 5 22:36:02 storageqe-109 systemd[1]: dev-sde.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_swap_multiple_devices #### INFO: #### will start test_swap_large_device ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:36:07 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:36:07 storageqe-109 INFO: #### END test_swap_multiple_devices #### Oct 5 22:36:07 storageqe-109 INFO: #### will start test_swap_large_device ##### Oct 5 22:36:07 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:36:13 storageqe-109 kernel: Adding 1562813780k swap on /dev/nvme0n1. Priority:-3 extents:1 across:1562813780k SS Oct 5 22:36:13 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418_1.swap: Deactivated successfully. Oct 5 22:36:13 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418.swap: Deactivated successfully. Oct 5 22:36:13 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.swap: Deactivated successfully. Oct 5 22:36:13 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2deui.35354a30549004180025384300000001.swap: Deactivated successfully. Oct 5 22:36:13 storageqe-109 systemd[1]: dev-disk-by\x2duuid-fc7fba6d\x2d4ae8\x2d469d\x2d82ea\x2da8213be85508.swap: Deactivated successfully. Oct 5 22:36:13 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-2.swap: Deactivated successfully. Oct 5 22:36:13 storageqe-109 systemd[1]: dev-nvme0n1.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_swap_large_device #### INFO: #### will start test_swap_invalid_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:36:18 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:36:18 storageqe-109 INFO: #### END test_swap_large_device #### Oct 5 22:36:18 storageqe-109 INFO: #### will start test_swap_invalid_operations ##### Oct 5 22:36:18 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_swap_invalid_operations #### INFO: #### will start test_swap_deactivate_nonexistent ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:36:28 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:36:28 storageqe-109 INFO: #### END test_swap_invalid_operations #### Oct 5 22:36:28 storageqe-109 INFO: #### will start test_swap_deactivate_nonexistent ##### Oct 5 22:36:28 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_swap_deactivate_nonexistent #### INFO: #### will start test_swap_label_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:36:38 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:36:38 storageqe-109 INFO: #### END test_swap_deactivate_nonexistent #### Oct 5 22:36:38 storageqe-109 INFO: #### will start test_swap_label_operations ##### Oct 5 22:36:38 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_swap_label_operations #### INFO: #### will start test_swap_priority_ranges ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:36:48 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:36:48 storageqe-109 INFO: #### END test_swap_label_operations #### Oct 5 22:36:48 storageqe-109 INFO: #### will start test_swap_priority_ranges ##### Oct 5 22:36:48 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:36:53 storageqe-109 kernel: Adding 780795900k swap on /dev/sdd. Priority:-3 extents:1 across:780795900k SS Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:110:0.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2duuid-0dd103ca\x2dfe4d\x2d42d8\x2d95e1\x2d75c0fa455894.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-6.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2dlabel-swap_label_0.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-sdd.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 kernel: Adding 780795900k swap on /dev/sdd. Priority:32767 extents:1 across:780795900k SS Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:110:0.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-6.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-disk-by\x2duuid-05276024\x2de66b\x2d4c0a\x2d9b1f\x2d8c06cd17e62c.swap: Deactivated successfully. Oct 5 22:36:53 storageqe-109 systemd[1]: dev-sdd.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_swap_priority_ranges #### INFO: #### will start test_swap_io_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:36:58 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:36:58 storageqe-109 INFO: #### END test_swap_priority_ranges #### Oct 5 22:36:58 storageqe-109 INFO: #### will start test_swap_io_operations ##### Oct 5 22:36:58 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:37:03 storageqe-109 kernel: Adding 468320252k swap on /dev/sde. Priority:-3 extents:1 across:468320252k SS Oct 5 22:37:03 storageqe-109 systemd[1]: dev-disk-by\x2dlabel-swap_label_1.swap: Deactivated successfully. Oct 5 22:37:03 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002e8943977a9fb0b3.swap: Deactivated successfully. Oct 5 22:37:03 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002e8943977a9fb0b3.swap: Deactivated successfully. Oct 5 22:37:03 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:111:0.swap: Deactivated successfully. Oct 5 22:37:03 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-7.swap: Deactivated successfully. Oct 5 22:37:03 storageqe-109 systemd[1]: dev-disk-by\x2duuid-6ef5f874\x2dedb2\x2d4e58\x2d86a4\x2d69478f0ad7d0.swap: Deactivated successfully. Oct 5 22:37:03 storageqe-109 systemd[1]: dev-sde.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_swap_io_operations #### INFO: #### will start test_swap_recreation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:37:08 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:37:08 storageqe-109 INFO: #### END test_swap_io_operations #### Oct 5 22:37:08 storageqe-109 INFO: #### will start test_swap_recreation ##### Oct 5 22:37:08 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:37:14 storageqe-109 kernel: Adding 1562813780k swap on /dev/nvme0n1. Priority:-3 extents:1 across:1562813780k SS Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2deui.35354a30549004180025384300000001.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2dlabel-large_swap.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-2.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418_1.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2duuid-ba1c5969\x2db30c\x2d4e4c\x2da520\x2dd209deeca708.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-nvme0n1.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 kernel: Adding 1562813780k swap on /dev/nvme0n1. Priority:-3 extents:1 across:1562813780k SS Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-2.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2duuid-c2f01cdc\x2da2b2\x2d42fc\x2d997b\x2d1aedf3777078.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2dlabel-first_label.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2deui.35354a30549004180025384300000001.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418_1.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-disk-by\x2did-nvme\x2dSAMSUNG_MZPLJ1T6HBJR\x2d00007_S55JNC0T900418.swap: Deactivated successfully. Oct 5 22:37:14 storageqe-109 systemd[1]: dev-nvme0n1.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_swap_recreation #### INFO: #### will start test_swap_small_device_limits ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:37:19 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 5 22:37:19 storageqe-109 INFO: #### END test_swap_recreation #### Oct 5 22:37:19 storageqe-109 INFO: #### will start test_swap_small_device_limits ##### Oct 5 22:37:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_swap_small_device_limits #### INFO: #### will start test_swap_device_busy_scenarios ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:37:29 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:37:29 storageqe-109 INFO: #### END test_swap_small_device_limits #### Oct 5 22:37:29 storageqe-109 INFO: #### will start test_swap_device_busy_scenarios ##### Oct 5 22:37:29 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 5 22:37:34 storageqe-109 kernel: Adding 780795900k swap on /dev/sdc. Priority:-3 extents:1 across:780795900k SS Oct 5 22:37:34 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:109:0.swap: Deactivated successfully. Oct 5 22:37:34 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002eab344bb7563dfc.swap: Deactivated successfully. Oct 5 22:37:34 storageqe-109 systemd[1]: dev-disk-by\x2duuid-e93fd10d\x2d20b3\x2d466b\x2d90a1\x2daa8dbb6e3802.swap: Deactivated successfully. Oct 5 22:37:34 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002eab344bb7563dfc.swap: Deactivated successfully. Oct 5 22:37:34 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-5.swap: Deactivated successfully. Oct 5 22:37:34 storageqe-109 systemd[1]: dev-disk-by\x2dlabel-aaaaaaaaaaaaaaa.swap: Deactivated successfully. Oct 5 22:37:34 storageqe-109 systemd[1]: dev-sdc.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_swap_device_busy_scenarios #### INFO: #### will start test_swap_zero_priority ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:37:39 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:37:39 storageqe-109 INFO: #### END test_swap_device_busy_scenarios #### Oct 5 22:37:39 storageqe-109 INFO: #### will start test_swap_zero_priority ##### Oct 5 22:37:39 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 5 22:37:44 storageqe-109 kernel: Adding 780795900k swap on /dev/sdd. Priority:0 extents:1 across:780795900k SS Oct 5 22:37:44 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-6.swap: Deactivated successfully. Oct 5 22:37:44 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:110:0.swap: Deactivated successfully. Oct 5 22:37:44 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:37:44 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002eab3436968b69a8.swap: Deactivated successfully. Oct 5 22:37:44 storageqe-109 systemd[1]: dev-sdd.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_swap_zero_priority #### INFO: #### will start test_swap_status_queries ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:37:49 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:37:49 storageqe-109 INFO: #### END test_swap_zero_priority #### Oct 5 22:37:49 storageqe-109 INFO: #### will start test_swap_status_queries ##### Oct 5 22:37:49 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 5 22:37:55 storageqe-109 kernel: Adding 468320252k swap on /dev/sde. Priority:5 extents:1 across:468320252k SS Oct 5 22:37:55 storageqe-109 systemd[1]: dev-disk-by\x2did-scsi\x2d36f4ee08076430d002e8943977a9fb0b3.swap: Deactivated successfully. Oct 5 22:37:55 storageqe-109 systemd[1]: dev-disk-by\x2did-wwn\x2d0x6f4ee08076430d002e8943977a9fb0b3.swap: Deactivated successfully. Oct 5 22:37:55 storageqe-109 systemd[1]: dev-disk-by\x2ddiskseq-7.swap: Deactivated successfully. Oct 5 22:37:55 storageqe-109 systemd[1]: dev-disk-by\x2dpath-pci\x2d0000:03:00.0\x2dscsi\x2d0:3:111:0.swap: Deactivated successfully. Oct 5 22:37:55 storageqe-109 systemd[1]: dev-disk-by\x2duuid-b2eb478d\x2dca89\x2d4040\x2d83f7\x2d6c7a030606d6.swap: Deactivated successfully. Oct 5 22:37:55 storageqe-109 systemd[1]: dev-sde.swap: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_swap_status_queries #### INFO: #### will start test_io_scheduler_atomic_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:00 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:00 storageqe-109 INFO: #### END test_swap_status_queries #### Oct 5 22:38:00 storageqe-109 INFO: #### will start test_io_scheduler_atomic_operations ##### Oct 5 22:38:00 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_io_scheduler_atomic_operations #### INFO: #### will start test_concurrent_atomic_access ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:10 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:10 storageqe-109 INFO: #### END test_io_scheduler_atomic_operations #### Oct 5 22:38:10 storageqe-109 INFO: #### will start test_concurrent_atomic_access ##### Oct 5 22:38:10 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_atomic_access #### INFO: #### will start test_atomic_counter_overflow ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:30 storageqe-109 INFO: #### END test_concurrent_atomic_access #### Oct 5 22:38:30 storageqe-109 INFO: #### will start test_atomic_counter_overflow ##### Oct 5 22:38:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_atomic_counter_overflow #### INFO: #### will start test_device_open_close_atomics ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:41 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:41 storageqe-109 INFO: #### END test_atomic_counter_overflow #### Oct 5 22:38:41 storageqe-109 INFO: #### will start test_device_open_close_atomics ##### Oct 5 22:38:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_device_open_close_atomics #### INFO: #### will start test_dio_atomic_reference_counting ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:38:56 storageqe-109 INFO: #### END test_device_open_close_atomics #### Oct 5 22:38:56 storageqe-109 INFO: #### will start test_dio_atomic_reference_counting ##### Oct 5 22:38:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dio_atomic_reference_counting #### INFO: #### will start test_partition_atomic_access ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:06 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:06 storageqe-109 INFO: #### END test_dio_atomic_reference_counting #### Oct 5 22:39:06 storageqe-109 INFO: #### will start test_partition_atomic_access ##### Oct 5 22:39:06 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_partition_atomic_access #### INFO: #### will start test_kernel_badblocks_set_clear_api ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:16 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:16 storageqe-109 INFO: #### END test_partition_atomic_access #### Oct 5 22:39:16 storageqe-109 INFO: #### will start test_kernel_badblocks_set_clear_api ##### Oct 5 22:39:16 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_kernel_badblocks_set_clear_api #### INFO: #### will start test_badblocks_seqlock_behavior ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:26 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:26 storageqe-109 INFO: #### END test_kernel_badblocks_set_clear_api #### Oct 5 22:39:26 storageqe-109 INFO: #### will start test_badblocks_seqlock_behavior ##### Oct 5 22:39:26 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_badblocks_seqlock_behavior #### INFO: #### will start test_badblocks_range_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:36 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:36 storageqe-109 INFO: #### END test_badblocks_seqlock_behavior #### Oct 5 22:39:36 storageqe-109 INFO: #### will start test_badblocks_range_operations ##### Oct 5 22:39:36 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_badblocks_range_operations #### INFO: #### will start test_badblocks_bio_integration ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:46 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:46 storageqe-109 INFO: #### END test_badblocks_range_operations #### Oct 5 22:39:46 storageqe-109 INFO: #### will start test_badblocks_bio_integration ##### Oct 5 22:39:46 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_badblocks_bio_integration #### INFO: #### will start test_hardware_integrity_capabilities ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:39:56 storageqe-109 INFO: #### END test_badblocks_bio_integration #### Oct 5 22:39:56 storageqe-109 INFO: #### will start test_hardware_integrity_capabilities ##### Oct 5 22:39:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hardware_integrity_capabilities #### INFO: #### will start test_automatic_integrity_generation_verification ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:06 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:06 storageqe-109 INFO: #### END test_hardware_integrity_capabilities #### Oct 5 22:40:06 storageqe-109 INFO: #### will start test_automatic_integrity_generation_verification ##### Oct 5 22:40:06 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_automatic_integrity_generation_verification #### INFO: #### will start test_integrity_error_injection_detection ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:16 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:16 storageqe-109 INFO: #### END test_automatic_integrity_generation_verification #### Oct 5 22:40:16 storageqe-109 INFO: #### will start test_integrity_error_injection_detection ##### Oct 5 22:40:17 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_error_injection_detection #### INFO: #### will start test_integrity_metadata_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:27 storageqe-109 INFO: #### END test_integrity_error_injection_detection #### Oct 5 22:40:27 storageqe-109 INFO: #### will start test_integrity_metadata_handling ##### Oct 5 22:40:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_metadata_handling #### INFO: #### will start test_blk_mq_functionality ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:37 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:37 storageqe-109 INFO: #### END test_integrity_metadata_handling #### Oct 5 22:40:37 storageqe-109 INFO: #### will start test_blk_mq_functionality ##### Oct 5 22:40:37 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_blk_mq_functionality #### INFO: #### will start test_bio_processing_pipeline ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:47 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:47 storageqe-109 INFO: #### END test_blk_mq_functionality #### Oct 5 22:40:47 storageqe-109 INFO: #### will start test_bio_processing_pipeline ##### Oct 5 22:40:47 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bio_processing_pipeline #### INFO: #### will start test_io_scheduler_interaction ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:57 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:40:57 storageqe-109 INFO: #### END test_bio_processing_pipeline #### Oct 5 22:40:57 storageqe-109 INFO: #### will start test_io_scheduler_interaction ##### Oct 5 22:40:57 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_io_scheduler_interaction #### INFO: #### will start test_basic_flush_semantics ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:07 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:07 storageqe-109 INFO: #### END test_io_scheduler_interaction #### Oct 5 22:41:07 storageqe-109 INFO: #### will start test_basic_flush_semantics ##### Oct 5 22:41:07 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_basic_flush_semantics #### INFO: #### will start test_fua_force_unit_access ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:17 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:17 storageqe-109 INFO: #### END test_basic_flush_semantics #### Oct 5 22:41:17 storageqe-109 INFO: #### will start test_fua_force_unit_access ##### Oct 5 22:41:17 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fua_force_unit_access #### INFO: #### will start test_flush_barrier_ordering ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:27 storageqe-109 INFO: #### END test_fua_force_unit_access #### Oct 5 22:41:27 storageqe-109 INFO: #### will start test_flush_barrier_ordering ##### Oct 5 22:41:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_flush_barrier_ordering #### INFO: #### will start test_concurrent_flush_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:37 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:38 storageqe-109 INFO: #### END test_flush_barrier_ordering #### Oct 5 22:41:38 storageqe-109 INFO: #### will start test_concurrent_flush_operations ##### Oct 5 22:41:38 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_flush_operations #### INFO: #### will start test_flush_failure_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:48 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:48 storageqe-109 INFO: #### END test_concurrent_flush_operations #### Oct 5 22:41:48 storageqe-109 INFO: #### will start test_flush_failure_recovery ##### Oct 5 22:41:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_flush_failure_recovery #### INFO: #### will start test_discard_operation_integrity ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:58 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:41:58 storageqe-109 INFO: #### END test_flush_failure_recovery #### Oct 5 22:41:58 storageqe-109 INFO: #### will start test_discard_operation_integrity ##### Oct 5 22:41:58 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_discard_operation_integrity #### INFO: #### will start test_write_zeroes_vs_regular_write ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:08 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:08 storageqe-109 INFO: #### END test_discard_operation_integrity #### Oct 5 22:42:08 storageqe-109 INFO: #### will start test_write_zeroes_vs_regular_write ##### Oct 5 22:42:08 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_write_zeroes_vs_regular_write #### INFO: #### will start test_secure_erase_functionality ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:18 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:18 storageqe-109 INFO: #### END test_write_zeroes_vs_regular_write #### Oct 5 22:42:18 storageqe-109 INFO: #### will start test_secure_erase_functionality ##### Oct 5 22:42:18 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_secure_erase_functionality #### INFO: #### will start test_unmap_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:28 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:28 storageqe-109 INFO: #### END test_secure_erase_functionality #### Oct 5 22:42:28 storageqe-109 INFO: #### will start test_unmap_operations ##### Oct 5 22:42:28 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_unmap_operations #### INFO: #### will start test_bio_merge_algorithms ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:39 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:39 storageqe-109 INFO: #### END test_unmap_operations #### Oct 5 22:42:39 storageqe-109 INFO: #### will start test_bio_merge_algorithms ##### Oct 5 22:42:39 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bio_merge_algorithms #### INFO: #### will start test_segment_boundary_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:49 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:42:49 storageqe-109 INFO: #### END test_bio_merge_algorithms #### Oct 5 22:42:49 storageqe-109 INFO: #### will start test_segment_boundary_handling ##### Oct 5 22:42:49 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_segment_boundary_handling #### Oct 5 22:43:24 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:43:24 storageqe-109 INFO: #### END test_segment_boundary_handling #### INFO: #### will start test_front_back_merge_performance ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:43:24 storageqe-109 INFO: #### will start test_front_back_merge_performance ##### Oct 5 22:43:24 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_front_back_merge_performance #### INFO: #### will start test_merge_failure_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:43:34 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:43:34 storageqe-109 INFO: #### END test_front_back_merge_performance #### Oct 5 22:43:34 storageqe-109 INFO: #### will start test_merge_failure_recovery ##### Oct 5 22:43:34 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_merge_failure_recovery #### INFO: #### will start test_tag_starvation_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:43:44 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:43:44 storageqe-109 INFO: #### END test_merge_failure_recovery #### Oct 5 22:43:44 storageqe-109 INFO: #### will start test_tag_starvation_recovery ##### Oct 5 22:43:44 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_tag_starvation_recovery #### INFO: #### will start test_shared_tags_pressure ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:44:09 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:44:09 storageqe-109 INFO: #### END test_tag_starvation_recovery #### Oct 5 22:44:09 storageqe-109 INFO: #### will start test_shared_tags_pressure ##### Oct 5 22:44:09 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_shared_tags_pressure #### INFO: #### will start test_tag_timeout_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:44:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:44:30 storageqe-109 INFO: #### END test_shared_tags_pressure #### Oct 5 22:44:30 storageqe-109 INFO: #### will start test_tag_timeout_handling ##### Oct 5 22:44:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_tag_timeout_handling #### INFO: #### will start test_memory_barrier_correctness ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:44:52 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:44:52 storageqe-109 INFO: #### END test_tag_timeout_handling #### Oct 5 22:44:52 storageqe-109 INFO: #### will start test_memory_barrier_correctness ##### Oct 5 22:44:52 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_memory_barrier_correctness #### INFO: #### will start test_basic_timeout_detection ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:45:08 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:45:08 storageqe-109 INFO: #### END test_memory_barrier_correctness #### Oct 5 22:45:08 storageqe-109 INFO: #### will start test_basic_timeout_detection ##### Oct 5 22:45:08 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_basic_timeout_detection #### INFO: #### will start test_concurrent_io_timeout_behavior ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:45:48 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:45:48 storageqe-109 INFO: #### END test_basic_timeout_detection #### Oct 5 22:45:48 storageqe-109 INFO: #### will start test_concurrent_io_timeout_behavior ##### Oct 5 22:45:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_io_timeout_behavior #### INFO: #### will start test_timeout_escalation_procedures ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:46:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:46:45 storageqe-109 INFO: #### END test_concurrent_io_timeout_behavior #### Oct 5 22:46:45 storageqe-109 INFO: #### will start test_timeout_escalation_procedures ##### Oct 5 22:46:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_timeout_escalation_procedures #### INFO: #### will start test_driver_timeout_integration ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:47:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:47:56 storageqe-109 INFO: #### END test_timeout_escalation_procedures #### Oct 5 22:47:56 storageqe-109 INFO: #### will start test_driver_timeout_integration ##### Oct 5 22:47:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_driver_timeout_integration #### INFO: #### will start test_dynamic_threshold_adjustment ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:48:36 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:48:36 storageqe-109 INFO: #### END test_driver_timeout_integration #### Oct 5 22:48:36 storageqe-109 INFO: #### will start test_dynamic_threshold_adjustment ##### Oct 5 22:48:36 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dynamic_threshold_adjustment #### INFO: #### will start test_ssd_vs_hdd_behavior_simulation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:48:46 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:48:46 storageqe-109 INFO: #### END test_dynamic_threshold_adjustment #### Oct 5 22:48:46 storageqe-109 INFO: #### will start test_ssd_vs_hdd_behavior_simulation ##### Oct 5 22:48:46 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_ssd_vs_hdd_behavior_simulation #### INFO: #### will start test_memory_pressure_throttling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:48:57 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:48:57 storageqe-109 INFO: #### END test_ssd_vs_hdd_behavior_simulation #### Oct 5 22:48:57 storageqe-109 INFO: #### will start test_memory_pressure_throttling ##### Oct 5 22:48:57 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_memory_pressure_throttling #### INFO: #### will start test_scheduler_interaction ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:08 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:08 storageqe-109 INFO: #### END test_memory_pressure_throttling #### Oct 5 22:49:08 storageqe-109 INFO: #### will start test_scheduler_interaction ##### Oct 5 22:49:08 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_scheduler_interaction #### INFO: #### will start test_bio_split_exhaustion_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:18 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:18 storageqe-109 INFO: #### END test_scheduler_interaction #### Oct 5 22:49:18 storageqe-109 INFO: #### will start test_bio_split_exhaustion_handling ##### Oct 5 22:49:18 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bio_split_exhaustion_handling #### INFO: #### will start test_request_queue_freeze_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:29 storageqe-109 INFO: #### END test_bio_split_exhaustion_handling #### Oct 5 22:49:29 storageqe-109 INFO: #### will start test_request_queue_freeze_recovery ##### Oct 5 22:49:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:36 storageqe-109 dmeventd[73612]: dmeventd was idle for 3600 second(s), exiting. Oct 5 22:49:36 storageqe-109 dmeventd[73612]: dmeventd shutting down. Oct 5 22:49:36 storageqe-109 systemd[1]: dm-event.service: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_request_queue_freeze_recovery #### INFO: #### will start test_bio_integrity_failure_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:40 storageqe-109 INFO: #### END test_request_queue_freeze_recovery #### Oct 5 22:49:40 storageqe-109 INFO: #### will start test_bio_integrity_failure_handling ##### Oct 5 22:49:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bio_integrity_failure_handling #### INFO: #### will start test_block_throttling_stress ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:51 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:49:51 storageqe-109 INFO: #### END test_bio_integrity_failure_handling #### Oct 5 22:49:51 storageqe-109 INFO: #### will start test_block_throttling_stress ##### Oct 5 22:49:51 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_block_throttling_stress #### INFO: #### will start test_cgroup_policy_conflicts ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:01 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:01 storageqe-109 INFO: #### END test_block_throttling_stress #### Oct 5 22:50:01 storageqe-109 INFO: #### will start test_cgroup_policy_conflicts ##### Oct 5 22:50:01 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_cgroup_policy_conflicts #### INFO: #### will start test_elevator_scheduler_stress ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:12 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:12 storageqe-109 INFO: #### END test_cgroup_policy_conflicts #### Oct 5 22:50:12 storageqe-109 INFO: #### will start test_elevator_scheduler_stress ##### Oct 5 22:50:12 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_elevator_scheduler_stress #### INFO: #### will start test_timeout_handling_stress ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:29 storageqe-109 INFO: #### END test_elevator_scheduler_stress #### Oct 5 22:50:29 storageqe-109 INFO: #### will start test_timeout_handling_stress ##### Oct 5 22:50:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_timeout_handling_stress #### INFO: #### will start test_merge_failure_conditions ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:39 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:39 storageqe-109 INFO: #### END test_timeout_handling_stress #### Oct 5 22:50:39 storageqe-109 INFO: #### will start test_merge_failure_conditions ##### Oct 5 22:50:39 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_merge_failure_conditions #### INFO: #### will start test_segment_boundary_violations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:50 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:50:50 storageqe-109 INFO: #### END test_merge_failure_conditions #### Oct 5 22:50:50 storageqe-109 INFO: #### will start test_segment_boundary_violations ##### Oct 5 22:50:50 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_segment_boundary_violations #### INFO: #### will start test_queue_limits_violations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:00 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:00 storageqe-109 INFO: #### END test_segment_boundary_violations #### Oct 5 22:51:00 storageqe-109 INFO: #### will start test_queue_limits_violations ##### Oct 5 22:51:00 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_queue_limits_violations #### INFO: #### will start test_concurrent_error_scenarios ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:11 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:11 storageqe-109 INFO: #### END test_queue_limits_violations #### Oct 5 22:51:11 storageqe-109 INFO: #### will start test_concurrent_error_scenarios ##### Oct 5 22:51:11 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_error_scenarios #### INFO: #### will start test_error_recovery_verification ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:27 storageqe-109 INFO: #### END test_concurrent_error_scenarios #### Oct 5 22:51:27 storageqe-109 INFO: #### will start test_error_recovery_verification ##### Oct 5 22:51:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_error_recovery_verification #### INFO: #### will start test_cgroup_io_weight_fairness ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:43 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:51:43 storageqe-109 INFO: #### END test_error_recovery_verification #### Oct 5 22:51:43 storageqe-109 INFO: #### will start test_cgroup_io_weight_fairness ##### Oct 5 22:51:43 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_cgroup_io_weight_fairness #### INFO: #### will start test_ionice_priority_levels ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:54:24 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:54:24 storageqe-109 INFO: #### END test_cgroup_io_weight_fairness #### Oct 5 22:54:24 storageqe-109 INFO: #### will start test_ionice_priority_levels ##### Oct 5 22:54:24 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_ionice_priority_levels #### INFO: #### will start test_mixed_weight_priority_interaction ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:56:19 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:56:19 storageqe-109 INFO: #### END test_ionice_priority_levels #### Oct 5 22:56:19 storageqe-109 INFO: #### will start test_mixed_weight_priority_interaction ##### Oct 5 22:56:19 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mixed_weight_priority_interaction #### INFO: #### will start test_io_weight_under_stress ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:57:34 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:57:34 storageqe-109 INFO: #### END test_mixed_weight_priority_interaction #### Oct 5 22:57:34 storageqe-109 INFO: #### will start test_io_weight_under_stress ##### Oct 5 22:57:34 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:57:39 storageqe-109 stress-ng[196509]: invoked with 'stress-ng --vm 2 --vm-bytes 512M --timeout 120s --quiet' by user 0 'root' Oct 5 22:57:39 storageqe-109 stress-ng[196508]: invoked with 'stress-ng --cpu 4 --timeout 120s --quiet' by user 0 'root' Oct 5 22:57:39 storageqe-109 stress-ng[196509]: system: 'storageqe-109.rhts.eng.pek2.redhat.com' Linux 6.12.0-134.el10.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Sep 24 10:59:26 EDT 2025 x86_64 Oct 5 22:57:39 storageqe-109 stress-ng[196508]: system: 'storageqe-109.rhts.eng.pek2.redhat.com' Linux 6.12.0-134.el10.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Sep 24 10:59:26 EDT 2025 x86_64 Oct 5 22:57:39 storageqe-109 stress-ng[196509]: memory (MB): total 15047.34, free 14103.52, shared 12.66, buffer 9.85, swap 7972.00, free swap 7969.50 Oct 5 22:57:39 storageqe-109 stress-ng[196508]: memory (MB): total 15047.34, free 14103.52, shared 12.66, buffer 9.85, swap 7972.00, free swap 7969.50 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_io_weight_under_stress #### INFO: #### will start test_dynamic_weight_adjustment ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:59:19 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 22:59:19 storageqe-109 INFO: #### END test_io_weight_under_stress #### Oct 5 22:59:19 storageqe-109 INFO: #### will start test_dynamic_weight_adjustment ##### Oct 5 22:59:19 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dynamic_weight_adjustment #### INFO: #### will start test_mq_deadline_with_cgroup_weights ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:01:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:01:29 storageqe-109 INFO: #### END test_dynamic_weight_adjustment #### Oct 5 23:01:29 storageqe-109 INFO: #### will start test_mq_deadline_with_cgroup_weights ##### Oct 5 23:01:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mq_deadline_with_cgroup_weights #### INFO: #### will start test_kyber_with_cgroup_weights ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:02:44 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:02:44 storageqe-109 INFO: #### END test_mq_deadline_with_cgroup_weights #### Oct 5 23:02:44 storageqe-109 INFO: #### will start test_kyber_with_cgroup_weights ##### Oct 5 23:02:44 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_kyber_with_cgroup_weights #### INFO: #### will start test_bfq_with_cgroup_weights ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:03:59 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:03:59 storageqe-109 INFO: #### END test_kyber_with_cgroup_weights #### Oct 5 23:03:59 storageqe-109 INFO: #### will start test_bfq_with_cgroup_weights ##### Oct 5 23:03:59 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bfq_with_cgroup_weights #### INFO: #### will start test_scheduler_comparison_same_weights ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:05:44 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:05:44 storageqe-109 INFO: #### END test_bfq_with_cgroup_weights #### Oct 5 23:05:44 storageqe-109 INFO: #### will start test_scheduler_comparison_same_weights ##### Oct 5 23:05:44 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:08:37 storageqe-109 kernel: sched: DL replenish lagged too much INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_scheduler_comparison_same_weights #### INFO: #### will start test_mixed_workload_scheduler_cgroup_interaction ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:09:14 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:09:14 storageqe-109 INFO: #### END test_scheduler_comparison_same_weights #### Oct 5 23:09:14 storageqe-109 INFO: #### will start test_mixed_workload_scheduler_cgroup_interaction ##### Oct 5 23:09:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mixed_workload_scheduler_cgroup_interaction #### INFO: #### will start test_dynamic_scheduler_switching_with_cgroups ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:10:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:10:45 storageqe-109 INFO: #### END test_mixed_workload_scheduler_cgroup_interaction #### Oct 5 23:10:45 storageqe-109 INFO: #### will start test_dynamic_scheduler_switching_with_cgroups ##### Oct 5 23:10:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dynamic_scheduler_switching_with_cgroups #### INFO: #### will start test_cgroup_hierarchy_with_schedulers ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:12:55 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:12:55 storageqe-109 INFO: #### END test_dynamic_scheduler_switching_with_cgroups #### Oct 5 23:12:55 storageqe-109 INFO: #### will start test_cgroup_hierarchy_with_schedulers ##### Oct 5 23:12:55 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_cgroup_hierarchy_with_schedulers #### INFO: #### will start test_blk_mq_basic_functionality ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:14:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:14:40 storageqe-109 INFO: #### END test_cgroup_hierarchy_with_schedulers #### Oct 5 23:14:40 storageqe-109 INFO: #### will start test_blk_mq_basic_functionality ##### Oct 5 23:14:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_blk_mq_basic_functionality #### INFO: #### will start test_blk_mq_queue_mapping ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:14:51 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:14:51 storageqe-109 INFO: #### END test_blk_mq_basic_functionality #### Oct 5 23:14:51 storageqe-109 INFO: #### will start test_blk_mq_queue_mapping ##### Oct 5 23:14:51 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_blk_mq_queue_mapping #### INFO: #### will start test_blk_mq_tag_management ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:02 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:02 storageqe-109 INFO: #### END test_blk_mq_queue_mapping #### Oct 5 23:15:02 storageqe-109 INFO: #### will start test_blk_mq_tag_management ##### Oct 5 23:15:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_blk_mq_tag_management #### INFO: #### will start test_blk_mq_scheduler_integration ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:14 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:14 storageqe-109 INFO: #### END test_blk_mq_tag_management #### Oct 5 23:15:14 storageqe-109 INFO: #### will start test_blk_mq_scheduler_integration ##### Oct 5 23:15:14 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_blk_mq_scheduler_integration #### INFO: #### will start test_blk_mq_hardware_queue_scaling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:24 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:24 storageqe-109 INFO: #### END test_blk_mq_scheduler_integration #### Oct 5 23:15:24 storageqe-109 INFO: #### will start test_blk_mq_hardware_queue_scaling ##### Oct 5 23:15:24 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_blk_mq_hardware_queue_scaling #### INFO: #### will start test_blk_mq_performance_comparison ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:41 storageqe-109 INFO: #### END test_blk_mq_hardware_queue_scaling #### Oct 5 23:15:41 storageqe-109 INFO: #### will start test_blk_mq_performance_comparison ##### Oct 5 23:15:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_blk_mq_performance_comparison #### INFO: #### will start test_iocost_model_and_qos ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:55 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:15:55 storageqe-109 INFO: #### END test_blk_mq_performance_comparison #### Oct 5 23:15:55 storageqe-109 INFO: #### will start test_iocost_model_and_qos ##### Oct 5 23:15:55 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_iocost_model_and_qos #### INFO: #### will start test_iolatency_controller ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:05 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:05 storageqe-109 INFO: #### END test_iocost_model_and_qos #### Oct 5 23:16:05 storageqe-109 INFO: #### will start test_iolatency_controller ##### Oct 5 23:16:05 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_iolatency_controller #### INFO: #### will start test_write_back_throttling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:15 storageqe-109 INFO: #### END test_iolatency_controller #### Oct 5 23:16:15 storageqe-109 INFO: #### will start test_write_back_throttling ##### Oct 5 23:16:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_write_back_throttling #### INFO: #### will start test_block_crypto_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:25 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:25 storageqe-109 INFO: #### END test_write_back_throttling #### Oct 5 23:16:25 storageqe-109 INFO: #### will start test_block_crypto_features ##### Oct 5 23:16:25 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_block_crypto_features #### INFO: #### will start test_zoned_device_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:35 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:35 storageqe-109 INFO: #### END test_block_crypto_features #### Oct 5 23:16:35 storageqe-109 INFO: #### will start test_zoned_device_features ##### Oct 5 23:16:35 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_zoned_device_features #### INFO: #### will start test_data_integrity_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:46 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:46 storageqe-109 INFO: #### END test_zoned_device_features #### Oct 5 23:16:46 storageqe-109 INFO: #### will start test_data_integrity_features ##### Oct 5 23:16:46 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_data_integrity_features #### INFO: #### will start test_block_debugging_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:16:56 storageqe-109 INFO: #### END test_data_integrity_features #### Oct 5 23:16:56 storageqe-109 INFO: #### will start test_block_debugging_features ##### Oct 5 23:16:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_block_debugging_features #### INFO: #### will start test_combined_advanced_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:06 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:06 storageqe-109 INFO: #### END test_block_debugging_features #### Oct 5 23:17:06 storageqe-109 INFO: #### will start test_combined_advanced_features ##### Oct 5 23:17:06 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_combined_advanced_features #### INFO: #### will start test_realtime_io_priority_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:16 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:16 storageqe-109 INFO: #### END test_combined_advanced_features #### Oct 5 23:17:16 storageqe-109 INFO: #### will start test_realtime_io_priority_features ##### Oct 5 23:17:16 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:26 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 5 23:17:26 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 5 23:17:26 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_realtime_io_priority_features #### INFO: #### will start test_interrupt_coalescing_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:33 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:33 storageqe-109 INFO: #### END test_realtime_io_priority_features #### Oct 5 23:17:33 storageqe-109 INFO: #### will start test_interrupt_coalescing_features ##### Oct 5 23:17:33 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_interrupt_coalescing_features #### INFO: #### will start test_low_latency_path_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:45 storageqe-109 INFO: #### END test_interrupt_coalescing_features #### Oct 5 23:17:45 storageqe-109 INFO: #### will start test_low_latency_path_features ##### Oct 5 23:17:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_low_latency_path_features #### INFO: #### will start test_combined_realtime_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:17:56 storageqe-109 INFO: #### END test_low_latency_path_features #### Oct 5 23:17:56 storageqe-109 INFO: #### will start test_combined_realtime_features ##### Oct 5 23:17:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_combined_realtime_features #### INFO: #### will start test_block_queue_freeze_features ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:18:13 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:18:13 storageqe-109 INFO: #### END test_combined_realtime_features #### Oct 5 23:18:13 storageqe-109 INFO: #### will start test_block_queue_freeze_features ##### Oct 5 23:18:13 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_block_queue_freeze_features #### INFO: #### will start test_queue_freeze_recovery_mechanisms ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:18:25 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:18:25 storageqe-109 INFO: #### END test_block_queue_freeze_features #### Oct 5 23:18:25 storageqe-109 INFO: #### will start test_queue_freeze_recovery_mechanisms ##### Oct 5 23:18:25 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_queue_freeze_recovery_mechanisms #### INFO: #### will start test_scheduler_switch_induced_freeze ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:18:55 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:18:55 storageqe-109 INFO: #### END test_queue_freeze_recovery_mechanisms #### Oct 5 23:18:55 storageqe-109 INFO: #### will start test_scheduler_switch_induced_freeze ##### Oct 5 23:18:55 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_scheduler_switch_induced_freeze #### INFO: #### will start test_combined_freeze_stress_scenarios ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:19:05 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:19:05 storageqe-109 INFO: #### END test_scheduler_switch_induced_freeze #### Oct 5 23:19:05 storageqe-109 INFO: #### will start test_combined_freeze_stress_scenarios ##### Oct 5 23:19:06 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_combined_freeze_stress_scenarios #### INFO: #### will start test_luks2_io_uring_performance_comparison ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:19:26 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:19:26 storageqe-109 INFO: #### END test_combined_freeze_stress_scenarios #### Oct 5 23:19:26 storageqe-109 INFO: #### will start test_luks2_io_uring_performance_comparison ##### Oct 5 23:19:26 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:19:31 storageqe-109 kernel: sh (199551): drop_caches: 3 cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:19:33 storageqe-109 kernel: sh (199572): drop_caches: 3 Oct 5 23:19:33 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:19:41 storageqe-109 stratisd[4947]: [2025-10-06T03:19:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:19:41 storageqe-109 stratisd[4947]: [2025-10-06T03:19:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 test_crypt_luks2_io_uring -q Oct 5 23:19:51 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 test_crypt_luks2_io_uring -q Oct 5 23:19:53 storageqe-109 stratisd[4947]: [2025-10-06T03:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:19:53 storageqe-109 stratisd[4947]: [2025-10-06T03:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs xfs in remove_crypt Oct 5 23:20:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.12gy_1tsmount_test with fs xfs Oct 5 23:20:15 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem cf289b8d-e7f5-45ba-bdeb-763bc6e4a059 Oct 5 23:20:15 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:20:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.12gy_1tsmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext4 in remove_crypt Oct 5 23:20:20 storageqe-109 systemd[1]: tmp-libblockdev.12gy_1tsmount_test.mount: Deactivated successfully. Oct 5 23:20:20 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem cf289b8d-e7f5-45ba-bdeb-763bc6e4a059 Oct 5 23:20:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs xfs in remove_crypt Oct 5 23:20:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1khdbw4umount_test with fs ext4 Oct 5 23:20:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 85aa2b2f-f101-4579-9fbc-c561fb4411fc r/w with ordered data mode. Quota mode: none. Oct 5 23:20:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1khdbw4umount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext3 in remove_crypt Oct 5 23:20:36 storageqe-109 systemd[1]: tmp-libblockdev.1khdbw4umount_test.mount: Deactivated successfully. Oct 5 23:20:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 85aa2b2f-f101-4579-9fbc-c561fb4411fc. Oct 5 23:20:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext4 in remove_crypt Oct 5 23:20:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qh84qcdvmount_test with fs ext3 Oct 5 23:20:56 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:20:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem cb46f9a3-d482-4d3e-968f-b20e2f10e545 r/w with ordered data mode. Quota mode: none. Oct 5 23:20:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qh84qcdvmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext2 in remove_crypt Oct 5 23:21:02 storageqe-109 systemd[1]: tmp-libblockdev.qh84qcdvmount_test.mount: Deactivated successfully. Oct 5 23:21:02 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem cb46f9a3-d482-4d3e-968f-b20e2f10e545. Oct 5 23:21:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext3 in remove_crypt Oct 5 23:21:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.25ftwgj2mount_test with fs ext2 Oct 5 23:21:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:21:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 066e5933-4c41-4e3e-959b-f676d92db714 r/w without journal. Quota mode: none. Oct 5 23:21:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.25ftwgj2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext2 in remove_crypt INFO: remove crypt device test_crypt_luks2_io_uring Oct 5 23:21:27 storageqe-109 systemd[1]: tmp-libblockdev.25ftwgj2mount_test.mount: Deactivated successfully. Oct 5 23:21:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 066e5933-4c41-4e3e-959b-f676d92db714. Oct 5 23:21:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_io_uring and fs ext2 in remove_crypt Oct 5 23:21:27 storageqe-109 INFO: remove crypt device test_crypt_luks2_io_uring INFO: finishe the remove crypt device test_crypt_luks2_io_uring cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:21:27 storageqe-109 INFO: finishe the remove crypt device test_crypt_luks2_io_uring Oct 5 23:21:27 storageqe-109 kernel: sh (200962): drop_caches: 3 Oct 5 23:21:27 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:21:35 storageqe-109 stratisd[4947]: [2025-10-06T03:21:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:21:35 storageqe-109 stratisd[4947]: [2025-10-06T03:21:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 test_crypt_luks2_libaio -q Oct 5 23:21:45 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 test_crypt_luks2_libaio -q Oct 5 23:21:47 storageqe-109 stratisd[4947]: [2025-10-06T03:21:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:21:47 storageqe-109 stratisd[4947]: [2025-10-06T03:21:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs xfs in remove_crypt Oct 5 23:21:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.33lc8a4imount_test with fs xfs Oct 5 23:22:09 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem dd87528d-d510-49e7-b8bc-f211aa2cef97 Oct 5 23:22:09 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:22:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.33lc8a4imount_test with fs xfs Oct 5 23:22:14 storageqe-109 systemd[1]: tmp-libblockdev.33lc8a4imount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext4 in remove_crypt Oct 5 23:22:14 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem dd87528d-d510-49e7-b8bc-f211aa2cef97 Oct 5 23:22:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs xfs in remove_crypt Oct 5 23:22:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jn32284cmount_test with fs ext4 Oct 5 23:22:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4cda0767-0db8-408a-9f3f-dcfb7117d651 r/w with ordered data mode. Quota mode: none. Oct 5 23:22:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jn32284cmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext3 in remove_crypt Oct 5 23:22:30 storageqe-109 systemd[1]: tmp-libblockdev.jn32284cmount_test.mount: Deactivated successfully. Oct 5 23:22:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4cda0767-0db8-408a-9f3f-dcfb7117d651. Oct 5 23:22:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext4 in remove_crypt Oct 5 23:22:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y1nww4d7mount_test with fs ext3 Oct 5 23:22:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:22:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8aba1584-df8f-4679-a4c4-13c2876e5669 r/w with ordered data mode. Quota mode: none. Oct 5 23:22:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y1nww4d7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext2 in remove_crypt Oct 5 23:22:56 storageqe-109 systemd[1]: tmp-libblockdev.y1nww4d7mount_test.mount: Deactivated successfully. Oct 5 23:22:56 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8aba1584-df8f-4679-a4c4-13c2876e5669. Oct 5 23:22:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext3 in remove_crypt Oct 5 23:22:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bz27pn7omount_test with fs ext2 Oct 5 23:23:24 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:23:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 88ec5807-c874-4c88-9e95-3ae01c304798 r/w without journal. Quota mode: none. Oct 5 23:23:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bz27pn7omount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext2 in remove_crypt INFO: remove crypt device test_crypt_luks2_libaio INFO: finishe the remove crypt device test_crypt_luks2_libaio Oct 5 23:23:29 storageqe-109 systemd[1]: tmp-libblockdev.bz27pn7omount_test.mount: Deactivated successfully. Oct 5 23:23:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 88ec5807-c874-4c88-9e95-3ae01c304798. Oct 5 23:23:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/test_crypt_luks2_libaio and fs ext2 in remove_crypt Oct 5 23:23:29 storageqe-109 INFO: remove crypt device test_crypt_luks2_libaio Oct 5 23:23:29 storageqe-109 INFO: finishe the remove crypt device test_crypt_luks2_libaio Oct 5 23:23:30 storageqe-109 kernel: sh (202272): drop_caches: 3 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks2_io_uring_performance_comparison #### INFO: #### will start test_luks_io_uring_concurrent_stress ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:23:35 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:23:35 storageqe-109 INFO: #### END test_luks2_io_uring_performance_comparison #### Oct 5 23:23:35 storageqe-109 INFO: #### will start test_luks_io_uring_concurrent_stress ##### Oct 5 23:23:35 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:23:40 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:23:47 storageqe-109 stratisd[4947]: [2025-10-06T03:23:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:23:47 storageqe-109 stratisd[4947]: [2025-10-06T03:23:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 stress_test_crypt -q Oct 5 23:23:57 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 stress_test_crypt -q Oct 5 23:23:59 storageqe-109 stratisd[4947]: [2025-10-06T03:23:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:23:59 storageqe-109 stratisd[4947]: [2025-10-06T03:23:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs xfs in remove_crypt Oct 5 23:24:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs xfs in remove_crypt Oct 5 23:24:22 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 26f2c0be-86b8-4d5b-8946-3950811b7a3e INFO: will run io in dir /tmp/libblockdev.3pah58b3mount_test with fs xfs Oct 5 23:24:22 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:24:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3pah58b3mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext4 in remove_crypt Oct 5 23:24:26 storageqe-109 systemd[1]: tmp-libblockdev.3pah58b3mount_test.mount: Deactivated successfully. Oct 5 23:24:26 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 26f2c0be-86b8-4d5b-8946-3950811b7a3e Oct 5 23:24:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs xfs in remove_crypt Oct 5 23:24:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1ox51bdimount_test with fs ext4 Oct 5 23:24:37 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 77a11c33-cfbe-42c7-829f-9c7f07ee1af1 r/w with ordered data mode. Quota mode: none. Oct 5 23:24:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1ox51bdimount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext3 in remove_crypt Oct 5 23:24:43 storageqe-109 systemd[1]: tmp-libblockdev.1ox51bdimount_test.mount: Deactivated successfully. Oct 5 23:24:43 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 77a11c33-cfbe-42c7-829f-9c7f07ee1af1. Oct 5 23:24:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext4 in remove_crypt Oct 5 23:24:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext3 in remove_crypt Oct 5 23:25:04 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.bs33al6rmount_test with fs ext3 Oct 5 23:25:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4744af68-df95-4eea-9417-c67d63de9986 r/w with ordered data mode. Quota mode: none. Oct 5 23:25:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bs33al6rmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext2 in remove_crypt Oct 5 23:25:09 storageqe-109 systemd[1]: tmp-libblockdev.bs33al6rmount_test.mount: Deactivated successfully. Oct 5 23:25:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4744af68-df95-4eea-9417-c67d63de9986. Oct 5 23:25:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext3 in remove_crypt Oct 5 23:25:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q33z7zpjmount_test with fs ext2 Oct 5 23:25:30 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:25:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5e9d723e-f8de-4db9-acdc-9f592d5acaf4 r/w without journal. Quota mode: none. Oct 5 23:25:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q33z7zpjmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device stress_test_crypt INFO: finishe the remove crypt device stress_test_crypt Oct 5 23:25:35 storageqe-109 systemd[1]: tmp-libblockdev.q33z7zpjmount_test.mount: Deactivated successfully. Oct 5 23:25:35 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5e9d723e-f8de-4db9-acdc-9f592d5acaf4. Oct 5 23:25:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/stress_test_crypt and fs ext2 in remove_crypt Oct 5 23:25:35 storageqe-109 INFO: remove crypt device stress_test_crypt Oct 5 23:25:35 storageqe-109 INFO: finishe the remove crypt device stress_test_crypt INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_io_uring_concurrent_stress #### INFO: #### will start test_opal_luks_hybrid_performance ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:25:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:25:40 storageqe-109 INFO: #### END test_luks_io_uring_concurrent_stress #### Oct 5 23:25:40 storageqe-109 INFO: #### will start test_opal_luks_hybrid_performance ##### Oct 5 23:25:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:25:45 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:25:45 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:25:45 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:25:45 storageqe-109 stratisd[4947]: [2025-10-06T03:25:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:25:45 storageqe-109 stratisd[4947]: [2025-10-06T03:25:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:25:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:25:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:25:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:25:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:25:56 storageqe-109 stratisd[4947]: [2025-10-06T03:25:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:25:56 storageqe-109 stratisd[4947]: [2025-10-06T03:25:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 hybrid_perf_test -q Oct 5 23:26:06 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 hybrid_perf_test -q Oct 5 23:26:08 storageqe-109 stratisd[4947]: [2025-10-06T03:26:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:26:08 storageqe-109 stratisd[4947]: [2025-10-06T03:26:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:26:15 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs xfs in remove_crypt Oct 5 23:26:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.22kinjm8mount_test with fs xfs Oct 5 23:26:30 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 6a1d9f9b-0666-43fb-a35c-6df2d66e555d Oct 5 23:26:30 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:26:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.22kinjm8mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext4 in remove_crypt Oct 5 23:26:35 storageqe-109 systemd[1]: tmp-libblockdev.22kinjm8mount_test.mount: Deactivated successfully. Oct 5 23:26:35 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 6a1d9f9b-0666-43fb-a35c-6df2d66e555d Oct 5 23:26:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs xfs in remove_crypt Oct 5 23:26:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ul0jien5mount_test with fs ext4 Oct 5 23:26:45 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3c17b877-6a24-47c7-b639-98281b89cc3a r/w with ordered data mode. Quota mode: none. Oct 5 23:26:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ul0jien5mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext3 in remove_crypt Oct 5 23:26:52 storageqe-109 systemd[1]: tmp-libblockdev.ul0jien5mount_test.mount: Deactivated successfully. Oct 5 23:26:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3c17b877-6a24-47c7-b639-98281b89cc3a. Oct 5 23:26:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext4 in remove_crypt Oct 5 23:26:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mrdbpeq_mount_test with fs ext3 Oct 5 23:27:13 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:27:13 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 82b414ac-2bb5-4990-a309-abc812c5c4f6 r/w with ordered data mode. Quota mode: none. Oct 5 23:27:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mrdbpeq_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext2 in remove_crypt Oct 5 23:27:18 storageqe-109 systemd[1]: tmp-libblockdev.mrdbpeq_mount_test.mount: Deactivated successfully. Oct 5 23:27:18 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 82b414ac-2bb5-4990-a309-abc812c5c4f6. Oct 5 23:27:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext3 in remove_crypt Oct 5 23:27:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.snxpdl30mount_test with fs ext2 Oct 5 23:27:38 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:27:38 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7155d240-a6eb-46f5-8fa5-b53e2111d9f2 r/w without journal. Quota mode: none. Oct 5 23:27:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.snxpdl30mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext2 in remove_crypt INFO: remove crypt device hybrid_perf_test Oct 5 23:27:43 storageqe-109 systemd[1]: tmp-libblockdev.snxpdl30mount_test.mount: Deactivated successfully. Oct 5 23:27:43 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7155d240-a6eb-46f5-8fa5-b53e2111d9f2. Oct 5 23:27:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hybrid_perf_test and fs ext2 in remove_crypt Oct 5 23:27:43 storageqe-109 INFO: remove crypt device hybrid_perf_test cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:27:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 5 23:27:53 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:28:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:28:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:28:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:28:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:28:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device hybrid_perf_test cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:28:37 storageqe-109 INFO: finishe the remove crypt device hybrid_perf_test Oct 5 23:28:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_opal_luks_hybrid_performance #### INFO: #### will start test_opal_performance_vs_software_encryption ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:28:52 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:28:52 storageqe-109 INFO: #### END test_opal_luks_hybrid_performance #### Oct 5 23:28:52 storageqe-109 INFO: #### will start test_opal_performance_vs_software_encryption ##### Oct 5 23:28:52 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:28:57 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:29:08 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:29:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:29:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:29:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:29:08 storageqe-109 stratisd[4947]: [2025-10-06T03:29:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:29:08 storageqe-109 stratisd[4947]: [2025-10-06T03:29:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 opal_perf_test -q Oct 5 23:29:18 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 opal_perf_test -q Oct 5 23:29:21 storageqe-109 stratisd[4947]: [2025-10-06T03:29:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:29:21 storageqe-109 stratisd[4947]: [2025-10-06T03:29:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:29:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs xfs in remove_crypt Oct 5 23:29:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.4jzy6ofimount_test with fs xfs Oct 5 23:29:42 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 8d8e13b1-d1ff-4a17-8d07-a259cf63fa20 Oct 5 23:29:42 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:29:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4jzy6ofimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs ext4 in remove_crypt Oct 5 23:29:47 storageqe-109 systemd[1]: tmp-libblockdev.4jzy6ofimount_test.mount: Deactivated successfully. Oct 5 23:29:47 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 8d8e13b1-d1ff-4a17-8d07-a259cf63fa20 Oct 5 23:29:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs xfs in remove_crypt Oct 5 23:29:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.iqxlf1femount_test with fs ext4 Oct 5 23:29:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4e05d356-f285-4ded-b5b9-03fe50ee7c65 r/w with ordered data mode. Quota mode: none. Oct 5 23:29:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iqxlf1femount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs ext3 in remove_crypt Oct 5 23:30:04 storageqe-109 systemd[1]: tmp-libblockdev.iqxlf1femount_test.mount: Deactivated successfully. Oct 5 23:30:04 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4e05d356-f285-4ded-b5b9-03fe50ee7c65. Oct 5 23:30:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs ext4 in remove_crypt Oct 5 23:30:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x3hecdc5mount_test with fs ext3 Oct 5 23:30:25 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:30:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d2c75883-9a45-4641-a447-243f912f4a86 r/w with ordered data mode. Quota mode: none. Oct 5 23:30:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x3hecdc5mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs ext2 in remove_crypt Oct 5 23:30:30 storageqe-109 systemd[1]: tmp-libblockdev.x3hecdc5mount_test.mount: Deactivated successfully. Oct 5 23:30:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d2c75883-9a45-4641-a447-243f912f4a86. Oct 5 23:30:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs ext3 in remove_crypt Oct 5 23:30:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_perf_test and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y9ov5uwwmount_test with fs ext2 Oct 5 23:30:50 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:30:50 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 381c5ba7-bf7f-45f1-ba80-77e6f7561618 r/w without journal. Quota mode: none. Oct 5 23:30:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y9ov5uwwmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs ext2 in remove_crypt INFO: remove crypt device opal_perf_test Oct 5 23:30:55 storageqe-109 systemd[1]: tmp-libblockdev.y9ov5uwwmount_test.mount: Deactivated successfully. Oct 5 23:30:55 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 381c5ba7-bf7f-45f1-ba80-77e6f7561618. Oct 5 23:30:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_perf_test and fs ext2 in remove_crypt Oct 5 23:30:55 storageqe-109 INFO: remove crypt device opal_perf_test cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:30:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 5 23:31:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:31:17 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:31:27 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:31:27 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:31:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:31:39 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device opal_perf_test cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:31:49 storageqe-109 INFO: finishe the remove crypt device opal_perf_test Oct 5 23:31:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:31:59 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:32:07 storageqe-109 stratisd[4947]: [2025-10-06T03:32:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:32:07 storageqe-109 stratisd[4947]: [2025-10-06T03:32:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 perf_test_crypt -q Oct 5 23:32:17 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 perf_test_crypt -q Oct 5 23:32:19 storageqe-109 stratisd[4947]: [2025-10-06T03:32:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:32:19 storageqe-109 stratisd[4947]: [2025-10-06T03:32:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:32:19 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs xfs in remove_crypt Oct 5 23:32:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.k3qhiiszmount_test with fs xfs Oct 5 23:32:40 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 8bf6e798-b770-4567-9aba-ac53d9f8a71c Oct 5 23:32:40 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:32:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k3qhiiszmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext4 in remove_crypt Oct 5 23:32:45 storageqe-109 systemd[1]: tmp-libblockdev.k3qhiiszmount_test.mount: Deactivated successfully. Oct 5 23:32:45 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 8bf6e798-b770-4567-9aba-ac53d9f8a71c Oct 5 23:32:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs xfs in remove_crypt Oct 5 23:32:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6yjodybmmount_test with fs ext4 Oct 5 23:32:56 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4b9f8e5c-037e-4077-9514-bbe6778f0439 r/w with ordered data mode. Quota mode: none. Oct 5 23:32:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6yjodybmmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext3 in remove_crypt Oct 5 23:33:01 storageqe-109 systemd[1]: tmp-libblockdev.6yjodybmmount_test.mount: Deactivated successfully. Oct 5 23:33:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4b9f8e5c-037e-4077-9514-bbe6778f0439. Oct 5 23:33:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext4 in remove_crypt Oct 5 23:33:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext3 in remove_crypt Oct 5 23:33:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:33:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2709a868-34d4-4dce-bd9d-916bf6b6b51b r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.ec54g5ynmount_test with fs ext3 Oct 5 23:33:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ec54g5ynmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext2 in remove_crypt Oct 5 23:33:27 storageqe-109 systemd[1]: tmp-libblockdev.ec54g5ynmount_test.mount: Deactivated successfully. Oct 5 23:33:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2709a868-34d4-4dce-bd9d-916bf6b6b51b. Oct 5 23:33:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext3 in remove_crypt Oct 5 23:33:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lm61qas1mount_test with fs ext2 Oct 5 23:33:48 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:33:48 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ecd8a0af-5afc-49e8-b570-a12c41dd35cb r/w without journal. Quota mode: none. Oct 5 23:33:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lm61qas1mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device perf_test_crypt Oct 5 23:33:52 storageqe-109 systemd[1]: tmp-libblockdev.lm61qas1mount_test.mount: Deactivated successfully. Oct 5 23:33:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ecd8a0af-5afc-49e8-b570-a12c41dd35cb. Oct 5 23:33:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/perf_test_crypt and fs ext2 in remove_crypt Oct 5 23:33:52 storageqe-109 INFO: remove crypt device perf_test_crypt INFO: finishe the remove crypt device perf_test_crypt cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:33:53 storageqe-109 INFO: finishe the remove crypt device perf_test_crypt Oct 5 23:33:53 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:33:53 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:33:53 storageqe-109 stratisd[4947]: [2025-10-06T03:33:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:33:53 storageqe-109 stratisd[4947]: [2025-10-06T03:33:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:33:53 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_opal_performance_vs_software_encryption #### INFO: #### will start test_opal_inline_encryption_security_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:34:08 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:34:08 storageqe-109 INFO: #### END test_opal_performance_vs_software_encryption #### Oct 5 23:34:08 storageqe-109 INFO: #### will start test_opal_inline_encryption_security_validation ##### Oct 5 23:34:08 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '512' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:34:13 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '512' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:34:13 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 5 23:34:13 storageqe-109 stratisd[4947]: [2025-10-06T03:34:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:34:13 storageqe-109 stratisd[4947]: [2025-10-06T03:34:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:34:13 storageqe-109 dnf[208432]: Updating Subscription Management repositories. Oct 5 23:34:13 storageqe-109 dnf[208432]: Unable to read consumer identity Oct 5 23:34:13 storageqe-109 dnf[208432]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 5 23:34:13 storageqe-109 dnf[208432]: Metadata cache refreshed recently. Oct 5 23:34:13 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 5 23:34:13 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 5 23:34:13 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 233ms CPU time, 64.3M memory peak. Oct 5 23:34:24 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:34:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:34:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:34:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:34:24 storageqe-109 stratisd[4947]: [2025-10-06T03:34:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:34:24 storageqe-109 stratisd[4947]: [2025-10-06T03:34:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 security_opal_aes256_secure -q Oct 5 23:34:34 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 security_opal_aes256_secure -q Oct 5 23:34:36 storageqe-109 stratisd[4947]: [2025-10-06T03:34:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:34:36 storageqe-109 stratisd[4947]: [2025-10-06T03:34:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:34:43 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs xfs in remove_crypt Oct 5 23:34:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.5req6t8amount_test with fs xfs Oct 5 23:35:01 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem a615a06b-8236-4828-990c-4824d02a92ce Oct 5 23:35:01 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:35:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5req6t8amount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext4 in remove_crypt Oct 5 23:35:06 storageqe-109 systemd[1]: tmp-libblockdev.5req6t8amount_test.mount: Deactivated successfully. Oct 5 23:35:06 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem a615a06b-8236-4828-990c-4824d02a92ce Oct 5 23:35:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs xfs in remove_crypt Oct 5 23:35:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rcg83eo6mount_test with fs ext4 Oct 5 23:35:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0f27a422-40ea-4b45-b618-b48ee60d99ad r/w with ordered data mode. Quota mode: none. Oct 5 23:35:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rcg83eo6mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext3 in remove_crypt Oct 5 23:35:22 storageqe-109 systemd[1]: tmp-libblockdev.rcg83eo6mount_test.mount: Deactivated successfully. Oct 5 23:35:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0f27a422-40ea-4b45-b618-b48ee60d99ad. Oct 5 23:35:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext4 in remove_crypt Oct 5 23:35:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x06h3rm4mount_test with fs ext3 Oct 5 23:35:43 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:35:43 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0a125dbc-f082-4bdd-bc02-99ec0b0c5dc2 r/w with ordered data mode. Quota mode: none. Oct 5 23:35:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x06h3rm4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext2 in remove_crypt Oct 5 23:35:48 storageqe-109 systemd[1]: tmp-libblockdev.x06h3rm4mount_test.mount: Deactivated successfully. Oct 5 23:35:48 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0a125dbc-f082-4bdd-bc02-99ec0b0c5dc2. Oct 5 23:35:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext3 in remove_crypt Oct 5 23:35:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q2_58xfzmount_test with fs ext2 Oct 5 23:36:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:36:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5889dce0-8015-49ef-88a9-ad5ba51703f6 r/w without journal. Quota mode: none. Oct 5 23:36:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q2_58xfzmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext2 in remove_crypt INFO: remove crypt device security_opal_aes256_secure Oct 5 23:36:13 storageqe-109 systemd[1]: tmp-libblockdev.q2_58xfzmount_test.mount: Deactivated successfully. Oct 5 23:36:13 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5889dce0-8015-49ef-88a9-ad5ba51703f6. Oct 5 23:36:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_aes256_secure and fs ext2 in remove_crypt Oct 5 23:36:13 storageqe-109 INFO: remove crypt device security_opal_aes256_secure cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:36:14 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 5 23:36:24 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:36:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:36:46 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:36:46 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:36:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:36:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device security_opal_aes256_secure cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:37:08 storageqe-109 INFO: finishe the remove crypt device security_opal_aes256_secure Oct 5 23:37:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '512' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 5 23:37:18 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '512' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 5 23:37:28 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:37:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:28 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:37:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:37:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:37:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:37:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:37:29 storageqe-109 stratisd[4947]: [2025-10-06T03:37:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:37:29 storageqe-109 stratisd[4947]: [2025-10-06T03:37:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 security_opal_only_mode -q Oct 5 23:37:39 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 security_opal_only_mode -q Oct 5 23:37:41 storageqe-109 stratisd[4947]: [2025-10-06T03:37:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:37:41 storageqe-109 stratisd[4947]: [2025-10-06T03:37:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:37:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs xfs in remove_crypt Oct 5 23:37:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.o53eabujmount_test with fs xfs Oct 5 23:38:06 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 66761faa-d7e3-408c-b68f-77ab2fc7fe3e Oct 5 23:38:06 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:38:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.o53eabujmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext4 in remove_crypt Oct 5 23:38:11 storageqe-109 systemd[1]: tmp-libblockdev.o53eabujmount_test.mount: Deactivated successfully. Oct 5 23:38:11 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 66761faa-d7e3-408c-b68f-77ab2fc7fe3e Oct 5 23:38:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs xfs in remove_crypt Oct 5 23:38:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.k2l39j1zmount_test with fs ext4 Oct 5 23:38:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e745fb9d-d53b-43dd-80c9-1269b7ab9eb2 r/w with ordered data mode. Quota mode: none. Oct 5 23:38:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k2l39j1zmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext3 in remove_crypt Oct 5 23:38:28 storageqe-109 systemd[1]: tmp-libblockdev.k2l39j1zmount_test.mount: Deactivated successfully. Oct 5 23:38:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e745fb9d-d53b-43dd-80c9-1269b7ab9eb2. Oct 5 23:38:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext4 in remove_crypt Oct 5 23:38:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z7ilkd6omount_test with fs ext3 Oct 5 23:38:50 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:38:50 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c09ae682-aa2e-4e9a-b18a-7b3d0ec2010f r/w with ordered data mode. Quota mode: none. Oct 5 23:38:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z7ilkd6omount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext2 in remove_crypt Oct 5 23:38:55 storageqe-109 systemd[1]: tmp-libblockdev.z7ilkd6omount_test.mount: Deactivated successfully. Oct 5 23:38:55 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c09ae682-aa2e-4e9a-b18a-7b3d0ec2010f. Oct 5 23:38:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext3 in remove_crypt Oct 5 23:38:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rlkmoiv2mount_test with fs ext2 Oct 5 23:39:16 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:39:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0f811f78-cd91-41e8-9beb-decabeba1f37 r/w without journal. Quota mode: none. Oct 5 23:39:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rlkmoiv2mount_test with fs ext2 Oct 5 23:39:21 storageqe-109 systemd[1]: tmp-libblockdev.rlkmoiv2mount_test.mount: Deactivated successfully. Oct 5 23:39:21 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0f811f78-cd91-41e8-9beb-decabeba1f37. INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext2 in remove_crypt INFO: remove crypt device security_opal_only_mode Oct 5 23:39:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/security_opal_only_mode and fs ext2 in remove_crypt Oct 5 23:39:21 storageqe-109 INFO: remove crypt device security_opal_only_mode cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:39:21 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 5 23:39:31 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:39:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:39:53 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:39:53 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:39:53 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:40:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device security_opal_only_mode cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:40:15 storageqe-109 INFO: finishe the remove crypt device security_opal_only_mode Oct 5 23:40:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:40:25 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_opal_inline_encryption_security_validation #### INFO: #### will start test_opal_key_management_security ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:40:41 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:40:41 storageqe-109 INFO: #### END test_opal_inline_encryption_security_validation #### Oct 5 23:40:41 storageqe-109 INFO: #### will start test_opal_key_management_security ##### Oct 5 23:40:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:40:46 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:40:56 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:40:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:56 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:40:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:40:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:40:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:40:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:40:57 storageqe-109 stratisd[4947]: [2025-10-06T03:40:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:40:57 storageqe-109 stratisd[4947]: [2025-10-06T03:40:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:41:07 storageqe-109 kernel: perf: interrupt took too long (3178 > 3163), lowering kernel.perf_event_max_sample_rate to 62000 Oct 5 23:41:16 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 23:41:17 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:41:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:41:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:41:17 storageqe-109 stratisd[4947]: [2025-10-06T03:41:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:41:17 storageqe-109 stratisd[4947]: [2025-10-06T03:41:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security_primary -q Oct 5 23:41:27 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security_primary -q Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:41:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:41:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:41:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:41:27 storageqe-109 stratisd[4947]: [2025-10-06T03:41:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:41:27 storageqe-109 stratisd[4947]: [2025-10-06T03:41:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:41:30 storageqe-109 stratisd[4947]: [2025-10-06T03:41:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:41:30 storageqe-109 stratisd[4947]: [2025-10-06T03:41:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security_backup -q Oct 5 23:41:40 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security_backup -q Oct 5 23:41:43 storageqe-109 stratisd[4947]: [2025-10-06T03:41:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:41:43 storageqe-109 stratisd[4947]: [2025-10-06T03:41:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security_emergency -q Oct 5 23:41:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security_emergency -q Oct 5 23:41:56 storageqe-109 stratisd[4947]: [2025-10-06T03:41:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:41:56 storageqe-109 stratisd[4947]: [2025-10-06T03:41:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' luksRemoveKey /dev/nvme0n1 -q Oct 5 23:42:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:42:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:16 storageqe-109 journal: cryptsetup --type 'luks2' luksRemoveKey /dev/nvme0n1 -q Oct 5 23:42:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:42:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:42:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:42:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:42:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:42:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:42:17 storageqe-109 stratisd[4947]: [2025-10-06T03:42:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:42:17 storageqe-109 stratisd[4947]: [2025-10-06T03:42:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:42:19 storageqe-109 stratisd[4947]: [2025-10-06T03:42:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:42:19 storageqe-109 stratisd[4947]: [2025-10-06T03:42:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security -q Oct 5 23:42:29 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 opal_key_security -q Oct 5 23:42:35 storageqe-109 stratisd[4947]: [2025-10-06T03:42:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:42:35 storageqe-109 stratisd[4947]: [2025-10-06T03:42:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs xfs in remove_crypt Oct 5 23:42:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.0fu26ykgmount_test with fs xfs Oct 5 23:42:57 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 8a3755d7-6bad-4176-9ba7-106448f03a9b Oct 5 23:42:57 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:42:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0fu26ykgmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs ext4 in remove_crypt Oct 5 23:43:01 storageqe-109 systemd[1]: tmp-libblockdev.0fu26ykgmount_test.mount: Deactivated successfully. Oct 5 23:43:01 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 8a3755d7-6bad-4176-9ba7-106448f03a9b Oct 5 23:43:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs xfs in remove_crypt Oct 5 23:43:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tdad_yozmount_test with fs ext4 Oct 5 23:43:12 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 26ed4721-7ac0-45c6-9047-00b56d19dd2e r/w with ordered data mode. Quota mode: none. Oct 5 23:43:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tdad_yozmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs ext3 in remove_crypt Oct 5 23:43:17 storageqe-109 systemd[1]: tmp-libblockdev.tdad_yozmount_test.mount: Deactivated successfully. Oct 5 23:43:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 26ed4721-7ac0-45c6-9047-00b56d19dd2e. Oct 5 23:43:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs ext4 in remove_crypt Oct 5 23:43:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.71ekn92kmount_test with fs ext3 Oct 5 23:43:38 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:43:38 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 569f1f94-f716-4b12-9ce4-a01fb92c1ddc r/w with ordered data mode. Quota mode: none. Oct 5 23:43:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.71ekn92kmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs ext2 in remove_crypt Oct 5 23:43:43 storageqe-109 systemd[1]: tmp-libblockdev.71ekn92kmount_test.mount: Deactivated successfully. Oct 5 23:43:43 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 569f1f94-f716-4b12-9ce4-a01fb92c1ddc. Oct 5 23:43:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs ext3 in remove_crypt Oct 5 23:43:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/opal_key_security and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kvyz5fozmount_test with fs ext2 Oct 5 23:44:04 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:44:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b897719a-c5cc-4aa6-bb05-a884bba0e69c r/w without journal. Quota mode: none. Oct 5 23:44:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kvyz5fozmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs ext2 in remove_crypt Oct 5 23:44:08 storageqe-109 systemd[1]: tmp-libblockdev.kvyz5fozmount_test.mount: Deactivated successfully. Oct 5 23:44:08 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b897719a-c5cc-4aa6-bb05-a884bba0e69c. Oct 5 23:44:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/opal_key_security and fs ext2 in remove_crypt INFO: remove crypt device opal_key_security Oct 5 23:44:09 storageqe-109 INFO: remove crypt device opal_key_security cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:44:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 5 23:44:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:44:31 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:44:41 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:44:41 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:44:41 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:44:53 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device opal_key_security cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:45:03 storageqe-109 INFO: finishe the remove crypt device opal_key_security Oct 5 23:45:03 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_opal_key_management_security #### INFO: #### will start test_opal_concurrent_access_security ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:45:18 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:45:18 storageqe-109 INFO: #### END test_opal_key_management_security #### Oct 5 23:45:18 storageqe-109 INFO: #### will start test_opal_concurrent_access_security ##### Oct 5 23:45:18 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:45:23 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:45:34 storageqe-109 kernel: nvme_log_error: 512 callbacks suppressed Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: blk_print_req_error: 512 callbacks suppressed Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: buffer_io_error: 502 callbacks suppressed Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:45:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:45:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:45:34 storageqe-109 stratisd[4947]: [2025-10-06T03:45:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:45:34 storageqe-109 stratisd[4947]: [2025-10-06T03:45:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:45:53 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 5 23:45:54 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:45:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:45:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:45:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:45:55 storageqe-109 stratisd[4947]: [2025-10-06T03:45:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:45:55 storageqe-109 stratisd[4947]: [2025-10-06T03:45:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 access_test_main -q Oct 5 23:46:05 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 access_test_main -q Oct 5 23:46:05 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:46:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:46:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:46:05 storageqe-109 stratisd[4947]: [2025-10-06T03:46:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:46:05 storageqe-109 stratisd[4947]: [2025-10-06T03:46:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:46:07 storageqe-109 stratisd[4947]: [2025-10-06T03:46:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:46:07 storageqe-109 stratisd[4947]: [2025-10-06T03:46:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 access_test_user1 -q Oct 5 23:46:18 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 access_test_user1 -q Oct 5 23:46:23 storageqe-109 stratisd[4947]: [2025-10-06T03:46:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:46:23 storageqe-109 stratisd[4947]: [2025-10-06T03:46:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 access_test_user2 -q Oct 5 23:46:34 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 access_test_user2 -q Oct 5 23:46:40 storageqe-109 stratisd[4947]: [2025-10-06T03:46:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:46:40 storageqe-109 stratisd[4947]: [2025-10-06T03:46:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:46:51 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:46:51 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:46:51 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:46:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:46:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:46:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_opal_concurrent_access_security #### INFO: #### will start test_opal_hardware_software_encryption_isolation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:47:09 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:47:09 storageqe-109 INFO: #### END test_opal_concurrent_access_security #### Oct 5 23:47:09 storageqe-109 INFO: #### will start test_opal_hardware_software_encryption_isolation ##### Oct 5 23:47:09 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 5 23:47:14 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:47:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:47:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:47:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:47:25 storageqe-109 stratisd[4947]: [2025-10-06T03:47:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:47:25 storageqe-109 stratisd[4947]: [2025-10-06T03:47:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 isolation_hardware_only -q Oct 5 23:47:35 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 isolation_hardware_only -q Oct 5 23:47:38 storageqe-109 stratisd[4947]: [2025-10-06T03:47:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:47:38 storageqe-109 stratisd[4947]: [2025-10-06T03:47:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:47:44 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs xfs in remove_crypt Oct 5 23:47:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2n9tiuq1mount_test with fs xfs Oct 5 23:47:59 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 7b8257ca-5ed1-43b6-aa4a-19b5a51e210f Oct 5 23:47:59 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:47:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2n9tiuq1mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext4 in remove_crypt Oct 5 23:48:04 storageqe-109 systemd[1]: tmp-libblockdev.2n9tiuq1mount_test.mount: Deactivated successfully. Oct 5 23:48:04 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 7b8257ca-5ed1-43b6-aa4a-19b5a51e210f Oct 5 23:48:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs xfs in remove_crypt Oct 5 23:48:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.aepo42a1mount_test with fs ext4 Oct 5 23:48:15 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 86dfa8ae-dfa0-4a58-991e-ef90872b0417 r/w with ordered data mode. Quota mode: none. Oct 5 23:48:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.aepo42a1mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext3 in remove_crypt Oct 5 23:48:20 storageqe-109 systemd[1]: tmp-libblockdev.aepo42a1mount_test.mount: Deactivated successfully. Oct 5 23:48:20 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 86dfa8ae-dfa0-4a58-991e-ef90872b0417. Oct 5 23:48:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext4 in remove_crypt Oct 5 23:48:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hram406cmount_test with fs ext3 Oct 5 23:48:42 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:48:42 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ece01f58-8003-4f52-8ad6-6572c6cfe126 r/w with ordered data mode. Quota mode: none. Oct 5 23:48:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hram406cmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext2 in remove_crypt Oct 5 23:48:47 storageqe-109 systemd[1]: tmp-libblockdev.hram406cmount_test.mount: Deactivated successfully. Oct 5 23:48:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ece01f58-8003-4f52-8ad6-6572c6cfe126. Oct 5 23:48:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext3 in remove_crypt Oct 5 23:48:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.arsgknl6mount_test with fs ext2 Oct 5 23:49:09 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:49:09 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1aa466bc-0ff7-4c75-b55f-3c8c898c550d r/w without journal. Quota mode: none. Oct 5 23:49:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.arsgknl6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext2 in remove_crypt INFO: remove crypt device isolation_hardware_only Oct 5 23:49:13 storageqe-109 systemd[1]: tmp-libblockdev.arsgknl6mount_test.mount: Deactivated successfully. Oct 5 23:49:13 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1aa466bc-0ff7-4c75-b55f-3c8c898c550d. Oct 5 23:49:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hardware_only and fs ext2 in remove_crypt Oct 5 23:49:13 storageqe-109 INFO: remove crypt device isolation_hardware_only cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:49:14 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 5 23:49:24 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:49:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:49:46 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:49:46 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:49:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:49:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device isolation_hardware_only cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:50:08 storageqe-109 INFO: finishe the remove crypt device isolation_hardware_only Oct 5 23:50:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:50:18 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 5 23:50:28 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 5 23:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:28 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 5 23:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 5 23:50:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 5 23:50:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 5 23:50:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 5 23:50:29 storageqe-109 stratisd[4947]: [2025-10-06T03:50:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:50:29 storageqe-109 stratisd[4947]: [2025-10-06T03:50:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 isolation_hybrid_mode -q Oct 5 23:50:39 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 isolation_hybrid_mode -q Oct 5 23:50:41 storageqe-109 stratisd[4947]: [2025-10-06T03:50:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:50:41 storageqe-109 stratisd[4947]: [2025-10-06T03:50:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:50:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs xfs in remove_crypt Oct 5 23:50:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2y76krwmmount_test with fs xfs Oct 5 23:51:02 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 4373430c-7540-440f-9310-f1996093ea05 Oct 5 23:51:02 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:51:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2y76krwmmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext4 in remove_crypt Oct 5 23:51:07 storageqe-109 systemd[1]: tmp-libblockdev.2y76krwmmount_test.mount: Deactivated successfully. Oct 5 23:51:07 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 4373430c-7540-440f-9310-f1996093ea05 Oct 5 23:51:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs xfs in remove_crypt Oct 5 23:51:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rm77w744mount_test with fs ext4 Oct 5 23:51:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 877a12fd-4833-4b6b-abc2-e8d5335c2b2f r/w with ordered data mode. Quota mode: none. Oct 5 23:51:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rm77w744mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext3 in remove_crypt Oct 5 23:51:24 storageqe-109 systemd[1]: tmp-libblockdev.rm77w744mount_test.mount: Deactivated successfully. Oct 5 23:51:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 877a12fd-4833-4b6b-abc2-e8d5335c2b2f. Oct 5 23:51:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext4 in remove_crypt Oct 5 23:51:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3wxa4vsvmount_test with fs ext3 Oct 5 23:51:45 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:51:45 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem efefe2c9-33bc-4ac2-8071-c4457f629ae6 r/w with ordered data mode. Quota mode: none. Oct 5 23:51:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3wxa4vsvmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext2 in remove_crypt Oct 5 23:51:50 storageqe-109 systemd[1]: tmp-libblockdev.3wxa4vsvmount_test.mount: Deactivated successfully. Oct 5 23:51:50 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem efefe2c9-33bc-4ac2-8071-c4457f629ae6. Oct 5 23:51:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext3 in remove_crypt Oct 5 23:51:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9ffg0dk8mount_test with fs ext2 Oct 5 23:52:10 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:52:10 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d556a420-12af-4c74-b024-4ecc3fa6c1fe r/w without journal. Quota mode: none. Oct 5 23:52:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9ffg0dk8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext2 in remove_crypt INFO: remove crypt device isolation_hybrid_mode Oct 5 23:52:15 storageqe-109 systemd[1]: tmp-libblockdev.9ffg0dk8mount_test.mount: Deactivated successfully. Oct 5 23:52:15 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d556a420-12af-4c74-b024-4ecc3fa6c1fe. Oct 5 23:52:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/isolation_hybrid_mode and fs ext2 in remove_crypt Oct 5 23:52:15 storageqe-109 INFO: remove crypt device isolation_hybrid_mode cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:52:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 5 23:52:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:52:37 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:52:48 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 5 23:52:48 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 5 23:52:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 5 23:52:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device isolation_hybrid_mode cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:53:09 storageqe-109 INFO: finishe the remove crypt device isolation_hybrid_mode Oct 5 23:53:09 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 5 23:53:20 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_opal_hardware_software_encryption_isolation #### INFO: #### will start test_luks_header_backup_restore ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:53:35 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:53:35 storageqe-109 INFO: #### END test_opal_hardware_software_encryption_isolation #### Oct 5 23:53:35 storageqe-109 INFO: #### will start test_luks_header_backup_restore ##### Oct 5 23:53:35 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:53:40 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:53:47 storageqe-109 stratisd[4947]: [2025-10-06T03:53:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:53:47 storageqe-109 stratisd[4947]: [2025-10-06T03:53:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:53:50 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --type 'luks2' open /dev/nvme0n1 disaster_test_crypt -q Oct 5 23:53:57 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 disaster_test_crypt -q Oct 5 23:53:59 storageqe-109 stratisd[4947]: [2025-10-06T03:53:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:53:59 storageqe-109 stratisd[4947]: [2025-10-06T03:53:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 disaster_test_crypt -q Oct 5 23:54:10 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 disaster_test_crypt -q cryptsetup --type 'luks2' open /dev/nvme0n1 disaster_test_crypt -q Oct 5 23:54:20 storageqe-109 stratisd[4947]: [2025-10-06T03:54:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:54:20 storageqe-109 stratisd[4947]: [2025-10-06T03:54:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:54:20 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 disaster_test_crypt -q Oct 5 23:54:22 storageqe-109 stratisd[4947]: [2025-10-06T03:54:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:54:22 storageqe-109 stratisd[4947]: [2025-10-06T03:54:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs xfs in remove_crypt Oct 5 23:54:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.eg0qyj2xmount_test with fs xfs Oct 5 23:54:42 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem e81ced8f-5722-40eb-87a1-edfd026f1ada Oct 5 23:54:42 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:54:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.eg0qyj2xmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext4 in remove_crypt Oct 5 23:54:47 storageqe-109 systemd[1]: tmp-libblockdev.eg0qyj2xmount_test.mount: Deactivated successfully. Oct 5 23:54:47 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem e81ced8f-5722-40eb-87a1-edfd026f1ada Oct 5 23:54:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs xfs in remove_crypt Oct 5 23:54:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xk_77utbmount_test with fs ext4 Oct 5 23:54:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2d36d2c4-de9f-4f68-ac94-ccc57835c878 r/w with ordered data mode. Quota mode: none. Oct 5 23:54:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xk_77utbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext3 in remove_crypt Oct 5 23:55:03 storageqe-109 systemd[1]: tmp-libblockdev.xk_77utbmount_test.mount: Deactivated successfully. Oct 5 23:55:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2d36d2c4-de9f-4f68-ac94-ccc57835c878. Oct 5 23:55:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext4 in remove_crypt Oct 5 23:55:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nh_5w4ahmount_test with fs ext3 Oct 5 23:55:24 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:55:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2f45dfb8-7706-4c11-ade6-c831341f80b2 r/w with ordered data mode. Quota mode: none. Oct 5 23:55:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nh_5w4ahmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext2 in remove_crypt Oct 5 23:55:30 storageqe-109 systemd[1]: tmp-libblockdev.nh_5w4ahmount_test.mount: Deactivated successfully. Oct 5 23:55:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2f45dfb8-7706-4c11-ade6-c831341f80b2. Oct 5 23:55:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext3 in remove_crypt Oct 5 23:55:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m25rboihmount_test with fs ext2 Oct 5 23:55:50 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:55:50 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a431734f-3b57-4e7e-80b0-4160a7e62cae r/w without journal. Quota mode: none. Oct 5 23:55:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m25rboihmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device disaster_test_crypt INFO: finishe the remove crypt device disaster_test_crypt Oct 5 23:55:55 storageqe-109 systemd[1]: tmp-libblockdev.m25rboihmount_test.mount: Deactivated successfully. Oct 5 23:55:55 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a431734f-3b57-4e7e-80b0-4160a7e62cae. Oct 5 23:55:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/disaster_test_crypt and fs ext2 in remove_crypt Oct 5 23:55:55 storageqe-109 INFO: remove crypt device disaster_test_crypt Oct 5 23:55:55 storageqe-109 INFO: finishe the remove crypt device disaster_test_crypt INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_header_backup_restore #### INFO: #### will start test_luks_key_slot_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:56:00 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:56:00 storageqe-109 INFO: #### END test_luks_header_backup_restore #### Oct 5 23:56:00 storageqe-109 INFO: #### will start test_luks_key_slot_recovery ##### Oct 5 23:56:00 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:56:05 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:56:13 storageqe-109 stratisd[4947]: [2025-10-06T03:56:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:56:13 storageqe-109 stratisd[4947]: [2025-10-06T03:56:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:56:33 storageqe-109 stratisd[4947]: [2025-10-06T03:56:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:56:33 storageqe-109 stratisd[4947]: [2025-10-06T03:56:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_primary -q Oct 5 23:56:43 storageqe-109 stratisd[4947]: [2025-10-06T03:56:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:56:43 storageqe-109 stratisd[4947]: [2025-10-06T03:56:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:56:43 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_primary -q Oct 5 23:56:45 storageqe-109 stratisd[4947]: [2025-10-06T03:56:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:56:45 storageqe-109 stratisd[4947]: [2025-10-06T03:56:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_recovery -q Oct 5 23:56:55 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_recovery -q Oct 5 23:56:57 storageqe-109 stratisd[4947]: [2025-10-06T03:56:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:56:57 storageqe-109 stratisd[4947]: [2025-10-06T03:56:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_emergency -q Oct 5 23:57:07 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_emergency -q Oct 5 23:57:09 storageqe-109 stratisd[4947]: [2025-10-06T03:57:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:57:09 storageqe-109 stratisd[4947]: [2025-10-06T03:57:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' luksRemoveKey /dev/nvme0n1 -q Oct 5 23:57:20 storageqe-109 journal: cryptsetup --type 'luks2' luksRemoveKey /dev/nvme0n1 -q Oct 5 23:57:22 storageqe-109 stratisd[4947]: [2025-10-06T03:57:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:57:22 storageqe-109 stratisd[4947]: [2025-10-06T03:57:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_primary -q Oct 5 23:57:32 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt_primary -q cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt -q Oct 5 23:57:46 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 keyslot_test_crypt -q Oct 5 23:57:48 storageqe-109 stratisd[4947]: [2025-10-06T03:57:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:57:48 storageqe-109 stratisd[4947]: [2025-10-06T03:57:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs xfs in remove_crypt Oct 5 23:58:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.jb5381iamount_test with fs xfs Oct 5 23:58:11 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 19d38d1b-c43c-47b3-937c-21b2259d4a1b Oct 5 23:58:11 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 5 23:58:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jb5381iamount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext4 in remove_crypt Oct 5 23:58:15 storageqe-109 systemd[1]: tmp-libblockdev.jb5381iamount_test.mount: Deactivated successfully. Oct 5 23:58:15 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 19d38d1b-c43c-47b3-937c-21b2259d4a1b Oct 5 23:58:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs xfs in remove_crypt Oct 5 23:58:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y0t059mvmount_test with fs ext4 Oct 5 23:58:26 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 15c31327-6064-4c2d-abbe-1a676a70005c r/w with ordered data mode. Quota mode: none. Oct 5 23:58:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y0t059mvmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext3 in remove_crypt Oct 5 23:58:31 storageqe-109 systemd[1]: tmp-libblockdev.y0t059mvmount_test.mount: Deactivated successfully. Oct 5 23:58:31 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 15c31327-6064-4c2d-abbe-1a676a70005c. Oct 5 23:58:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext4 in remove_crypt Oct 5 23:58:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f56e28jumount_test with fs ext3 Oct 5 23:58:53 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 5 23:58:53 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f142587a-c216-41e2-bd1e-89def7ba040a r/w with ordered data mode. Quota mode: none. Oct 5 23:58:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f56e28jumount_test with fs ext3 Oct 5 23:58:57 storageqe-109 systemd[1]: tmp-libblockdev.f56e28jumount_test.mount: Deactivated successfully. Oct 5 23:58:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f142587a-c216-41e2-bd1e-89def7ba040a. INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext2 in remove_crypt Oct 5 23:58:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext3 in remove_crypt Oct 5 23:58:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r349s24vmount_test with fs ext2 Oct 5 23:59:18 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 5 23:59:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem de52d7e9-8757-4ba8-b91e-574ebe8484da r/w without journal. Quota mode: none. Oct 5 23:59:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r349s24vmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device keyslot_test_crypt INFO: finishe the remove crypt device keyslot_test_crypt Oct 5 23:59:23 storageqe-109 systemd[1]: tmp-libblockdev.r349s24vmount_test.mount: Deactivated successfully. Oct 5 23:59:23 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem de52d7e9-8757-4ba8-b91e-574ebe8484da. Oct 5 23:59:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/keyslot_test_crypt and fs ext2 in remove_crypt Oct 5 23:59:23 storageqe-109 INFO: remove crypt device keyslot_test_crypt Oct 5 23:59:23 storageqe-109 INFO: finishe the remove crypt device keyslot_test_crypt INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_key_slot_recovery #### INFO: #### will start test_encrypted_device_fsck_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:59:28 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 5 23:59:28 storageqe-109 INFO: #### END test_luks_key_slot_recovery #### Oct 5 23:59:28 storageqe-109 INFO: #### will start test_encrypted_device_fsck_recovery ##### Oct 5 23:59:28 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:59:33 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 5 23:59:40 storageqe-109 stratisd[4947]: [2025-10-06T03:59:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:59:40 storageqe-109 stratisd[4947]: [2025-10-06T03:59:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 fsck_test_crypt -q Oct 5 23:59:51 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 fsck_test_crypt -q Oct 5 23:59:53 storageqe-109 stratisd[4947]: [2025-10-06T03:59:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 5 23:59:53 storageqe-109 stratisd[4947]: [2025-10-06T03:59:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs xfs in remove_crypt Oct 6 00:00:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 139d749e-f881-4d86-ab3a-1e56b61e6780 r/w with ordered data mode. Quota mode: none. Oct 6 00:00:03 storageqe-109 systemd[1]: tmp-luks_fsck_test_4jyglzgj.mount: Deactivated successfully. Oct 6 00:00:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 139d749e-f881-4d86-ab3a-1e56b61e6780. Oct 6 00:00:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 139d749e-f881-4d86-ab3a-1e56b61e6780 r/w with ordered data mode. Quota mode: none. Oct 6 00:00:03 storageqe-109 systemd[1]: tmp-luks_fsck_test_4jyglzgj.mount: Deactivated successfully. Oct 6 00:00:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 139d749e-f881-4d86-ab3a-1e56b61e6780. Oct 6 00:00:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ah8__o83mount_test with fs xfs Oct 6 00:00:14 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem a10b9201-58e4-4a5c-af1b-ce598be7dbbf Oct 6 00:00:14 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 00:00:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ah8__o83mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext4 in remove_crypt Oct 6 00:00:18 storageqe-109 systemd[1]: tmp-libblockdev.ah8__o83mount_test.mount: Deactivated successfully. Oct 6 00:00:18 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem a10b9201-58e4-4a5c-af1b-ce598be7dbbf Oct 6 00:00:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs xfs in remove_crypt Oct 6 00:00:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.n2md1e6vmount_test with fs ext4 Oct 6 00:00:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 622c524e-5d2b-4d40-9133-59e9041653f0 r/w with ordered data mode. Quota mode: none. Oct 6 00:00:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n2md1e6vmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext3 in remove_crypt Oct 6 00:00:35 storageqe-109 systemd[1]: tmp-libblockdev.n2md1e6vmount_test.mount: Deactivated successfully. Oct 6 00:00:35 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 622c524e-5d2b-4d40-9133-59e9041653f0. Oct 6 00:00:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext4 in remove_crypt Oct 6 00:00:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q3625u0pmount_test with fs ext3 Oct 6 00:00:56 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 00:00:56 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9e858357-77d0-4f1e-ba37-76e66b16cdca r/w with ordered data mode. Quota mode: none. Oct 6 00:00:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q3625u0pmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext2 in remove_crypt Oct 6 00:01:01 storageqe-109 systemd[1]: tmp-libblockdev.q3625u0pmount_test.mount: Deactivated successfully. Oct 6 00:01:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9e858357-77d0-4f1e-ba37-76e66b16cdca. Oct 6 00:01:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext3 in remove_crypt Oct 6 00:01:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tae95cc4mount_test with fs ext2 Oct 6 00:01:21 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 00:01:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e1099652-b874-4fc7-9fa8-ea426c60545d r/w without journal. Quota mode: none. Oct 6 00:01:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tae95cc4mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device fsck_test_crypt Oct 6 00:01:26 storageqe-109 systemd[1]: tmp-libblockdev.tae95cc4mount_test.mount: Deactivated successfully. Oct 6 00:01:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e1099652-b874-4fc7-9fa8-ea426c60545d. Oct 6 00:01:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fsck_test_crypt and fs ext2 in remove_crypt Oct 6 00:01:26 storageqe-109 INFO: remove crypt device fsck_test_crypt INFO: finishe the remove crypt device fsck_test_crypt Oct 6 00:01:26 storageqe-109 INFO: finishe the remove crypt device fsck_test_crypt INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_encrypted_device_fsck_recovery #### INFO: #### will start test_emergency_key_slot_total_loss_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:01:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:01:31 storageqe-109 INFO: #### END test_encrypted_device_fsck_recovery #### Oct 6 00:01:31 storageqe-109 INFO: #### will start test_emergency_key_slot_total_loss_recovery ##### Oct 6 00:01:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 00:01:36 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 00:01:44 storageqe-109 stratisd[4947]: [2025-10-06T04:01:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:01:44 storageqe-109 stratisd[4947]: [2025-10-06T04:01:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_primary -q Oct 6 00:02:04 storageqe-109 stratisd[4947]: [2025-10-06T04:02:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:02:04 storageqe-109 stratisd[4947]: [2025-10-06T04:02:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:02:04 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_primary -q Oct 6 00:02:06 storageqe-109 stratisd[4947]: [2025-10-06T04:02:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:02:06 storageqe-109 stratisd[4947]: [2025-10-06T04:02:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_emergency -q Oct 6 00:02:16 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_emergency -q Oct 6 00:02:18 storageqe-109 stratisd[4947]: [2025-10-06T04:02:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:02:18 storageqe-109 stratisd[4947]: [2025-10-06T04:02:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_test1 -q Oct 6 00:02:28 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_test1 -q cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_test2 -q Oct 6 00:02:38 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt_test2 -q cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt -q Oct 6 00:02:49 storageqe-109 stratisd[4947]: [2025-10-06T04:02:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:02:49 storageqe-109 stratisd[4947]: [2025-10-06T04:02:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:02:49 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 emergency_test_crypt -q Oct 6 00:02:51 storageqe-109 stratisd[4947]: [2025-10-06T04:02:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:02:51 storageqe-109 stratisd[4947]: [2025-10-06T04:02:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs xfs in remove_crypt Oct 6 00:03:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.a95yydjxmount_test with fs xfs Oct 6 00:03:12 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 79175692-1b89-4a80-afef-fbc82607d351 Oct 6 00:03:12 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 00:03:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a95yydjxmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext4 in remove_crypt Oct 6 00:03:17 storageqe-109 systemd[1]: tmp-libblockdev.a95yydjxmount_test.mount: Deactivated successfully. Oct 6 00:03:17 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 79175692-1b89-4a80-afef-fbc82607d351 Oct 6 00:03:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs xfs in remove_crypt Oct 6 00:03:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m2t098lymount_test with fs ext4 Oct 6 00:03:28 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e62854c5-665e-4957-92cf-7350ff0ed382 r/w with ordered data mode. Quota mode: none. Oct 6 00:03:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m2t098lymount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext3 in remove_crypt Oct 6 00:03:33 storageqe-109 systemd[1]: tmp-libblockdev.m2t098lymount_test.mount: Deactivated successfully. Oct 6 00:03:33 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e62854c5-665e-4957-92cf-7350ff0ed382. Oct 6 00:03:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext4 in remove_crypt Oct 6 00:03:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.58v64w6vmount_test with fs ext3 Oct 6 00:03:54 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 00:03:54 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1ea2ce27-42ee-4184-8d93-3a89eab2c757 r/w with ordered data mode. Quota mode: none. Oct 6 00:03:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.58v64w6vmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext2 in remove_crypt Oct 6 00:03:59 storageqe-109 systemd[1]: tmp-libblockdev.58v64w6vmount_test.mount: Deactivated successfully. Oct 6 00:03:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1ea2ce27-42ee-4184-8d93-3a89eab2c757. Oct 6 00:03:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext3 in remove_crypt Oct 6 00:03:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7jtzvyxbmount_test with fs ext2 Oct 6 00:04:20 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 00:04:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b5465540-a298-463a-86e3-55b2b785610d r/w without journal. Quota mode: none. Oct 6 00:04:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7jtzvyxbmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device emergency_test_crypt INFO: finishe the remove crypt device emergency_test_crypt Oct 6 00:04:25 storageqe-109 systemd[1]: tmp-libblockdev.7jtzvyxbmount_test.mount: Deactivated successfully. Oct 6 00:04:25 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b5465540-a298-463a-86e3-55b2b785610d. Oct 6 00:04:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/emergency_test_crypt and fs ext2 in remove_crypt Oct 6 00:04:25 storageqe-109 INFO: remove crypt device emergency_test_crypt Oct 6 00:04:25 storageqe-109 INFO: finishe the remove crypt device emergency_test_crypt INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_emergency_key_slot_total_loss_recovery #### INFO: #### will start test_encrypted_device_clone_disaster_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:04:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:04:30 storageqe-109 INFO: #### END test_emergency_key_slot_total_loss_recovery #### Oct 6 00:04:30 storageqe-109 INFO: #### will start test_encrypted_device_clone_disaster_recovery ##### Oct 6 00:04:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 00:04:35 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 00:04:43 storageqe-109 stratisd[4947]: [2025-10-06T04:04:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:04:43 storageqe-109 stratisd[4947]: [2025-10-06T04:04:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 clone_test_crypt -q Oct 6 00:04:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 clone_test_crypt -q Oct 6 00:04:55 storageqe-109 stratisd[4947]: [2025-10-06T04:04:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:04:55 storageqe-109 stratisd[4947]: [2025-10-06T04:04:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt Oct 6 00:05:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.x4_5tfczmount_test with fs xfs Oct 6 00:05:16 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 4267c46f-66cc-42fb-8b62-cc22bfb2c956 Oct 6 00:05:16 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 00:05:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x4_5tfczmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt Oct 6 00:05:21 storageqe-109 systemd[1]: tmp-libblockdev.x4_5tfczmount_test.mount: Deactivated successfully. Oct 6 00:05:21 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 4267c46f-66cc-42fb-8b62-cc22bfb2c956 Oct 6 00:05:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt Oct 6 00:05:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h4ucijj5mount_test with fs ext4 Oct 6 00:05:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 89b80a25-7d83-467b-a8bd-25e098d2bb65 r/w with ordered data mode. Quota mode: none. Oct 6 00:05:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h4ucijj5mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt Oct 6 00:05:37 storageqe-109 systemd[1]: tmp-libblockdev.h4ucijj5mount_test.mount: Deactivated successfully. Oct 6 00:05:37 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 89b80a25-7d83-467b-a8bd-25e098d2bb65. Oct 6 00:05:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt Oct 6 00:05:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt Oct 6 00:05:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.7ll9eyngmount_test with fs ext3 Oct 6 00:05:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2c7b1ee3-ad41-41b7-8824-677a29520f60 r/w with ordered data mode. Quota mode: none. Oct 6 00:05:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7ll9eyngmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt Oct 6 00:06:03 storageqe-109 systemd[1]: tmp-libblockdev.7ll9eyngmount_test.mount: Deactivated successfully. Oct 6 00:06:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2c7b1ee3-ad41-41b7-8824-677a29520f60. Oct 6 00:06:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt Oct 6 00:06:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5wjxdjbxmount_test with fs ext2 Oct 6 00:06:23 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 00:06:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7a9e2280-6d62-47f1-a494-baa5195ec185 r/w without journal. Quota mode: none. Oct 6 00:06:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5wjxdjbxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device clone_test_crypt INFO: finishe the remove crypt device clone_test_crypt cryptsetup --type 'luks2' open /dev/nvme0n1 clone_test_crypt_failed -q Oct 6 00:06:28 storageqe-109 systemd[1]: tmp-libblockdev.5wjxdjbxmount_test.mount: Deactivated successfully. Oct 6 00:06:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7a9e2280-6d62-47f1-a494-baa5195ec185. Oct 6 00:06:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt Oct 6 00:06:29 storageqe-109 INFO: remove crypt device clone_test_crypt Oct 6 00:06:29 storageqe-109 INFO: finishe the remove crypt device clone_test_crypt Oct 6 00:06:29 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 clone_test_crypt_failed -q cryptsetup --type 'luks2' open /dev/nvme0n1 clone_test_crypt -q Oct 6 00:06:39 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 clone_test_crypt -q Oct 6 00:06:42 storageqe-109 stratisd[4947]: [2025-10-06T04:06:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:06:42 storageqe-109 stratisd[4947]: [2025-10-06T04:06:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:06:44 storageqe-109 stratisd[4947]: [2025-10-06T04:06:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:06:44 storageqe-109 stratisd[4947]: [2025-10-06T04:06:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt Oct 6 00:06:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.au7ue8h3mount_test with fs xfs Oct 6 00:07:05 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem c9e5937d-67c6-4491-827b-ce98d4a94d88 Oct 6 00:07:05 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 00:07:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.au7ue8h3mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt Oct 6 00:07:10 storageqe-109 systemd[1]: tmp-libblockdev.au7ue8h3mount_test.mount: Deactivated successfully. Oct 6 00:07:10 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem c9e5937d-67c6-4491-827b-ce98d4a94d88 Oct 6 00:07:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs xfs in remove_crypt Oct 6 00:07:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.badlllr3mount_test with fs ext4 Oct 6 00:07:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a2c0c8c9-1ce2-4dbf-a8e0-dda2ad094bd8 r/w with ordered data mode. Quota mode: none. Oct 6 00:07:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.badlllr3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt Oct 6 00:07:26 storageqe-109 systemd[1]: tmp-libblockdev.badlllr3mount_test.mount: Deactivated successfully. Oct 6 00:07:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a2c0c8c9-1ce2-4dbf-a8e0-dda2ad094bd8. Oct 6 00:07:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext4 in remove_crypt Oct 6 00:07:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.393e6_5vmount_test with fs ext3 Oct 6 00:07:47 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 00:07:47 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3ca39962-db1f-4b7e-b602-86fa010aec3a r/w with ordered data mode. Quota mode: none. Oct 6 00:07:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.393e6_5vmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt Oct 6 00:07:52 storageqe-109 systemd[1]: tmp-libblockdev.393e6_5vmount_test.mount: Deactivated successfully. Oct 6 00:07:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3ca39962-db1f-4b7e-b602-86fa010aec3a. Oct 6 00:07:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext3 in remove_crypt Oct 6 00:07:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.iidqn9s7mount_test with fs ext2 Oct 6 00:08:12 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 00:08:12 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 644038ec-6504-4a7c-803f-187161790010 r/w without journal. Quota mode: none. Oct 6 00:08:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iidqn9s7mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt INFO: remove crypt device clone_test_crypt INFO: finishe the remove crypt device clone_test_crypt Oct 6 00:08:17 storageqe-109 systemd[1]: tmp-libblockdev.iidqn9s7mount_test.mount: Deactivated successfully. Oct 6 00:08:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 644038ec-6504-4a7c-803f-187161790010. Oct 6 00:08:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/clone_test_crypt and fs ext2 in remove_crypt Oct 6 00:08:17 storageqe-109 INFO: remove crypt device clone_test_crypt Oct 6 00:08:17 storageqe-109 INFO: finishe the remove crypt device clone_test_crypt INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_encrypted_device_clone_disaster_recovery #### INFO: #### will start test_device_event_detection ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:08:23 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:08:23 storageqe-109 INFO: #### END test_encrypted_device_clone_disaster_recovery #### Oct 6 00:08:23 storageqe-109 INFO: #### will start test_device_event_detection ##### Oct 6 00:08:23 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_device_event_detection #### INFO: #### will start test_media_change_detection ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:08:48 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:08:48 storageqe-109 INFO: #### END test_device_event_detection #### Oct 6 00:08:48 storageqe-109 INFO: #### will start test_media_change_detection ##### Oct 6 00:08:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_media_change_detection #### INFO: #### will start test_device_removal_simulation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:09:03 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:09:03 storageqe-109 INFO: #### END test_media_change_detection #### Oct 6 00:09:03 storageqe-109 INFO: #### will start test_device_removal_simulation ##### Oct 6 00:09:03 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_device_removal_simulation #### INFO: #### will start test_event_polling_accuracy ##### Oct 6 00:09:33 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:09:33 storageqe-109 INFO: #### END test_device_removal_simulation #### Oct 6 00:09:33 storageqe-109 INFO: #### will start test_event_polling_accuracy ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:09:33 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_event_polling_accuracy #### INFO: #### will start test_uuid_device_lookup ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:09:53 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:09:53 storageqe-109 INFO: #### END test_event_polling_accuracy #### Oct 6 00:09:53 storageqe-109 INFO: #### will start test_uuid_device_lookup ##### Oct 6 00:09:53 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:09:58 storageqe-109 kernel: nvme0n1: Oct 6 00:09:58 storageqe-109 kernel: nvme0n1: INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_uuid_device_lookup #### INFO: #### will start test_partuuid_device_lookup ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:03 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:03 storageqe-109 INFO: #### END test_uuid_device_lookup #### Oct 6 00:10:03 storageqe-109 INFO: #### will start test_partuuid_device_lookup ##### Oct 6 00:10:03 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:08 storageqe-109 kernel: nvme0n1: Oct 6 00:10:08 storageqe-109 kernel: nvme0n1: INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_partuuid_device_lookup #### INFO: #### will start test_device_name_resolution ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:13 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:13 storageqe-109 INFO: #### END test_partuuid_device_lookup #### Oct 6 00:10:13 storageqe-109 INFO: #### will start test_device_name_resolution ##### Oct 6 00:10:13 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_device_name_resolution #### INFO: #### will start test_early_boot_device_enumeration ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:23 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:23 storageqe-109 INFO: #### END test_device_name_resolution #### Oct 6 00:10:23 storageqe-109 INFO: #### will start test_early_boot_device_enumeration ##### Oct 6 00:10:24 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_early_boot_device_enumeration #### INFO: #### will start test_ioprio_class_differentiation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:34 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:34 storageqe-109 INFO: #### END test_early_boot_device_enumeration #### Oct 6 00:10:34 storageqe-109 INFO: #### will start test_ioprio_class_differentiation ##### Oct 6 00:10:34 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_ioprio_class_differentiation #### INFO: #### will start test_ioprio_level_granularity ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:44 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:44 storageqe-109 INFO: #### END test_ioprio_class_differentiation #### Oct 6 00:10:44 storageqe-109 INFO: #### will start test_ioprio_level_granularity ##### Oct 6 00:10:44 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_ioprio_level_granularity #### INFO: #### will start test_concurrent_ioprio_competition ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:54 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:10:54 storageqe-109 INFO: #### END test_ioprio_level_granularity #### Oct 6 00:10:54 storageqe-109 INFO: #### will start test_concurrent_ioprio_competition ##### Oct 6 00:10:54 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_ioprio_competition #### INFO: #### will start test_ioprio_inheritance ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:04 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:04 storageqe-109 INFO: #### END test_concurrent_ioprio_competition #### Oct 6 00:11:04 storageqe-109 INFO: #### will start test_ioprio_inheritance ##### Oct 6 00:11:04 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_ioprio_inheritance #### INFO: #### will start test_ioprio_cgroup_integration ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:15 storageqe-109 INFO: #### END test_ioprio_inheritance #### Oct 6 00:11:15 storageqe-109 INFO: #### will start test_ioprio_cgroup_integration ##### Oct 6 00:11:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_ioprio_cgroup_integration #### INFO: #### will start test_device_power_management_capabilities ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:25 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:25 storageqe-109 INFO: #### END test_ioprio_cgroup_integration #### Oct 6 00:11:25 storageqe-109 INFO: #### will start test_device_power_management_capabilities ##### Oct 6 00:11:25 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_device_power_management_capabilities #### INFO: #### will start test_autosuspend_configuration ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:35 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:35 storageqe-109 INFO: #### END test_device_power_management_capabilities #### Oct 6 00:11:35 storageqe-109 INFO: #### will start test_autosuspend_configuration ##### Oct 6 00:11:35 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_autosuspend_configuration #### INFO: #### will start test_runtime_power_state_transitions ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:11:45 storageqe-109 INFO: #### END test_autosuspend_configuration #### Oct 6 00:11:45 storageqe-109 INFO: #### will start test_runtime_power_state_transitions ##### Oct 6 00:11:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_runtime_power_state_transitions #### INFO: #### will start test_power_management_with_io_load ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:02 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:02 storageqe-109 INFO: #### END test_runtime_power_state_transitions #### Oct 6 00:12:02 storageqe-109 INFO: #### will start test_power_management_with_io_load ##### Oct 6 00:12:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_power_management_with_io_load #### INFO: #### will start test_t10_pi_type_support ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:18 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:18 storageqe-109 INFO: #### END test_power_management_with_io_load #### Oct 6 00:12:18 storageqe-109 INFO: #### will start test_t10_pi_type_support ##### Oct 6 00:12:18 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_t10_pi_type_support #### INFO: #### will start test_t10_pi_guard_tag_algorithms ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:30 storageqe-109 INFO: #### END test_t10_pi_type_support #### Oct 6 00:12:30 storageqe-109 INFO: #### will start test_t10_pi_guard_tag_algorithms ##### Oct 6 00:12:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_t10_pi_guard_tag_algorithms #### INFO: #### will start test_t10_pi_metadata_formats ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:40 storageqe-109 INFO: #### END test_t10_pi_guard_tag_algorithms #### Oct 6 00:12:40 storageqe-109 INFO: #### will start test_t10_pi_metadata_formats ##### Oct 6 00:12:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_t10_pi_metadata_formats #### INFO: #### will start test_t10_pi_error_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:50 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:12:50 storageqe-109 INFO: #### END test_t10_pi_metadata_formats #### Oct 6 00:12:50 storageqe-109 INFO: #### will start test_t10_pi_error_handling ##### Oct 6 00:12:50 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_t10_pi_error_handling #### INFO: #### will start test_t10_pi_performance_impact ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:00 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:00 storageqe-109 INFO: #### END test_t10_pi_error_handling #### Oct 6 00:13:00 storageqe-109 INFO: #### will start test_t10_pi_performance_impact ##### Oct 6 00:13:00 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_t10_pi_performance_impact #### Oct 6 00:13:10 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:10 storageqe-109 INFO: #### END test_t10_pi_performance_impact #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 00:13:11 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 00:13:11 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 00:13:11 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 00:13:22 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_aead_aes_gcm_modes[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:27 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:27 storageqe-109 INFO: #### will start test_aead_aes_gcm_modes[npo2_linear] ##### Oct 6 00:13:27 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_aead_aes_gcm_modes[npo2_linear] #### INFO: #### will start test_aead_chacha20_poly1305[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:37 storageqe-109 INFO: #### END test_aead_aes_gcm_modes[npo2_linear] #### Oct 6 00:13:37 storageqe-109 INFO: #### will start test_aead_chacha20_poly1305[npo2_linear] ##### Oct 6 00:13:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:41 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_aead_chacha20_poly1305[npo2_linear] #### INFO: #### will start test_advanced_iv_algorithms[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:47 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:13:47 storageqe-109 INFO: #### END test_aead_chacha20_poly1305[npo2_linear] #### Oct 6 00:13:47 storageqe-109 INFO: #### will start test_advanced_iv_algorithms[npo2_linear] ##### Oct 6 00:13:47 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:13:52 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:13:53 storageqe-109 stratisd[4947]: [2025-10-06T04:13:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:13:53 storageqe-109 stratisd[4947]: [2025-10-06T04:13:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear nSlfhIDtNq -q Oct 6 00:14:03 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear nSlfhIDtNq -q Oct 6 00:14:03 storageqe-109 stratisd[4947]: [2025-10-06T04:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:14:03 storageqe-109 stratisd[4947]: [2025-10-06T04:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status nSlfhIDtNq -q Oct 6 00:14:13 storageqe-109 journal: cryptsetup status nSlfhIDtNq -q INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs xfs in remove_crypt Oct 6 00:14:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.t4vuky7rmount_test with fs xfs Oct 6 00:14:33 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem bc51b8b8-7d26-408a-8f63-c9a7777e4007 Oct 6 00:14:33 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:14:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t4vuky7rmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext4 in remove_crypt Oct 6 00:14:37 storageqe-109 systemd[1]: tmp-libblockdev.t4vuky7rmount_test.mount: Deactivated successfully. Oct 6 00:14:37 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem bc51b8b8-7d26-408a-8f63-c9a7777e4007 Oct 6 00:14:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs xfs in remove_crypt Oct 6 00:14:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.s9up_36imount_test with fs ext4 Oct 6 00:14:48 storageqe-109 systemd[1]: Starting fstrim.service - Discard unused blocks on filesystems from /etc/fstab... Oct 6 00:14:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f20c4b3f-c516-4965-a44f-b54c50897efd r/w with ordered data mode. Quota mode: none. Oct 6 00:14:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s9up_36imount_test with fs ext4 Oct 6 00:14:48 storageqe-109 systemd[1]: fstrim.service: Deactivated successfully. Oct 6 00:14:48 storageqe-109 systemd[1]: Finished fstrim.service - Discard unused blocks on filesystems from /etc/fstab. INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext3 in remove_crypt Oct 6 00:14:52 storageqe-109 systemd[1]: tmp-libblockdev.s9up_36imount_test.mount: Deactivated successfully. Oct 6 00:14:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f20c4b3f-c516-4965-a44f-b54c50897efd. Oct 6 00:14:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext4 in remove_crypt Oct 6 00:14:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ks5gy69ymount_test with fs ext3 Oct 6 00:15:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:15:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ac8b2e7e-a293-4a0d-9c9c-4c1ec6320fce r/w with ordered data mode. Quota mode: none. Oct 6 00:15:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ks5gy69ymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext3 in remove_crypt Oct 6 00:15:07 storageqe-109 systemd[1]: tmp-libblockdev.ks5gy69ymount_test.mount: Deactivated successfully. Oct 6 00:15:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ac8b2e7e-a293-4a0d-9c9c-4c1ec6320fce. Oct 6 00:15:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext2 in remove_crypt Oct 6 00:15:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4fos2jdfmount_test with fs ext2 Oct 6 00:15:18 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:15:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 78c553fc-faa4-48b0-99c6-3b3ed7d311b3 r/w without journal. Quota mode: none. Oct 6 00:15:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4fos2jdfmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext2 in remove_crypt INFO: remove crypt device nSlfhIDtNq Oct 6 00:15:22 storageqe-109 systemd[1]: tmp-libblockdev.4fos2jdfmount_test.mount: Deactivated successfully. Oct 6 00:15:22 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 78c553fc-faa4-48b0-99c6-3b3ed7d311b3. Oct 6 00:15:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nSlfhIDtNq and fs ext2 in remove_crypt Oct 6 00:15:22 storageqe-109 INFO: remove crypt device nSlfhIDtNq INFO: finishe the remove crypt device nSlfhIDtNq cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:15:23 storageqe-109 INFO: finishe the remove crypt device nSlfhIDtNq Oct 6 00:15:23 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:15:23 storageqe-109 stratisd[4947]: [2025-10-06T04:15:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:15:23 storageqe-109 stratisd[4947]: [2025-10-06T04:15:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear utKgvDrHNw -q Oct 6 00:15:33 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear utKgvDrHNw -q Oct 6 00:15:33 storageqe-109 stratisd[4947]: [2025-10-06T04:15:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:15:33 storageqe-109 stratisd[4947]: [2025-10-06T04:15:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status utKgvDrHNw -q Oct 6 00:15:43 storageqe-109 journal: cryptsetup status utKgvDrHNw -q INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs xfs in remove_crypt Oct 6 00:15:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.qm97zpn2mount_test with fs xfs Oct 6 00:16:03 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 5f7ca077-0d3d-4fb8-b603-faad96dac0e6 Oct 6 00:16:03 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:16:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qm97zpn2mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext4 in remove_crypt Oct 6 00:16:08 storageqe-109 systemd[1]: tmp-libblockdev.qm97zpn2mount_test.mount: Deactivated successfully. Oct 6 00:16:08 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 5f7ca077-0d3d-4fb8-b603-faad96dac0e6 Oct 6 00:16:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs xfs in remove_crypt Oct 6 00:16:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2vy8k5yamount_test with fs ext4 Oct 6 00:16:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 549e8c58-c913-4c51-b958-758284bef6c7 r/w with ordered data mode. Quota mode: none. Oct 6 00:16:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2vy8k5yamount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext3 in remove_crypt Oct 6 00:16:23 storageqe-109 systemd[1]: tmp-libblockdev.2vy8k5yamount_test.mount: Deactivated successfully. Oct 6 00:16:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 549e8c58-c913-4c51-b958-758284bef6c7. Oct 6 00:16:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext4 in remove_crypt Oct 6 00:16:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ixfjyewxmount_test with fs ext3 Oct 6 00:16:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:16:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 32e06a40-4e1c-45af-b90b-0a17c47ade8a r/w with ordered data mode. Quota mode: none. Oct 6 00:16:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ixfjyewxmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext3 in remove_crypt Oct 6 00:16:38 storageqe-109 systemd[1]: tmp-libblockdev.ixfjyewxmount_test.mount: Deactivated successfully. Oct 6 00:16:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 32e06a40-4e1c-45af-b90b-0a17c47ade8a. Oct 6 00:16:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext2 in remove_crypt Oct 6 00:16:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qpzg729jmount_test with fs ext2 Oct 6 00:16:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:16:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fb84476d-08b0-4ef9-aca0-158b76a3afe0 r/w without journal. Quota mode: none. Oct 6 00:16:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qpzg729jmount_test with fs ext2 Oct 6 00:16:53 storageqe-109 systemd[1]: tmp-libblockdev.qpzg729jmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext2 in remove_crypt INFO: remove crypt device utKgvDrHNw INFO: finishe the remove crypt device utKgvDrHNw cryptsetup --type 'luks2' --cipher 'aes-cbc-plain' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:16:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fb84476d-08b0-4ef9-aca0-158b76a3afe0. Oct 6 00:16:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/utKgvDrHNw and fs ext2 in remove_crypt Oct 6 00:16:53 storageqe-109 INFO: remove crypt device utKgvDrHNw Oct 6 00:16:53 storageqe-109 INFO: finishe the remove crypt device utKgvDrHNw Oct 6 00:16:53 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:16:53 storageqe-109 stratisd[4947]: [2025-10-06T04:16:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:16:53 storageqe-109 stratisd[4947]: [2025-10-06T04:16:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear oZJFlSRigC -q Oct 6 00:17:03 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear oZJFlSRigC -q Oct 6 00:17:03 storageqe-109 stratisd[4947]: [2025-10-06T04:17:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:17:03 storageqe-109 stratisd[4947]: [2025-10-06T04:17:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status oZJFlSRigC -q Oct 6 00:17:13 storageqe-109 journal: cryptsetup status oZJFlSRigC -q INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs xfs in remove_crypt Oct 6 00:17:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ifzmmfg2mount_test with fs xfs Oct 6 00:17:33 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 202c8fdf-ee46-44d6-a362-b2dd3550967b Oct 6 00:17:33 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:17:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ifzmmfg2mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext4 in remove_crypt Oct 6 00:17:38 storageqe-109 systemd[1]: tmp-libblockdev.ifzmmfg2mount_test.mount: Deactivated successfully. Oct 6 00:17:38 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 202c8fdf-ee46-44d6-a362-b2dd3550967b Oct 6 00:17:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs xfs in remove_crypt Oct 6 00:17:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._p2eaihwmount_test with fs ext4 Oct 6 00:17:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bd91b6b1-1df8-422d-9e5f-011cac268413 r/w with ordered data mode. Quota mode: none. Oct 6 00:17:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev._p2eaihwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext3 in remove_crypt Oct 6 00:17:53 storageqe-109 systemd[1]: tmp-libblockdev._p2eaihwmount_test.mount: Deactivated successfully. Oct 6 00:17:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bd91b6b1-1df8-422d-9e5f-011cac268413. Oct 6 00:17:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext4 in remove_crypt Oct 6 00:17:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y0jlpwfxmount_test with fs ext3 Oct 6 00:18:04 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:18:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 692576f2-6336-46c9-b758-f7626147761e r/w with ordered data mode. Quota mode: none. Oct 6 00:18:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y0jlpwfxmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext2 in remove_crypt Oct 6 00:18:09 storageqe-109 systemd[1]: tmp-libblockdev.y0jlpwfxmount_test.mount: Deactivated successfully. Oct 6 00:18:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 692576f2-6336-46c9-b758-f7626147761e. Oct 6 00:18:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext3 in remove_crypt Oct 6 00:18:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y4meh0limount_test with fs ext2 Oct 6 00:18:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:18:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2e500be7-e77a-413c-8137-70fa0d3a708b r/w without journal. Quota mode: none. Oct 6 00:18:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y4meh0limount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext2 in remove_crypt INFO: remove crypt device oZJFlSRigC Oct 6 00:18:24 storageqe-109 systemd[1]: tmp-libblockdev.y4meh0limount_test.mount: Deactivated successfully. Oct 6 00:18:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2e500be7-e77a-413c-8137-70fa0d3a708b. Oct 6 00:18:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oZJFlSRigC and fs ext2 in remove_crypt Oct 6 00:18:24 storageqe-109 INFO: remove crypt device oZJFlSRigC INFO: finishe the remove crypt device oZJFlSRigC cryptsetup --type 'luks2' --cipher 'aes-xts-benbi' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:18:24 storageqe-109 INFO: finishe the remove crypt device oZJFlSRigC Oct 6 00:18:24 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-benbi' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:18:24 storageqe-109 stratisd[4947]: [2025-10-06T04:18:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:18:24 storageqe-109 stratisd[4947]: [2025-10-06T04:18:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear jDNdunTvAV -q Oct 6 00:18:34 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear jDNdunTvAV -q Oct 6 00:18:34 storageqe-109 stratisd[4947]: [2025-10-06T04:18:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:18:34 storageqe-109 stratisd[4947]: [2025-10-06T04:18:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status jDNdunTvAV -q Oct 6 00:18:44 storageqe-109 journal: cryptsetup status jDNdunTvAV -q INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs xfs in remove_crypt Oct 6 00:18:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.w3i0r9b7mount_test with fs xfs Oct 6 00:19:04 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 79fe2182-3461-42ae-8fa0-d428cb2c144e Oct 6 00:19:04 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:19:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.w3i0r9b7mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext4 in remove_crypt Oct 6 00:19:09 storageqe-109 systemd[1]: tmp-libblockdev.w3i0r9b7mount_test.mount: Deactivated successfully. Oct 6 00:19:09 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 79fe2182-3461-42ae-8fa0-d428cb2c144e Oct 6 00:19:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs xfs in remove_crypt Oct 6 00:19:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bhushexrmount_test with fs ext4 Oct 6 00:19:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7651fdc4-be7a-4399-8734-5d7a13513a43 r/w with ordered data mode. Quota mode: none. Oct 6 00:19:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bhushexrmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext4 in remove_crypt Oct 6 00:19:24 storageqe-109 systemd[1]: tmp-libblockdev.bhushexrmount_test.mount: Deactivated successfully. Oct 6 00:19:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7651fdc4-be7a-4399-8734-5d7a13513a43. Oct 6 00:19:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext3 in remove_crypt Oct 6 00:19:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.oe7_gq6omount_test with fs ext3 Oct 6 00:19:34 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:19:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7bae661a-4590-4e3b-a181-6e8125ad820d r/w with ordered data mode. Quota mode: none. Oct 6 00:19:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.oe7_gq6omount_test with fs ext3 Oct 6 00:19:39 storageqe-109 systemd[1]: tmp-libblockdev.oe7_gq6omount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext2 in remove_crypt Oct 6 00:19:39 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7bae661a-4590-4e3b-a181-6e8125ad820d. Oct 6 00:19:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext3 in remove_crypt Oct 6 00:19:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z57e5zynmount_test with fs ext2 Oct 6 00:19:49 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:19:49 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 28c645ce-b0ad-4d82-81ad-5cd8f0eee05a r/w without journal. Quota mode: none. Oct 6 00:19:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z57e5zynmount_test with fs ext2 Oct 6 00:19:54 storageqe-109 systemd[1]: tmp-libblockdev.z57e5zynmount_test.mount: Deactivated successfully. Oct 6 00:19:54 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 28c645ce-b0ad-4d82-81ad-5cd8f0eee05a. Oct 6 00:19:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext2 in remove_crypt INFO: End IO testing with the luks device /dev/mapper/jDNdunTvAV and fs ext2 in remove_crypt INFO: remove crypt device jDNdunTvAV INFO: finishe the remove crypt device jDNdunTvAV Oct 6 00:19:54 storageqe-109 INFO: remove crypt device jDNdunTvAV Oct 6 00:19:54 storageqe-109 INFO: finishe the remove crypt device jDNdunTvAV cryptsetup --type 'luks2' --cipher 'twofish-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:19:56 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'twofish-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:19:56 storageqe-109 stratisd[4947]: [2025-10-06T04:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:19:56 storageqe-109 stratisd[4947]: [2025-10-06T04:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear qhYsgmwSrk -q Oct 6 00:20:06 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear qhYsgmwSrk -q Oct 6 00:20:06 storageqe-109 stratisd[4947]: [2025-10-06T04:20:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:20:06 storageqe-109 stratisd[4947]: [2025-10-06T04:20:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status qhYsgmwSrk -q Oct 6 00:20:16 storageqe-109 journal: cryptsetup status qhYsgmwSrk -q INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs xfs in remove_crypt Oct 6 00:20:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.hn3id9o0mount_test with fs xfs Oct 6 00:20:36 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem a7f35237-a239-4a92-901c-d6b52e10eb07 Oct 6 00:20:36 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:20:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hn3id9o0mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext4 in remove_crypt Oct 6 00:20:42 storageqe-109 systemd[1]: tmp-libblockdev.hn3id9o0mount_test.mount: Deactivated successfully. Oct 6 00:20:42 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem a7f35237-a239-4a92-901c-d6b52e10eb07 Oct 6 00:20:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs xfs in remove_crypt Oct 6 00:20:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext4 in remove_crypt Oct 6 00:20:52 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1ae260ed-400f-4cea-a56e-1a425089728b r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.xsjx59iimount_test with fs ext4 Oct 6 00:20:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xsjx59iimount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext3 in remove_crypt Oct 6 00:20:58 storageqe-109 systemd[1]: tmp-libblockdev.xsjx59iimount_test.mount: Deactivated successfully. Oct 6 00:20:58 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1ae260ed-400f-4cea-a56e-1a425089728b. Oct 6 00:20:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext4 in remove_crypt Oct 6 00:20:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gmten_f3mount_test with fs ext3 Oct 6 00:21:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:21:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9c158613-fe3f-4d67-bbe1-901b42f2faae r/w with ordered data mode. Quota mode: none. Oct 6 00:21:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gmten_f3mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext2 in remove_crypt Oct 6 00:21:14 storageqe-109 systemd[1]: tmp-libblockdev.gmten_f3mount_test.mount: Deactivated successfully. Oct 6 00:21:15 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9c158613-fe3f-4d67-bbe1-901b42f2faae. Oct 6 00:21:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext3 in remove_crypt Oct 6 00:21:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m1osy9g7mount_test with fs ext2 Oct 6 00:21:25 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:21:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 26b4a0ca-1b5a-4d09-95cc-90ab7699665b r/w without journal. Quota mode: none. Oct 6 00:21:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m1osy9g7mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext2 in remove_crypt INFO: remove crypt device qhYsgmwSrk INFO: finishe the remove crypt device qhYsgmwSrk Oct 6 00:21:31 storageqe-109 systemd[1]: tmp-libblockdev.m1osy9g7mount_test.mount: Deactivated successfully. Oct 6 00:21:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 26b4a0ca-1b5a-4d09-95cc-90ab7699665b. Oct 6 00:21:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qhYsgmwSrk and fs ext2 in remove_crypt Oct 6 00:21:31 storageqe-109 INFO: remove crypt device qhYsgmwSrk Oct 6 00:21:31 storageqe-109 INFO: finishe the remove crypt device qhYsgmwSrk cryptsetup --type 'luks2' --cipher 'serpent-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:21:33 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:21:33 storageqe-109 stratisd[4947]: [2025-10-06T04:21:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:21:33 storageqe-109 stratisd[4947]: [2025-10-06T04:21:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear FlNKyHOVpq -q Oct 6 00:21:43 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear FlNKyHOVpq -q Oct 6 00:21:43 storageqe-109 stratisd[4947]: [2025-10-06T04:21:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:21:43 storageqe-109 stratisd[4947]: [2025-10-06T04:21:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status FlNKyHOVpq -q Oct 6 00:21:53 storageqe-109 journal: cryptsetup status FlNKyHOVpq -q INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs xfs in remove_crypt Oct 6 00:22:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.857dou10mount_test with fs xfs Oct 6 00:22:13 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ed44cf5f-a2e0-4c5f-9fe4-585d980777cc Oct 6 00:22:13 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:22:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.857dou10mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext4 in remove_crypt Oct 6 00:22:19 storageqe-109 systemd[1]: tmp-libblockdev.857dou10mount_test.mount: Deactivated successfully. Oct 6 00:22:19 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ed44cf5f-a2e0-4c5f-9fe4-585d980777cc Oct 6 00:22:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs xfs in remove_crypt Oct 6 00:22:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7gq2bvonmount_test with fs ext4 Oct 6 00:22:30 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fb3ff208-a0c3-4d62-8b66-0613e154c603 r/w with ordered data mode. Quota mode: none. Oct 6 00:22:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7gq2bvonmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext3 in remove_crypt Oct 6 00:22:36 storageqe-109 systemd[1]: tmp-libblockdev.7gq2bvonmount_test.mount: Deactivated successfully. Oct 6 00:22:36 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fb3ff208-a0c3-4d62-8b66-0613e154c603. Oct 6 00:22:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext4 in remove_crypt Oct 6 00:22:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m9opqxadmount_test with fs ext3 Oct 6 00:22:47 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:22:47 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1092617f-ca35-4dd5-9e03-2a4726867676 r/w with ordered data mode. Quota mode: none. Oct 6 00:22:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m9opqxadmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext2 in remove_crypt Oct 6 00:22:53 storageqe-109 systemd[1]: tmp-libblockdev.m9opqxadmount_test.mount: Deactivated successfully. Oct 6 00:22:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1092617f-ca35-4dd5-9e03-2a4726867676. Oct 6 00:22:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext3 in remove_crypt Oct 6 00:22:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._wto72mmmount_test with fs ext2 Oct 6 00:23:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:23:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3c34511e-1db4-4a79-9d42-ee206aff1918 r/w without journal. Quota mode: none. Oct 6 00:23:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev._wto72mmmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext2 in remove_crypt INFO: remove crypt device FlNKyHOVpq INFO: finishe the remove crypt device FlNKyHOVpq Oct 6 00:23:09 storageqe-109 systemd[1]: tmp-libblockdev._wto72mmmount_test.mount: Deactivated successfully. Oct 6 00:23:10 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3c34511e-1db4-4a79-9d42-ee206aff1918. Oct 6 00:23:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FlNKyHOVpq and fs ext2 in remove_crypt Oct 6 00:23:10 storageqe-109 INFO: remove crypt device FlNKyHOVpq Oct 6 00:23:10 storageqe-109 INFO: finishe the remove crypt device FlNKyHOVpq INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_advanced_iv_algorithms[npo2_linear] #### INFO: #### will start test_performance_optimizations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:23:15 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:23:15 storageqe-109 INFO: #### END test_advanced_iv_algorithms[npo2_linear] #### Oct 6 00:23:15 storageqe-109 INFO: #### will start test_performance_optimizations[npo2_linear] ##### Oct 6 00:23:15 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_performance_optimizations[npo2_linear] #### INFO: #### will start test_sector_size_variations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:23:25 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:23:25 storageqe-109 INFO: #### END test_performance_optimizations[npo2_linear] #### Oct 6 00:23:25 storageqe-109 INFO: #### will start test_sector_size_variations[npo2_linear] ##### Oct 6 00:23:25 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:23:30 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:23:30 storageqe-109 stratisd[4947]: [2025-10-06T04:23:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:23:30 storageqe-109 stratisd[4947]: [2025-10-06T04:23:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear oezbsFSPpM -q Oct 6 00:23:40 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear oezbsFSPpM -q Oct 6 00:23:40 storageqe-109 stratisd[4947]: [2025-10-06T04:23:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:23:40 storageqe-109 stratisd[4947]: [2025-10-06T04:23:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status oezbsFSPpM -q Oct 6 00:23:50 storageqe-109 journal: cryptsetup status oezbsFSPpM -q INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs xfs in remove_crypt Oct 6 00:24:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.jj67z2rqmount_test with fs xfs Oct 6 00:24:10 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 81e65cf4-43e1-461e-ab60-9058ba55f57e Oct 6 00:24:10 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:24:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jj67z2rqmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext4 in remove_crypt Oct 6 00:24:15 storageqe-109 systemd[1]: tmp-libblockdev.jj67z2rqmount_test.mount: Deactivated successfully. Oct 6 00:24:15 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 81e65cf4-43e1-461e-ab60-9058ba55f57e Oct 6 00:24:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs xfs in remove_crypt Oct 6 00:24:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.noeymvl3mount_test with fs ext4 Oct 6 00:24:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 355a4ce2-f0ad-4bec-aa43-9cae44e91f52 r/w with ordered data mode. Quota mode: none. Oct 6 00:24:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.noeymvl3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext3 in remove_crypt Oct 6 00:24:30 storageqe-109 systemd[1]: tmp-libblockdev.noeymvl3mount_test.mount: Deactivated successfully. Oct 6 00:24:30 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 355a4ce2-f0ad-4bec-aa43-9cae44e91f52. Oct 6 00:24:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext4 in remove_crypt Oct 6 00:24:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zsi7y72rmount_test with fs ext3 Oct 6 00:24:40 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:24:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 830a6dd4-b1ad-4c84-a975-fe59afc7f1c0 r/w with ordered data mode. Quota mode: none. Oct 6 00:24:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zsi7y72rmount_test with fs ext3 Oct 6 00:24:45 storageqe-109 systemd[1]: tmp-libblockdev.zsi7y72rmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext2 in remove_crypt Oct 6 00:24:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 830a6dd4-b1ad-4c84-a975-fe59afc7f1c0. Oct 6 00:24:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext3 in remove_crypt Oct 6 00:24:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2sxf8576mount_test with fs ext2 Oct 6 00:24:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:24:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0dad9eee-464a-4323-a69d-a2a74b5766cb r/w without journal. Quota mode: none. Oct 6 00:24:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2sxf8576mount_test with fs ext2 Oct 6 00:25:00 storageqe-109 systemd[1]: tmp-libblockdev.2sxf8576mount_test.mount: Deactivated successfully. Oct 6 00:25:00 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0dad9eee-464a-4323-a69d-a2a74b5766cb. INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext2 in remove_crypt INFO: remove crypt device oezbsFSPpM INFO: finishe the remove crypt device oezbsFSPpM cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:25:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oezbsFSPpM and fs ext2 in remove_crypt Oct 6 00:25:00 storageqe-109 INFO: remove crypt device oezbsFSPpM Oct 6 00:25:00 storageqe-109 INFO: finishe the remove crypt device oezbsFSPpM Oct 6 00:25:00 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:25:00 storageqe-109 stratisd[4947]: [2025-10-06T04:25:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:25:00 storageqe-109 stratisd[4947]: [2025-10-06T04:25:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear PoOzraKZWR -q Oct 6 00:25:10 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear PoOzraKZWR -q Oct 6 00:25:10 storageqe-109 stratisd[4947]: [2025-10-06T04:25:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:25:10 storageqe-109 stratisd[4947]: [2025-10-06T04:25:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status PoOzraKZWR -q Oct 6 00:25:20 storageqe-109 journal: cryptsetup status PoOzraKZWR -q INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs xfs in remove_crypt Oct 6 00:25:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.z0n1ysahmount_test with fs xfs Oct 6 00:25:40 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 733d4f52-a737-4db8-86a0-ea871b70ad6e Oct 6 00:25:40 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:25:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z0n1ysahmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext4 in remove_crypt Oct 6 00:25:45 storageqe-109 systemd[1]: tmp-libblockdev.z0n1ysahmount_test.mount: Deactivated successfully. Oct 6 00:25:45 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 733d4f52-a737-4db8-86a0-ea871b70ad6e Oct 6 00:25:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs xfs in remove_crypt Oct 6 00:25:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hp9au9g2mount_test with fs ext4 Oct 6 00:25:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1c6032a7-b6bb-48b3-acd3-50713cbcd541 r/w with ordered data mode. Quota mode: none. Oct 6 00:25:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hp9au9g2mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext3 in remove_crypt Oct 6 00:26:00 storageqe-109 systemd[1]: tmp-libblockdev.hp9au9g2mount_test.mount: Deactivated successfully. Oct 6 00:26:00 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1c6032a7-b6bb-48b3-acd3-50713cbcd541. Oct 6 00:26:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext4 in remove_crypt Oct 6 00:26:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fm7sbwdjmount_test with fs ext3 Oct 6 00:26:10 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:26:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 148375b5-34b4-4e66-913f-6faf8c58f18a r/w with ordered data mode. Quota mode: none. Oct 6 00:26:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fm7sbwdjmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext2 in remove_crypt Oct 6 00:26:15 storageqe-109 systemd[1]: tmp-libblockdev.fm7sbwdjmount_test.mount: Deactivated successfully. Oct 6 00:26:15 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 148375b5-34b4-4e66-913f-6faf8c58f18a. Oct 6 00:26:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext3 in remove_crypt Oct 6 00:26:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mflbkyfhmount_test with fs ext2 Oct 6 00:26:25 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:26:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8ae51d12-2ac2-4f7d-8df2-0250917348a0 r/w without journal. Quota mode: none. Oct 6 00:26:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mflbkyfhmount_test with fs ext2 Oct 6 00:26:30 storageqe-109 systemd[1]: tmp-libblockdev.mflbkyfhmount_test.mount: Deactivated successfully. Oct 6 00:26:30 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8ae51d12-2ac2-4f7d-8df2-0250917348a0. INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext2 in remove_crypt INFO: remove crypt device PoOzraKZWR INFO: finishe the remove crypt device PoOzraKZWR cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:26:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/PoOzraKZWR and fs ext2 in remove_crypt Oct 6 00:26:30 storageqe-109 INFO: remove crypt device PoOzraKZWR Oct 6 00:26:30 storageqe-109 INFO: finishe the remove crypt device PoOzraKZWR Oct 6 00:26:30 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:26:30 storageqe-109 stratisd[4947]: [2025-10-06T04:26:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:26:30 storageqe-109 stratisd[4947]: [2025-10-06T04:26:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear RselamzvCw -q Oct 6 00:26:40 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear RselamzvCw -q Oct 6 00:26:40 storageqe-109 stratisd[4947]: [2025-10-06T04:26:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:26:40 storageqe-109 stratisd[4947]: [2025-10-06T04:26:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status RselamzvCw -q Oct 6 00:26:50 storageqe-109 journal: cryptsetup status RselamzvCw -q INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs xfs in remove_crypt Oct 6 00:27:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.5w4hlothmount_test with fs xfs Oct 6 00:27:10 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 430f24bb-4b27-4457-b7f3-6f4d0bb06378 Oct 6 00:27:10 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:27:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5w4hlothmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs ext4 in remove_crypt Oct 6 00:27:15 storageqe-109 systemd[1]: tmp-libblockdev.5w4hlothmount_test.mount: Deactivated successfully. Oct 6 00:27:15 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 430f24bb-4b27-4457-b7f3-6f4d0bb06378 Oct 6 00:27:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs xfs in remove_crypt Oct 6 00:27:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tw8z5hurmount_test with fs ext4 Oct 6 00:27:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 47099cd3-b64b-453a-a726-f65104dcad7f r/w with ordered data mode. Quota mode: none. Oct 6 00:27:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tw8z5hurmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs ext3 in remove_crypt Oct 6 00:27:31 storageqe-109 systemd[1]: tmp-libblockdev.tw8z5hurmount_test.mount: Deactivated successfully. Oct 6 00:27:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 47099cd3-b64b-453a-a726-f65104dcad7f. Oct 6 00:27:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs ext4 in remove_crypt Oct 6 00:27:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q3n083m8mount_test with fs ext3 Oct 6 00:27:41 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:27:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 275ef719-6735-40ea-afab-0d61ebed9bbe r/w with ordered data mode. Quota mode: none. Oct 6 00:27:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q3n083m8mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs ext2 in remove_crypt Oct 6 00:27:46 storageqe-109 systemd[1]: tmp-libblockdev.q3n083m8mount_test.mount: Deactivated successfully. Oct 6 00:27:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 275ef719-6735-40ea-afab-0d61ebed9bbe. Oct 6 00:27:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs ext3 in remove_crypt Oct 6 00:27:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RselamzvCw and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r85u4vjxmount_test with fs ext2 Oct 6 00:27:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:27:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2360dec1-222e-4c9d-8d19-b113521b0633 r/w without journal. Quota mode: none. Oct 6 00:27:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r85u4vjxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs ext2 in remove_crypt INFO: remove crypt device RselamzvCw INFO: finishe the remove crypt device RselamzvCw cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:28:01 storageqe-109 systemd[1]: tmp-libblockdev.r85u4vjxmount_test.mount: Deactivated successfully. Oct 6 00:28:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2360dec1-222e-4c9d-8d19-b113521b0633. Oct 6 00:28:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RselamzvCw and fs ext2 in remove_crypt Oct 6 00:28:01 storageqe-109 INFO: remove crypt device RselamzvCw Oct 6 00:28:01 storageqe-109 INFO: finishe the remove crypt device RselamzvCw Oct 6 00:28:01 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:28:02 storageqe-109 stratisd[4947]: [2025-10-06T04:28:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:28:02 storageqe-109 stratisd[4947]: [2025-10-06T04:28:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear kHMSgjGeZw -q Oct 6 00:28:12 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear kHMSgjGeZw -q Oct 6 00:28:12 storageqe-109 stratisd[4947]: [2025-10-06T04:28:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:28:12 storageqe-109 stratisd[4947]: [2025-10-06T04:28:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status kHMSgjGeZw -q Oct 6 00:28:22 storageqe-109 journal: cryptsetup status kHMSgjGeZw -q INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs xfs in remove_crypt Oct 6 00:28:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.npsxsbc5mount_test with fs xfs Oct 6 00:28:42 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 0c806df3-4081-448f-a40e-f4ea872af88b Oct 6 00:28:42 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:28:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.npsxsbc5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext4 in remove_crypt Oct 6 00:28:46 storageqe-109 systemd[1]: tmp-libblockdev.npsxsbc5mount_test.mount: Deactivated successfully. Oct 6 00:28:46 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 0c806df3-4081-448f-a40e-f4ea872af88b Oct 6 00:28:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs xfs in remove_crypt Oct 6 00:28:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fwi8zy7tmount_test with fs ext4 Oct 6 00:28:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 49dc04b4-944b-470e-a3ba-029f745575bd r/w with ordered data mode. Quota mode: none. Oct 6 00:28:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fwi8zy7tmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext3 in remove_crypt Oct 6 00:29:02 storageqe-109 systemd[1]: tmp-libblockdev.fwi8zy7tmount_test.mount: Deactivated successfully. Oct 6 00:29:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 49dc04b4-944b-470e-a3ba-029f745575bd. Oct 6 00:29:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext4 in remove_crypt Oct 6 00:29:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6w7ms8yymount_test with fs ext3 Oct 6 00:29:12 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:29:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 93ca981f-d1a6-4974-8b58-b4c3d97965b5 r/w with ordered data mode. Quota mode: none. Oct 6 00:29:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6w7ms8yymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext2 in remove_crypt Oct 6 00:29:17 storageqe-109 systemd[1]: tmp-libblockdev.6w7ms8yymount_test.mount: Deactivated successfully. Oct 6 00:29:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 93ca981f-d1a6-4974-8b58-b4c3d97965b5. Oct 6 00:29:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext3 in remove_crypt Oct 6 00:29:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.w7jo34t2mount_test with fs ext2 Oct 6 00:29:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:29:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d7a5dd72-af84-4662-a358-d42de32700ec r/w without journal. Quota mode: none. Oct 6 00:29:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.w7jo34t2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext2 in remove_crypt INFO: remove crypt device kHMSgjGeZw INFO: finishe the remove crypt device kHMSgjGeZw Oct 6 00:29:32 storageqe-109 systemd[1]: tmp-libblockdev.w7jo34t2mount_test.mount: Deactivated successfully. Oct 6 00:29:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d7a5dd72-af84-4662-a358-d42de32700ec. Oct 6 00:29:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/kHMSgjGeZw and fs ext2 in remove_crypt Oct 6 00:29:32 storageqe-109 INFO: remove crypt device kHMSgjGeZw Oct 6 00:29:32 storageqe-109 INFO: finishe the remove crypt device kHMSgjGeZw INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_sector_size_variations[npo2_linear] #### INFO: #### will start test_cipher_combinations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:29:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:29:37 storageqe-109 INFO: #### END test_sector_size_variations[npo2_linear] #### Oct 6 00:29:37 storageqe-109 INFO: #### will start test_cipher_combinations[npo2_linear] ##### Oct 6 00:29:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --cipher 'aes-cbc-essiv:sha256' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:29:44 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-essiv:sha256' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:29:44 storageqe-109 stratisd[4947]: [2025-10-06T04:29:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:29:44 storageqe-109 stratisd[4947]: [2025-10-06T04:29:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear dKXiFgHSox -q Oct 6 00:29:54 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear dKXiFgHSox -q Oct 6 00:29:54 storageqe-109 stratisd[4947]: [2025-10-06T04:29:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:29:54 storageqe-109 stratisd[4947]: [2025-10-06T04:29:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs xfs in remove_crypt Oct 6 00:30:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.p0e41mtjmount_test with fs xfs Oct 6 00:30:14 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 7db500e4-4796-4d66-83f0-30a1cab72efa Oct 6 00:30:14 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:30:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p0e41mtjmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext4 in remove_crypt Oct 6 00:30:19 storageqe-109 systemd[1]: tmp-libblockdev.p0e41mtjmount_test.mount: Deactivated successfully. Oct 6 00:30:19 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 7db500e4-4796-4d66-83f0-30a1cab72efa Oct 6 00:30:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs xfs in remove_crypt Oct 6 00:30:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.l84jzmncmount_test with fs ext4 Oct 6 00:30:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0295fd72-8b2b-43cc-91a7-839afb072ec5 r/w with ordered data mode. Quota mode: none. Oct 6 00:30:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l84jzmncmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext3 in remove_crypt Oct 6 00:30:34 storageqe-109 systemd[1]: tmp-libblockdev.l84jzmncmount_test.mount: Deactivated successfully. Oct 6 00:30:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0295fd72-8b2b-43cc-91a7-839afb072ec5. Oct 6 00:30:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext4 in remove_crypt Oct 6 00:30:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f26tguitmount_test with fs ext3 Oct 6 00:30:45 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:30:45 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 51c21616-9720-48f2-9575-dead110c34bf r/w with ordered data mode. Quota mode: none. Oct 6 00:30:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f26tguitmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext2 in remove_crypt Oct 6 00:30:49 storageqe-109 systemd[1]: tmp-libblockdev.f26tguitmount_test.mount: Deactivated successfully. Oct 6 00:30:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 51c21616-9720-48f2-9575-dead110c34bf. Oct 6 00:30:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext3 in remove_crypt Oct 6 00:30:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nx2151xtmount_test with fs ext2 Oct 6 00:31:00 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:31:00 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7f1408a3-d556-47bb-a396-eef820b967fe r/w without journal. Quota mode: none. Oct 6 00:31:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nx2151xtmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext2 in remove_crypt INFO: remove crypt device dKXiFgHSox Oct 6 00:31:04 storageqe-109 systemd[1]: tmp-libblockdev.nx2151xtmount_test.mount: Deactivated successfully. Oct 6 00:31:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7f1408a3-d556-47bb-a396-eef820b967fe. Oct 6 00:31:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dKXiFgHSox and fs ext2 in remove_crypt Oct 6 00:31:04 storageqe-109 INFO: remove crypt device dKXiFgHSox INFO: finishe the remove crypt device dKXiFgHSox cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:31:05 storageqe-109 INFO: finishe the remove crypt device dKXiFgHSox Oct 6 00:31:05 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:31:05 storageqe-109 stratisd[4947]: [2025-10-06T04:31:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:31:05 storageqe-109 stratisd[4947]: [2025-10-06T04:31:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear csVnaUlSGt -q Oct 6 00:31:15 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear csVnaUlSGt -q Oct 6 00:31:15 storageqe-109 stratisd[4947]: [2025-10-06T04:31:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:31:15 storageqe-109 stratisd[4947]: [2025-10-06T04:31:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs xfs in remove_crypt Oct 6 00:31:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.1s0ee4hjmount_test with fs xfs Oct 6 00:31:35 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem c4466e36-ec2d-4bd2-8ad8-7caad011953c Oct 6 00:31:35 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:31:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1s0ee4hjmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext4 in remove_crypt Oct 6 00:31:40 storageqe-109 systemd[1]: tmp-libblockdev.1s0ee4hjmount_test.mount: Deactivated successfully. Oct 6 00:31:40 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem c4466e36-ec2d-4bd2-8ad8-7caad011953c Oct 6 00:31:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs xfs in remove_crypt Oct 6 00:31:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mvf2k1u9mount_test with fs ext4 Oct 6 00:31:50 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 82bd8302-7e49-434d-86ac-589fac84d568 r/w with ordered data mode. Quota mode: none. Oct 6 00:31:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mvf2k1u9mount_test with fs ext4 Oct 6 00:31:54 storageqe-109 systemd[1]: tmp-libblockdev.mvf2k1u9mount_test.mount: Deactivated successfully. Oct 6 00:31:55 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 82bd8302-7e49-434d-86ac-589fac84d568. INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext3 in remove_crypt Oct 6 00:31:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext4 in remove_crypt Oct 6 00:31:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext3 in remove_crypt Oct 6 00:32:05 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.qbgp2u5wmount_test with fs ext3 Oct 6 00:32:05 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 16b9292f-66e2-48f4-9e0a-05d1a738713e r/w with ordered data mode. Quota mode: none. Oct 6 00:32:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qbgp2u5wmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext2 in remove_crypt Oct 6 00:32:10 storageqe-109 systemd[1]: tmp-libblockdev.qbgp2u5wmount_test.mount: Deactivated successfully. Oct 6 00:32:10 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 16b9292f-66e2-48f4-9e0a-05d1a738713e. Oct 6 00:32:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext3 in remove_crypt Oct 6 00:32:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.64e1_gmsmount_test with fs ext2 Oct 6 00:32:20 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:32:20 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 44ea7b0d-f115-4568-aa50-3ba31ab541bb r/w without journal. Quota mode: none. Oct 6 00:32:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.64e1_gmsmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext2 in remove_crypt Oct 6 00:32:24 storageqe-109 systemd[1]: tmp-libblockdev.64e1_gmsmount_test.mount: Deactivated successfully. Oct 6 00:32:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 44ea7b0d-f115-4568-aa50-3ba31ab541bb. Oct 6 00:32:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/csVnaUlSGt and fs ext2 in remove_crypt INFO: remove crypt device csVnaUlSGt INFO: finishe the remove crypt device csVnaUlSGt cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:32:25 storageqe-109 INFO: remove crypt device csVnaUlSGt Oct 6 00:32:25 storageqe-109 INFO: finishe the remove crypt device csVnaUlSGt Oct 6 00:32:25 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:32:25 storageqe-109 stratisd[4947]: [2025-10-06T04:32:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:32:25 storageqe-109 stratisd[4947]: [2025-10-06T04:32:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear JlpFhRUcHg -q Oct 6 00:32:35 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear JlpFhRUcHg -q Oct 6 00:32:35 storageqe-109 stratisd[4947]: [2025-10-06T04:32:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:32:35 storageqe-109 stratisd[4947]: [2025-10-06T04:32:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs xfs in remove_crypt Oct 6 00:32:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2hix22egmount_test with fs xfs Oct 6 00:32:55 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b7def7af-eb6e-4d09-aff4-c602d152baff Oct 6 00:32:55 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:32:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2hix22egmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext4 in remove_crypt Oct 6 00:33:00 storageqe-109 systemd[1]: tmp-libblockdev.2hix22egmount_test.mount: Deactivated successfully. Oct 6 00:33:00 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b7def7af-eb6e-4d09-aff4-c602d152baff Oct 6 00:33:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs xfs in remove_crypt Oct 6 00:33:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1jz8c263mount_test with fs ext4 Oct 6 00:33:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 512318db-1df5-4e07-a969-f9a88bb23521 r/w with ordered data mode. Quota mode: none. Oct 6 00:33:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1jz8c263mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext3 in remove_crypt Oct 6 00:33:15 storageqe-109 systemd[1]: tmp-libblockdev.1jz8c263mount_test.mount: Deactivated successfully. Oct 6 00:33:15 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 512318db-1df5-4e07-a969-f9a88bb23521. Oct 6 00:33:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext4 in remove_crypt Oct 6 00:33:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.peqs_g0wmount_test with fs ext3 Oct 6 00:33:25 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:33:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 58d518e3-f55c-499b-b285-724ebe54aa13 r/w with ordered data mode. Quota mode: none. Oct 6 00:33:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.peqs_g0wmount_test with fs ext3 Oct 6 00:33:30 storageqe-109 systemd[1]: tmp-libblockdev.peqs_g0wmount_test.mount: Deactivated successfully. Oct 6 00:33:30 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 58d518e3-f55c-499b-b285-724ebe54aa13. INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext2 in remove_crypt Oct 6 00:33:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext3 in remove_crypt Oct 6 00:33:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uet8t0iymount_test with fs ext2 Oct 6 00:33:40 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:33:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2eb216dc-d6ef-42b7-9750-bba8697dbb69 r/w without journal. Quota mode: none. Oct 6 00:33:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uet8t0iymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext2 in remove_crypt INFO: remove crypt device JlpFhRUcHg INFO: finishe the remove crypt device JlpFhRUcHg cryptsetup --type 'luks2' --cipher 'twofish-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:33:45 storageqe-109 systemd[1]: tmp-libblockdev.uet8t0iymount_test.mount: Deactivated successfully. Oct 6 00:33:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2eb216dc-d6ef-42b7-9750-bba8697dbb69. Oct 6 00:33:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JlpFhRUcHg and fs ext2 in remove_crypt Oct 6 00:33:45 storageqe-109 INFO: remove crypt device JlpFhRUcHg Oct 6 00:33:45 storageqe-109 INFO: finishe the remove crypt device JlpFhRUcHg Oct 6 00:33:45 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'twofish-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:33:45 storageqe-109 stratisd[4947]: [2025-10-06T04:33:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:33:45 storageqe-109 stratisd[4947]: [2025-10-06T04:33:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear KvLQHxlTri -q Oct 6 00:33:55 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear KvLQHxlTri -q Oct 6 00:33:55 storageqe-109 stratisd[4947]: [2025-10-06T04:33:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:33:55 storageqe-109 stratisd[4947]: [2025-10-06T04:33:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs xfs in remove_crypt Oct 6 00:34:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.dk4__z1bmount_test with fs xfs Oct 6 00:34:15 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3d31e845-05b9-48a5-99f1-4de7a8d04294 Oct 6 00:34:15 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:34:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dk4__z1bmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext4 in remove_crypt Oct 6 00:34:21 storageqe-109 systemd[1]: tmp-libblockdev.dk4__z1bmount_test.mount: Deactivated successfully. Oct 6 00:34:21 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3d31e845-05b9-48a5-99f1-4de7a8d04294 Oct 6 00:34:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs xfs in remove_crypt Oct 6 00:34:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.n5g6q_1fmount_test with fs ext4 Oct 6 00:34:31 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 14310268-c5a7-407d-bb0b-708a12a3ffbe r/w with ordered data mode. Quota mode: none. Oct 6 00:34:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n5g6q_1fmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext3 in remove_crypt Oct 6 00:34:36 storageqe-109 systemd[1]: tmp-libblockdev.n5g6q_1fmount_test.mount: Deactivated successfully. Oct 6 00:34:36 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 14310268-c5a7-407d-bb0b-708a12a3ffbe. Oct 6 00:34:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext4 in remove_crypt Oct 6 00:34:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext3 in remove_crypt Oct 6 00:34:47 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.c7ep36b5mount_test with fs ext3 Oct 6 00:34:47 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 01dac22f-7b80-4a14-833a-836d7e057df5 r/w with ordered data mode. Quota mode: none. Oct 6 00:34:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c7ep36b5mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext2 in remove_crypt Oct 6 00:34:52 storageqe-109 systemd[1]: tmp-libblockdev.c7ep36b5mount_test.mount: Deactivated successfully. Oct 6 00:34:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 01dac22f-7b80-4a14-833a-836d7e057df5. Oct 6 00:34:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext3 in remove_crypt Oct 6 00:34:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hlvn4dd5mount_test with fs ext2 Oct 6 00:35:02 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:35:02 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4396c3ad-7901-4fbd-af25-4af5dabd4d11 r/w without journal. Quota mode: none. Oct 6 00:35:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hlvn4dd5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext2 in remove_crypt INFO: remove crypt device KvLQHxlTri INFO: finishe the remove crypt device KvLQHxlTri cryptsetup --type 'luks2' --cipher 'serpent-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:35:08 storageqe-109 systemd[1]: tmp-libblockdev.hlvn4dd5mount_test.mount: Deactivated successfully. Oct 6 00:35:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4396c3ad-7901-4fbd-af25-4af5dabd4d11. Oct 6 00:35:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KvLQHxlTri and fs ext2 in remove_crypt Oct 6 00:35:08 storageqe-109 INFO: remove crypt device KvLQHxlTri Oct 6 00:35:08 storageqe-109 INFO: finishe the remove crypt device KvLQHxlTri Oct 6 00:35:08 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 00:35:08 storageqe-109 stratisd[4947]: [2025-10-06T04:35:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:35:08 storageqe-109 stratisd[4947]: [2025-10-06T04:35:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear QjPMqBArCN -q Oct 6 00:35:18 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear QjPMqBArCN -q Oct 6 00:35:18 storageqe-109 stratisd[4947]: [2025-10-06T04:35:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:35:18 storageqe-109 stratisd[4947]: [2025-10-06T04:35:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs xfs in remove_crypt Oct 6 00:35:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.re7uog91mount_test with fs xfs Oct 6 00:35:38 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ee0dda09-2173-409f-89dc-8838855cae75 Oct 6 00:35:38 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:35:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.re7uog91mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext4 in remove_crypt Oct 6 00:35:43 storageqe-109 systemd[1]: tmp-libblockdev.re7uog91mount_test.mount: Deactivated successfully. Oct 6 00:35:43 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ee0dda09-2173-409f-89dc-8838855cae75 Oct 6 00:35:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs xfs in remove_crypt Oct 6 00:35:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ox26rjgbmount_test with fs ext4 Oct 6 00:35:53 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f58122b6-39c1-4776-96c9-29cf326ef94f r/w with ordered data mode. Quota mode: none. Oct 6 00:35:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ox26rjgbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext3 in remove_crypt Oct 6 00:35:59 storageqe-109 systemd[1]: tmp-libblockdev.ox26rjgbmount_test.mount: Deactivated successfully. Oct 6 00:35:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f58122b6-39c1-4776-96c9-29cf326ef94f. Oct 6 00:35:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext4 in remove_crypt Oct 6 00:35:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.yl7rqfg2mount_test with fs ext3 Oct 6 00:36:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:36:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7404baed-6abd-4637-b02c-a0f66530cc0d r/w with ordered data mode. Quota mode: none. Oct 6 00:36:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yl7rqfg2mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext2 in remove_crypt Oct 6 00:36:14 storageqe-109 systemd[1]: tmp-libblockdev.yl7rqfg2mount_test.mount: Deactivated successfully. Oct 6 00:36:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7404baed-6abd-4637-b02c-a0f66530cc0d. Oct 6 00:36:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext3 in remove_crypt Oct 6 00:36:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e6rkvp1lmount_test with fs ext2 Oct 6 00:36:25 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:36:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 52144139-2200-4a1b-878c-2b7822ffa6a3 r/w without journal. Quota mode: none. Oct 6 00:36:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e6rkvp1lmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext2 in remove_crypt INFO: remove crypt device QjPMqBArCN INFO: finishe the remove crypt device QjPMqBArCN Oct 6 00:36:30 storageqe-109 systemd[1]: tmp-libblockdev.e6rkvp1lmount_test.mount: Deactivated successfully. Oct 6 00:36:30 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 52144139-2200-4a1b-878c-2b7822ffa6a3. Oct 6 00:36:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QjPMqBArCN and fs ext2 in remove_crypt Oct 6 00:36:30 storageqe-109 INFO: remove crypt device QjPMqBArCN Oct 6 00:36:30 storageqe-109 INFO: finishe the remove crypt device QjPMqBArCN INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_cipher_combinations[npo2_linear] #### INFO: #### will start test_keyslot_encryption_variations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:36:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:36:35 storageqe-109 INFO: #### END test_cipher_combinations[npo2_linear] #### Oct 6 00:36:35 storageqe-109 INFO: #### will start test_keyslot_encryption_variations[npo2_linear] ##### Oct 6 00:36:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileBYZ Oct 6 00:36:42 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileBYZ Oct 6 00:36:42 storageqe-109 stratisd[4947]: [2025-10-06T04:36:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:36:42 storageqe-109 stratisd[4947]: [2025-10-06T04:36:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileBYZ' open /dev/mapper/npo2linear WxZJNXCQhl -q Oct 6 00:36:52 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileBYZ' open /dev/mapper/npo2linear WxZJNXCQhl -q Oct 6 00:36:52 storageqe-109 stratisd[4947]: [2025-10-06T04:36:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:36:52 storageqe-109 stratisd[4947]: [2025-10-06T04:36:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs xfs in remove_crypt Oct 6 00:37:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2p89hn_8mount_test with fs xfs Oct 6 00:37:12 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem bcfd5132-b449-434c-a8cd-21d4bdd7121f Oct 6 00:37:12 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:37:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2p89hn_8mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext4 in remove_crypt Oct 6 00:37:17 storageqe-109 systemd[1]: tmp-libblockdev.2p89hn_8mount_test.mount: Deactivated successfully. Oct 6 00:37:17 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem bcfd5132-b449-434c-a8cd-21d4bdd7121f Oct 6 00:37:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs xfs in remove_crypt Oct 6 00:37:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.394rw_yymount_test with fs ext4 Oct 6 00:37:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ecd7188a-79a4-48ae-b3c5-61ec18f94d7e r/w with ordered data mode. Quota mode: none. Oct 6 00:37:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.394rw_yymount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext3 in remove_crypt Oct 6 00:37:32 storageqe-109 systemd[1]: tmp-libblockdev.394rw_yymount_test.mount: Deactivated successfully. Oct 6 00:37:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ecd7188a-79a4-48ae-b3c5-61ec18f94d7e. Oct 6 00:37:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext4 in remove_crypt Oct 6 00:37:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8uajl_98mount_test with fs ext3 Oct 6 00:37:43 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:37:43 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4e5644a4-8460-4b4d-b084-4f35b39fa75b r/w with ordered data mode. Quota mode: none. Oct 6 00:37:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8uajl_98mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext2 in remove_crypt Oct 6 00:37:47 storageqe-109 systemd[1]: tmp-libblockdev.8uajl_98mount_test.mount: Deactivated successfully. Oct 6 00:37:47 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4e5644a4-8460-4b4d-b084-4f35b39fa75b. Oct 6 00:37:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext3 in remove_crypt Oct 6 00:37:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ejh12k7hmount_test with fs ext2 Oct 6 00:37:57 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:37:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b336d22a-c772-4b88-ad34-c92260ee1834 r/w without journal. Quota mode: none. Oct 6 00:37:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ejh12k7hmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext2 in remove_crypt INFO: remove crypt device WxZJNXCQhl INFO: finishe the remove crypt device WxZJNXCQhl Oct 6 00:38:02 storageqe-109 systemd[1]: tmp-libblockdev.ejh12k7hmount_test.mount: Deactivated successfully. Oct 6 00:38:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b336d22a-c772-4b88-ad34-c92260ee1834. Oct 6 00:38:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WxZJNXCQhl and fs ext2 in remove_crypt Oct 6 00:38:02 storageqe-109 INFO: remove crypt device WxZJNXCQhl Oct 6 00:38:02 storageqe-109 INFO: finishe the remove crypt device WxZJNXCQhl cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileUuj Oct 6 00:38:04 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileUuj Oct 6 00:38:04 storageqe-109 stratisd[4947]: [2025-10-06T04:38:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:38:04 storageqe-109 stratisd[4947]: [2025-10-06T04:38:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileUuj' open /dev/mapper/npo2linear cCGPXEkhZM -q Oct 6 00:38:15 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileUuj' open /dev/mapper/npo2linear cCGPXEkhZM -q Oct 6 00:38:15 storageqe-109 stratisd[4947]: [2025-10-06T04:38:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:38:15 storageqe-109 stratisd[4947]: [2025-10-06T04:38:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs xfs in remove_crypt Oct 6 00:38:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2gvhaak4mount_test with fs xfs Oct 6 00:38:35 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem c68d0dfc-c905-4ca0-92aa-6e0b10f81a33 Oct 6 00:38:35 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:38:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2gvhaak4mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext4 in remove_crypt Oct 6 00:38:39 storageqe-109 systemd[1]: tmp-libblockdev.2gvhaak4mount_test.mount: Deactivated successfully. Oct 6 00:38:39 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem c68d0dfc-c905-4ca0-92aa-6e0b10f81a33 Oct 6 00:38:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs xfs in remove_crypt Oct 6 00:38:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m8tycz_wmount_test with fs ext4 Oct 6 00:38:50 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a9095ae1-b5d7-4a06-9e32-4954f8fc7b18 r/w with ordered data mode. Quota mode: none. Oct 6 00:38:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m8tycz_wmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext3 in remove_crypt Oct 6 00:38:54 storageqe-109 systemd[1]: tmp-libblockdev.m8tycz_wmount_test.mount: Deactivated successfully. Oct 6 00:38:54 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a9095ae1-b5d7-4a06-9e32-4954f8fc7b18. Oct 6 00:38:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext4 in remove_crypt Oct 6 00:38:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.a5myzxvjmount_test with fs ext3 Oct 6 00:39:05 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:39:05 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 74e53361-0979-4570-8120-856e0d3dab8e r/w with ordered data mode. Quota mode: none. Oct 6 00:39:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a5myzxvjmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext2 in remove_crypt Oct 6 00:39:09 storageqe-109 systemd[1]: tmp-libblockdev.a5myzxvjmount_test.mount: Deactivated successfully. Oct 6 00:39:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 74e53361-0979-4570-8120-856e0d3dab8e. Oct 6 00:39:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext3 in remove_crypt Oct 6 00:39:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jcuw56tamount_test with fs ext2 Oct 6 00:39:20 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:39:20 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fd53f694-1143-416a-aa97-5b5ef1db78c0 r/w without journal. Quota mode: none. Oct 6 00:39:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jcuw56tamount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext2 in remove_crypt INFO: remove crypt device cCGPXEkhZM INFO: finishe the remove crypt device cCGPXEkhZM Oct 6 00:39:24 storageqe-109 systemd[1]: tmp-libblockdev.jcuw56tamount_test.mount: Deactivated successfully. Oct 6 00:39:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fd53f694-1143-416a-aa97-5b5ef1db78c0. Oct 6 00:39:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cCGPXEkhZM and fs ext2 in remove_crypt Oct 6 00:39:24 storageqe-109 INFO: remove crypt device cCGPXEkhZM Oct 6 00:39:24 storageqe-109 INFO: finishe the remove crypt device cCGPXEkhZM cryptsetup --type 'luks2' --keyslot-cipher 'aes-xts-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileQDo Oct 6 00:39:26 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'aes-xts-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileQDo Oct 6 00:39:27 storageqe-109 stratisd[4947]: [2025-10-06T04:39:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:39:27 storageqe-109 stratisd[4947]: [2025-10-06T04:39:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileQDo' open /dev/mapper/npo2linear iTVWadewru -q Oct 6 00:39:37 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQDo' open /dev/mapper/npo2linear iTVWadewru -q Oct 6 00:39:37 storageqe-109 stratisd[4947]: [2025-10-06T04:39:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:39:37 storageqe-109 stratisd[4947]: [2025-10-06T04:39:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs xfs in remove_crypt Oct 6 00:39:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.pyytvd6wmount_test with fs xfs Oct 6 00:39:57 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 6fa2f83c-0648-4d73-a390-6e610bfc5686 Oct 6 00:39:57 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:39:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pyytvd6wmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs ext4 in remove_crypt Oct 6 00:40:01 storageqe-109 systemd[1]: tmp-libblockdev.pyytvd6wmount_test.mount: Deactivated successfully. Oct 6 00:40:01 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 6fa2f83c-0648-4d73-a390-6e610bfc5686 Oct 6 00:40:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs xfs in remove_crypt Oct 6 00:40:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.yv9md1llmount_test with fs ext4 Oct 6 00:40:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4b9445e5-ce52-4358-b2c7-132578193872 r/w with ordered data mode. Quota mode: none. Oct 6 00:40:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yv9md1llmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs ext3 in remove_crypt Oct 6 00:40:16 storageqe-109 systemd[1]: tmp-libblockdev.yv9md1llmount_test.mount: Deactivated successfully. Oct 6 00:40:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4b9445e5-ce52-4358-b2c7-132578193872. Oct 6 00:40:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs ext4 in remove_crypt Oct 6 00:40:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g5deo8wmmount_test with fs ext3 Oct 6 00:40:26 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:40:26 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem db454284-998e-415a-8d42-153c85643a94 r/w with ordered data mode. Quota mode: none. Oct 6 00:40:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g5deo8wmmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs ext2 in remove_crypt Oct 6 00:40:31 storageqe-109 systemd[1]: tmp-libblockdev.g5deo8wmmount_test.mount: Deactivated successfully. Oct 6 00:40:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem db454284-998e-415a-8d42-153c85643a94. Oct 6 00:40:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs ext3 in remove_crypt Oct 6 00:40:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/iTVWadewru and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rp8mjuxdmount_test with fs ext2 Oct 6 00:40:41 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:40:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ef993c72-b611-4c14-b790-9e1528209182 r/w without journal. Quota mode: none. Oct 6 00:40:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rp8mjuxdmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs ext2 in remove_crypt INFO: remove crypt device iTVWadewru INFO: finishe the remove crypt device iTVWadewru Oct 6 00:40:46 storageqe-109 systemd[1]: tmp-libblockdev.rp8mjuxdmount_test.mount: Deactivated successfully. Oct 6 00:40:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ef993c72-b611-4c14-b790-9e1528209182. Oct 6 00:40:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/iTVWadewru and fs ext2 in remove_crypt Oct 6 00:40:46 storageqe-109 INFO: remove crypt device iTVWadewru Oct 6 00:40:46 storageqe-109 INFO: finishe the remove crypt device iTVWadewru cryptsetup --type 'luks2' --keyslot-cipher 'twofish-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilepqZ Oct 6 00:40:48 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'twofish-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilepqZ Oct 6 00:40:49 storageqe-109 stratisd[4947]: [2025-10-06T04:40:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:40:49 storageqe-109 stratisd[4947]: [2025-10-06T04:40:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilepqZ' open /dev/mapper/npo2linear vAfsebuVxO -q Oct 6 00:40:59 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilepqZ' open /dev/mapper/npo2linear vAfsebuVxO -q Oct 6 00:40:59 storageqe-109 stratisd[4947]: [2025-10-06T04:40:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:40:59 storageqe-109 stratisd[4947]: [2025-10-06T04:40:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs xfs in remove_crypt Oct 6 00:41:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.t03siu90mount_test with fs xfs Oct 6 00:41:19 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 9c2af0c8-bd07-4093-8321-c772e7b9025c Oct 6 00:41:19 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 00:41:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t03siu90mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext4 in remove_crypt Oct 6 00:41:23 storageqe-109 systemd[1]: tmp-libblockdev.t03siu90mount_test.mount: Deactivated successfully. Oct 6 00:41:23 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 9c2af0c8-bd07-4093-8321-c772e7b9025c Oct 6 00:41:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs xfs in remove_crypt Oct 6 00:41:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0rjgttelmount_test with fs ext4 Oct 6 00:41:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0bf75241-3895-4f73-89a6-d379499fa5e8 r/w with ordered data mode. Quota mode: none. Oct 6 00:41:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0rjgttelmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext3 in remove_crypt Oct 6 00:41:38 storageqe-109 systemd[1]: tmp-libblockdev.0rjgttelmount_test.mount: Deactivated successfully. Oct 6 00:41:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0bf75241-3895-4f73-89a6-d379499fa5e8. Oct 6 00:41:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext4 in remove_crypt Oct 6 00:41:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pttjl43tmount_test with fs ext3 Oct 6 00:41:49 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 00:41:49 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c23c36a7-20a9-4a63-8925-582659385a57 r/w with ordered data mode. Quota mode: none. Oct 6 00:41:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pttjl43tmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext2 in remove_crypt Oct 6 00:41:53 storageqe-109 systemd[1]: tmp-libblockdev.pttjl43tmount_test.mount: Deactivated successfully. Oct 6 00:41:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c23c36a7-20a9-4a63-8925-582659385a57. Oct 6 00:41:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext3 in remove_crypt Oct 6 00:41:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mgvhmrremount_test with fs ext2 Oct 6 00:42:04 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 00:42:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 93d11176-eac5-4698-aa55-237b615c6896 r/w without journal. Quota mode: none. Oct 6 00:42:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mgvhmrremount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext2 in remove_crypt INFO: remove crypt device vAfsebuVxO INFO: finishe the remove crypt device vAfsebuVxO Oct 6 00:42:08 storageqe-109 systemd[1]: tmp-libblockdev.mgvhmrremount_test.mount: Deactivated successfully. Oct 6 00:42:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 93d11176-eac5-4698-aa55-237b615c6896. Oct 6 00:42:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vAfsebuVxO and fs ext2 in remove_crypt Oct 6 00:42:08 storageqe-109 INFO: remove crypt device vAfsebuVxO Oct 6 00:42:08 storageqe-109 INFO: finishe the remove crypt device vAfsebuVxO INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_keyslot_encryption_variations[npo2_linear] #### Oct 6 00:42:14 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:42:14 storageqe-109 INFO: #### END test_keyslot_encryption_variations[npo2_linear] #### Oct 6 00:42:14 storageqe-109 stratisd[4947]: [2025-10-06T04:42:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:42:14 storageqe-109 stratisd[4947]: [2025-10-06T04:42:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:42:14 storageqe-109 stratisd[4947]: [2025-10-06T04:42:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:42:14 storageqe-109 stratisd[4947]: [2025-10-06T04:42:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 00:42:15 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:42:15 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 00:42:16 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 00:42:16 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 00:42:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 00:42:26 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_integrity_stress_scenarios[npo2_linear] ##### Oct 6 00:42:32 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:42:32 storageqe-109 INFO: #### will start test_integrity_stress_scenarios[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:42:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' format /dev/mapper/npo2linear -q Oct 6 00:42:38 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' format /dev/mapper/npo2linear -q Oct 6 00:42:46 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. integritysetup --integrity 'sha256' open /dev/mapper/npo2linear GkxFXLDeIE -q Oct 6 00:42:52 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear GkxFXLDeIE -q integritysetup close GkxFXLDeIE -q Oct 6 00:43:02 storageqe-109 journal: integritysetup close GkxFXLDeIE -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --tag-size '32' --integrity-key-file '/tmp/testfileMHY' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 00:43:13 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --tag-size '32' --integrity-key-file '/tmp/testfileMHY' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileMHY' --integrity-key-size '32' open /dev/mapper/npo2linear GkxFXLDeIE -q Oct 6 00:43:27 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileMHY' --integrity-key-size '32' open /dev/mapper/npo2linear GkxFXLDeIE -q integritysetup close GkxFXLDeIE -q Oct 6 00:43:37 storageqe-109 journal: integritysetup close GkxFXLDeIE -q integritysetup --integrity 'crc32c' --sector-size '4096' --tag-size '4' format /dev/mapper/npo2linear -q Oct 6 00:43:48 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' --tag-size '4' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear GkxFXLDeIE -q Oct 6 00:44:01 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear GkxFXLDeIE -q integritysetup close GkxFXLDeIE -q Oct 6 00:44:11 storageqe-109 journal: integritysetup close GkxFXLDeIE -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_stress_scenarios[npo2_linear] #### INFO: #### will start test_advanced_journal_parameters[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:44:26 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:44:26 storageqe-109 INFO: #### END test_integrity_stress_scenarios[npo2_linear] #### Oct 6 00:44:26 storageqe-109 INFO: #### will start test_advanced_journal_parameters[npo2_linear] ##### Oct 6 00:44:26 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' --journal-watermark '5' --journal-commit-time '50' format /dev/mapper/npo2linear -q Oct 6 00:44:32 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' --journal-watermark '5' --journal-commit-time '50' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' --journal-watermark '5' --journal-commit-time '50' open /dev/mapper/npo2linear yfEeFcgDJG -q Oct 6 00:44:46 storageqe-109 journal: integritysetup --integrity 'sha256' --journal-watermark '5' --journal-commit-time '50' open /dev/mapper/npo2linear yfEeFcgDJG -q integritysetup status yfEeFcgDJG -q Oct 6 00:44:56 storageqe-109 journal: integritysetup status yfEeFcgDJG -q integritysetup close yfEeFcgDJG -q Oct 6 00:45:07 storageqe-109 journal: integritysetup close yfEeFcgDJG -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '2048' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileJKz' --integrity-key-size '64' format /dev/mapper/npo2linear -q Oct 6 00:45:18 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '2048' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileJKz' --integrity-key-size '64' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileJKz' --integrity-key-size '64' open /dev/mapper/npo2linear dBiLvAQXrh -q Oct 6 00:45:33 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileJKz' --integrity-key-size '64' open /dev/mapper/npo2linear dBiLvAQXrh -q Oct 6 00:45:33 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 00:45:33 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 00:45:33 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. integritysetup status dBiLvAQXrh -q Oct 6 00:45:43 storageqe-109 journal: integritysetup status dBiLvAQXrh -q integritysetup close dBiLvAQXrh -q Oct 6 00:46:24 storageqe-109 journal: integritysetup close dBiLvAQXrh -q integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '1024' --journal-watermark '33' --journal-commit-time '1337' format /dev/mapper/npo2linear -q Oct 6 00:46:35 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '1024' --journal-watermark '33' --journal-commit-time '1337' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' --journal-watermark '33' --journal-commit-time '1337' open /dev/mapper/npo2linear blDtXHRcCd -q Oct 6 00:46:47 storageqe-109 journal: integritysetup --integrity 'crc32c' --journal-watermark '33' --journal-commit-time '1337' open /dev/mapper/npo2linear blDtXHRcCd -q integritysetup status blDtXHRcCd -q Oct 6 00:46:57 storageqe-109 journal: integritysetup status blDtXHRcCd -q integritysetup close blDtXHRcCd -q Oct 6 00:47:10 storageqe-109 journal: integritysetup close blDtXHRcCd -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_advanced_journal_parameters[npo2_linear] #### INFO: #### will start test_bitmap_mode_advanced[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:47:25 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 00:47:25 storageqe-109 INFO: #### END test_advanced_journal_parameters[npo2_linear] #### Oct 6 00:47:25 storageqe-109 INFO: #### will start test_bitmap_mode_advanced[npo2_linear] ##### Oct 6 00:47:25 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb Oct 6 00:47:30 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb integritysetup --integrity 'crc32c' --bitmap-sectors-per-bit '32768' --bitmap-flush-time '1000' open /dev/mapper/npo2linear TWyOdBDFls -q --integrity-bitmap-mode Oct 6 00:47:43 storageqe-109 journal: integritysetup --integrity 'crc32c' --bitmap-sectors-per-bit '32768' --bitmap-flush-time '1000' open /dev/mapper/npo2linear TWyOdBDFls -q --integrity-bitmap-mode integritysetup status TWyOdBDFls -q Oct 6 00:47:53 storageqe-109 journal: integritysetup status TWyOdBDFls -q integritysetup status TWyOdBDFls -q Oct 6 00:48:03 storageqe-109 journal: integritysetup status TWyOdBDFls -q integritysetup close TWyOdBDFls -q Oct 6 00:48:15 storageqe-109 journal: integritysetup close TWyOdBDFls -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb Oct 6 00:48:25 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb integritysetup --integrity 'sha256' --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear OVolhawCnX -q --integrity-bitmap-mode Oct 6 00:48:39 storageqe-109 journal: integritysetup --integrity 'sha256' --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear OVolhawCnX -q --integrity-bitmap-mode integritysetup status OVolhawCnX -q Oct 6 00:48:49 storageqe-109 journal: integritysetup status OVolhawCnX -q integritysetup status OVolhawCnX -q Oct 6 00:48:59 storageqe-109 journal: integritysetup status OVolhawCnX -q integritysetup close OVolhawCnX -q Oct 6 00:49:15 storageqe-109 journal: integritysetup close OVolhawCnX -q INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### INFO: #### END test_bitmap_mode_advanced[npo2_linear] #### INFO: #### will start test_metadata_device_configurations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### Oct 6 00:49:30 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### Oct 6 00:49:30 storageqe-109 INFO: #### END test_bitmap_mode_advanced[npo2_linear] #### Oct 6 00:49:30 storageqe-109 INFO: #### will start test_metadata_device_configurations[npo2_linear] ##### Oct 6 00:49:30 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### integritysetup --data-device '/dev/sdc' --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 00:49:37 storageqe-109 journal: integritysetup --data-device '/dev/sdc' --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 00:58:40 storageqe-109 systemd[1]: Starting logrotate.service - Rotate log files... Oct 6 00:58:40 storageqe-109 systemd[1]: logrotate.service: Deactivated successfully. Oct 6 00:58:40 storageqe-109 systemd[1]: Finished logrotate.service - Rotate log files. integritysetup --integrity 'crc32c' --data-device '/dev/sdc' open /dev/mapper/npo2linear maZGoVjRcD -q Oct 6 01:01:35 storageqe-109 journal: integritysetup --integrity 'crc32c' --data-device '/dev/sdc' open /dev/mapper/npo2linear maZGoVjRcD -q integritysetup status maZGoVjRcD -q Oct 6 01:01:45 storageqe-109 journal: integritysetup status maZGoVjRcD -q integritysetup close maZGoVjRcD -q Oct 6 01:01:55 storageqe-109 journal: integritysetup close maZGoVjRcD -q integritysetup --data-device '/dev/sdd' --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 01:02:07 storageqe-109 journal: integritysetup --data-device '/dev/sdd' --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' --data-device '/dev/sdd' open /dev/mapper/npo2linear QNFszEtpnJ -q Oct 6 01:14:05 storageqe-109 journal: integritysetup --integrity 'sha256' --data-device '/dev/sdd' open /dev/mapper/npo2linear QNFszEtpnJ -q integritysetup status QNFszEtpnJ -q Oct 6 01:14:15 storageqe-109 journal: integritysetup status QNFszEtpnJ -q integritysetup close QNFszEtpnJ -q Oct 6 01:14:25 storageqe-109 journal: integritysetup close QNFszEtpnJ -q INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_metadata_device_configurations[npo2_linear] #### INFO: #### will start test_concurrent_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 6 01:14:40 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 6 01:14:40 storageqe-109 INFO: #### END test_metadata_device_configurations[npo2_linear] #### Oct 6 01:14:40 storageqe-109 INFO: #### will start test_concurrent_operations[npo2_linear] ##### Oct 6 01:14:40 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 01:14:45 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear BjIfAlCTcF -q Oct 6 01:14:59 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear BjIfAlCTcF -q integritysetup close BjIfAlCTcF -q Oct 6 01:15:13 storageqe-109 journal: integritysetup close BjIfAlCTcF -q INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_concurrent_operations[npo2_linear] #### INFO: #### will start test_large_device_parameters[npo2_linear] ##### INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 6 01:15:28 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 6 01:15:28 storageqe-109 INFO: #### END test_concurrent_operations[npo2_linear] #### Oct 6 01:15:28 storageqe-109 INFO: #### will start test_large_device_parameters[npo2_linear] ##### Oct 6 01:15:28 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '4096' format /dev/sde -q Oct 6 01:15:35 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '4096' format /dev/sde -q Oct 6 01:17:43 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 01:17:43 storageqe-109 dnf[250057]: Updating Subscription Management repositories. Oct 6 01:17:43 storageqe-109 dnf[250057]: Unable to read consumer identity Oct 6 01:17:43 storageqe-109 dnf[250057]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 01:17:43 storageqe-109 dnf[250057]: beaker-AppStream 539 kB/s | 2.8 kB 00:00 Oct 6 01:17:43 storageqe-109 dnf[250057]: beaker-AppStream-debuginfo 487 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-BaseOS 931 kB/s | 2.7 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-BaseOS-debuginfo 383 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-CRB 718 kB/s | 2.7 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-CRB-debuginfo 608 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-HighAvailability 867 kB/s | 2.8 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-HighAvailability-debuginfo 665 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-NFV 859 kB/s | 2.7 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-NFV-debuginfo 529 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-RT 899 kB/s | 2.7 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-RT-debuginfo 235 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-SAP 728 kB/s | 2.7 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-SAP-debuginfo 433 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-SAPHANA 728 kB/s | 2.7 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: beaker-SAPHANA-debuginfo 510 kB/s | 1.5 kB 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 6 01:17:44 storageqe-109 dnf[250057]: Errors during downloading metadata for repository 'beaker-client': Oct 6 01:17:44 storageqe-109 dnf[250057]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 6 01:17:44 storageqe-109 dnf[250057]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 6 01:17:45 storageqe-109 dnf[250057]: beaker-harness 753 B/s | 1.3 kB 00:01 Oct 6 01:17:46 storageqe-109 dnf[250057]: Google Cloud CLI 4.8 kB/s | 1.4 kB 00:00 Oct 6 01:17:47 storageqe-109 dnf[250057]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 6 01:17:47 storageqe-109 dnf[250057]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 6 01:17:48 storageqe-109 dnf[250057]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 6 01:17:48 storageqe-109 dnf[250057]: Ignoring repositories: beaker-client Oct 6 01:17:48 storageqe-109 dnf[250057]: Metadata cache created. Oct 6 01:17:48 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 01:17:48 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 01:17:48 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 335ms CPU time, 82.1M memory peak. Oct 6 01:30:32 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 01:30:32 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 01:30:32 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. integritysetup --integrity 'crc32c' open /dev/sde gtHNxsXUkJ -q Oct 6 01:30:42 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/sde gtHNxsXUkJ -q integritysetup close gtHNxsXUkJ -q Oct 6 01:30:52 storageqe-109 journal: integritysetup close gtHNxsXUkJ -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/sdb -q Oct 6 01:31:05 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/sdb -q integritysetup --integrity 'sha256' open /dev/sdb boztxFukDV -q Oct 6 01:43:05 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/sdb boztxFukDV -q integritysetup close boztxFukDV -q Oct 6 01:43:16 storageqe-109 journal: integritysetup close boztxFukDV -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '1024' --integrity-key-file '/tmp/testfileqWQ' --integrity-key-size '32' format /dev/sdc -q Oct 6 01:43:28 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '1024' --integrity-key-file '/tmp/testfileqWQ' --integrity-key-size '32' format /dev/sdc -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqWQ' --integrity-key-size '32' open /dev/sdc XridNlYDHh -q Oct 6 01:55:52 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqWQ' --integrity-key-size '32' open /dev/sdc XridNlYDHh -q integritysetup close XridNlYDHh -q Oct 6 01:56:02 storageqe-109 journal: integritysetup close XridNlYDHh -q INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_large_device_parameters[npo2_linear] #### INFO: #### will start test_all_supported_sector_sizes[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 6 01:56:17 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 6 01:56:17 storageqe-109 INFO: #### END test_large_device_parameters[npo2_linear] #### Oct 6 01:56:17 storageqe-109 INFO: #### will start test_all_supported_sector_sizes[npo2_linear] ##### Oct 6 01:56:17 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 01:56:23 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear YaxLiudcte -q Oct 6 01:56:36 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear YaxLiudcte -q integritysetup status YaxLiudcte -q Oct 6 01:56:46 storageqe-109 journal: integritysetup status YaxLiudcte -q integritysetup close YaxLiudcte -q Oct 6 01:56:56 storageqe-109 journal: integritysetup close YaxLiudcte -q integritysetup --integrity 'sha1' --tag-size '20' --sector-size '1024' format /dev/mapper/npo2linear -q Oct 6 01:57:07 storageqe-109 journal: integritysetup --integrity 'sha1' --tag-size '20' --sector-size '1024' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear YNnAFKIycx -q Oct 6 01:57:22 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear YNnAFKIycx -q integritysetup status YNnAFKIycx -q Oct 6 01:57:32 storageqe-109 journal: integritysetup status YNnAFKIycx -q integritysetup close YNnAFKIycx -q Oct 6 01:57:42 storageqe-109 journal: integritysetup close YNnAFKIycx -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/mapper/npo2linear -q Oct 6 01:57:53 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear XpczARZDVH -q Oct 6 01:58:07 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear XpczARZDVH -q integritysetup status XpczARZDVH -q Oct 6 01:58:17 storageqe-109 journal: integritysetup status XpczARZDVH -q integritysetup close XpczARZDVH -q Oct 6 01:58:27 storageqe-109 journal: integritysetup close XpczARZDVH -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfilecNY' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 01:58:38 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfilecNY' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecNY' --integrity-key-size '32' open /dev/mapper/npo2linear dyKXRaPZkD -q Oct 6 01:58:52 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecNY' --integrity-key-size '32' open /dev/mapper/npo2linear dyKXRaPZkD -q integritysetup status dyKXRaPZkD -q Oct 6 01:59:02 storageqe-109 journal: integritysetup status dyKXRaPZkD -q integritysetup close dyKXRaPZkD -q Oct 6 01:59:12 storageqe-109 journal: integritysetup close dyKXRaPZkD -q INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_all_supported_sector_sizes[npo2_linear] #### INFO: #### will start test_recovery_mode_advanced[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 6 01:59:27 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 6 01:59:27 storageqe-109 INFO: #### END test_all_supported_sector_sizes[npo2_linear] #### Oct 6 01:59:27 storageqe-109 INFO: #### will start test_recovery_mode_advanced[npo2_linear] ##### Oct 6 01:59:28 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### integritysetup --integrity 'sha256' format /dev/mapper/npo2linear -q --no-wipe Oct 6 01:59:33 storageqe-109 journal: integritysetup --integrity 'sha256' format /dev/mapper/npo2linear -q --no-wipe integritysetup --integrity 'sha256' open /dev/mapper/npo2linear PTKCGbWfeQ -q --integrity-recovery-mode Oct 6 01:59:43 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear PTKCGbWfeQ -q --integrity-recovery-mode integritysetup status PTKCGbWfeQ -q Oct 6 01:59:53 storageqe-109 journal: integritysetup status PTKCGbWfeQ -q integritysetup close PTKCGbWfeQ -q Oct 6 02:00:03 storageqe-109 journal: integritysetup close PTKCGbWfeQ -q INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_recovery_mode_advanced[npo2_linear] #### Oct 6 02:00:18 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 6 02:00:18 storageqe-109 INFO: #### END test_recovery_mode_advanced[npo2_linear] #### Oct 6 02:00:19 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:00:20 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 02:00:20 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 02:00:20 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 02:00:20 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 02:00:31 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_signature_verification_basic[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:00:37 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:00:37 storageqe-109 INFO: #### will start test_signature_verification_basic[npo2_linear] ##### Oct 6 02:00:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 Oct 6 02:00:42 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 6 02:00:42 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 Oct 6 02:00:50 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. veritysetup verify /dev/mapper/npo2linear /dev/loop0 c614d5553d2633c547d06f572a4eedb6a493f22597c31d3f15bafd2b2d98e7d2 /tmp/verity_certs/signature.sig Oct 6 02:00:57 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop0 c614d5553d2633c547d06f572a4eedb6a493f22597c31d3f15bafd2b2d98e7d2 /tmp/verity_certs/signature.sig INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_verification_basic[npo2_linear] #### INFO: #### will start test_signature_verification_invalid[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:01:17 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:01:17 storageqe-109 INFO: #### END test_signature_verification_basic[npo2_linear] #### Oct 6 02:01:17 storageqe-109 INFO: #### will start test_signature_verification_invalid[npo2_linear] ##### Oct 6 02:01:17 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop1 Oct 6 02:01:22 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 6 02:01:22 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop1 veritysetup verify /dev/mapper/npo2linear /dev/loop1 ca3a431499c6dfd219252c988a234f3b7b18692519799a744e15b8dde52a7d1f /tmp/verity_certs/signature.sig Oct 6 02:01:37 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop1 ca3a431499c6dfd219252c988a234f3b7b18692519799a744e15b8dde52a7d1f /tmp/verity_certs/signature.sig INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_verification_invalid[npo2_linear] #### INFO: #### will start test_signature_keyring_integration[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:02:02 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:02:02 storageqe-109 INFO: #### END test_signature_verification_invalid[npo2_linear] #### Oct 6 02:02:02 storageqe-109 INFO: #### will start test_signature_keyring_integration[npo2_linear] ##### Oct 6 02:02:03 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop2 Oct 6 02:02:08 storageqe-109 kernel: loop2: detected capacity change from 0 to 12582912 Oct 6 02:02:08 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop2 veritysetup verify /dev/mapper/npo2linear /dev/loop2 9f68e820072bea7bc4c1186f1c641f42ddf9b1bd93fb001623584c030ca315d9 /tmp/verity_certs/signature.sig verity_test Oct 6 02:02:23 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop2 9f68e820072bea7bc4c1186f1c641f42ddf9b1bd93fb001623584c030ca315d9 /tmp/verity_certs/signature.sig verity_test INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_keyring_integration[npo2_linear] #### INFO: #### will start test_signature_multiple_algorithms[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:02:43 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:02:43 storageqe-109 INFO: #### END test_signature_keyring_integration[npo2_linear] #### Oct 6 02:02:43 storageqe-109 INFO: #### will start test_signature_multiple_algorithms[npo2_linear] ##### Oct 6 02:02:43 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop3 Oct 6 02:02:48 storageqe-109 kernel: loop3: detected capacity change from 0 to 12582912 Oct 6 02:02:48 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop3 veritysetup verify /dev/mapper/npo2linear /dev/loop3 f86552179de1fd55e002f9aec95e8080dadc2dd2aa900bbf91829097dfcc7304 /tmp/verity_certs/signature.sig Oct 6 02:03:03 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop3 f86552179de1fd55e002f9aec95e8080dadc2dd2aa900bbf91829097dfcc7304 /tmp/verity_certs/signature.sig veritysetup --hash 'sha512' format /dev/mapper/npo2linear /dev/loop4 Oct 6 02:03:18 storageqe-109 kernel: loop4: detected capacity change from 0 to 12582912 Oct 6 02:03:18 storageqe-109 journal: veritysetup --hash 'sha512' format /dev/mapper/npo2linear /dev/loop4 veritysetup verify /dev/mapper/npo2linear /dev/loop4 4710ecbd5fbc4e6f96c9fe60dc1d06769d253b644f9b6dcc5ee64b337bb05de23c4677fbd514f0511e50f969db5f3cad11ffb46d577e40582e8e55976e841b91 /tmp/verity_certs/signature.sig Oct 6 02:03:38 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop4 4710ecbd5fbc4e6f96c9fe60dc1d06769d253b644f9b6dcc5ee64b337bb05de23c4677fbd514f0511e50f969db5f3cad11ffb46d577e40582e8e55976e841b91 /tmp/verity_certs/signature.sig veritysetup --hash 'sha1' format /dev/mapper/npo2linear /dev/loop5 Oct 6 02:03:58 storageqe-109 kernel: loop5: detected capacity change from 0 to 12582912 Oct 6 02:03:58 storageqe-109 journal: veritysetup --hash 'sha1' format /dev/mapper/npo2linear /dev/loop5 veritysetup verify /dev/mapper/npo2linear /dev/loop5 6933721eec5c0842a98f6e403bb4d6f99fde79ae /tmp/verity_certs/signature.sig Oct 6 02:04:12 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop5 6933721eec5c0842a98f6e403bb4d6f99fde79ae /tmp/verity_certs/signature.sig INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_multiple_algorithms[npo2_linear] #### INFO: #### will start test_signature_enforcement_module_param[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:04:32 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:04:32 storageqe-109 INFO: #### END test_signature_multiple_algorithms[npo2_linear] #### Oct 6 02:04:32 storageqe-109 INFO: #### will start test_signature_enforcement_module_param[npo2_linear] ##### Oct 6 02:04:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop6 Oct 6 02:04:37 storageqe-109 kernel: loop6: detected capacity change from 0 to 12582912 Oct 6 02:04:37 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop6 veritysetup create BoiuyXEzPL /dev/mapper/npo2linear /dev/loop6 f071936144e3737a573b02b2c1f63b7cef457813b71529263451b0bca3c4c3e3 Oct 6 02:04:53 storageqe-109 journal: veritysetup create BoiuyXEzPL /dev/mapper/npo2linear /dev/loop6 f071936144e3737a573b02b2c1f63b7cef457813b71529263451b0bca3c4c3e3 Oct 6 02:04:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BoiuyXEzPL Oct 6 02:05:03 storageqe-109 journal: veritysetup close BoiuyXEzPL INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_enforcement_module_param[npo2_linear] #### INFO: #### will start test_signature_platform_keyring[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:05:18 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:05:18 storageqe-109 INFO: #### END test_signature_enforcement_module_param[npo2_linear] #### Oct 6 02:05:18 storageqe-109 INFO: #### will start test_signature_platform_keyring[npo2_linear] ##### Oct 6 02:05:18 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_platform_keyring[npo2_linear] #### Oct 6 02:05:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:05:28 storageqe-109 INFO: #### END test_signature_platform_keyring[npo2_linear] #### Oct 6 02:05:29 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:05:30 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 02:05:30 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 02:05:30 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 02:05:30 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 02:05:41 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_dm_crypt_module_parameters[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:05:46 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:05:46 storageqe-109 INFO: #### will start test_dm_crypt_module_parameters[npo2_linear] ##### Oct 6 02:05:46 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 02:05:52 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 02:05:52 storageqe-109 stratisd[4947]: [2025-10-06T06:05:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:05:52 storageqe-109 stratisd[4947]: [2025-10-06T06:05:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:06:00 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/mapper/npo2linear hxrMIlZvjO -q Oct 6 02:06:02 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear hxrMIlZvjO -q Oct 6 02:06:02 storageqe-109 stratisd[4947]: [2025-10-06T06:06:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:06:02 storageqe-109 stratisd[4947]: [2025-10-06T06:06:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs xfs in remove_crypt Oct 6 02:06:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.v94_7l_cmount_test with fs xfs Oct 6 02:06:22 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b5021c47-fbdb-4f77-a556-4ec3ed3af9dd Oct 6 02:06:22 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 02:06:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v94_7l_cmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext4 in remove_crypt Oct 6 02:06:27 storageqe-109 systemd[1]: tmp-libblockdev.v94_7l_cmount_test.mount: Deactivated successfully. Oct 6 02:06:27 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b5021c47-fbdb-4f77-a556-4ec3ed3af9dd Oct 6 02:06:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs xfs in remove_crypt Oct 6 02:06:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0ub35t23mount_test with fs ext4 Oct 6 02:06:37 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8dd7610b-6183-4d2a-b032-6eef0bbb9f46 r/w with ordered data mode. Quota mode: none. Oct 6 02:06:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0ub35t23mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext3 in remove_crypt Oct 6 02:06:42 storageqe-109 systemd[1]: tmp-libblockdev.0ub35t23mount_test.mount: Deactivated successfully. Oct 6 02:06:42 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8dd7610b-6183-4d2a-b032-6eef0bbb9f46. Oct 6 02:06:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext4 in remove_crypt Oct 6 02:06:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cui6eb1smount_test with fs ext3 Oct 6 02:06:52 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 02:06:52 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dde4d478-19c5-4288-a1f9-145cc1b5a706 r/w with ordered data mode. Quota mode: none. Oct 6 02:06:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cui6eb1smount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext2 in remove_crypt Oct 6 02:06:57 storageqe-109 systemd[1]: tmp-libblockdev.cui6eb1smount_test.mount: Deactivated successfully. Oct 6 02:06:57 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dde4d478-19c5-4288-a1f9-145cc1b5a706. Oct 6 02:06:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext3 in remove_crypt Oct 6 02:06:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8wsiv0rfmount_test with fs ext2 Oct 6 02:07:07 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 02:07:07 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 355a4048-19a8-4c8f-97f0-f7b438018fc1 r/w without journal. Quota mode: none. Oct 6 02:07:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8wsiv0rfmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext2 in remove_crypt INFO: remove crypt device hxrMIlZvjO INFO: finishe the remove crypt device hxrMIlZvjO Oct 6 02:07:12 storageqe-109 systemd[1]: tmp-libblockdev.8wsiv0rfmount_test.mount: Deactivated successfully. Oct 6 02:07:12 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 355a4048-19a8-4c8f-97f0-f7b438018fc1. Oct 6 02:07:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hxrMIlZvjO and fs ext2 in remove_crypt Oct 6 02:07:12 storageqe-109 INFO: remove crypt device hxrMIlZvjO Oct 6 02:07:12 storageqe-109 INFO: finishe the remove crypt device hxrMIlZvjO INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_crypt_module_parameters[npo2_linear] #### INFO: #### will start test_dm_verity_loadpin_integration[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:07:17 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:07:17 storageqe-109 INFO: #### END test_dm_crypt_module_parameters[npo2_linear] #### Oct 6 02:07:17 storageqe-109 INFO: #### will start test_dm_verity_loadpin_integration[npo2_linear] ##### Oct 6 02:07:17 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 Oct 6 02:07:22 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 6 02:07:22 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 veritysetup create sRCYvknzZm /dev/mapper/npo2linear /dev/loop0 d607e838aab0cf0163b9f81214a2c771bce9e6ad94388fa92bcc62ea7145948a Oct 6 02:07:38 storageqe-109 journal: veritysetup create sRCYvknzZm /dev/mapper/npo2linear /dev/loop0 d607e838aab0cf0163b9f81214a2c771bce9e6ad94388fa92bcc62ea7145948a Oct 6 02:07:38 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close sRCYvknzZm Oct 6 02:07:48 storageqe-109 journal: veritysetup close sRCYvknzZm INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_loadpin_integration[npo2_linear] #### INFO: #### will start test_memory_pressure_scenarios[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:08:03 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:08:03 storageqe-109 INFO: #### END test_dm_verity_loadpin_integration[npo2_linear] #### Oct 6 02:08:03 storageqe-109 INFO: #### will start test_memory_pressure_scenarios[npo2_linear] ##### Oct 6 02:08:03 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 02:08:08 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 02:08:08 storageqe-109 stratisd[4947]: [2025-10-06T06:08:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:08:08 storageqe-109 stratisd[4947]: [2025-10-06T06:08:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear OIftSCBdyg -q Oct 6 02:08:18 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear OIftSCBdyg -q Oct 6 02:08:18 storageqe-109 stratisd[4947]: [2025-10-06T06:08:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:08:18 storageqe-109 stratisd[4947]: [2025-10-06T06:08:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs xfs in remove_crypt Oct 6 02:08:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.y_tdm6w9mount_test with fs xfs Oct 6 02:08:38 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f1a1bc9c-d340-4039-944d-3e12ace02b64 Oct 6 02:08:38 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 02:08:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y_tdm6w9mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext4 in remove_crypt Oct 6 02:08:43 storageqe-109 systemd[1]: tmp-libblockdev.y_tdm6w9mount_test.mount: Deactivated successfully. Oct 6 02:08:43 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f1a1bc9c-d340-4039-944d-3e12ace02b64 Oct 6 02:08:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs xfs in remove_crypt Oct 6 02:08:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.aaptqkr7mount_test with fs ext4 Oct 6 02:08:53 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8c11825a-7250-4bbd-9683-a9cbda80ab0d r/w with ordered data mode. Quota mode: none. Oct 6 02:08:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.aaptqkr7mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext3 in remove_crypt Oct 6 02:08:58 storageqe-109 systemd[1]: tmp-libblockdev.aaptqkr7mount_test.mount: Deactivated successfully. Oct 6 02:08:58 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8c11825a-7250-4bbd-9683-a9cbda80ab0d. Oct 6 02:08:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext4 in remove_crypt Oct 6 02:08:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.u8udnvyzmount_test with fs ext3 Oct 6 02:09:08 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 02:09:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6ee50eaa-36d6-410a-b969-0b3dc86d73d0 r/w with ordered data mode. Quota mode: none. Oct 6 02:09:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u8udnvyzmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext2 in remove_crypt Oct 6 02:09:13 storageqe-109 systemd[1]: tmp-libblockdev.u8udnvyzmount_test.mount: Deactivated successfully. Oct 6 02:09:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6ee50eaa-36d6-410a-b969-0b3dc86d73d0. Oct 6 02:09:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext3 in remove_crypt Oct 6 02:09:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p1b55qxzmount_test with fs ext2 Oct 6 02:09:23 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 02:09:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 91939d55-dba5-4335-9607-5d8d2ec7185f r/w without journal. Quota mode: none. Oct 6 02:09:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p1b55qxzmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext2 in remove_crypt INFO: remove crypt device OIftSCBdyg INFO: finishe the remove crypt device OIftSCBdyg Oct 6 02:09:28 storageqe-109 systemd[1]: tmp-libblockdev.p1b55qxzmount_test.mount: Deactivated successfully. Oct 6 02:09:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 91939d55-dba5-4335-9607-5d8d2ec7185f. Oct 6 02:09:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OIftSCBdyg and fs ext2 in remove_crypt Oct 6 02:09:28 storageqe-109 INFO: remove crypt device OIftSCBdyg Oct 6 02:09:28 storageqe-109 INFO: finishe the remove crypt device OIftSCBdyg INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_memory_pressure_scenarios[npo2_linear] #### INFO: #### will start test_io_error_injection[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:09:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:09:33 storageqe-109 INFO: #### END test_memory_pressure_scenarios[npo2_linear] #### Oct 6 02:09:33 storageqe-109 INFO: #### will start test_io_error_injection[npo2_linear] ##### Oct 6 02:09:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/aLpUXGbQWv -q Oct 6 02:09:38 storageqe-109 stratisd[4947]: [2025-10-06T06:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:09:38 storageqe-109 stratisd[4947]: [2025-10-06T06:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:09:38 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/aLpUXGbQWv -q Oct 6 02:09:38 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 02:09:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, lost async page write Oct 6 02:09:38 storageqe-109 stratisd[4947]: [2025-10-06T06:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:09:38 storageqe-109 stratisd[4947]: [2025-10-06T06:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:09:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, lost async page write Oct 6 02:09:38 storageqe-109 stratisd[4947]: [2025-10-06T06:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:09:38 storageqe-109 stratisd[4947]: [2025-10-06T06:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_io_error_injection[npo2_linear] #### INFO: #### will start test_device_removal_scenarios[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:09:43 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:09:43 storageqe-109 INFO: #### END test_io_error_injection[npo2_linear] #### Oct 6 02:09:43 storageqe-109 INFO: #### will start test_device_removal_scenarios[npo2_linear] ##### Oct 6 02:09:43 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q Oct 6 02:09:48 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 6 02:09:48 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q Oct 6 02:09:49 storageqe-109 stratisd[4947]: [2025-10-06T06:09:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:09:49 storageqe-109 stratisd[4947]: [2025-10-06T06:09:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/loop1 eiONtRxDds -q Oct 6 02:09:59 storageqe-109 journal: cryptsetup open /dev/loop1 eiONtRxDds -q Oct 6 02:09:59 storageqe-109 stratisd[4947]: [2025-10-06T06:09:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:09:59 storageqe-109 stratisd[4947]: [2025-10-06T06:09:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status eiONtRxDds -q Oct 6 02:10:09 storageqe-109 journal: cryptsetup status eiONtRxDds -q Oct 6 02:10:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1568752, async page read INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_device_removal_scenarios[npo2_linear] #### INFO: #### will start test_concurrent_device_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:10:24 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:10:24 storageqe-109 INFO: #### END test_device_removal_scenarios[npo2_linear] #### Oct 6 02:10:24 storageqe-109 INFO: #### will start test_concurrent_device_operations[npo2_linear] ##### Oct 6 02:10:24 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop4 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop2 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop3 -q Oct 6 02:10:29 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 6 02:10:29 storageqe-109 kernel: loop2: detected capacity change from 0 to 12582912 Oct 6 02:10:29 storageqe-109 kernel: loop3: detected capacity change from 0 to 12582912 Oct 6 02:10:29 storageqe-109 kernel: loop4: detected capacity change from 0 to 12582912 Oct 6 02:10:29 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop2 -q Oct 6 02:10:29 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop3 -q Oct 6 02:10:29 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q Oct 6 02:10:29 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop4 -q Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:29 storageqe-109 stratisd[4947]: [2025-10-06T06:10:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/loop1 LlDyZfqdYh -q cryptsetup open /dev/loop4 wkhtsdILmx -q cryptsetup open /dev/loop2 ktogYMBnbp -q Oct 6 02:10:39 storageqe-109 journal: cryptsetup open /dev/loop1 LlDyZfqdYh -q Oct 6 02:10:39 storageqe-109 journal: cryptsetup open /dev/loop4 wkhtsdILmx -q Oct 6 02:10:39 storageqe-109 journal: cryptsetup open /dev/loop2 ktogYMBnbp -q Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/loop3 IUTEZteSlR -q Oct 6 02:10:39 storageqe-109 journal: cryptsetup open /dev/loop3 IUTEZteSlR -q Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:39 storageqe-109 stratisd[4947]: [2025-10-06T06:10:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_device_operations[npo2_linear] #### Oct 6 02:10:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:10:54 storageqe-109 INFO: #### END test_concurrent_device_operations[npo2_linear] #### Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:54 storageqe-109 stratisd[4947]: [2025-10-06T06:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:10:55 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:10:56 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 02:10:57 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 02:10:57 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 02:10:57 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 02:11:07 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_luks[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:11:13 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:11:13 storageqe-109 INFO: #### will start test_luks[npo2_linear] ##### Oct 6 02:11:13 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 02:11:18 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 02:11:21 storageqe-109 kernel: perf: interrupt took too long (3979 > 3972), lowering kernel.perf_event_max_sample_rate to 50000 Oct 6 02:11:25 storageqe-109 stratisd[4947]: [2025-10-06T06:11:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:11:25 storageqe-109 stratisd[4947]: [2025-10-06T06:11:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:11:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --key-description 'mykey' --token-id '10' token add /dev/mapper/npo2linear -q Oct 6 02:11:35 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '10' token add /dev/mapper/npo2linear -q Oct 6 02:11:35 storageqe-109 stratisd[4947]: [2025-10-06T06:11:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:11:35 storageqe-109 stratisd[4947]: [2025-10-06T06:11:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GeKv -q --allow-discards --token-only --token-id 10 cryptsetup --type 'luks2' open /dev/mapper/npo2linear GeKv -q --allow-discards --token-only Oct 6 02:11:45 storageqe-109 stratisd[4947]: [2025-10-06T06:11:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:11:45 storageqe-109 stratisd[4947]: [2025-10-06T06:11:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:11:45 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GeKv -q --allow-discards --token-only --token-id 10 Oct 6 02:11:45 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GeKv -q --allow-discards --token-only INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks[npo2_linear] #### INFO: #### will start test_luks_bz2003748[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:11:51 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:11:51 storageqe-109 INFO: #### END test_luks[npo2_linear] #### Oct 6 02:11:51 storageqe-109 INFO: #### will start test_luks_bz2003748[npo2_linear] ##### Oct 6 02:11:51 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/mapper/npo2linear -q Oct 6 02:11:56 storageqe-109 journal: cryptsetup erase /dev/mapper/npo2linear -q Oct 6 02:11:56 storageqe-109 stratisd[4947]: [2025-10-06T06:11:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:11:56 storageqe-109 stratisd[4947]: [2025-10-06T06:11:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '32m' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 02:12:06 storageqe-109 journal: cryptsetup --reduce-device-size '32m' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 02:12:15 storageqe-109 stratisd[4947]: [2025-10-06T06:12:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:12:15 storageqe-109 stratisd[4947]: [2025-10-06T06:12:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:12:20 storageqe-109 stratisd[4947]: [2025-10-06T06:12:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:12:20 storageqe-109 stratisd[4947]: [2025-10-06T06:12:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --header 'key1-key2' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 6 02:12:30 storageqe-109 journal: cryptsetup --header 'key1-key2' reencrypt /dev/mapper/npo2linear -q --decrypt INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz2003748[npo2_linear] #### INFO: #### will start test_luks_paramter[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:12:55 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:12:55 storageqe-109 INFO: #### END test_luks_bz2003748[npo2_linear] #### Oct 6 02:12:55 storageqe-109 INFO: #### will start test_luks_paramter[npo2_linear] ##### Oct 6 02:12:55 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:13:00 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:13:02 storageqe-109 stratisd[4947]: [2025-10-06T06:13:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:02 storageqe-109 stratisd[4947]: [2025-10-06T06:13:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:13:12 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:13:13 storageqe-109 stratisd[4947]: [2025-10-06T06:13:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:13 storageqe-109 stratisd[4947]: [2025-10-06T06:13:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:13:23 storageqe-109 stratisd[4947]: [2025-10-06T06:13:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:23 storageqe-109 stratisd[4947]: [2025-10-06T06:13:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:23 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:13:23 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:13:23 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:13:25 storageqe-109 stratisd[4947]: [2025-10-06T06:13:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:25 storageqe-109 stratisd[4947]: [2025-10-06T06:13:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:13:35 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:13:36 storageqe-109 stratisd[4947]: [2025-10-06T06:13:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:36 storageqe-109 stratisd[4947]: [2025-10-06T06:13:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:13:46 storageqe-109 stratisd[4947]: [2025-10-06T06:13:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:46 storageqe-109 stratisd[4947]: [2025-10-06T06:13:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:46 storageqe-109 stratisd[4947]: [2025-10-06T06:13:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:46 storageqe-109 stratisd[4947]: [2025-10-06T06:13:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:13:46 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:13:46 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:13:46 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:15:11 storageqe-109 stratisd[4947]: [2025-10-06T06:15:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:15:11 storageqe-109 stratisd[4947]: [2025-10-06T06:15:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:15:21 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:15:51 storageqe-109 stratisd[4947]: [2025-10-06T06:15:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:15:51 storageqe-109 stratisd[4947]: [2025-10-06T06:15:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:16:32 storageqe-109 stratisd[4947]: [2025-10-06T06:16:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:16:32 storageqe-109 stratisd[4947]: [2025-10-06T06:16:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:16:32 storageqe-109 stratisd[4947]: [2025-10-06T06:16:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:16:32 storageqe-109 stratisd[4947]: [2025-10-06T06:16:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:16:32 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:16:32 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:16:32 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:17:57 storageqe-109 stratisd[4947]: [2025-10-06T06:17:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:17:57 storageqe-109 stratisd[4947]: [2025-10-06T06:17:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:18:07 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:18:37 storageqe-109 stratisd[4947]: [2025-10-06T06:18:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:18:37 storageqe-109 stratisd[4947]: [2025-10-06T06:18:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:19:17 storageqe-109 stratisd[4947]: [2025-10-06T06:19:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:17 storageqe-109 stratisd[4947]: [2025-10-06T06:19:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:17 storageqe-109 stratisd[4947]: [2025-10-06T06:19:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:17 storageqe-109 stratisd[4947]: [2025-10-06T06:19:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:17 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:19:17 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:19:17 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:19:20 storageqe-109 stratisd[4947]: [2025-10-06T06:19:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:20 storageqe-109 stratisd[4947]: [2025-10-06T06:19:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:19:30 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:19:30 storageqe-109 stratisd[4947]: [2025-10-06T06:19:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:30 storageqe-109 stratisd[4947]: [2025-10-06T06:19:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:30 storageqe-109 kernel: alg: No test for essiv(cbc(aes),sha3-256) (essiv(cbc-aes-aesni,sha3-256-generic)) INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:19:40 storageqe-109 stratisd[4947]: [2025-10-06T06:19:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:40 storageqe-109 stratisd[4947]: [2025-10-06T06:19:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:40 storageqe-109 stratisd[4947]: [2025-10-06T06:19:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:40 storageqe-109 stratisd[4947]: [2025-10-06T06:19:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:40 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:19:40 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:19:40 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:19:43 storageqe-109 stratisd[4947]: [2025-10-06T06:19:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:43 storageqe-109 stratisd[4947]: [2025-10-06T06:19:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:19:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:19:53 storageqe-109 stratisd[4947]: [2025-10-06T06:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:19:53 storageqe-109 stratisd[4947]: [2025-10-06T06:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:20:03 storageqe-109 stratisd[4947]: [2025-10-06T06:20:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:20:03 storageqe-109 stratisd[4947]: [2025-10-06T06:20:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:20:03 storageqe-109 stratisd[4947]: [2025-10-06T06:20:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:20:03 storageqe-109 stratisd[4947]: [2025-10-06T06:20:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:20:03 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:20:03 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:20:03 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:21:29 storageqe-109 stratisd[4947]: [2025-10-06T06:21:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:21:29 storageqe-109 stratisd[4947]: [2025-10-06T06:21:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:21:39 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:22:09 storageqe-109 stratisd[4947]: [2025-10-06T06:22:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:22:09 storageqe-109 stratisd[4947]: [2025-10-06T06:22:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:22:49 storageqe-109 stratisd[4947]: [2025-10-06T06:22:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:22:49 storageqe-109 stratisd[4947]: [2025-10-06T06:22:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:22:49 storageqe-109 stratisd[4947]: [2025-10-06T06:22:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:22:49 storageqe-109 stratisd[4947]: [2025-10-06T06:22:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:22:49 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:22:49 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:22:49 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:24:14 storageqe-109 stratisd[4947]: [2025-10-06T06:24:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:24:14 storageqe-109 stratisd[4947]: [2025-10-06T06:24:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:24:24 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:24:55 storageqe-109 stratisd[4947]: [2025-10-06T06:24:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:24:55 storageqe-109 stratisd[4947]: [2025-10-06T06:24:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:25:35 storageqe-109 stratisd[4947]: [2025-10-06T06:25:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:35 storageqe-109 stratisd[4947]: [2025-10-06T06:25:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:35 storageqe-109 stratisd[4947]: [2025-10-06T06:25:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:35 storageqe-109 stratisd[4947]: [2025-10-06T06:25:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:35 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:25:35 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:25:35 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:25:37 storageqe-109 stratisd[4947]: [2025-10-06T06:25:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:37 storageqe-109 stratisd[4947]: [2025-10-06T06:25:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:25:47 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:25:47 storageqe-109 stratisd[4947]: [2025-10-06T06:25:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:47 storageqe-109 stratisd[4947]: [2025-10-06T06:25:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:58 storageqe-109 stratisd[4947]: [2025-10-06T06:25:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:58 storageqe-109 stratisd[4947]: [2025-10-06T06:25:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:58 storageqe-109 stratisd[4947]: [2025-10-06T06:25:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:25:58 storageqe-109 stratisd[4947]: [2025-10-06T06:25:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:25:58 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:25:58 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:25:58 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:26:00 storageqe-109 stratisd[4947]: [2025-10-06T06:26:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:26:00 storageqe-109 stratisd[4947]: [2025-10-06T06:26:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:26:10 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:26:10 storageqe-109 stratisd[4947]: [2025-10-06T06:26:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:26:10 storageqe-109 stratisd[4947]: [2025-10-06T06:26:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:26:21 storageqe-109 stratisd[4947]: [2025-10-06T06:26:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:26:21 storageqe-109 stratisd[4947]: [2025-10-06T06:26:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:26:21 storageqe-109 stratisd[4947]: [2025-10-06T06:26:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:26:21 storageqe-109 stratisd[4947]: [2025-10-06T06:26:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:26:21 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:26:21 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:26:21 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:27:46 storageqe-109 stratisd[4947]: [2025-10-06T06:27:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:27:46 storageqe-109 stratisd[4947]: [2025-10-06T06:27:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:27:56 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:28:26 storageqe-109 stratisd[4947]: [2025-10-06T06:28:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:28:26 storageqe-109 stratisd[4947]: [2025-10-06T06:28:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:29:06 storageqe-109 stratisd[4947]: [2025-10-06T06:29:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:29:06 storageqe-109 stratisd[4947]: [2025-10-06T06:29:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:29:06 storageqe-109 stratisd[4947]: [2025-10-06T06:29:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:29:06 storageqe-109 stratisd[4947]: [2025-10-06T06:29:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:29:06 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:29:06 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:29:07 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:30:25 storageqe-109 kernel: perf: interrupt took too long (4982 > 4973), lowering kernel.perf_event_max_sample_rate to 40000 Oct 6 02:30:32 storageqe-109 stratisd[4947]: [2025-10-06T06:30:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:30:32 storageqe-109 stratisd[4947]: [2025-10-06T06:30:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:30:42 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:31:12 storageqe-109 stratisd[4947]: [2025-10-06T06:31:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:31:12 storageqe-109 stratisd[4947]: [2025-10-06T06:31:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:31:52 storageqe-109 stratisd[4947]: [2025-10-06T06:31:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:31:52 storageqe-109 stratisd[4947]: [2025-10-06T06:31:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:31:52 storageqe-109 stratisd[4947]: [2025-10-06T06:31:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:31:52 storageqe-109 stratisd[4947]: [2025-10-06T06:31:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:31:52 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:31:52 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:31:52 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:31:55 storageqe-109 stratisd[4947]: [2025-10-06T06:31:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:31:55 storageqe-109 stratisd[4947]: [2025-10-06T06:31:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:32:05 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:32:05 storageqe-109 stratisd[4947]: [2025-10-06T06:32:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:05 storageqe-109 stratisd[4947]: [2025-10-06T06:32:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:32:15 storageqe-109 stratisd[4947]: [2025-10-06T06:32:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:15 storageqe-109 stratisd[4947]: [2025-10-06T06:32:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:15 storageqe-109 stratisd[4947]: [2025-10-06T06:32:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:15 storageqe-109 stratisd[4947]: [2025-10-06T06:32:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:15 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:32:15 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:32:15 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:32:18 storageqe-109 stratisd[4947]: [2025-10-06T06:32:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:18 storageqe-109 stratisd[4947]: [2025-10-06T06:32:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:32:28 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:32:28 storageqe-109 stratisd[4947]: [2025-10-06T06:32:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:28 storageqe-109 stratisd[4947]: [2025-10-06T06:32:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:32:38 storageqe-109 stratisd[4947]: [2025-10-06T06:32:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:38 storageqe-109 stratisd[4947]: [2025-10-06T06:32:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:38 storageqe-109 stratisd[4947]: [2025-10-06T06:32:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:38 storageqe-109 stratisd[4947]: [2025-10-06T06:32:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:32:38 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:32:38 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:32:38 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:34:04 storageqe-109 stratisd[4947]: [2025-10-06T06:34:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:34:04 storageqe-109 stratisd[4947]: [2025-10-06T06:34:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:34:14 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:34:44 storageqe-109 stratisd[4947]: [2025-10-06T06:34:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:34:44 storageqe-109 stratisd[4947]: [2025-10-06T06:34:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:35:24 storageqe-109 stratisd[4947]: [2025-10-06T06:35:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:35:24 storageqe-109 stratisd[4947]: [2025-10-06T06:35:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:35:24 storageqe-109 stratisd[4947]: [2025-10-06T06:35:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:35:24 storageqe-109 stratisd[4947]: [2025-10-06T06:35:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:35:24 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:35:24 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:35:24 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:36:49 storageqe-109 stratisd[4947]: [2025-10-06T06:36:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:36:49 storageqe-109 stratisd[4947]: [2025-10-06T06:36:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:36:59 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:37:29 storageqe-109 stratisd[4947]: [2025-10-06T06:37:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:37:29 storageqe-109 stratisd[4947]: [2025-10-06T06:37:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:38:10 storageqe-109 stratisd[4947]: [2025-10-06T06:38:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:10 storageqe-109 stratisd[4947]: [2025-10-06T06:38:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:10 storageqe-109 stratisd[4947]: [2025-10-06T06:38:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:10 storageqe-109 stratisd[4947]: [2025-10-06T06:38:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:10 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:38:10 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:38:10 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:38:12 storageqe-109 stratisd[4947]: [2025-10-06T06:38:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:12 storageqe-109 stratisd[4947]: [2025-10-06T06:38:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:38:22 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:38:22 storageqe-109 stratisd[4947]: [2025-10-06T06:38:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:22 storageqe-109 stratisd[4947]: [2025-10-06T06:38:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:38:33 storageqe-109 stratisd[4947]: [2025-10-06T06:38:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:33 storageqe-109 stratisd[4947]: [2025-10-06T06:38:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:33 storageqe-109 stratisd[4947]: [2025-10-06T06:38:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:33 storageqe-109 stratisd[4947]: [2025-10-06T06:38:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:33 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:38:33 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:38:33 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:38:35 storageqe-109 stratisd[4947]: [2025-10-06T06:38:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:35 storageqe-109 stratisd[4947]: [2025-10-06T06:38:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:38:45 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:38:45 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 02:38:45 storageqe-109 stratisd[4947]: [2025-10-06T06:38:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:45 storageqe-109 stratisd[4947]: [2025-10-06T06:38:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:45 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 02:38:45 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:38:56 storageqe-109 stratisd[4947]: [2025-10-06T06:38:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:56 storageqe-109 stratisd[4947]: [2025-10-06T06:38:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:56 storageqe-109 stratisd[4947]: [2025-10-06T06:38:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:56 storageqe-109 stratisd[4947]: [2025-10-06T06:38:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:38:56 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:38:56 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:38:56 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:40:20 storageqe-109 stratisd[4947]: [2025-10-06T06:40:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:40:20 storageqe-109 stratisd[4947]: [2025-10-06T06:40:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:40:30 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:41:00 storageqe-109 stratisd[4947]: [2025-10-06T06:41:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:41:00 storageqe-109 stratisd[4947]: [2025-10-06T06:41:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:41:41 storageqe-109 stratisd[4947]: [2025-10-06T06:41:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:41:41 storageqe-109 stratisd[4947]: [2025-10-06T06:41:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:41:41 storageqe-109 stratisd[4947]: [2025-10-06T06:41:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:41:41 storageqe-109 stratisd[4947]: [2025-10-06T06:41:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:41:41 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:41:41 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:41:41 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:43:06 storageqe-109 stratisd[4947]: [2025-10-06T06:43:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:43:06 storageqe-109 stratisd[4947]: [2025-10-06T06:43:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:43:16 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:43:46 storageqe-109 stratisd[4947]: [2025-10-06T06:43:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:43:46 storageqe-109 stratisd[4947]: [2025-10-06T06:43:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:44:26 storageqe-109 stratisd[4947]: [2025-10-06T06:44:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:26 storageqe-109 stratisd[4947]: [2025-10-06T06:44:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:26 storageqe-109 stratisd[4947]: [2025-10-06T06:44:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:26 storageqe-109 stratisd[4947]: [2025-10-06T06:44:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:26 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:44:26 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:44:26 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:44:28 storageqe-109 stratisd[4947]: [2025-10-06T06:44:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:28 storageqe-109 stratisd[4947]: [2025-10-06T06:44:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:44:38 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:44:38 storageqe-109 stratisd[4947]: [2025-10-06T06:44:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:38 storageqe-109 stratisd[4947]: [2025-10-06T06:44:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:44:48 storageqe-109 stratisd[4947]: [2025-10-06T06:44:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:48 storageqe-109 stratisd[4947]: [2025-10-06T06:44:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:48 storageqe-109 stratisd[4947]: [2025-10-06T06:44:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:48 storageqe-109 stratisd[4947]: [2025-10-06T06:44:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:48 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:44:49 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:44:49 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:44:51 storageqe-109 stratisd[4947]: [2025-10-06T06:44:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:44:51 storageqe-109 stratisd[4947]: [2025-10-06T06:44:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:45:01 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:45:01 storageqe-109 stratisd[4947]: [2025-10-06T06:45:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:45:01 storageqe-109 stratisd[4947]: [2025-10-06T06:45:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:45:11 storageqe-109 stratisd[4947]: [2025-10-06T06:45:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:45:11 storageqe-109 stratisd[4947]: [2025-10-06T06:45:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:45:11 storageqe-109 stratisd[4947]: [2025-10-06T06:45:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:45:11 storageqe-109 stratisd[4947]: [2025-10-06T06:45:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:45:11 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:45:12 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:45:12 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:45:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 02:45:53 storageqe-109 dnf[420763]: Updating Subscription Management repositories. Oct 6 02:45:53 storageqe-109 dnf[420763]: Unable to read consumer identity Oct 6 02:45:53 storageqe-109 dnf[420763]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 02:45:53 storageqe-109 dnf[420763]: Metadata cache refreshed recently. Oct 6 02:45:54 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 02:45:54 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 02:46:37 storageqe-109 stratisd[4947]: [2025-10-06T06:46:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:46:37 storageqe-109 stratisd[4947]: [2025-10-06T06:46:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:46:47 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:47:17 storageqe-109 stratisd[4947]: [2025-10-06T06:47:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:47:17 storageqe-109 stratisd[4947]: [2025-10-06T06:47:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:47:56 storageqe-109 stratisd[4947]: [2025-10-06T06:47:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:47:56 storageqe-109 stratisd[4947]: [2025-10-06T06:47:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:47:56 storageqe-109 stratisd[4947]: [2025-10-06T06:47:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:47:56 storageqe-109 stratisd[4947]: [2025-10-06T06:47:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:47:56 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:47:57 storageqe-109 INFO: finishe the remove crypt device cSmz Oct 6 02:47:57 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 02:49:22 storageqe-109 stratisd[4947]: [2025-10-06T06:49:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:49:22 storageqe-109 stratisd[4947]: [2025-10-06T06:49:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:49:32 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear cSmz -q --allow-discards Oct 6 02:50:02 storageqe-109 stratisd[4947]: [2025-10-06T06:50:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:50:02 storageqe-109 stratisd[4947]: [2025-10-06T06:50:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device cSmz INFO: finishe the remove crypt device cSmz Oct 6 02:50:42 storageqe-109 stratisd[4947]: [2025-10-06T06:50:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:50:42 storageqe-109 stratisd[4947]: [2025-10-06T06:50:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:50:42 storageqe-109 stratisd[4947]: [2025-10-06T06:50:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:50:42 storageqe-109 stratisd[4947]: [2025-10-06T06:50:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:50:42 storageqe-109 INFO: remove crypt device cSmz Oct 6 02:50:42 storageqe-109 INFO: finishe the remove crypt device cSmz INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_paramter[npo2_linear] #### INFO: #### will start test_luks_bz1750680[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:50:47 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:50:47 storageqe-109 INFO: #### END test_luks_paramter[npo2_linear] #### Oct 6 02:50:47 storageqe-109 INFO: #### will start test_luks_bz1750680[npo2_linear] ##### Oct 6 02:50:47 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 02:50:52 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 02:51:00 storageqe-109 stratisd[4947]: [2025-10-06T06:51:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:51:00 storageqe-109 stratisd[4947]: [2025-10-06T06:51:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear ZSMY -q --disable-keyring Oct 6 02:51:10 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear ZSMY -q --disable-keyring Oct 6 02:51:12 storageqe-109 stratisd[4947]: [2025-10-06T06:51:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:51:12 storageqe-109 stratisd[4947]: [2025-10-06T06:51:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs xfs in remove_crypt Oct 6 02:51:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.1p9o4cbtmount_test with fs xfs Oct 6 02:51:32 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 87b89f75-3e33-46d7-bdfe-080bd3dd84eb Oct 6 02:51:32 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 02:51:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1p9o4cbtmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs ext4 in remove_crypt Oct 6 02:51:37 storageqe-109 systemd[1]: tmp-libblockdev.1p9o4cbtmount_test.mount: Deactivated successfully. Oct 6 02:51:37 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 87b89f75-3e33-46d7-bdfe-080bd3dd84eb Oct 6 02:51:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs xfs in remove_crypt Oct 6 02:51:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.u_54k_f9mount_test with fs ext4 Oct 6 02:51:47 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 63332f1e-ce39-42f1-bcd8-a6036a6a628c r/w with ordered data mode. Quota mode: none. Oct 6 02:51:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u_54k_f9mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs ext3 in remove_crypt Oct 6 02:51:52 storageqe-109 systemd[1]: tmp-libblockdev.u_54k_f9mount_test.mount: Deactivated successfully. Oct 6 02:51:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 63332f1e-ce39-42f1-bcd8-a6036a6a628c. Oct 6 02:51:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs ext4 in remove_crypt Oct 6 02:51:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.su3rvocfmount_test with fs ext3 Oct 6 02:52:02 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 02:52:02 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5bcd88ec-8a7d-4144-abac-974175cc04bf r/w with ordered data mode. Quota mode: none. Oct 6 02:52:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.su3rvocfmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs ext2 in remove_crypt Oct 6 02:52:07 storageqe-109 systemd[1]: tmp-libblockdev.su3rvocfmount_test.mount: Deactivated successfully. Oct 6 02:52:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5bcd88ec-8a7d-4144-abac-974175cc04bf. Oct 6 02:52:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs ext3 in remove_crypt Oct 6 02:52:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZSMY and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vj4k_sormount_test with fs ext2 Oct 6 02:52:17 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 02:52:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9dfd7e9b-9f7e-4a1b-84e7-1e4f43d73c72 r/w without journal. Quota mode: none. Oct 6 02:52:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vj4k_sormount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs ext2 in remove_crypt INFO: remove crypt device ZSMY INFO: finishe the remove crypt device ZSMY Oct 6 02:52:22 storageqe-109 systemd[1]: tmp-libblockdev.vj4k_sormount_test.mount: Deactivated successfully. Oct 6 02:52:22 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9dfd7e9b-9f7e-4a1b-84e7-1e4f43d73c72. Oct 6 02:52:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZSMY and fs ext2 in remove_crypt Oct 6 02:52:22 storageqe-109 INFO: remove crypt device ZSMY Oct 6 02:52:22 storageqe-109 INFO: finishe the remove crypt device ZSMY INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz1750680[npo2_linear] #### INFO: #### will start test_luks_bz2073433[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:52:27 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:52:27 storageqe-109 INFO: #### END test_luks_bz1750680[npo2_linear] #### Oct 6 02:52:27 storageqe-109 INFO: #### will start test_luks_bz2073433[npo2_linear] ##### Oct 6 02:52:27 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 6 02:52:32 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear Jwxn -q --perf-no_read_workqueue --perf-no_write_workqueue Oct 6 02:52:46 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear Jwxn -q --perf-no_read_workqueue --perf-no_write_workqueue cryptsetup refresh Jwxn -q --perf-no_write_workqueue Oct 6 02:52:58 storageqe-109 journal: cryptsetup refresh Jwxn -q --perf-no_write_workqueue cryptsetup refresh Jwxn -q --perf-no_read_workqueue Oct 6 02:53:10 storageqe-109 journal: cryptsetup refresh Jwxn -q --perf-no_read_workqueue cryptsetup refresh Jwxn -q --perf-no_write_workqueue --perf-no_read_workqueue Oct 6 02:53:23 storageqe-109 journal: cryptsetup refresh Jwxn -q --perf-no_write_workqueue --perf-no_read_workqueue INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt Oct 6 02:53:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.e1t3na5dmount_test with fs xfs Oct 6 02:53:45 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ee8fb077-4612-4bb7-b1f2-847f7287d797 Oct 6 02:53:45 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 02:53:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e1t3na5dmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt Oct 6 02:53:50 storageqe-109 systemd[1]: tmp-libblockdev.e1t3na5dmount_test.mount: Deactivated successfully. Oct 6 02:53:50 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ee8fb077-4612-4bb7-b1f2-847f7287d797 Oct 6 02:53:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt Oct 6 02:53:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uj0mbo_emount_test with fs ext4 Oct 6 02:54:00 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bef1d2f9-f41d-4de9-bf8f-ed238fdfa08e r/w with ordered data mode. Quota mode: none. Oct 6 02:54:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uj0mbo_emount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt Oct 6 02:54:04 storageqe-109 systemd[1]: tmp-libblockdev.uj0mbo_emount_test.mount: Deactivated successfully. Oct 6 02:54:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bef1d2f9-f41d-4de9-bf8f-ed238fdfa08e. Oct 6 02:54:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt Oct 6 02:54:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.szenm8u5mount_test with fs ext3 Oct 6 02:54:15 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 02:54:15 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6fc6c236-ab2b-43f1-b073-3c72b2b4123f r/w with ordered data mode. Quota mode: none. Oct 6 02:54:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.szenm8u5mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt Oct 6 02:54:19 storageqe-109 systemd[1]: tmp-libblockdev.szenm8u5mount_test.mount: Deactivated successfully. Oct 6 02:54:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6fc6c236-ab2b-43f1-b073-3c72b2b4123f. Oct 6 02:54:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt Oct 6 02:54:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y4_h1y8gmount_test with fs ext2 Oct 6 02:54:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 02:54:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 062cbb2a-0fab-4f77-9cd0-78e6b82a58ba r/w without journal. Quota mode: none. Oct 6 02:54:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y4_h1y8gmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt INFO: remove crypt device Jwxn INFO: finishe the remove crypt device Jwxn cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 02:54:34 storageqe-109 systemd[1]: tmp-libblockdev.y4_h1y8gmount_test.mount: Deactivated successfully. Oct 6 02:54:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 062cbb2a-0fab-4f77-9cd0-78e6b82a58ba. Oct 6 02:54:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt Oct 6 02:54:34 storageqe-109 INFO: remove crypt device Jwxn Oct 6 02:54:34 storageqe-109 INFO: finishe the remove crypt device Jwxn Oct 6 02:54:34 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 02:54:42 storageqe-109 stratisd[4947]: [2025-10-06T06:54:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:54:42 storageqe-109 stratisd[4947]: [2025-10-06T06:54:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear Jwxn -q --perf-no_read_workqueue --perf-no_write_workqueue --persistent Oct 6 02:54:52 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear Jwxn -q --perf-no_read_workqueue --perf-no_write_workqueue --persistent Oct 6 02:54:54 storageqe-109 stratisd[4947]: [2025-10-06T06:54:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:54:54 storageqe-109 stratisd[4947]: [2025-10-06T06:54:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:54:54 storageqe-109 stratisd[4947]: [2025-10-06T06:54:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:54:54 storageqe-109 stratisd[4947]: [2025-10-06T06:54:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup refresh Jwxn -q --perf-no_write_workqueue Oct 6 02:55:04 storageqe-109 journal: cryptsetup refresh Jwxn -q --perf-no_write_workqueue Oct 6 02:55:06 storageqe-109 stratisd[4947]: [2025-10-06T06:55:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:55:06 storageqe-109 stratisd[4947]: [2025-10-06T06:55:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup refresh Jwxn -q --perf-no_read_workqueue Oct 6 02:55:16 storageqe-109 journal: cryptsetup refresh Jwxn -q --perf-no_read_workqueue Oct 6 02:55:18 storageqe-109 stratisd[4947]: [2025-10-06T06:55:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:55:18 storageqe-109 stratisd[4947]: [2025-10-06T06:55:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup refresh Jwxn -q --perf-no_write_workqueue --perf-no_read_workqueue Oct 6 02:55:28 storageqe-109 journal: cryptsetup refresh Jwxn -q --perf-no_write_workqueue --perf-no_read_workqueue Oct 6 02:55:30 storageqe-109 stratisd[4947]: [2025-10-06T06:55:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:55:30 storageqe-109 stratisd[4947]: [2025-10-06T06:55:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt Oct 6 02:55:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8riu9ilimount_test with fs xfs Oct 6 02:55:50 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 4590ad4e-fd69-4f81-a076-78229e434574 Oct 6 02:55:50 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 02:55:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8riu9ilimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt Oct 6 02:55:55 storageqe-109 systemd[1]: tmp-libblockdev.8riu9ilimount_test.mount: Deactivated successfully. Oct 6 02:55:55 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 4590ad4e-fd69-4f81-a076-78229e434574 Oct 6 02:55:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs xfs in remove_crypt Oct 6 02:55:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qeokhgccmount_test with fs ext4 Oct 6 02:56:05 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2b9a871f-7bb6-43d9-88d0-74ff7de9cc5e r/w with ordered data mode. Quota mode: none. Oct 6 02:56:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qeokhgccmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt Oct 6 02:56:10 storageqe-109 systemd[1]: tmp-libblockdev.qeokhgccmount_test.mount: Deactivated successfully. Oct 6 02:56:10 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2b9a871f-7bb6-43d9-88d0-74ff7de9cc5e. Oct 6 02:56:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext4 in remove_crypt Oct 6 02:56:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vgx8mf0nmount_test with fs ext3 Oct 6 02:56:20 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 02:56:20 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 70e41a10-44d0-462a-b986-552307d3b0f0 r/w with ordered data mode. Quota mode: none. Oct 6 02:56:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vgx8mf0nmount_test with fs ext3 Oct 6 02:56:25 storageqe-109 systemd[1]: tmp-libblockdev.vgx8mf0nmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt Oct 6 02:56:25 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 70e41a10-44d0-462a-b986-552307d3b0f0. Oct 6 02:56:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext3 in remove_crypt Oct 6 02:56:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ql09fob4mount_test with fs ext2 Oct 6 02:56:35 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 02:56:35 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f5891616-4e8b-4ce2-b738-3b63f5a933e7 r/w without journal. Quota mode: none. Oct 6 02:56:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ql09fob4mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt INFO: remove crypt device Jwxn INFO: finishe the remove crypt device Jwxn Oct 6 02:56:40 storageqe-109 systemd[1]: tmp-libblockdev.ql09fob4mount_test.mount: Deactivated successfully. Oct 6 02:56:40 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f5891616-4e8b-4ce2-b738-3b63f5a933e7. Oct 6 02:56:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Jwxn and fs ext2 in remove_crypt Oct 6 02:56:40 storageqe-109 INFO: remove crypt device Jwxn Oct 6 02:56:40 storageqe-109 INFO: finishe the remove crypt device Jwxn INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz2073433[npo2_linear] #### INFO: #### will start test_luks_conversion[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:56:45 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 02:56:45 storageqe-109 INFO: #### END test_luks_bz2073433[npo2_linear] #### Oct 6 02:56:45 storageqe-109 INFO: #### will start test_luks_conversion[npo2_linear] ##### Oct 6 02:56:45 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 6 02:56:50 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 02:57:04 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 02:57:04 storageqe-109 stratisd[4947]: [2025-10-06T06:57:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:57:04 storageqe-109 stratisd[4947]: [2025-10-06T06:57:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear NvaX -q Oct 6 02:57:14 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear NvaX -q Oct 6 02:57:16 storageqe-109 stratisd[4947]: [2025-10-06T06:57:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:57:16 storageqe-109 stratisd[4947]: [2025-10-06T06:57:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt Oct 6 02:57:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.r0rpc_zdmount_test with fs xfs Oct 6 02:57:36 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ee4e267f-416b-4625-8257-c01d25e3d4b9 Oct 6 02:57:36 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 02:57:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r0rpc_zdmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt Oct 6 02:57:41 storageqe-109 systemd[1]: tmp-libblockdev.r0rpc_zdmount_test.mount: Deactivated successfully. Oct 6 02:57:41 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ee4e267f-416b-4625-8257-c01d25e3d4b9 Oct 6 02:57:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt Oct 6 02:57:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dn5c9_45mount_test with fs ext4 Oct 6 02:57:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 462a7d23-02c7-4cc9-a59a-e140a234d473 r/w with ordered data mode. Quota mode: none. Oct 6 02:57:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dn5c9_45mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt Oct 6 02:57:56 storageqe-109 systemd[1]: tmp-libblockdev.dn5c9_45mount_test.mount: Deactivated successfully. Oct 6 02:57:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 462a7d23-02c7-4cc9-a59a-e140a234d473. Oct 6 02:57:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt Oct 6 02:57:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.n80k7l28mount_test with fs ext3 Oct 6 02:58:07 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 02:58:07 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem db79aeef-d6ca-402b-933c-344c30712b1a r/w with ordered data mode. Quota mode: none. Oct 6 02:58:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n80k7l28mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt Oct 6 02:58:11 storageqe-109 systemd[1]: tmp-libblockdev.n80k7l28mount_test.mount: Deactivated successfully. Oct 6 02:58:11 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem db79aeef-d6ca-402b-933c-344c30712b1a. Oct 6 02:58:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt Oct 6 02:58:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kj47bic2mount_test with fs ext2 Oct 6 02:58:22 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 02:58:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1b8708b5-58c9-48e6-b142-449f0928cb84 r/w without journal. Quota mode: none. Oct 6 02:58:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kj47bic2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt INFO: remove crypt device NvaX INFO: finishe the remove crypt device NvaX Oct 6 02:58:26 storageqe-109 systemd[1]: tmp-libblockdev.kj47bic2mount_test.mount: Deactivated successfully. Oct 6 02:58:26 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1b8708b5-58c9-48e6-b142-449f0928cb84. Oct 6 02:58:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt Oct 6 02:58:26 storageqe-109 INFO: remove crypt device NvaX Oct 6 02:58:26 storageqe-109 INFO: finishe the remove crypt device NvaX cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 6 02:58:27 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear NvaX -q Oct 6 02:58:37 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear NvaX -q INFO: start IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt Oct 6 02:58:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.iolyk0d0mount_test with fs xfs Oct 6 02:58:59 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem a2a26be0-4874-4be4-be39-5a57b7282119 Oct 6 02:58:59 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 02:58:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iolyk0d0mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt Oct 6 02:59:04 storageqe-109 systemd[1]: tmp-libblockdev.iolyk0d0mount_test.mount: Deactivated successfully. Oct 6 02:59:04 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem a2a26be0-4874-4be4-be39-5a57b7282119 Oct 6 02:59:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt Oct 6 02:59:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f6ta6j4wmount_test with fs ext4 Oct 6 02:59:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8a1745e9-ec39-4ff5-98dd-cdd547b45861 r/w with ordered data mode. Quota mode: none. Oct 6 02:59:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f6ta6j4wmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt Oct 6 02:59:19 storageqe-109 systemd[1]: tmp-libblockdev.f6ta6j4wmount_test.mount: Deactivated successfully. Oct 6 02:59:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8a1745e9-ec39-4ff5-98dd-cdd547b45861. Oct 6 02:59:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt Oct 6 02:59:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ussyy53kmount_test with fs ext3 Oct 6 02:59:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 02:59:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7cdbdefe-7e36-474c-aa68-55f4e6256810 r/w with ordered data mode. Quota mode: none. Oct 6 02:59:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ussyy53kmount_test with fs ext3 Oct 6 02:59:34 storageqe-109 systemd[1]: tmp-libblockdev.ussyy53kmount_test.mount: Deactivated successfully. Oct 6 02:59:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7cdbdefe-7e36-474c-aa68-55f4e6256810. INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt Oct 6 02:59:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt Oct 6 02:59:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.as7_9q65mount_test with fs ext2 Oct 6 02:59:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 02:59:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 970fb10f-22de-4fa3-a974-0cc4c4d2a04e r/w without journal. Quota mode: none. Oct 6 02:59:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.as7_9q65mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt INFO: remove crypt device NvaX INFO: finishe the remove crypt device NvaX cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 02:59:49 storageqe-109 systemd[1]: tmp-libblockdev.as7_9q65mount_test.mount: Deactivated successfully. Oct 6 02:59:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 970fb10f-22de-4fa3-a974-0cc4c4d2a04e. Oct 6 02:59:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt Oct 6 02:59:49 storageqe-109 INFO: remove crypt device NvaX Oct 6 02:59:49 storageqe-109 INFO: finishe the remove crypt device NvaX Oct 6 02:59:49 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 02:59:49 storageqe-109 stratisd[4947]: [2025-10-06T06:59:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 02:59:49 storageqe-109 stratisd[4947]: [2025-10-06T06:59:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear NvaX -q Oct 6 02:59:59 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear NvaX -q Oct 6 03:00:01 storageqe-109 stratisd[4947]: [2025-10-06T07:00:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:00:01 storageqe-109 stratisd[4947]: [2025-10-06T07:00:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt Oct 6 03:00:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.fkcxeuckmount_test with fs xfs Oct 6 03:00:21 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 8ade9cb4-9207-4c8a-a3ee-be8d81ece337 Oct 6 03:00:21 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:00:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fkcxeuckmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt Oct 6 03:00:26 storageqe-109 systemd[1]: tmp-libblockdev.fkcxeuckmount_test.mount: Deactivated successfully. Oct 6 03:00:26 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 8ade9cb4-9207-4c8a-a3ee-be8d81ece337 Oct 6 03:00:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs xfs in remove_crypt Oct 6 03:00:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.23q2e9pimount_test with fs ext4 Oct 6 03:00:36 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ff211f3d-9f6b-47cc-acb9-487b8b84004c r/w with ordered data mode. Quota mode: none. Oct 6 03:00:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.23q2e9pimount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt Oct 6 03:00:41 storageqe-109 systemd[1]: tmp-libblockdev.23q2e9pimount_test.mount: Deactivated successfully. Oct 6 03:00:41 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ff211f3d-9f6b-47cc-acb9-487b8b84004c. Oct 6 03:00:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext4 in remove_crypt Oct 6 03:00:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e8_jm2tnmount_test with fs ext3 Oct 6 03:00:51 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:00:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1881ca8a-77fc-4117-8fcb-ebc9d222a90e r/w with ordered data mode. Quota mode: none. Oct 6 03:00:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e8_jm2tnmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt Oct 6 03:00:56 storageqe-109 systemd[1]: tmp-libblockdev.e8_jm2tnmount_test.mount: Deactivated successfully. Oct 6 03:00:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1881ca8a-77fc-4117-8fcb-ebc9d222a90e. Oct 6 03:00:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext3 in remove_crypt Oct 6 03:00:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.aj9oseykmount_test with fs ext2 Oct 6 03:01:06 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:01:06 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8f48ccfe-de9c-4f3c-976d-31ab6775ff85 r/w without journal. Quota mode: none. Oct 6 03:01:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.aj9oseykmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt INFO: remove crypt device NvaX INFO: finishe the remove crypt device NvaX Oct 6 03:01:11 storageqe-109 systemd[1]: tmp-libblockdev.aj9oseykmount_test.mount: Deactivated successfully. Oct 6 03:01:11 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8f48ccfe-de9c-4f3c-976d-31ab6775ff85. Oct 6 03:01:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NvaX and fs ext2 in remove_crypt Oct 6 03:01:11 storageqe-109 INFO: remove crypt device NvaX Oct 6 03:01:11 storageqe-109 INFO: finishe the remove crypt device NvaX INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_conversion[npo2_linear] #### INFO: #### will start test_luks_bz1862173[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:01:16 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:01:16 storageqe-109 INFO: #### END test_luks_conversion[npo2_linear] #### Oct 6 03:01:16 storageqe-109 INFO: #### will start test_luks_bz1862173[npo2_linear] ##### Oct 6 03:01:16 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:01:21 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:01:28 storageqe-109 stratisd[4947]: [2025-10-06T07:01:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:01:28 storageqe-109 stratisd[4947]: [2025-10-06T07:01:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' token add /dev/mapper/npo2linear -q Oct 6 03:01:39 storageqe-109 journal: cryptsetup --key-description 'mykey' token add /dev/mapper/npo2linear -q Oct 6 03:01:39 storageqe-109 stratisd[4947]: [2025-10-06T07:01:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:01:39 storageqe-109 stratisd[4947]: [2025-10-06T07:01:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear fdey -q --allow-discards --token-only Oct 6 03:01:49 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear fdey -q --allow-discards --token-only INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz1862173[npo2_linear] #### INFO: #### will start test_luks_passphrases[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:01:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:01:54 storageqe-109 INFO: #### END test_luks_bz1862173[npo2_linear] #### Oct 6 03:01:54 storageqe-109 INFO: #### will start test_luks_passphrases[npo2_linear] ##### Oct 6 03:01:54 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 6 03:01:59 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear SkTe -q --allow-discards Oct 6 03:02:13 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear SkTe -q --allow-discards INFO: will run io in dir /tmp/libblockdev.dj6usonnmount_test with fs xfs Oct 6 03:03:34 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem c14c11c3-1ae4-4dd0-98cc-b63325923c3e Oct 6 03:03:34 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:03:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dj6usonnmount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/SkTe and fs xfs in remove_crypt Oct 6 03:03:40 storageqe-109 systemd[1]: tmp-libblockdev.dj6usonnmount_test.mount: Deactivated successfully. Oct 6 03:03:40 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem c14c11c3-1ae4-4dd0-98cc-b63325923c3e Oct 6 03:03:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SkTe and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.l7qy68p_mount_test with fs xfs Oct 6 03:03:50 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem cc887067-5fe5-464a-9528-c9d090a0e149 Oct 6 03:03:50 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:03:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l7qy68p_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/SkTe and fs xfs in remove_crypt Oct 6 03:03:54 storageqe-109 systemd[1]: tmp-libblockdev.l7qy68p_mount_test.mount: Deactivated successfully. Oct 6 03:03:54 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem cc887067-5fe5-464a-9528-c9d090a0e149 Oct 6 03:03:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SkTe and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SkTe and fs ext4 in remove_crypt Oct 6 03:03:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SkTe and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y4nzzzlnmount_test with fs ext4 Oct 6 03:04:05 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 397c8524-a03e-4ca8-9891-ff3ba37b9120 r/w with ordered data mode. Quota mode: none. Oct 6 03:04:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y4nzzzlnmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/SkTe and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SkTe and fs ext3 in remove_crypt Oct 6 03:04:09 storageqe-109 systemd[1]: tmp-libblockdev.y4nzzzlnmount_test.mount: Deactivated successfully. Oct 6 03:04:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 397c8524-a03e-4ca8-9891-ff3ba37b9120. Oct 6 03:04:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SkTe and fs ext4 in remove_crypt Oct 6 03:04:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SkTe and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kt39mvbpmount_test with fs ext3 Oct 6 03:04:20 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:04:20 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fe2c9642-e2a4-4c33-bb1c-5812ba36f1ef r/w with ordered data mode. Quota mode: none. Oct 6 03:04:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kt39mvbpmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/SkTe and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SkTe and fs ext2 in remove_crypt Oct 6 03:04:25 storageqe-109 systemd[1]: tmp-libblockdev.kt39mvbpmount_test.mount: Deactivated successfully. Oct 6 03:04:25 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fe2c9642-e2a4-4c33-bb1c-5812ba36f1ef. Oct 6 03:04:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SkTe and fs ext3 in remove_crypt Oct 6 03:04:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SkTe and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.akyrsb38mount_test with fs ext2 Oct 6 03:04:35 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:04:35 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 981d0782-0e7c-499f-bde8-50e36e28add0 r/w without journal. Quota mode: none. Oct 6 03:04:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.akyrsb38mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/SkTe and fs ext2 in remove_crypt INFO: remove crypt device SkTe INFO: finishe the remove crypt device SkTe cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:04:40 storageqe-109 systemd[1]: tmp-libblockdev.akyrsb38mount_test.mount: Deactivated successfully. Oct 6 03:04:40 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 981d0782-0e7c-499f-bde8-50e36e28add0. Oct 6 03:04:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SkTe and fs ext2 in remove_crypt Oct 6 03:04:40 storageqe-109 INFO: remove crypt device SkTe Oct 6 03:04:40 storageqe-109 INFO: finishe the remove crypt device SkTe Oct 6 03:04:40 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:04:47 storageqe-109 stratisd[4947]: [2025-10-06T07:04:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:04:47 storageqe-109 stratisd[4947]: [2025-10-06T07:04:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear ZRtF -q --allow-discards Oct 6 03:04:57 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear ZRtF -q --allow-discards Oct 6 03:04:59 storageqe-109 stratisd[4947]: [2025-10-06T07:04:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:04:59 storageqe-109 stratisd[4947]: [2025-10-06T07:04:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:17 storageqe-109 stratisd[4947]: [2025-10-06T07:05:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:17 storageqe-109 stratisd[4947]: [2025-10-06T07:05:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:26 storageqe-109 stratisd[4947]: [2025-10-06T07:05:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:26 storageqe-109 stratisd[4947]: [2025-10-06T07:05:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:26 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 03:05:26 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 03:05:26 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 03:05:34 storageqe-109 stratisd[4947]: [2025-10-06T07:05:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:34 storageqe-109 stratisd[4947]: [2025-10-06T07:05:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:42 storageqe-109 stratisd[4947]: [2025-10-06T07:05:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:42 storageqe-109 stratisd[4947]: [2025-10-06T07:05:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:50 storageqe-109 stratisd[4947]: [2025-10-06T07:05:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:50 storageqe-109 stratisd[4947]: [2025-10-06T07:05:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:59 storageqe-109 stratisd[4947]: [2025-10-06T07:05:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:05:59 storageqe-109 stratisd[4947]: [2025-10-06T07:05:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:07 storageqe-109 stratisd[4947]: [2025-10-06T07:06:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:07 storageqe-109 stratisd[4947]: [2025-10-06T07:06:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:15 storageqe-109 stratisd[4947]: [2025-10-06T07:06:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:15 storageqe-109 stratisd[4947]: [2025-10-06T07:06:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:24 storageqe-109 stratisd[4947]: [2025-10-06T07:06:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:24 storageqe-109 stratisd[4947]: [2025-10-06T07:06:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:32 storageqe-109 stratisd[4947]: [2025-10-06T07:06:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:32 storageqe-109 stratisd[4947]: [2025-10-06T07:06:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:40 storageqe-109 stratisd[4947]: [2025-10-06T07:06:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:40 storageqe-109 stratisd[4947]: [2025-10-06T07:06:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:49 storageqe-109 stratisd[4947]: [2025-10-06T07:06:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:49 storageqe-109 stratisd[4947]: [2025-10-06T07:06:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:57 storageqe-109 stratisd[4947]: [2025-10-06T07:06:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:06:57 storageqe-109 stratisd[4947]: [2025-10-06T07:06:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:05 storageqe-109 stratisd[4947]: [2025-10-06T07:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:05 storageqe-109 stratisd[4947]: [2025-10-06T07:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:13 storageqe-109 stratisd[4947]: [2025-10-06T07:07:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:13 storageqe-109 stratisd[4947]: [2025-10-06T07:07:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:22 storageqe-109 stratisd[4947]: [2025-10-06T07:07:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:22 storageqe-109 stratisd[4947]: [2025-10-06T07:07:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:30 storageqe-109 stratisd[4947]: [2025-10-06T07:07:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:30 storageqe-109 stratisd[4947]: [2025-10-06T07:07:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:38 storageqe-109 stratisd[4947]: [2025-10-06T07:07:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:38 storageqe-109 stratisd[4947]: [2025-10-06T07:07:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:46 storageqe-109 stratisd[4947]: [2025-10-06T07:07:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:46 storageqe-109 stratisd[4947]: [2025-10-06T07:07:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:55 storageqe-109 stratisd[4947]: [2025-10-06T07:07:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:07:55 storageqe-109 stratisd[4947]: [2025-10-06T07:07:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:03 storageqe-109 stratisd[4947]: [2025-10-06T07:08:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:03 storageqe-109 stratisd[4947]: [2025-10-06T07:08:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:12 storageqe-109 stratisd[4947]: [2025-10-06T07:08:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:12 storageqe-109 stratisd[4947]: [2025-10-06T07:08:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:20 storageqe-109 stratisd[4947]: [2025-10-06T07:08:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:20 storageqe-109 stratisd[4947]: [2025-10-06T07:08:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:28 storageqe-109 stratisd[4947]: [2025-10-06T07:08:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:28 storageqe-109 stratisd[4947]: [2025-10-06T07:08:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:37 storageqe-109 stratisd[4947]: [2025-10-06T07:08:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:37 storageqe-109 stratisd[4947]: [2025-10-06T07:08:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:45 storageqe-109 stratisd[4947]: [2025-10-06T07:08:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:45 storageqe-109 stratisd[4947]: [2025-10-06T07:08:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:53 storageqe-109 stratisd[4947]: [2025-10-06T07:08:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:08:53 storageqe-109 stratisd[4947]: [2025-10-06T07:08:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:01 storageqe-109 stratisd[4947]: [2025-10-06T07:09:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:01 storageqe-109 stratisd[4947]: [2025-10-06T07:09:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:10 storageqe-109 stratisd[4947]: [2025-10-06T07:09:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:10 storageqe-109 stratisd[4947]: [2025-10-06T07:09:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:18 storageqe-109 stratisd[4947]: [2025-10-06T07:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:18 storageqe-109 stratisd[4947]: [2025-10-06T07:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:26 storageqe-109 stratisd[4947]: [2025-10-06T07:09:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:26 storageqe-109 stratisd[4947]: [2025-10-06T07:09:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:30 storageqe-109 stratisd[4947]: [2025-10-06T07:09:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:30 storageqe-109 stratisd[4947]: [2025-10-06T07:09:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:34 storageqe-109 stratisd[4947]: [2025-10-06T07:09:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:34 storageqe-109 stratisd[4947]: [2025-10-06T07:09:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:38 storageqe-109 stratisd[4947]: [2025-10-06T07:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:38 storageqe-109 stratisd[4947]: [2025-10-06T07:09:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:42 storageqe-109 stratisd[4947]: [2025-10-06T07:09:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:42 storageqe-109 stratisd[4947]: [2025-10-06T07:09:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:46 storageqe-109 stratisd[4947]: [2025-10-06T07:09:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:46 storageqe-109 stratisd[4947]: [2025-10-06T07:09:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:50 storageqe-109 stratisd[4947]: [2025-10-06T07:09:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:50 storageqe-109 stratisd[4947]: [2025-10-06T07:09:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:54 storageqe-109 stratisd[4947]: [2025-10-06T07:09:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:54 storageqe-109 stratisd[4947]: [2025-10-06T07:09:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:58 storageqe-109 stratisd[4947]: [2025-10-06T07:09:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:09:58 storageqe-109 stratisd[4947]: [2025-10-06T07:09:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:02 storageqe-109 stratisd[4947]: [2025-10-06T07:10:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:02 storageqe-109 stratisd[4947]: [2025-10-06T07:10:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:06 storageqe-109 stratisd[4947]: [2025-10-06T07:10:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:06 storageqe-109 stratisd[4947]: [2025-10-06T07:10:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:10 storageqe-109 stratisd[4947]: [2025-10-06T07:10:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:10 storageqe-109 stratisd[4947]: [2025-10-06T07:10:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:14 storageqe-109 stratisd[4947]: [2025-10-06T07:10:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:14 storageqe-109 stratisd[4947]: [2025-10-06T07:10:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:18 storageqe-109 stratisd[4947]: [2025-10-06T07:10:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:18 storageqe-109 stratisd[4947]: [2025-10-06T07:10:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:22 storageqe-109 stratisd[4947]: [2025-10-06T07:10:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:22 storageqe-109 stratisd[4947]: [2025-10-06T07:10:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:26 storageqe-109 stratisd[4947]: [2025-10-06T07:10:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:26 storageqe-109 stratisd[4947]: [2025-10-06T07:10:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:30 storageqe-109 stratisd[4947]: [2025-10-06T07:10:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:30 storageqe-109 stratisd[4947]: [2025-10-06T07:10:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:34 storageqe-109 stratisd[4947]: [2025-10-06T07:10:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:34 storageqe-109 stratisd[4947]: [2025-10-06T07:10:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:38 storageqe-109 stratisd[4947]: [2025-10-06T07:10:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:38 storageqe-109 stratisd[4947]: [2025-10-06T07:10:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:42 storageqe-109 stratisd[4947]: [2025-10-06T07:10:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:42 storageqe-109 stratisd[4947]: [2025-10-06T07:10:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:46 storageqe-109 stratisd[4947]: [2025-10-06T07:10:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:46 storageqe-109 stratisd[4947]: [2025-10-06T07:10:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:50 storageqe-109 stratisd[4947]: [2025-10-06T07:10:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:50 storageqe-109 stratisd[4947]: [2025-10-06T07:10:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:54 storageqe-109 stratisd[4947]: [2025-10-06T07:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:54 storageqe-109 stratisd[4947]: [2025-10-06T07:10:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:58 storageqe-109 stratisd[4947]: [2025-10-06T07:10:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:10:58 storageqe-109 stratisd[4947]: [2025-10-06T07:10:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:02 storageqe-109 stratisd[4947]: [2025-10-06T07:11:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:02 storageqe-109 stratisd[4947]: [2025-10-06T07:11:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:06 storageqe-109 stratisd[4947]: [2025-10-06T07:11:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:06 storageqe-109 stratisd[4947]: [2025-10-06T07:11:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:10 storageqe-109 stratisd[4947]: [2025-10-06T07:11:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:10 storageqe-109 stratisd[4947]: [2025-10-06T07:11:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:14 storageqe-109 stratisd[4947]: [2025-10-06T07:11:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:14 storageqe-109 stratisd[4947]: [2025-10-06T07:11:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:18 storageqe-109 stratisd[4947]: [2025-10-06T07:11:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:18 storageqe-109 stratisd[4947]: [2025-10-06T07:11:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:22 storageqe-109 stratisd[4947]: [2025-10-06T07:11:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:22 storageqe-109 stratisd[4947]: [2025-10-06T07:11:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:25 storageqe-109 stratisd[4947]: [2025-10-06T07:11:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:25 storageqe-109 stratisd[4947]: [2025-10-06T07:11:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:29 storageqe-109 stratisd[4947]: [2025-10-06T07:11:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:11:29 storageqe-109 stratisd[4947]: [2025-10-06T07:11:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: will run io in dir /tmp/libblockdev.ejjfnkjdmount_test with fs xfs Oct 6 03:11:40 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 653bc568-4d1b-4bad-9d21-e6d8574887e9 Oct 6 03:11:40 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:11:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ejjfnkjdmount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs xfs in remove_crypt Oct 6 03:11:44 storageqe-109 systemd[1]: tmp-libblockdev.ejjfnkjdmount_test.mount: Deactivated successfully. Oct 6 03:11:44 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 653bc568-4d1b-4bad-9d21-e6d8574887e9 Oct 6 03:11:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.rlaf9c86mount_test with fs xfs Oct 6 03:11:54 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 7da28839-1146-49ab-9ee3-8d3d3aec0233 Oct 6 03:11:54 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:11:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rlaf9c86mount_test with fs xfs Oct 6 03:11:59 storageqe-109 systemd[1]: tmp-libblockdev.rlaf9c86mount_test.mount: Deactivated successfully. Oct 6 03:11:59 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 7da28839-1146-49ab-9ee3-8d3d3aec0233 INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs ext4 in remove_crypt Oct 6 03:11:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs xfs in remove_crypt Oct 6 03:11:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gbbdymffmount_test with fs ext4 Oct 6 03:12:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4eca0405-174c-4bbf-9a3e-3e38a0095419 r/w with ordered data mode. Quota mode: none. Oct 6 03:12:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gbbdymffmount_test with fs ext4 Oct 6 03:12:14 storageqe-109 systemd[1]: tmp-libblockdev.gbbdymffmount_test.mount: Deactivated successfully. Oct 6 03:12:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4eca0405-174c-4bbf-9a3e-3e38a0095419. INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs ext3 in remove_crypt Oct 6 03:12:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs ext4 in remove_crypt Oct 6 03:12:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.l3140o4imount_test with fs ext3 Oct 6 03:12:24 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:12:24 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e82494c7-3fba-498a-9a21-19c169985c1f r/w with ordered data mode. Quota mode: none. Oct 6 03:12:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l3140o4imount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs ext2 in remove_crypt Oct 6 03:12:29 storageqe-109 systemd[1]: tmp-libblockdev.l3140o4imount_test.mount: Deactivated successfully. Oct 6 03:12:29 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e82494c7-3fba-498a-9a21-19c169985c1f. Oct 6 03:12:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs ext3 in remove_crypt Oct 6 03:12:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZRtF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.of4tz804mount_test with fs ext2 Oct 6 03:12:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:12:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 475b000b-2aca-43e8-a577-bfb7e9dd96a6 r/w without journal. Quota mode: none. Oct 6 03:12:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.of4tz804mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs ext2 in remove_crypt INFO: remove crypt device ZRtF INFO: finishe the remove crypt device ZRtF Oct 6 03:12:44 storageqe-109 systemd[1]: tmp-libblockdev.of4tz804mount_test.mount: Deactivated successfully. Oct 6 03:12:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 475b000b-2aca-43e8-a577-bfb7e9dd96a6. Oct 6 03:12:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZRtF and fs ext2 in remove_crypt Oct 6 03:12:44 storageqe-109 INFO: remove crypt device ZRtF Oct 6 03:12:44 storageqe-109 INFO: finishe the remove crypt device ZRtF INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_passphrases[npo2_linear] #### INFO: #### will start test_integrity_setup[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:12:49 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:12:49 storageqe-109 INFO: #### END test_luks_passphrases[npo2_linear] #### Oct 6 03:12:49 storageqe-109 INFO: #### will start test_integrity_setup[npo2_linear] ##### Oct 6 03:12:49 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --progress-frequency '5' --integrity 'sha1' --tag-size '20' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 03:12:54 storageqe-109 journal: integritysetup --progress-frequency '5' --integrity 'sha1' --tag-size '20' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear YjFR -q --integrity-no-journal Oct 6 03:13:08 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear YjFR -q --integrity-no-journal INFO: will run io in dir /tmp/libblockdev.wrqgcn27mount_test with fs xfs Oct 6 03:13:28 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 5724b6d8-5563-4b0a-9c12-6635406a5ed7 Oct 6 03:13:28 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:13:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wrqgcn27mount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/YjFR and fs xfs in remove_crypt Oct 6 03:13:33 storageqe-109 systemd[1]: tmp-libblockdev.wrqgcn27mount_test.mount: Deactivated successfully. Oct 6 03:13:33 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 5724b6d8-5563-4b0a-9c12-6635406a5ed7 Oct 6 03:13:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/YjFR and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.xvqch41imount_test with fs xfs Oct 6 03:13:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 6c5c655c-28c1-4126-a06f-2537942d2007 Oct 6 03:13:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:13:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xvqch41imount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/YjFR and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/YjFR and fs ext4 in remove_crypt Oct 6 03:13:48 storageqe-109 systemd[1]: tmp-libblockdev.xvqch41imount_test.mount: Deactivated successfully. Oct 6 03:13:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 6c5c655c-28c1-4126-a06f-2537942d2007 Oct 6 03:13:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/YjFR and fs xfs in remove_crypt Oct 6 03:13:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/YjFR and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qa3d6avumount_test with fs ext4 Oct 6 03:13:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 21bd7526-5517-42ce-89f1-fb955a4733f8 r/w with ordered data mode. Quota mode: none. Oct 6 03:13:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qa3d6avumount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/YjFR and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/YjFR and fs ext3 in remove_crypt Oct 6 03:14:03 storageqe-109 systemd[1]: tmp-libblockdev.qa3d6avumount_test.mount: Deactivated successfully. Oct 6 03:14:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 21bd7526-5517-42ce-89f1-fb955a4733f8. Oct 6 03:14:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/YjFR and fs ext4 in remove_crypt Oct 6 03:14:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/YjFR and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2j918bmzmount_test with fs ext3 Oct 6 03:14:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:14:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fe4f1a07-e09c-41ec-8aa1-ef69b77b6d32 r/w with ordered data mode. Quota mode: none. Oct 6 03:14:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2j918bmzmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/YjFR and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/YjFR and fs ext2 in remove_crypt Oct 6 03:14:18 storageqe-109 systemd[1]: tmp-libblockdev.2j918bmzmount_test.mount: Deactivated successfully. Oct 6 03:14:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fe4f1a07-e09c-41ec-8aa1-ef69b77b6d32. Oct 6 03:14:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/YjFR and fs ext3 in remove_crypt Oct 6 03:14:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/YjFR and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0pwx0o2vmount_test with fs ext2 Oct 6 03:14:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:14:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f643aa70-04cd-435f-9ab1-7e554fd03b0b r/w without journal. Quota mode: none. Oct 6 03:14:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0pwx0o2vmount_test with fs ext2 Oct 6 03:14:33 storageqe-109 systemd[1]: tmp-libblockdev.0pwx0o2vmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/YjFR and fs ext2 in remove_crypt INFO: remove crypt device YjFR INFO: finishe the remove crypt device YjFR Oct 6 03:14:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f643aa70-04cd-435f-9ab1-7e554fd03b0b. Oct 6 03:14:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/YjFR and fs ext2 in remove_crypt Oct 6 03:14:33 storageqe-109 INFO: remove crypt device YjFR Oct 6 03:14:33 storageqe-109 INFO: finishe the remove crypt device YjFR INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_setup[npo2_linear] #### INFO: #### will start test_reencrypt_online[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:14:38 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:14:38 storageqe-109 INFO: #### END test_integrity_setup[npo2_linear] #### Oct 6 03:14:38 storageqe-109 INFO: #### will start test_reencrypt_online[npo2_linear] ##### Oct 6 03:14:38 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:14:43 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:14:52 storageqe-109 stratisd[4947]: [2025-10-06T07:14:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:14:52 storageqe-109 stratisd[4947]: [2025-10-06T07:14:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear bPcH -q --allow-discards Oct 6 03:15:02 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear bPcH -q --allow-discards Oct 6 03:15:04 storageqe-109 stratisd[4947]: [2025-10-06T07:15:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:15:04 storageqe-109 stratisd[4947]: [2025-10-06T07:15:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/bPcH and fs xfs in remove_crypt Oct 6 03:15:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bPcH and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ach8hk8pmount_test with fs xfs Oct 6 03:15:24 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 6b5771d3-ab0a-484c-9ad6-6621222db5b5 Oct 6 03:15:24 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:15:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ach8hk8pmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/bPcH and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bPcH and fs ext4 in remove_crypt Oct 6 03:15:29 storageqe-109 systemd[1]: tmp-libblockdev.ach8hk8pmount_test.mount: Deactivated successfully. Oct 6 03:15:29 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 6b5771d3-ab0a-484c-9ad6-6621222db5b5 Oct 6 03:15:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bPcH and fs xfs in remove_crypt Oct 6 03:15:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bPcH and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dj8hcuy7mount_test with fs ext4 Oct 6 03:15:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4358bc79-db1b-4400-9a41-9e77300f74cb r/w with ordered data mode. Quota mode: none. Oct 6 03:15:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dj8hcuy7mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/bPcH and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bPcH and fs ext3 in remove_crypt Oct 6 03:15:44 storageqe-109 systemd[1]: tmp-libblockdev.dj8hcuy7mount_test.mount: Deactivated successfully. Oct 6 03:15:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4358bc79-db1b-4400-9a41-9e77300f74cb. Oct 6 03:15:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bPcH and fs ext4 in remove_crypt Oct 6 03:15:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bPcH and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.io6nzr6fmount_test with fs ext3 Oct 6 03:15:54 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:15:54 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a84352ae-3842-4afe-965e-70ef3650195a r/w with ordered data mode. Quota mode: none. Oct 6 03:15:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.io6nzr6fmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/bPcH and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bPcH and fs ext2 in remove_crypt Oct 6 03:15:59 storageqe-109 systemd[1]: tmp-libblockdev.io6nzr6fmount_test.mount: Deactivated successfully. Oct 6 03:15:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a84352ae-3842-4afe-965e-70ef3650195a. Oct 6 03:15:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bPcH and fs ext3 in remove_crypt Oct 6 03:15:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bPcH and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.v35w7sgymount_test with fs ext2 Oct 6 03:16:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:16:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bf43cf23-f4c6-4546-adc8-ff6dcaa02edf r/w without journal. Quota mode: none. Oct 6 03:16:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v35w7sgymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/bPcH and fs ext2 in remove_crypt INFO: remove crypt device bPcH Oct 6 03:16:14 storageqe-109 systemd[1]: tmp-libblockdev.v35w7sgymount_test.mount: Deactivated successfully. Oct 6 03:16:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bf43cf23-f4c6-4546-adc8-ff6dcaa02edf. Oct 6 03:16:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bPcH and fs ext2 in remove_crypt Oct 6 03:16:14 storageqe-109 INFO: remove crypt device bPcH INFO: finishe the remove crypt device bPcH cryptsetup --header '/tmp/testheadereru' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 6 03:16:14 storageqe-109 INFO: finishe the remove crypt device bPcH Oct 6 03:16:14 storageqe-109 journal: cryptsetup --header '/tmp/testheadereru' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --type 'luks2' --header '/tmp/testheadereru' open /dev/mapper/npo2linear bPcH --allow-discards -q Oct 6 03:16:33 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheadereru' open /dev/mapper/npo2linear bPcH --allow-discards -q cryptsetup --active-name 'bPcH' --resilience 'none' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheadereru' reencrypt /dev/mapper/npo2linear -q Oct 6 03:16:45 storageqe-109 journal: cryptsetup --active-name 'bPcH' --resilience 'none' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheadereru' reencrypt /dev/mapper/npo2linear -q cryptsetup --active-name 'bPcH' --header '/tmp/testheadereru' reencrypt /dev/mapper/npo2linear --decrypt -q Oct 6 03:17:07 storageqe-109 journal: cryptsetup --active-name 'bPcH' --header '/tmp/testheadereru' reencrypt /dev/mapper/npo2linear --decrypt -q cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:17:30 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:17:38 storageqe-109 stratisd[4947]: [2025-10-06T07:17:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:17:38 storageqe-109 stratisd[4947]: [2025-10-06T07:17:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear ciQS -q --allow-discards Oct 6 03:17:48 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear ciQS -q --allow-discards Oct 6 03:17:50 storageqe-109 stratisd[4947]: [2025-10-06T07:17:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:17:50 storageqe-109 stratisd[4947]: [2025-10-06T07:17:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/ciQS and fs xfs in remove_crypt Oct 6 03:18:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ciQS and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.jjq86ta5mount_test with fs xfs Oct 6 03:18:10 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 0fea2df5-111e-49ce-b353-749f73f1a323 Oct 6 03:18:10 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:18:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jjq86ta5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ciQS and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ciQS and fs ext4 in remove_crypt Oct 6 03:18:16 storageqe-109 systemd[1]: tmp-libblockdev.jjq86ta5mount_test.mount: Deactivated successfully. Oct 6 03:18:16 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 0fea2df5-111e-49ce-b353-749f73f1a323 Oct 6 03:18:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ciQS and fs xfs in remove_crypt Oct 6 03:18:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ciQS and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.woecikc2mount_test with fs ext4 Oct 6 03:18:26 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 84f9be96-f8ba-40ef-8e89-bdbde91c7070 r/w with ordered data mode. Quota mode: none. Oct 6 03:18:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.woecikc2mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ciQS and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ciQS and fs ext3 in remove_crypt Oct 6 03:18:31 storageqe-109 systemd[1]: tmp-libblockdev.woecikc2mount_test.mount: Deactivated successfully. Oct 6 03:18:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 84f9be96-f8ba-40ef-8e89-bdbde91c7070. Oct 6 03:18:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ciQS and fs ext4 in remove_crypt Oct 6 03:18:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ciQS and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.076m0dkemount_test with fs ext3 Oct 6 03:18:41 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:18:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 233c4c8b-d8db-401e-bd0a-a8d08c186810 r/w with ordered data mode. Quota mode: none. Oct 6 03:18:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.076m0dkemount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ciQS and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ciQS and fs ext2 in remove_crypt Oct 6 03:18:46 storageqe-109 systemd[1]: tmp-libblockdev.076m0dkemount_test.mount: Deactivated successfully. Oct 6 03:18:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 233c4c8b-d8db-401e-bd0a-a8d08c186810. Oct 6 03:18:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ciQS and fs ext3 in remove_crypt Oct 6 03:18:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ciQS and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._4el0ys4mount_test with fs ext2 Oct 6 03:18:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:18:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b2b6996d-c68e-4306-a8f5-8c4caed76beb r/w without journal. Quota mode: none. Oct 6 03:18:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev._4el0ys4mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ciQS and fs ext2 in remove_crypt INFO: remove crypt device ciQS INFO: finishe the remove crypt device ciQS cryptsetup --header '/tmp/testheaderFYt' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 6 03:19:01 storageqe-109 systemd[1]: tmp-libblockdev._4el0ys4mount_test.mount: Deactivated successfully. Oct 6 03:19:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b2b6996d-c68e-4306-a8f5-8c4caed76beb. Oct 6 03:19:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ciQS and fs ext2 in remove_crypt Oct 6 03:19:01 storageqe-109 INFO: remove crypt device ciQS Oct 6 03:19:01 storageqe-109 INFO: finishe the remove crypt device ciQS Oct 6 03:19:01 storageqe-109 journal: cryptsetup --header '/tmp/testheaderFYt' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --type 'luks2' --header '/tmp/testheaderFYt' open /dev/mapper/npo2linear ciQS --allow-discards -q Oct 6 03:19:19 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderFYt' open /dev/mapper/npo2linear ciQS --allow-discards -q cryptsetup --active-name 'ciQS' --resilience 'checksum' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderFYt' reencrypt /dev/mapper/npo2linear -q Oct 6 03:19:31 storageqe-109 journal: cryptsetup --active-name 'ciQS' --resilience 'checksum' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderFYt' reencrypt /dev/mapper/npo2linear -q cryptsetup --active-name 'ciQS' --header '/tmp/testheaderFYt' reencrypt /dev/mapper/npo2linear --decrypt -q Oct 6 03:19:55 storageqe-109 journal: cryptsetup --active-name 'ciQS' --header '/tmp/testheaderFYt' reencrypt /dev/mapper/npo2linear --decrypt -q cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:20:19 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:20:26 storageqe-109 stratisd[4947]: [2025-10-06T07:20:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:20:26 storageqe-109 stratisd[4947]: [2025-10-06T07:20:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear shpt -q --allow-discards Oct 6 03:20:36 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear shpt -q --allow-discards Oct 6 03:20:38 storageqe-109 stratisd[4947]: [2025-10-06T07:20:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:20:38 storageqe-109 stratisd[4947]: [2025-10-06T07:20:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/shpt and fs xfs in remove_crypt Oct 6 03:20:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/shpt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.3vys9_3qmount_test with fs xfs Oct 6 03:20:58 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 7819d460-c365-4be2-98b8-33318c543e4d Oct 6 03:20:58 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:20:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3vys9_3qmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/shpt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/shpt and fs ext4 in remove_crypt Oct 6 03:21:04 storageqe-109 systemd[1]: tmp-libblockdev.3vys9_3qmount_test.mount: Deactivated successfully. Oct 6 03:21:04 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 7819d460-c365-4be2-98b8-33318c543e4d Oct 6 03:21:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/shpt and fs xfs in remove_crypt Oct 6 03:21:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/shpt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j4a02cjwmount_test with fs ext4 Oct 6 03:21:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 23a5dcf9-cdb3-4a42-8a99-afaaf3d349e1 r/w with ordered data mode. Quota mode: none. Oct 6 03:21:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j4a02cjwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/shpt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/shpt and fs ext3 in remove_crypt Oct 6 03:21:19 storageqe-109 systemd[1]: tmp-libblockdev.j4a02cjwmount_test.mount: Deactivated successfully. Oct 6 03:21:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 23a5dcf9-cdb3-4a42-8a99-afaaf3d349e1. Oct 6 03:21:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/shpt and fs ext4 in remove_crypt Oct 6 03:21:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/shpt and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jttmgxe7mount_test with fs ext3 Oct 6 03:21:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:21:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bbcc1ba5-7444-4cac-a8fe-4522674cb94a r/w with ordered data mode. Quota mode: none. Oct 6 03:21:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jttmgxe7mount_test with fs ext3 Oct 6 03:21:34 storageqe-109 systemd[1]: tmp-libblockdev.jttmgxe7mount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/shpt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/shpt and fs ext2 in remove_crypt Oct 6 03:21:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bbcc1ba5-7444-4cac-a8fe-4522674cb94a. Oct 6 03:21:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/shpt and fs ext3 in remove_crypt Oct 6 03:21:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/shpt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.atv7rh9tmount_test with fs ext2 Oct 6 03:21:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:21:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e044c916-6fa1-4dda-bd30-ff0889650050 r/w without journal. Quota mode: none. Oct 6 03:21:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.atv7rh9tmount_test with fs ext2 Oct 6 03:21:49 storageqe-109 systemd[1]: tmp-libblockdev.atv7rh9tmount_test.mount: Deactivated successfully. Oct 6 03:21:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e044c916-6fa1-4dda-bd30-ff0889650050. INFO: End IO testing with the luks device /dev/mapper/shpt and fs ext2 in remove_crypt INFO: remove crypt device shpt INFO: finishe the remove crypt device shpt cryptsetup --header '/tmp/testheaderufV' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 6 03:21:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/shpt and fs ext2 in remove_crypt Oct 6 03:21:49 storageqe-109 INFO: remove crypt device shpt Oct 6 03:21:49 storageqe-109 INFO: finishe the remove crypt device shpt Oct 6 03:21:49 storageqe-109 journal: cryptsetup --header '/tmp/testheaderufV' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --type 'luks2' --header '/tmp/testheaderufV' open /dev/mapper/npo2linear shpt --allow-discards -q Oct 6 03:22:08 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderufV' open /dev/mapper/npo2linear shpt --allow-discards -q cryptsetup --active-name 'shpt' --resilience 'journal' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderufV' reencrypt /dev/mapper/npo2linear -q Oct 6 03:22:20 storageqe-109 journal: cryptsetup --active-name 'shpt' --resilience 'journal' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderufV' reencrypt /dev/mapper/npo2linear -q cryptsetup --active-name 'shpt' --header '/tmp/testheaderufV' reencrypt /dev/mapper/npo2linear --decrypt -q Oct 6 03:22:47 storageqe-109 journal: cryptsetup --active-name 'shpt' --header '/tmp/testheaderufV' reencrypt /dev/mapper/npo2linear --decrypt -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_online[npo2_linear] #### INFO: #### will start test_bz2080516_fips[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:23:15 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:23:15 storageqe-109 INFO: #### END test_reencrypt_online[npo2_linear] #### Oct 6 03:23:15 storageqe-109 INFO: #### will start test_bz2080516_fips[npo2_linear] ##### Oct 6 03:23:15 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'argon2id' luksFormat /dev/mapper/npo2linear -q Oct 6 03:23:20 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'argon2id' luksFormat /dev/mapper/npo2linear -q Oct 6 03:23:28 storageqe-109 stratisd[4947]: [2025-10-06T07:23:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:23:28 storageqe-109 stratisd[4947]: [2025-10-06T07:23:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:23:38 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:23:48 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:23:52 storageqe-109 stratisd[4947]: [2025-10-06T07:23:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:23:52 storageqe-109 stratisd[4947]: [2025-10-06T07:23:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:23:56 storageqe-109 stratisd[4947]: [2025-10-06T07:23:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:23:56 storageqe-109 stratisd[4947]: [2025-10-06T07:23:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz2080516_fips[npo2_linear] #### INFO: #### will start test_luks_sche_test[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:24:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:24:12 storageqe-109 INFO: #### END test_bz2080516_fips[npo2_linear] #### Oct 6 03:24:12 storageqe-109 INFO: #### will start test_luks_sche_test[npo2_linear] ##### Oct 6 03:24:12 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 6 03:24:17 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear rogx -q Oct 6 03:24:31 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear rogx -q INFO: start IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt Oct 6 03:25:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.9x0pdbxcmount_test with fs xfs Oct 6 03:26:03 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem c62f56bc-ea13-4b0c-a04b-1ab355a94e82 Oct 6 03:26:03 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:26:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9x0pdbxcmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt Oct 6 03:26:08 storageqe-109 systemd[1]: tmp-libblockdev.9x0pdbxcmount_test.mount: Deactivated successfully. Oct 6 03:26:08 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem c62f56bc-ea13-4b0c-a04b-1ab355a94e82 Oct 6 03:26:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt Oct 6 03:26:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.no3qrqb0mount_test with fs ext4 Oct 6 03:26:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 52060fad-7963-4455-b8a4-e67ada67e5ae r/w with ordered data mode. Quota mode: none. Oct 6 03:26:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.no3qrqb0mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt Oct 6 03:26:23 storageqe-109 systemd[1]: tmp-libblockdev.no3qrqb0mount_test.mount: Deactivated successfully. Oct 6 03:26:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 52060fad-7963-4455-b8a4-e67ada67e5ae. Oct 6 03:26:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt Oct 6 03:26:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.eqy0hs4mmount_test with fs ext3 Oct 6 03:26:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:26:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c2c40fb9-3d74-4fea-a1d9-72d9ddd47929 r/w with ordered data mode. Quota mode: none. Oct 6 03:26:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.eqy0hs4mmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt Oct 6 03:26:38 storageqe-109 systemd[1]: tmp-libblockdev.eqy0hs4mmount_test.mount: Deactivated successfully. Oct 6 03:26:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c2c40fb9-3d74-4fea-a1d9-72d9ddd47929. Oct 6 03:26:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt Oct 6 03:26:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9croif2xmount_test with fs ext2 Oct 6 03:26:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:26:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e98ee751-18e3-4f88-98a8-117712867b66 r/w without journal. Quota mode: none. Oct 6 03:26:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9croif2xmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt INFO: remove crypt device rogx INFO: finishe the remove crypt device rogx cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:26:53 storageqe-109 systemd[1]: tmp-libblockdev.9croif2xmount_test.mount: Deactivated successfully. Oct 6 03:26:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e98ee751-18e3-4f88-98a8-117712867b66. Oct 6 03:26:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt Oct 6 03:26:53 storageqe-109 INFO: remove crypt device rogx Oct 6 03:26:53 storageqe-109 INFO: finishe the remove crypt device rogx Oct 6 03:26:53 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 6 03:27:01 storageqe-109 stratisd[4947]: [2025-10-06T07:27:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:27:01 storageqe-109 stratisd[4947]: [2025-10-06T07:27:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear rogx -q Oct 6 03:27:11 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear rogx -q Oct 6 03:27:13 storageqe-109 stratisd[4947]: [2025-10-06T07:27:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:27:13 storageqe-109 stratisd[4947]: [2025-10-06T07:27:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt Oct 6 03:28:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.cdk00qb1mount_test with fs xfs Oct 6 03:28:42 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3cacbaad-6b70-46a6-a39d-20fc46fdae85 Oct 6 03:28:42 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:28:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cdk00qb1mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt Oct 6 03:28:47 storageqe-109 systemd[1]: tmp-libblockdev.cdk00qb1mount_test.mount: Deactivated successfully. Oct 6 03:28:47 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3cacbaad-6b70-46a6-a39d-20fc46fdae85 Oct 6 03:28:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs xfs in remove_crypt Oct 6 03:28:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ltl6j710mount_test with fs ext4 Oct 6 03:28:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9b4ab271-a3d5-4159-92bc-debfb8a57cd7 r/w with ordered data mode. Quota mode: none. Oct 6 03:28:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ltl6j710mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt Oct 6 03:29:02 storageqe-109 systemd[1]: tmp-libblockdev.ltl6j710mount_test.mount: Deactivated successfully. Oct 6 03:29:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9b4ab271-a3d5-4159-92bc-debfb8a57cd7. Oct 6 03:29:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext4 in remove_crypt Oct 6 03:29:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e8k022sfmount_test with fs ext3 Oct 6 03:29:12 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:29:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9a01d318-fe43-4b69-9c06-1aa206a0e50f r/w with ordered data mode. Quota mode: none. Oct 6 03:29:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e8k022sfmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt Oct 6 03:29:17 storageqe-109 systemd[1]: tmp-libblockdev.e8k022sfmount_test.mount: Deactivated successfully. Oct 6 03:29:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9a01d318-fe43-4b69-9c06-1aa206a0e50f. Oct 6 03:29:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext3 in remove_crypt Oct 6 03:29:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qx7bmj78mount_test with fs ext2 Oct 6 03:29:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:29:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 79fff89b-6d9e-45fd-8523-71f15a4b8d62 r/w without journal. Quota mode: none. Oct 6 03:29:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qx7bmj78mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt INFO: remove crypt device rogx Oct 6 03:29:32 storageqe-109 systemd[1]: tmp-libblockdev.qx7bmj78mount_test.mount: Deactivated successfully. Oct 6 03:29:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 79fff89b-6d9e-45fd-8523-71f15a4b8d62. Oct 6 03:29:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/rogx and fs ext2 in remove_crypt Oct 6 03:29:32 storageqe-109 INFO: remove crypt device rogx INFO: finishe the remove crypt device rogx Oct 6 03:29:32 storageqe-109 INFO: finishe the remove crypt device rogx INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_sche_test[npo2_linear] #### INFO: #### will start test_bz2212771[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:29:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:29:37 storageqe-109 INFO: #### END test_luks_sche_test[npo2_linear] #### Oct 6 03:29:37 storageqe-109 INFO: #### will start test_bz2212771[npo2_linear] ##### Oct 6 03:29:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --cipher 'capi:xts(ecb(aes-generic))-plain64' luksFormat /dev/mapper/npo2linear -q Oct 6 03:29:42 storageqe-109 journal: cryptsetup --cipher 'capi:xts(ecb(aes-generic))-plain64' luksFormat /dev/mapper/npo2linear -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz2212771[npo2_linear] #### INFO: #### will start test_RHEL_29679[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:29:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:29:57 storageqe-109 INFO: #### END test_bz2212771[npo2_linear] #### Oct 6 03:29:57 storageqe-109 INFO: #### will start test_RHEL_29679[npo2_linear] ##### Oct 6 03:29:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_RHEL_29679[npo2_linear] #### INFO: #### will start test_RHEL_41238[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:30:07 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:30:07 storageqe-109 INFO: #### END test_RHEL_29679[npo2_linear] #### Oct 6 03:30:07 storageqe-109 INFO: #### will start test_RHEL_41238[npo2_linear] ##### Oct 6 03:30:07 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_RHEL_41238[npo2_linear] #### Oct 6 03:30:17 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:30:17 storageqe-109 INFO: #### END test_RHEL_41238[npo2_linear] #### Oct 6 03:30:18 storageqe-109 stratisd[4947]: [2025-10-06T07:30:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:30:18 storageqe-109 stratisd[4947]: [2025-10-06T07:30:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:30:18 storageqe-109 stratisd[4947]: [2025-10-06T07:30:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:30:18 storageqe-109 stratisd[4947]: [2025-10-06T07:30:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:30:19 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:30:19 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 03:30:20 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 03:30:20 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 03:30:20 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 03:30:30 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_compat_test[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:30:36 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:30:36 storageqe-109 INFO: #### will start test_compat_test[npo2_linear] ##### Oct 6 03:30:36 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 03:30:41 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 03:30:50 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 03:30:51 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 03:31:01 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' luksFormat /dev/mapper/npo2linear -q Oct 6 03:31:11 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderzYS' open /dev/mapper/npo2linear --test-passphrase -q Oct 6 03:31:21 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 03:31:31 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 03:31:41 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 03:31:51 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q cryptsetup --header-backup-file '/tmp/testheaderWYinew' luksHeaderBackup /dev/mapper/npo2linear -q Oct 6 03:32:02 storageqe-109 journal: cryptsetup --header-backup-file '/tmp/testheaderWYinew' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q Oct 6 03:32:12 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 03:32:22 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --header-backup-file '/tmp/testheaderWYinew' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 03:32:32 storageqe-109 journal: cryptsetup --header-backup-file '/tmp/testheaderWYinew' luksHeaderRestore /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 03:32:42 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --uuid '12345678-1234-1234-1234-123456789abc' luksFormat /dev/mapper/npo2linear -q Oct 6 03:32:52 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --uuid '12345678-1234-1234-1234-123456789abc' luksFormat /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key Oct 6 03:33:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key Oct 6 03:33:12 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key cryptsetup --type 'luks1' open /dev/mapper/npo2linear qZbp -q Oct 6 03:33:22 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear qZbp -q INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:33:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.pnc8s56dmount_test with fs xfs Oct 6 03:33:42 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 7af0c990-7c1f-42c7-a95f-a4a4cb02c23c Oct 6 03:33:42 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:33:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pnc8s56dmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:33:47 storageqe-109 systemd[1]: tmp-libblockdev.pnc8s56dmount_test.mount: Deactivated successfully. Oct 6 03:33:47 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 7af0c990-7c1f-42c7-a95f-a4a4cb02c23c Oct 6 03:33:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:33:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kpze1y3zmount_test with fs ext4 Oct 6 03:33:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem de96b637-e24d-4e8e-8557-c3405002b622 r/w with ordered data mode. Quota mode: none. Oct 6 03:33:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kpze1y3zmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:34:02 storageqe-109 systemd[1]: tmp-libblockdev.kpze1y3zmount_test.mount: Deactivated successfully. Oct 6 03:34:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem de96b637-e24d-4e8e-8557-c3405002b622. Oct 6 03:34:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:34:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m61sqte_mount_test with fs ext3 Oct 6 03:34:12 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:34:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0d7bb6b2-4632-47cf-a2e0-2e5a322a7f4b r/w with ordered data mode. Quota mode: none. Oct 6 03:34:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m61sqte_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:34:17 storageqe-109 systemd[1]: tmp-libblockdev.m61sqte_mount_test.mount: Deactivated successfully. Oct 6 03:34:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0d7bb6b2-4632-47cf-a2e0-2e5a322a7f4b. Oct 6 03:34:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:34:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tns9hlpbmount_test with fs ext2 Oct 6 03:34:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:34:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3effc924-b014-47f9-a651-c04cfa540709 r/w without journal. Quota mode: none. Oct 6 03:34:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tns9hlpbmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --type 'luks1' open /dev/mapper/npo2linear qZbp -q Oct 6 03:34:32 storageqe-109 systemd[1]: tmp-libblockdev.tns9hlpbmount_test.mount: Deactivated successfully. Oct 6 03:34:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3effc924-b014-47f9-a651-c04cfa540709. Oct 6 03:34:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:34:32 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:34:32 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:34:32 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear qZbp -q cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 6 03:34:42 storageqe-109 journal: cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q Oct 6 03:34:55 storageqe-109 journal: cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --key-file '/tmp/testfileVvW' luksFormat /dev/mapper/npo2linear -q Oct 6 03:35:08 storageqe-109 journal: cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --key-file '/tmp/testfileVvW' luksFormat /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q Oct 6 03:35:22 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:35:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.nz_5i7zbmount_test with fs xfs Oct 6 03:35:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 360fc051-f9c8-4e53-89e7-5298e7dfcca6 Oct 6 03:35:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:35:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nz_5i7zbmount_test with fs xfs Oct 6 03:35:48 storageqe-109 systemd[1]: tmp-libblockdev.nz_5i7zbmount_test.mount: Deactivated successfully. Oct 6 03:35:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 360fc051-f9c8-4e53-89e7-5298e7dfcca6 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:35:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:35:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vlo5341dmount_test with fs ext4 Oct 6 03:35:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8fbd24ec-de31-4832-b659-b49f9b260796 r/w with ordered data mode. Quota mode: none. Oct 6 03:35:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vlo5341dmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:36:03 storageqe-109 systemd[1]: tmp-libblockdev.vlo5341dmount_test.mount: Deactivated successfully. Oct 6 03:36:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8fbd24ec-de31-4832-b659-b49f9b260796. Oct 6 03:36:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:36:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:36:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:36:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 72279965-8ba7-4e01-b99e-73e746fbb8ab r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.6jxgc3e5mount_test with fs ext3 Oct 6 03:36:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6jxgc3e5mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:36:19 storageqe-109 systemd[1]: tmp-libblockdev.6jxgc3e5mount_test.mount: Deactivated successfully. Oct 6 03:36:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 72279965-8ba7-4e01-b99e-73e746fbb8ab. Oct 6 03:36:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:36:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ojokenpfmount_test with fs ext2 Oct 6 03:36:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:36:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 68627a7e-e023-4313-b13d-545a46f6c27b r/w without journal. Quota mode: none. Oct 6 03:36:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ojokenpfmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 03:36:34 storageqe-109 systemd[1]: tmp-libblockdev.ojokenpfmount_test.mount: Deactivated successfully. Oct 6 03:36:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 68627a7e-e023-4313-b13d-545a46f6c27b. Oct 6 03:36:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:36:34 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:36:34 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:36:34 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear qZbp -q Oct 6 03:36:44 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear qZbp -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/qZbp -q Oct 6 03:36:54 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/qZbp -q cryptsetup open /dev/mapper/qZbp dummy -q Oct 6 03:37:04 storageqe-109 journal: cryptsetup open /dev/mapper/qZbp dummy -q INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 6 03:37:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.blkei0s6mount_test with fs xfs Oct 6 03:37:24 storageqe-109 kernel: XFS (dm-5): Mounting V5 Filesystem 565df8ea-322d-4a1e-a61f-53223daf8f94 Oct 6 03:37:24 storageqe-109 kernel: XFS (dm-5): Ending clean mount Oct 6 03:37:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.blkei0s6mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 6 03:37:30 storageqe-109 systemd[1]: tmp-libblockdev.blkei0s6mount_test.mount: Deactivated successfully. Oct 6 03:37:30 storageqe-109 kernel: XFS (dm-5): Unmounting Filesystem 565df8ea-322d-4a1e-a61f-53223daf8f94 Oct 6 03:37:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 6 03:37:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3q55nu4hmount_test with fs ext4 Oct 6 03:37:40 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem cd35568a-6ee5-4f0e-83a8-6aa2c20f5f3d r/w with ordered data mode. Quota mode: none. Oct 6 03:37:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3q55nu4hmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 6 03:37:45 storageqe-109 systemd[1]: tmp-libblockdev.3q55nu4hmount_test.mount: Deactivated successfully. Oct 6 03:37:45 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem cd35568a-6ee5-4f0e-83a8-6aa2c20f5f3d. Oct 6 03:37:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 6 03:37:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 6 03:37:55 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.uw0khtwnmount_test with fs ext3 Oct 6 03:37:55 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 09b94d69-b57e-4728-adfc-1252c994582f r/w with ordered data mode. Quota mode: none. Oct 6 03:37:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uw0khtwnmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 6 03:38:01 storageqe-109 systemd[1]: tmp-libblockdev.uw0khtwnmount_test.mount: Deactivated successfully. Oct 6 03:38:01 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 09b94d69-b57e-4728-adfc-1252c994582f. Oct 6 03:38:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 6 03:38:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nwvbyut6mount_test with fs ext2 Oct 6 03:38:11 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext2 file system using the ext4 subsystem Oct 6 03:38:11 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem aaf4fafc-aaa1-42cf-9d82-bba13173eb91 r/w without journal. Quota mode: none. Oct 6 03:38:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nwvbyut6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: remove crypt device dummy INFO: finishe the remove crypt device dummy INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:38:16 storageqe-109 systemd[1]: tmp-libblockdev.nwvbyut6mount_test.mount: Deactivated successfully. Oct 6 03:38:16 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem aaf4fafc-aaa1-42cf-9d82-bba13173eb91. Oct 6 03:38:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 6 03:38:16 storageqe-109 INFO: remove crypt device dummy Oct 6 03:38:16 storageqe-109 INFO: finishe the remove crypt device dummy Oct 6 03:38:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ko1o306hmount_test with fs xfs Oct 6 03:38:26 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 9e9d6b1e-125d-4278-a8cf-e45c733eb265 Oct 6 03:38:26 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:38:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ko1o306hmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:38:31 storageqe-109 systemd[1]: tmp-libblockdev.ko1o306hmount_test.mount: Deactivated successfully. Oct 6 03:38:31 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 9e9d6b1e-125d-4278-a8cf-e45c733eb265 Oct 6 03:38:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:38:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lu758e_omount_test with fs ext4 Oct 6 03:38:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ced09f2a-d4ca-449a-8339-d68f8a8c9adf r/w with ordered data mode. Quota mode: none. Oct 6 03:38:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lu758e_omount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:38:46 storageqe-109 systemd[1]: tmp-libblockdev.lu758e_omount_test.mount: Deactivated successfully. Oct 6 03:38:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ced09f2a-d4ca-449a-8339-d68f8a8c9adf. Oct 6 03:38:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:38:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9pqa6waxmount_test with fs ext3 Oct 6 03:38:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:38:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1e49a0ee-19f9-47eb-91d2-d27382bd3369 r/w with ordered data mode. Quota mode: none. Oct 6 03:38:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9pqa6waxmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:39:01 storageqe-109 systemd[1]: tmp-libblockdev.9pqa6waxmount_test.mount: Deactivated successfully. Oct 6 03:39:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1e49a0ee-19f9-47eb-91d2-d27382bd3369. Oct 6 03:39:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:39:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vorzobdamount_test with fs ext2 Oct 6 03:39:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:39:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6410bea9-3718-4a1a-a1cf-3811a58c4cae r/w without journal. Quota mode: none. Oct 6 03:39:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vorzobdamount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:39:16 storageqe-109 systemd[1]: tmp-libblockdev.vorzobdamount_test.mount: Deactivated successfully. Oct 6 03:39:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6410bea9-3718-4a1a-a1cf-3811a58c4cae. Oct 6 03:39:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:39:16 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:39:16 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:39:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.3mo0ondkmount_test with fs xfs Oct 6 03:39:26 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem acaed044-ffd4-4f83-b02a-984ef75b0be5 Oct 6 03:39:26 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:39:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3mo0ondkmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:39:31 storageqe-109 systemd[1]: tmp-libblockdev.3mo0ondkmount_test.mount: Deactivated successfully. Oct 6 03:39:31 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem acaed044-ffd4-4f83-b02a-984ef75b0be5 Oct 6 03:39:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:39:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rnhiuavzmount_test with fs ext4 Oct 6 03:39:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ae60a014-d3e0-46d3-87d5-040dfcbccafa r/w with ordered data mode. Quota mode: none. Oct 6 03:39:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rnhiuavzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:39:46 storageqe-109 systemd[1]: tmp-libblockdev.rnhiuavzmount_test.mount: Deactivated successfully. Oct 6 03:39:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ae60a014-d3e0-46d3-87d5-040dfcbccafa. Oct 6 03:39:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:39:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.18cyy7fjmount_test with fs ext3 Oct 6 03:39:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:39:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8798226f-7479-4a81-bac9-6d65aeec729b r/w with ordered data mode. Quota mode: none. Oct 6 03:39:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.18cyy7fjmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:40:01 storageqe-109 systemd[1]: tmp-libblockdev.18cyy7fjmount_test.mount: Deactivated successfully. Oct 6 03:40:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8798226f-7479-4a81-bac9-6d65aeec729b. Oct 6 03:40:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:40:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.12zegb4xmount_test with fs ext2 Oct 6 03:40:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:40:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem eb29cd75-5798-4b34-bbd1-894d569a209f r/w without journal. Quota mode: none. Oct 6 03:40:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.12zegb4xmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --hash 'sha256' --cipher 'aes-cbc-essiv:sha256' --offset '8' --skip '4' create qZbp /dev/mapper/npo2linear -q --readonly Oct 6 03:40:16 storageqe-109 systemd[1]: tmp-libblockdev.12zegb4xmount_test.mount: Deactivated successfully. Oct 6 03:40:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem eb29cd75-5798-4b34-bbd1-894d569a209f. Oct 6 03:40:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:40:16 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:40:16 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:40:16 storageqe-109 journal: cryptsetup --hash 'sha256' --cipher 'aes-cbc-essiv:sha256' --offset '8' --skip '4' create qZbp /dev/mapper/npo2linear -q --readonly cryptsetup status qZbp -q Oct 6 03:40:26 storageqe-109 journal: cryptsetup status qZbp -q cryptsetup status qZbp -q Oct 6 03:40:36 storageqe-109 journal: cryptsetup status qZbp -q cryptsetup status qZbp -q Oct 6 03:40:46 storageqe-109 journal: cryptsetup status qZbp -q cryptsetup status qZbp -q Oct 6 03:40:56 storageqe-109 journal: cryptsetup status qZbp -q cryptsetup --size '409600' resize qZbp -q Oct 6 03:41:06 storageqe-109 journal: cryptsetup --size '409600' resize qZbp -q cryptsetup status qZbp -q Oct 6 03:41:16 storageqe-109 journal: cryptsetup status qZbp -q cryptsetup resize qZbp -q Oct 6 03:41:26 storageqe-109 journal: cryptsetup resize qZbp -q cryptsetup resize qZbp -q Oct 6 03:41:36 storageqe-109 journal: cryptsetup resize qZbp -q cryptsetup remove qZbp -q Oct 6 03:41:46 storageqe-109 journal: cryptsetup remove qZbp -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q Oct 6 03:41:57 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q cryptsetup --key-slot '4' open /dev/mapper/npo2linear qZbp -q Oct 6 03:42:07 storageqe-109 journal: cryptsetup --key-slot '4' open /dev/mapper/npo2linear qZbp -q cryptsetup --key-slot '5' open /dev/mapper/npo2linear qZbp -q Oct 6 03:42:17 storageqe-109 journal: cryptsetup --key-slot '5' open /dev/mapper/npo2linear qZbp -q INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:42:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.tnqtqzq3mount_test with fs xfs Oct 6 03:42:37 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem df16da53-c69a-4867-95c0-8bda812b4c0b Oct 6 03:42:37 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:42:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tnqtqzq3mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:42:42 storageqe-109 systemd[1]: tmp-libblockdev.tnqtqzq3mount_test.mount: Deactivated successfully. Oct 6 03:42:42 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem df16da53-c69a-4867-95c0-8bda812b4c0b Oct 6 03:42:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:42:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pk5dp47amount_test with fs ext4 Oct 6 03:42:52 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 09ca8ff1-9fa4-41fc-9889-ea8463e4ec32 r/w with ordered data mode. Quota mode: none. Oct 6 03:42:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pk5dp47amount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:42:57 storageqe-109 systemd[1]: tmp-libblockdev.pk5dp47amount_test.mount: Deactivated successfully. Oct 6 03:42:57 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 09ca8ff1-9fa4-41fc-9889-ea8463e4ec32. Oct 6 03:42:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:42:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h37flgqumount_test with fs ext3 Oct 6 03:43:07 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:43:07 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 50014ebe-2470-4519-969f-e78233c09991 r/w with ordered data mode. Quota mode: none. Oct 6 03:43:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h37flgqumount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:43:12 storageqe-109 systemd[1]: tmp-libblockdev.h37flgqumount_test.mount: Deactivated successfully. Oct 6 03:43:12 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 50014ebe-2470-4519-969f-e78233c09991. Oct 6 03:43:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:43:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e4a5dtgomount_test with fs ext2 Oct 6 03:43:22 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:43:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ced30901-7b89-40bf-8275-a14acf29bcc9 r/w without journal. Quota mode: none. Oct 6 03:43:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e4a5dtgomount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup open /dev/mapper/npo2linear qZbp -q Oct 6 03:43:27 storageqe-109 systemd[1]: tmp-libblockdev.e4a5dtgomount_test.mount: Deactivated successfully. Oct 6 03:43:27 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ced30901-7b89-40bf-8275-a14acf29bcc9. Oct 6 03:43:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:43:27 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:43:27 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:43:27 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear qZbp -q cryptsetup open /dev/mapper/npo2linear qZbp -q Oct 6 03:43:37 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear qZbp -q INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:43:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.exzk1kbnmount_test with fs xfs Oct 6 03:43:57 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 624d289d-1a0e-439b-b5f5-e35dc27ebd5a Oct 6 03:43:57 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:43:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.exzk1kbnmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:44:02 storageqe-109 systemd[1]: tmp-libblockdev.exzk1kbnmount_test.mount: Deactivated successfully. Oct 6 03:44:02 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 624d289d-1a0e-439b-b5f5-e35dc27ebd5a Oct 6 03:44:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:44:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tka3fchbmount_test with fs ext4 Oct 6 03:44:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7c2eafac-f295-4e0f-8a75-9e7874368d7c r/w with ordered data mode. Quota mode: none. Oct 6 03:44:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tka3fchbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:44:17 storageqe-109 systemd[1]: tmp-libblockdev.tka3fchbmount_test.mount: Deactivated successfully. Oct 6 03:44:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7c2eafac-f295-4e0f-8a75-9e7874368d7c. Oct 6 03:44:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:44:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0j5odgphmount_test with fs ext3 Oct 6 03:44:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:44:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem be73bdc3-4409-4a7f-8adc-94f864d1fb53 r/w with ordered data mode. Quota mode: none. Oct 6 03:44:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0j5odgphmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:44:32 storageqe-109 systemd[1]: tmp-libblockdev.0j5odgphmount_test.mount: Deactivated successfully. Oct 6 03:44:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem be73bdc3-4409-4a7f-8adc-94f864d1fb53. Oct 6 03:44:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:44:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8r_2kf8lmount_test with fs ext2 Oct 6 03:44:42 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:44:42 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 05449b52-7c94-49aa-a4b2-c3424137795b r/w without journal. Quota mode: none. Oct 6 03:44:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8r_2kf8lmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --type 'luks1' --key-slot '5' --key-file '/tmp/testfilePEo' luksFormat /dev/mapper/npo2linear -q Oct 6 03:44:47 storageqe-109 systemd[1]: tmp-libblockdev.8r_2kf8lmount_test.mount: Deactivated successfully. Oct 6 03:44:47 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 05449b52-7c94-49aa-a4b2-c3424137795b. Oct 6 03:44:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:44:47 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:44:47 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:44:47 storageqe-109 journal: cryptsetup --type 'luks1' --key-slot '5' --key-file '/tmp/testfilePEo' luksFormat /dev/mapper/npo2linear -q cryptsetup --key-slot '5' --key-file '/tmp/testfilePEo' open /dev/mapper/npo2linear qZbp -q Oct 6 03:45:02 storageqe-109 journal: cryptsetup --key-slot '5' --key-file '/tmp/testfilePEo' open /dev/mapper/npo2linear qZbp -q INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:45:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.uizb6dl9mount_test with fs xfs Oct 6 03:45:24 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 963ca82a-9399-464c-a188-9c75933bb40a Oct 6 03:45:24 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:45:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uizb6dl9mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:45:29 storageqe-109 systemd[1]: tmp-libblockdev.uizb6dl9mount_test.mount: Deactivated successfully. Oct 6 03:45:29 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 963ca82a-9399-464c-a188-9c75933bb40a Oct 6 03:45:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:45:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.50svht1dmount_test with fs ext4 Oct 6 03:45:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1aa2fc5e-bc7e-43fc-a767-b26d834b0f7a r/w with ordered data mode. Quota mode: none. Oct 6 03:45:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.50svht1dmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:45:44 storageqe-109 systemd[1]: tmp-libblockdev.50svht1dmount_test.mount: Deactivated successfully. Oct 6 03:45:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1aa2fc5e-bc7e-43fc-a767-b26d834b0f7a. Oct 6 03:45:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:45:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ovgsag73mount_test with fs ext3 Oct 6 03:45:54 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:45:54 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d5189775-96e8-4707-b13e-8fe0cac8f0ea r/w with ordered data mode. Quota mode: none. Oct 6 03:45:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ovgsag73mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:45:59 storageqe-109 systemd[1]: tmp-libblockdev.ovgsag73mount_test.mount: Deactivated successfully. Oct 6 03:45:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d5189775-96e8-4707-b13e-8fe0cac8f0ea. Oct 6 03:45:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:45:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0kzo1mnmmount_test with fs ext2 Oct 6 03:46:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:46:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c27b449e-3e83-4484-ba5f-81dd4a3b5614 r/w without journal. Quota mode: none. Oct 6 03:46:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0kzo1mnmmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp Oct 6 03:46:14 storageqe-109 systemd[1]: tmp-libblockdev.0kzo1mnmmount_test.mount: Deactivated successfully. Oct 6 03:46:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c27b449e-3e83-4484-ba5f-81dd4a3b5614. Oct 6 03:46:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:46:14 storageqe-109 INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' luksFormat /dev/mapper/npo2linear -q Oct 6 03:46:14 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:46:14 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '1' luksFormat /dev/mapper/npo2linear -q Oct 6 03:46:24 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '8192' luksFormat /dev/mapper/npo2linear -q Oct 6 03:46:34 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '0' luksFormat /dev/mapper/npo2linear -q Oct 6 03:46:44 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '0' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '8192' --offset '8192' luksFormat /dev/mapper/npo2linear -q Oct 6 03:46:54 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --align-payload '8192' --offset '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --key-slot '7' luksFormat /dev/mapper/npo2linear -q Oct 6 03:47:04 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --key-slot '7' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --offset '80000' luksFormat /dev/mapper/npo2linear -q Oct 6 03:47:14 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --offset '80000' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --offset '8192' luksFormat /dev/mapper/npo2linear -q Oct 6 03:47:24 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --offset '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --offset '0' luksFormat /dev/mapper/npo2linear -q Oct 6 03:47:34 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' --offset '0' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderzYS' open /dev/mapper/npo2linear qZbp -q Oct 6 03:47:44 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' open /dev/mapper/npo2linear qZbp -q cryptsetup --size '409600' --header '/tmp/testheaderzYS' resize qZbp -q Oct 6 03:47:54 storageqe-109 journal: cryptsetup --size '409600' --header '/tmp/testheaderzYS' resize qZbp -q cryptsetup --header '/tmp/testheaderzYS' status qZbp -q Oct 6 03:48:04 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' status qZbp -q cryptsetup --header '/tmp/testheaderzYS' status qZbp -q Oct 6 03:48:14 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' status qZbp -q cryptsetup status qZbp -q Oct 6 03:48:24 storageqe-109 journal: cryptsetup status qZbp -q cryptsetup --header '/tmp/testheaderzYS' luksSuspend qZbp -q Oct 6 03:48:34 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' luksSuspend qZbp -q cryptsetup --header '/tmp/testheaderzYS' luksResume qZbp -q Oct 6 03:48:44 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' luksResume qZbp -q INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --type 'luks1' --key-slot '5' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' luksAddKey _fake_dev_ /tmp/testfilePEo -q Oct 6 03:48:55 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:48:55 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:48:55 storageqe-109 journal: cryptsetup --type 'luks1' --key-slot '5' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderzYS' luksAddKey _fake_dev_ /tmp/testfilePEo -q cryptsetup --header '/tmp/testheaderzYS' luksDump _fake_dev_ -q Oct 6 03:49:05 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' luksDump _fake_dev_ -q cryptsetup --header '/tmp/testheaderzYS' luksDump _fake_dev_ -q Oct 6 03:49:15 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' luksDump _fake_dev_ -q cryptsetup --header '/tmp/testheaderzYS' luksKillSlot _fake_dev_ 5 -q Oct 6 03:49:25 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' luksKillSlot _fake_dev_ 5 -q cryptsetup --header '/tmp/testheaderzYS' luksDump _fake_dev_ -q Oct 6 03:49:35 storageqe-109 journal: cryptsetup --header '/tmp/testheaderzYS' luksDump _fake_dev_ -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' luksFormat /dev/mapper/npo2linear /tmp/testfileVvW -q Oct 6 03:49:45 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' luksFormat /dev/mapper/npo2linear /tmp/testfileVvW -q cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q Oct 6 03:49:55 storageqe-109 udisksd[5174]: Error getting '/dev/dm-3' metadata_size: Unknown or unsupported LUKS version (g-bd-crypto-error-quark, 0) Oct 6 03:49:55 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q cryptsetup repair /dev/mapper/npo2linear -q Oct 6 03:50:05 storageqe-109 journal: cryptsetup repair /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q Oct 6 03:50:16 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:50:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.b15c8t8vmount_test with fs xfs Oct 6 03:50:36 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f5c166b4-3742-4b03-b98a-29ae3e1b369e Oct 6 03:50:36 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:50:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b15c8t8vmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:50:41 storageqe-109 systemd[1]: tmp-libblockdev.b15c8t8vmount_test.mount: Deactivated successfully. Oct 6 03:50:41 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f5c166b4-3742-4b03-b98a-29ae3e1b369e Oct 6 03:50:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:50:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1pvu2s87mount_test with fs ext4 Oct 6 03:50:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5d74cd7f-08bc-4525-b965-23e122a2b52d r/w with ordered data mode. Quota mode: none. Oct 6 03:50:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1pvu2s87mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:50:56 storageqe-109 systemd[1]: tmp-libblockdev.1pvu2s87mount_test.mount: Deactivated successfully. Oct 6 03:50:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5d74cd7f-08bc-4525-b965-23e122a2b52d. Oct 6 03:50:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:50:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cs82f1efmount_test with fs ext3 Oct 6 03:51:06 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:51:06 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fdaa97b4-b300-4b53-ace8-a3d0c9c0532d r/w with ordered data mode. Quota mode: none. Oct 6 03:51:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cs82f1efmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:51:11 storageqe-109 systemd[1]: tmp-libblockdev.cs82f1efmount_test.mount: Deactivated successfully. Oct 6 03:51:11 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fdaa97b4-b300-4b53-ace8-a3d0c9c0532d. Oct 6 03:51:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:51:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.seln2nnhmount_test with fs ext2 Oct 6 03:51:21 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:51:21 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8403d3f6-b97a-4c96-9d50-62bf4abd9e73 r/w without journal. Quota mode: none. Oct 6 03:51:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.seln2nnhmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp Oct 6 03:51:26 storageqe-109 systemd[1]: tmp-libblockdev.seln2nnhmount_test.mount: Deactivated successfully. Oct 6 03:51:26 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8403d3f6-b97a-4c96-9d50-62bf4abd9e73. Oct 6 03:51:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:51:26 storageqe-109 INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --hash 'sha256' --cipher 'aes-ecb' luksFormat /dev/mapper/npo2linear /tmp/testfileVvW -q Oct 6 03:51:26 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:51:26 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --hash 'sha256' --cipher 'aes-ecb' luksFormat /dev/mapper/npo2linear /tmp/testfileVvW -q cryptsetup repair /dev/mapper/npo2linear -q Oct 6 03:51:36 storageqe-109 journal: cryptsetup repair /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q Oct 6 03:51:47 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileVvW' open /dev/mapper/npo2linear qZbp -q INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:51:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.nr2943fymount_test with fs xfs Oct 6 03:52:07 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 2ea2a3d0-1d90-408e-b072-945871e02189 Oct 6 03:52:07 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:52:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nr2943fymount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:52:12 storageqe-109 systemd[1]: tmp-libblockdev.nr2943fymount_test.mount: Deactivated successfully. Oct 6 03:52:12 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 2ea2a3d0-1d90-408e-b072-945871e02189 Oct 6 03:52:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs xfs in remove_crypt Oct 6 03:52:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pvxpb74tmount_test with fs ext4 Oct 6 03:52:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 498c1b06-18b9-428f-8266-502aedb88981 r/w with ordered data mode. Quota mode: none. Oct 6 03:52:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pvxpb74tmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:52:27 storageqe-109 systemd[1]: tmp-libblockdev.pvxpb74tmount_test.mount: Deactivated successfully. Oct 6 03:52:27 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 498c1b06-18b9-428f-8266-502aedb88981. Oct 6 03:52:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext4 in remove_crypt Oct 6 03:52:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.o57uqrc8mount_test with fs ext3 Oct 6 03:52:37 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:52:37 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 729549e2-6017-4c32-8bab-edd75c89d866 r/w with ordered data mode. Quota mode: none. Oct 6 03:52:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.o57uqrc8mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:52:42 storageqe-109 systemd[1]: tmp-libblockdev.o57uqrc8mount_test.mount: Deactivated successfully. Oct 6 03:52:42 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 729549e2-6017-4c32-8bab-edd75c89d866. Oct 6 03:52:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext3 in remove_crypt Oct 6 03:52:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xqm61o7fmount_test with fs ext2 Oct 6 03:52:52 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:52:52 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 391f7c11-b18f-4d43-bfca-e493ece5633a r/w without journal. Quota mode: none. Oct 6 03:52:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xqm61o7fmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt INFO: remove crypt device qZbp INFO: finishe the remove crypt device qZbp cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear /tmp/testfilePEo -q Oct 6 03:52:57 storageqe-109 systemd[1]: tmp-libblockdev.xqm61o7fmount_test.mount: Deactivated successfully. Oct 6 03:52:57 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 391f7c11-b18f-4d43-bfca-e493ece5633a. Oct 6 03:52:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/qZbp and fs ext2 in remove_crypt Oct 6 03:52:57 storageqe-109 INFO: remove crypt device qZbp Oct 6 03:52:57 storageqe-109 INFO: finishe the remove crypt device qZbp Oct 6 03:52:57 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear /tmp/testfilePEo -q cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --key-file '/tmp/testfilePEo' luksAddKey /dev/mapper/npo2linear /tmp/testfileVvW -q Oct 6 03:53:07 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --key-file '/tmp/testfilePEo' luksAddKey /dev/mapper/npo2linear /tmp/testfileVvW -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:53:17 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:53:28 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksErase /dev/mapper/npo2linear -q Oct 6 03:53:38 storageqe-109 journal: cryptsetup luksErase /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:53:48 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:53:58 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_compat_test[npo2_linear] #### Oct 6 03:54:13 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:54:13 storageqe-109 INFO: #### END test_compat_test[npo2_linear] #### Oct 6 03:54:14 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:54:14 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 03:54:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 03:54:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 03:54:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 03:54:26 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_compat_test2[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:54:31 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 03:54:31 storageqe-109 INFO: #### will start test_compat_test2[npo2_linear] ##### Oct 6 03:54:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 03:54:36 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 03:54:36 storageqe-109 stratisd[4947]: [2025-10-06T07:54:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:54:36 storageqe-109 stratisd[4947]: [2025-10-06T07:54:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:54:45 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 03:54:46 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 03:54:46 storageqe-109 stratisd[4947]: [2025-10-06T07:54:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:54:46 storageqe-109 stratisd[4947]: [2025-10-06T07:54:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 03:54:56 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 03:55:07 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 03:55:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.wj1x9vgumount_test with fs xfs Oct 6 03:55:27 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 7e8efe9c-9c9c-44be-9d8a-d33080f01ca7 Oct 6 03:55:27 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 03:55:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wj1x9vgumount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 03:55:31 storageqe-109 systemd[1]: tmp-libblockdev.wj1x9vgumount_test.mount: Deactivated successfully. Oct 6 03:55:31 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 7e8efe9c-9c9c-44be-9d8a-d33080f01ca7 Oct 6 03:55:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 03:55:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2e_28485mount_test with fs ext4 Oct 6 03:55:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d5927d55-4cec-4aae-8d19-15d262ad864d r/w with ordered data mode. Quota mode: none. Oct 6 03:55:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2e_28485mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 03:55:46 storageqe-109 systemd[1]: tmp-libblockdev.2e_28485mount_test.mount: Deactivated successfully. Oct 6 03:55:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d5927d55-4cec-4aae-8d19-15d262ad864d. Oct 6 03:55:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 03:55:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wtm_nghhmount_test with fs ext3 Oct 6 03:55:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 03:55:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 67500958-6da6-4abb-b564-4099c8e93909 r/w with ordered data mode. Quota mode: none. Oct 6 03:55:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wtm_nghhmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 03:56:01 storageqe-109 systemd[1]: tmp-libblockdev.wtm_nghhmount_test.mount: Deactivated successfully. Oct 6 03:56:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 67500958-6da6-4abb-b564-4099c8e93909. Oct 6 03:56:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 03:56:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h41cxrhwmount_test with fs ext2 Oct 6 03:56:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 03:56:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1300f47a-622d-49b0-b29a-c069453d471c r/w without journal. Quota mode: none. Oct 6 03:56:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h41cxrhwmount_test with fs ext2 Oct 6 03:56:16 storageqe-109 systemd[1]: tmp-libblockdev.h41cxrhwmount_test.mount: Deactivated successfully. Oct 6 03:56:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1300f47a-622d-49b0-b29a-c069453d471c. INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '1' luksFormat /dev/mapper/npo2linear -q Oct 6 03:56:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 03:56:16 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 03:56:16 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 03:56:16 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16385' luksFormat /dev/mapper/npo2linear -q Oct 6 03:56:26 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16385' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '32' luksFormat /dev/mapper/npo2linear -q Oct 6 03:56:36 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '32' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --align-payload '16384' luksFormat /dev/mapper/npo2linear -q Oct 6 03:56:46 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --align-payload '16384' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' luksFormat /dev/mapper/npo2linear -q Oct 6 03:56:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' luksFormat /dev/mapper/npo2linear -q Oct 6 03:56:57 storageqe-109 stratisd[4947]: [2025-10-06T07:56:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:56:57 storageqe-109 stratisd[4947]: [2025-10-06T07:56:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:57:07 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --sector-size '1024' luksFormat /dev/mapper/npo2linear -q Oct 6 03:57:17 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --sector-size '1024' luksFormat /dev/mapper/npo2linear -q Oct 6 03:57:17 storageqe-109 stratisd[4947]: [2025-10-06T07:57:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:57:17 storageqe-109 stratisd[4947]: [2025-10-06T07:57:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:57:27 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '80000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q Oct 6 03:57:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '80000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '511' luksFormat /dev/mapper/npo2linear -q Oct 6 03:57:47 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '511' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '256' luksFormat /dev/mapper/npo2linear -q Oct 6 03:57:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '256' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '8192' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:07 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:17 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:17 storageqe-109 stratisd[4947]: [2025-10-06T07:58:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:58:17 storageqe-109 stratisd[4947]: [2025-10-06T07:58:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:27 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:27 storageqe-109 stratisd[4947]: [2025-10-06T07:58:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:58:27 storageqe-109 stratisd[4947]: [2025-10-06T07:58:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:37 storageqe-109 stratisd[4947]: [2025-10-06T07:58:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:58:37 storageqe-109 stratisd[4947]: [2025-10-06T07:58:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:47 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:47 storageqe-109 stratisd[4947]: [2025-10-06T07:58:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:58:47 storageqe-109 stratisd[4947]: [2025-10-06T07:58:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 03:58:57 storageqe-109 stratisd[4947]: [2025-10-06T07:58:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:58:57 storageqe-109 stratisd[4947]: [2025-10-06T07:58:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:07 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:07 storageqe-109 stratisd[4947]: [2025-10-06T07:59:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:59:07 storageqe-109 stratisd[4947]: [2025-10-06T07:59:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:59:17 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:27 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:28 storageqe-109 stratisd[4947]: [2025-10-06T07:59:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:59:28 storageqe-109 stratisd[4947]: [2025-10-06T07:59:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:38 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:38 storageqe-109 stratisd[4947]: [2025-10-06T07:59:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:59:38 storageqe-109 stratisd[4947]: [2025-10-06T07:59:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 03:59:48 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:58 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 6 03:59:58 storageqe-109 stratisd[4947]: [2025-10-06T07:59:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 03:59:58 storageqe-109 stratisd[4947]: [2025-10-06T07:59:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --hash 'sha512' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 6 04:00:08 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --hash 'sha512' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 6 04:00:08 storageqe-109 stratisd[4947]: [2025-10-06T08:00:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:00:08 storageqe-109 stratisd[4947]: [2025-10-06T08:00:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:00:18 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear --dump-json-metadata -q Oct 6 04:00:28 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear --dump-json-metadata -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:00:38 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:00:48 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:00:58 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:00:58 storageqe-109 stratisd[4947]: [2025-10-06T08:00:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:00:58 storageqe-109 stratisd[4947]: [2025-10-06T08:00:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:01:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.uo6q9a3pmount_test with fs xfs Oct 6 04:01:18 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem a50118c3-dfca-40bf-a85d-eee530aabb2d Oct 6 04:01:18 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:01:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uo6q9a3pmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:01:23 storageqe-109 systemd[1]: tmp-libblockdev.uo6q9a3pmount_test.mount: Deactivated successfully. Oct 6 04:01:23 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem a50118c3-dfca-40bf-a85d-eee530aabb2d Oct 6 04:01:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:01:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vb_7tx1tmount_test with fs ext4 Oct 6 04:01:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 39cac2c9-0553-4e76-af04-54781dcde022 r/w with ordered data mode. Quota mode: none. Oct 6 04:01:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vb_7tx1tmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:01:38 storageqe-109 systemd[1]: tmp-libblockdev.vb_7tx1tmount_test.mount: Deactivated successfully. Oct 6 04:01:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 39cac2c9-0553-4e76-af04-54781dcde022. Oct 6 04:01:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:01:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.skfrw0ermount_test with fs ext3 Oct 6 04:01:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:01:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0790b19c-1e88-48d7-b39b-e62e3e42353a r/w with ordered data mode. Quota mode: none. Oct 6 04:01:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.skfrw0ermount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:01:53 storageqe-109 systemd[1]: tmp-libblockdev.skfrw0ermount_test.mount: Deactivated successfully. Oct 6 04:01:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0790b19c-1e88-48d7-b39b-e62e3e42353a. Oct 6 04:01:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:01:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dl41e7gwmount_test with fs ext2 Oct 6 04:02:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:02:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 69816638-8f11-4248-9b3e-745ba4807e63 r/w without journal. Quota mode: none. Oct 6 04:02:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dl41e7gwmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD Oct 6 04:02:08 storageqe-109 systemd[1]: tmp-libblockdev.dl41e7gwmount_test.mount: Deactivated successfully. Oct 6 04:02:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 69816638-8f11-4248-9b3e-745ba4807e63. Oct 6 04:02:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:02:08 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:02:08 storageqe-109 INFO: finishe the remove crypt device URchgyJekD cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:02:08 storageqe-109 stratisd[4947]: [2025-10-06T08:02:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:02:08 storageqe-109 stratisd[4947]: [2025-10-06T08:02:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:02:08 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 6 04:02:18 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 6 04:02:28 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 6 04:02:28 storageqe-109 stratisd[4947]: [2025-10-06T08:02:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:02:28 storageqe-109 stratisd[4947]: [2025-10-06T08:02:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:02:38 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:02:48 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:02:48 storageqe-109 stratisd[4947]: [2025-10-06T08:02:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:02:48 storageqe-109 stratisd[4947]: [2025-10-06T08:02:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:02:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.7aorbsgnmount_test with fs xfs Oct 6 04:03:09 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem fc3385a5-1822-4835-b3d5-cef1205b9498 Oct 6 04:03:09 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:03:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7aorbsgnmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:03:13 storageqe-109 systemd[1]: tmp-libblockdev.7aorbsgnmount_test.mount: Deactivated successfully. Oct 6 04:03:13 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem fc3385a5-1822-4835-b3d5-cef1205b9498 Oct 6 04:03:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:03:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.py9j9ehrmount_test with fs ext4 Oct 6 04:03:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 26af042e-299f-4027-8517-3792403cd9f4 r/w with ordered data mode. Quota mode: none. Oct 6 04:03:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.py9j9ehrmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:03:28 storageqe-109 systemd[1]: tmp-libblockdev.py9j9ehrmount_test.mount: Deactivated successfully. Oct 6 04:03:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 26af042e-299f-4027-8517-3792403cd9f4. Oct 6 04:03:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:03:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._c_9v657mount_test with fs ext3 Oct 6 04:03:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:03:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 040cc978-6a43-4fd3-8097-b093daba283d r/w with ordered data mode. Quota mode: none. Oct 6 04:03:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev._c_9v657mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:03:44 storageqe-109 systemd[1]: tmp-libblockdev._c_9v657mount_test.mount: Deactivated successfully. Oct 6 04:03:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 040cc978-6a43-4fd3-8097-b093daba283d. Oct 6 04:03:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:03:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y6awagd_mount_test with fs ext2 Oct 6 04:03:54 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:03:54 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dd1cdf60-4715-4678-920b-64644077669c r/w without journal. Quota mode: none. Oct 6 04:03:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y6awagd_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:03:59 storageqe-109 systemd[1]: tmp-libblockdev.y6awagd_mount_test.mount: Deactivated successfully. Oct 6 04:03:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dd1cdf60-4715-4678-920b-64644077669c. Oct 6 04:03:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:03:59 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:03:59 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:03:59 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:03:59 storageqe-109 stratisd[4947]: [2025-10-06T08:03:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:03:59 storageqe-109 stratisd[4947]: [2025-10-06T08:03:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:04:09 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:04:09 storageqe-109 stratisd[4947]: [2025-10-06T08:04:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:04:09 storageqe-109 stratisd[4947]: [2025-10-06T08:04:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:04:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.qs81jva1mount_test with fs xfs Oct 6 04:04:29 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 169766b4-8d3b-4482-9172-3b2a18e1e820 Oct 6 04:04:29 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:04:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qs81jva1mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:04:34 storageqe-109 systemd[1]: tmp-libblockdev.qs81jva1mount_test.mount: Deactivated successfully. Oct 6 04:04:34 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 169766b4-8d3b-4482-9172-3b2a18e1e820 Oct 6 04:04:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:04:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q1m4r_thmount_test with fs ext4 Oct 6 04:04:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 12b974bd-ec10-46cd-9899-ac8d88c971a2 r/w with ordered data mode. Quota mode: none. Oct 6 04:04:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q1m4r_thmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:04:49 storageqe-109 systemd[1]: tmp-libblockdev.q1m4r_thmount_test.mount: Deactivated successfully. Oct 6 04:04:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 12b974bd-ec10-46cd-9899-ac8d88c971a2. Oct 6 04:04:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:04:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hsexqklsmount_test with fs ext3 Oct 6 04:04:59 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:04:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem edc9263a-4689-411b-a78a-c96ccfc935d3 r/w with ordered data mode. Quota mode: none. Oct 6 04:04:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hsexqklsmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:05:04 storageqe-109 systemd[1]: tmp-libblockdev.hsexqklsmount_test.mount: Deactivated successfully. Oct 6 04:05:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem edc9263a-4689-411b-a78a-c96ccfc935d3. Oct 6 04:05:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:05:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fgotr0tomount_test with fs ext2 Oct 6 04:05:14 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:05:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c0004817-4201-4b7d-8a9b-4089bd22c3e6 r/w without journal. Quota mode: none. Oct 6 04:05:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fgotr0tomount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --key-file '/tmp/testfileQzG' luksKillSlot /dev/mapper/npo2linear 0 -q Oct 6 04:05:19 storageqe-109 systemd[1]: tmp-libblockdev.fgotr0tomount_test.mount: Deactivated successfully. Oct 6 04:05:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c0004817-4201-4b7d-8a9b-4089bd22c3e6. Oct 6 04:05:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:05:19 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:05:19 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:05:19 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' luksKillSlot /dev/mapper/npo2linear 0 -q Oct 6 04:05:19 storageqe-109 stratisd[4947]: [2025-10-06T08:05:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:05:19 storageqe-109 stratisd[4947]: [2025-10-06T08:05:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:05:29 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:05:39 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:05:39 storageqe-109 stratisd[4947]: [2025-10-06T08:05:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:05:39 storageqe-109 stratisd[4947]: [2025-10-06T08:05:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:05:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.gczzr3_kmount_test with fs xfs Oct 6 04:05:59 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 087691a0-412b-4fe8-abed-7710a89b4ba5 Oct 6 04:05:59 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:05:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gczzr3_kmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:06:04 storageqe-109 systemd[1]: tmp-libblockdev.gczzr3_kmount_test.mount: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:06:04 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 087691a0-412b-4fe8-abed-7710a89b4ba5 Oct 6 04:06:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:06:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.awg98uvjmount_test with fs ext4 Oct 6 04:06:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7df91f40-b650-46ab-a288-11949c4acbf5 r/w with ordered data mode. Quota mode: none. Oct 6 04:06:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.awg98uvjmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:06:19 storageqe-109 systemd[1]: tmp-libblockdev.awg98uvjmount_test.mount: Deactivated successfully. Oct 6 04:06:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7df91f40-b650-46ab-a288-11949c4acbf5. Oct 6 04:06:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:06:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.17032ipymount_test with fs ext3 Oct 6 04:06:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:06:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e5f535f3-5971-4b2f-be28-de0bc55a7ec4 r/w with ordered data mode. Quota mode: none. Oct 6 04:06:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.17032ipymount_test with fs ext3 Oct 6 04:06:34 storageqe-109 systemd[1]: tmp-libblockdev.17032ipymount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:06:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e5f535f3-5971-4b2f-be28-de0bc55a7ec4. Oct 6 04:06:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:06:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wri3r8bgmount_test with fs ext2 Oct 6 04:06:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:06:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 44ff9365-f67d-47a1-854e-3e24328e8f71 r/w without journal. Quota mode: none. Oct 6 04:06:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wri3r8bgmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:06:49 storageqe-109 systemd[1]: tmp-libblockdev.wri3r8bgmount_test.mount: Deactivated successfully. Oct 6 04:06:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 44ff9365-f67d-47a1-854e-3e24328e8f71. Oct 6 04:06:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:06:49 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:06:49 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:06:49 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:06:49 storageqe-109 stratisd[4947]: [2025-10-06T08:06:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:06:49 storageqe-109 stratisd[4947]: [2025-10-06T08:06:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksKillSlot /dev/mapper/npo2linear 0 -q Oct 6 04:06:59 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 0 -q Oct 6 04:06:59 storageqe-109 stratisd[4947]: [2025-10-06T08:06:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:06:59 storageqe-109 stratisd[4947]: [2025-10-06T08:06:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:07:09 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' luksFormat /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:07:19 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' luksFormat /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:07:19 storageqe-109 stratisd[4947]: [2025-10-06T08:07:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:07:19 storageqe-109 stratisd[4947]: [2025-10-06T08:07:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:07:29 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:07:29 storageqe-109 stratisd[4947]: [2025-10-06T08:07:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:07:29 storageqe-109 stratisd[4947]: [2025-10-06T08:07:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:07:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.cmyf2o4wmount_test with fs xfs Oct 6 04:07:49 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 04:07:49 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f2dcebb1-8708-47dc-a2d3-9f7d7d878407 Oct 6 04:07:49 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:07:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cmyf2o4wmount_test with fs xfs Oct 6 04:07:49 storageqe-109 dnf[520961]: Updating Subscription Management repositories. Oct 6 04:07:49 storageqe-109 dnf[520961]: Unable to read consumer identity Oct 6 04:07:49 storageqe-109 dnf[520961]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 04:07:49 storageqe-109 dnf[520961]: Metadata cache refreshed recently. Oct 6 04:07:49 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 04:07:49 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 04:07:54 storageqe-109 systemd[1]: tmp-libblockdev.cmyf2o4wmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:07:54 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f2dcebb1-8708-47dc-a2d3-9f7d7d878407 Oct 6 04:07:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:07:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.k5rxq7g1mount_test with fs ext4 Oct 6 04:08:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 55a48311-8090-40b3-830e-6ec71bd08f20 r/w with ordered data mode. Quota mode: none. Oct 6 04:08:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k5rxq7g1mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:08:09 storageqe-109 systemd[1]: tmp-libblockdev.k5rxq7g1mount_test.mount: Deactivated successfully. Oct 6 04:08:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 55a48311-8090-40b3-830e-6ec71bd08f20. Oct 6 04:08:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:08:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:08:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.kbvjkjp9mount_test with fs ext3 Oct 6 04:08:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fad3b502-d2ac-4d61-a90c-ca47c8577380 r/w with ordered data mode. Quota mode: none. Oct 6 04:08:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kbvjkjp9mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:08:24 storageqe-109 systemd[1]: tmp-libblockdev.kbvjkjp9mount_test.mount: Deactivated successfully. Oct 6 04:08:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fad3b502-d2ac-4d61-a90c-ca47c8577380. Oct 6 04:08:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:08:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g5s_zu28mount_test with fs ext2 Oct 6 04:08:34 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:08:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b2f9bebb-3cf1-4880-94fd-3e759ffcba6a r/w without journal. Quota mode: none. Oct 6 04:08:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g5s_zu28mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:08:39 storageqe-109 systemd[1]: tmp-libblockdev.g5s_zu28mount_test.mount: Deactivated successfully. Oct 6 04:08:39 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b2f9bebb-3cf1-4880-94fd-3e759ffcba6a. Oct 6 04:08:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:08:39 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:08:39 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:08:39 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:08:39 storageqe-109 stratisd[4947]: [2025-10-06T08:08:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:08:39 storageqe-109 stratisd[4947]: [2025-10-06T08:08:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:08:50 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:08:50 storageqe-109 stratisd[4947]: [2025-10-06T08:08:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:08:50 storageqe-109 stratisd[4947]: [2025-10-06T08:08:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/URchgyJekD -q Oct 6 04:09:00 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/URchgyJekD -q Oct 6 04:09:00 storageqe-109 stratisd[4947]: [2025-10-06T08:09:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:09:00 storageqe-109 stratisd[4947]: [2025-10-06T08:09:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/URchgyJekD dummy -q Oct 6 04:09:10 storageqe-109 journal: cryptsetup open /dev/mapper/URchgyJekD dummy -q Oct 6 04:09:10 storageqe-109 stratisd[4947]: [2025-10-06T08:09:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:09:10 storageqe-109 stratisd[4947]: [2025-10-06T08:09:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 6 04:09:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.lmtw24slmount_test with fs xfs Oct 6 04:09:30 storageqe-109 kernel: XFS (dm-5): Mounting V5 Filesystem c9ad847c-0bca-4d51-ba85-4eebc0b9a890 Oct 6 04:09:30 storageqe-109 kernel: XFS (dm-5): Ending clean mount Oct 6 04:09:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lmtw24slmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 6 04:09:35 storageqe-109 systemd[1]: tmp-libblockdev.lmtw24slmount_test.mount: Deactivated successfully. Oct 6 04:09:35 storageqe-109 kernel: XFS (dm-5): Unmounting Filesystem c9ad847c-0bca-4d51-ba85-4eebc0b9a890 Oct 6 04:09:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 6 04:09:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jxllz2h4mount_test with fs ext4 Oct 6 04:09:45 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 0d803e5e-b8b8-4b55-a733-dcc070e025ce r/w with ordered data mode. Quota mode: none. Oct 6 04:09:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jxllz2h4mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 6 04:09:50 storageqe-109 systemd[1]: tmp-libblockdev.jxllz2h4mount_test.mount: Deactivated successfully. Oct 6 04:09:50 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 0d803e5e-b8b8-4b55-a733-dcc070e025ce. Oct 6 04:09:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 6 04:09:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1drh7pxymount_test with fs ext3 Oct 6 04:10:00 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext3 file system using the ext4 subsystem Oct 6 04:10:00 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem a31e6f90-4618-44ff-8c38-7028ddb18c9e r/w with ordered data mode. Quota mode: none. Oct 6 04:10:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1drh7pxymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 6 04:10:06 storageqe-109 systemd[1]: tmp-libblockdev.1drh7pxymount_test.mount: Deactivated successfully. Oct 6 04:10:06 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem a31e6f90-4618-44ff-8c38-7028ddb18c9e. Oct 6 04:10:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 6 04:10:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.aoowi6g6mount_test with fs ext2 Oct 6 04:10:16 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext2 file system using the ext4 subsystem Oct 6 04:10:16 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 55c10003-c63a-429e-8fd7-24c77f76a3ab r/w without journal. Quota mode: none. Oct 6 04:10:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.aoowi6g6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: remove crypt device dummy INFO: finishe the remove crypt device dummy INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:10:21 storageqe-109 systemd[1]: tmp-libblockdev.aoowi6g6mount_test.mount: Deactivated successfully. Oct 6 04:10:21 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 55c10003-c63a-429e-8fd7-24c77f76a3ab. Oct 6 04:10:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 6 04:10:21 storageqe-109 INFO: remove crypt device dummy Oct 6 04:10:21 storageqe-109 INFO: finishe the remove crypt device dummy Oct 6 04:10:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.0ps4687jmount_test with fs xfs Oct 6 04:10:32 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 636800b5-252f-4a14-8064-1c3b970e20c8 Oct 6 04:10:32 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:10:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0ps4687jmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:10:36 storageqe-109 systemd[1]: tmp-libblockdev.0ps4687jmount_test.mount: Deactivated successfully. Oct 6 04:10:36 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 636800b5-252f-4a14-8064-1c3b970e20c8 Oct 6 04:10:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:10:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gbzbw46imount_test with fs ext4 Oct 6 04:10:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e0b8b917-2bd8-416f-a6f0-a826cbda8e0d r/w with ordered data mode. Quota mode: none. Oct 6 04:10:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gbzbw46imount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:10:51 storageqe-109 systemd[1]: tmp-libblockdev.gbzbw46imount_test.mount: Deactivated successfully. Oct 6 04:10:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e0b8b917-2bd8-416f-a6f0-a826cbda8e0d. Oct 6 04:10:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:10:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.od7x9tsfmount_test with fs ext3 Oct 6 04:11:01 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:11:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 62ba957b-5dd7-485e-9256-8045bfeaa2ea r/w with ordered data mode. Quota mode: none. Oct 6 04:11:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.od7x9tsfmount_test with fs ext3 Oct 6 04:11:06 storageqe-109 systemd[1]: tmp-libblockdev.od7x9tsfmount_test.mount: Deactivated successfully. Oct 6 04:11:06 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 62ba957b-5dd7-485e-9256-8045bfeaa2ea. INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:11:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:11:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.a184_mx8mount_test with fs ext2 Oct 6 04:11:16 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:11:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b9a69383-ff8f-4f5d-9064-3f61afa9220a r/w without journal. Quota mode: none. Oct 6 04:11:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a184_mx8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD Oct 6 04:11:21 storageqe-109 systemd[1]: tmp-libblockdev.a184_mx8mount_test.mount: Deactivated successfully. Oct 6 04:11:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b9a69383-ff8f-4f5d-9064-3f61afa9220a. Oct 6 04:11:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:11:21 storageqe-109 INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:11:21 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:11:21 storageqe-109 stratisd[4947]: [2025-10-06T08:11:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:11:21 storageqe-109 stratisd[4947]: [2025-10-06T08:11:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:11:21 storageqe-109 stratisd[4947]: [2025-10-06T08:11:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:11:21 storageqe-109 stratisd[4947]: [2025-10-06T08:11:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:11:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.x4bs4rx4mount_test with fs xfs Oct 6 04:11:31 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f4f1612a-7b5d-4a9a-b927-d45a5ac8410c Oct 6 04:11:31 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:11:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x4bs4rx4mount_test with fs xfs Oct 6 04:11:36 storageqe-109 systemd[1]: tmp-libblockdev.x4bs4rx4mount_test.mount: Deactivated successfully. Oct 6 04:11:36 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f4f1612a-7b5d-4a9a-b927-d45a5ac8410c INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:11:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:11:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.w9v2707cmount_test with fs ext4 Oct 6 04:11:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8c2288e3-91a4-48da-a6d0-48ee6d9b525f r/w with ordered data mode. Quota mode: none. Oct 6 04:11:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.w9v2707cmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:11:51 storageqe-109 systemd[1]: tmp-libblockdev.w9v2707cmount_test.mount: Deactivated successfully. Oct 6 04:11:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8c2288e3-91a4-48da-a6d0-48ee6d9b525f. Oct 6 04:11:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:11:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.b2f2q5bwmount_test with fs ext3 Oct 6 04:12:01 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:12:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b7a406f4-ec91-4e75-8432-f163bee8dcd6 r/w with ordered data mode. Quota mode: none. Oct 6 04:12:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b2f2q5bwmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:12:06 storageqe-109 systemd[1]: tmp-libblockdev.b2f2q5bwmount_test.mount: Deactivated successfully. Oct 6 04:12:06 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b7a406f4-ec91-4e75-8432-f163bee8dcd6. Oct 6 04:12:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:12:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2gdd_lnfmount_test with fs ext2 Oct 6 04:12:16 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:12:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f159e83c-a0da-46b0-86a2-75346e66664f r/w without journal. Quota mode: none. Oct 6 04:12:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2gdd_lnfmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD Oct 6 04:12:21 storageqe-109 systemd[1]: tmp-libblockdev.2gdd_lnfmount_test.mount: Deactivated successfully. Oct 6 04:12:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f159e83c-a0da-46b0-86a2-75346e66664f. Oct 6 04:12:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:12:21 storageqe-109 INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:12:21 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:12:21 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:12:21 storageqe-109 stratisd[4947]: [2025-10-06T08:12:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:12:21 storageqe-109 stratisd[4947]: [2025-10-06T08:12:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:12:31 storageqe-109 stratisd[4947]: [2025-10-06T08:12:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:12:31 storageqe-109 stratisd[4947]: [2025-10-06T08:12:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:12:31 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --key-file '-' open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:12:41 storageqe-109 journal: cryptsetup --key-file '-' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --pbkdf 'pbkdf2' --key-file '-' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileDxg -q Oct 6 04:12:51 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '-' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileDxg -q Oct 6 04:12:51 storageqe-109 stratisd[4947]: [2025-10-06T08:12:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:12:51 storageqe-109 stratisd[4947]: [2025-10-06T08:12:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileDxg' open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:13:02 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileDxg' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:13:12 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileQzG -q Oct 6 04:13:12 storageqe-109 stratisd[4947]: [2025-10-06T08:13:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:13:12 storageqe-109 stratisd[4947]: [2025-10-06T08:13:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:13:22 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear /tmp/testfileDxg -q Oct 6 04:13:32 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear /tmp/testfileDxg -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '4' --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear /tmp/testfileDxg -q Oct 6 04:13:42 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '4' --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear /tmp/testfileDxg -q Oct 6 04:13:42 storageqe-109 stratisd[4947]: [2025-10-06T08:13:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:13:42 storageqe-109 stratisd[4947]: [2025-10-06T08:13:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileDxg' --key-slot '4' open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:13:52 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileDxg' --key-slot '4' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:14:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear -q Oct 6 04:14:12 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear -q Oct 6 04:14:12 storageqe-109 stratisd[4947]: [2025-10-06T08:14:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:14:12 storageqe-109 stratisd[4947]: [2025-10-06T08:14:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:14:22 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-slot '0' open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:14:32 storageqe-109 journal: cryptsetup --key-slot '0' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --key-slot '1' open /dev/mapper/npo2linear --test-passphrase -q Oct 6 04:14:42 storageqe-109 stratisd[4947]: [2025-10-06T08:14:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:14:42 storageqe-109 stratisd[4947]: [2025-10-06T08:14:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:14:42 storageqe-109 journal: cryptsetup --key-slot '1' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:14:52 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:15:02 storageqe-109 stratisd[4947]: [2025-10-06T08:15:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:15:02 storageqe-109 stratisd[4947]: [2025-10-06T08:15:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:15:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:15:12 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:15:22 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:15:32 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:15:32 storageqe-109 stratisd[4947]: [2025-10-06T08:15:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:15:32 storageqe-109 stratisd[4947]: [2025-10-06T08:15:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:15:42 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:15:52 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:16:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:16:12 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileQzG cryptsetup --keyfile-size '1' luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:16:22 storageqe-109 journal: cryptsetup --keyfile-size '1' luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileDxg cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:16:32 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:16:42 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear /tmp/testfileDxg -q Oct 6 04:16:52 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear /tmp/testfileDxg -q Oct 6 04:16:52 storageqe-109 stratisd[4947]: [2025-10-06T08:16:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:16:52 storageqe-109 stratisd[4947]: [2025-10-06T08:16:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:17:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 Oct 6 04:17:12 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 Oct 6 04:17:22 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q Oct 6 04:17:32 storageqe-109 journal: cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q Oct 6 04:17:42 storageqe-109 journal: cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:17:53 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear 2 -q Oct 6 04:18:03 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 2 -q Oct 6 04:18:03 storageqe-109 stratisd[4947]: [2025-10-06T08:18:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:18:03 storageqe-109 stratisd[4947]: [2025-10-06T08:18:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:18:13 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q Oct 6 04:18:23 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q Oct 6 04:18:23 storageqe-109 stratisd[4947]: [2025-10-06T08:18:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:18:23 storageqe-109 stratisd[4947]: [2025-10-06T08:18:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:18:33 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 6 04:18:43 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 6 04:18:43 storageqe-109 stratisd[4947]: [2025-10-06T08:18:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:18:43 storageqe-109 stratisd[4947]: [2025-10-06T08:18:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:18:53 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear -q Oct 6 04:19:03 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear -q Oct 6 04:19:03 storageqe-109 stratisd[4947]: [2025-10-06T08:19:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:03 storageqe-109 stratisd[4947]: [2025-10-06T08:19:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:19:13 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:19:13 storageqe-109 stratisd[4947]: [2025-10-06T08:19:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:13 storageqe-109 stratisd[4947]: [2025-10-06T08:19:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '16000' resize URchgyJekD -q Oct 6 04:19:23 storageqe-109 journal: cryptsetup --size '16000' resize URchgyJekD -q cryptsetup --size '1600000' resize URchgyJekD -q Oct 6 04:19:33 storageqe-109 journal: cryptsetup --size '1600000' resize URchgyJekD -q Oct 6 04:19:33 storageqe-109 stratisd[4947]: [2025-10-06T08:19:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:33 storageqe-109 stratisd[4947]: [2025-10-06T08:19:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:33 storageqe-109 stratisd[4947]: [2025-10-06T08:19:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:33 storageqe-109 stratisd[4947]: [2025-10-06T08:19:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:19:43 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup --device-size '81920' resize URchgyJekD -q Oct 6 04:19:53 storageqe-109 journal: cryptsetup --device-size '81920' resize URchgyJekD -q Oct 6 04:19:53 storageqe-109 stratisd[4947]: [2025-10-06T08:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:53 storageqe-109 stratisd[4947]: [2025-10-06T08:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:53 storageqe-109 stratisd[4947]: [2025-10-06T08:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:19:53 storageqe-109 stratisd[4947]: [2025-10-06T08:19:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:20:03 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup --device-size '800M' resize URchgyJekD -q Oct 6 04:20:13 storageqe-109 journal: cryptsetup --device-size '800M' resize URchgyJekD -q Oct 6 04:20:13 storageqe-109 stratisd[4947]: [2025-10-06T08:20:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:20:13 storageqe-109 stratisd[4947]: [2025-10-06T08:20:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:20:13 storageqe-109 stratisd[4947]: [2025-10-06T08:20:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:20:13 storageqe-109 stratisd[4947]: [2025-10-06T08:20:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:20:23 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup --device-size '512k' --size '1024' resize URchgyJekD -q Oct 6 04:20:33 storageqe-109 journal: cryptsetup --device-size '512k' --size '1024' resize URchgyJekD -q cryptsetup --device-size '4097' resize URchgyJekD -q Oct 6 04:20:43 storageqe-109 journal: cryptsetup --device-size '4097' resize URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 04:20:53 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:21:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.u_a97m5kmount_test with fs xfs Oct 6 04:21:13 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 981b88b4-b9cc-4409-835b-5dfe66da7241 Oct 6 04:21:13 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:21:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u_a97m5kmount_test with fs xfs Oct 6 04:21:18 storageqe-109 systemd[1]: tmp-libblockdev.u_a97m5kmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:21:18 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 981b88b4-b9cc-4409-835b-5dfe66da7241 Oct 6 04:21:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:21:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._gbra_y8mount_test with fs ext4 Oct 6 04:21:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 301abcbc-8a86-43b6-a4a2-9f0495ee8ac5 r/w with ordered data mode. Quota mode: none. Oct 6 04:21:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev._gbra_y8mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:21:33 storageqe-109 systemd[1]: tmp-libblockdev._gbra_y8mount_test.mount: Deactivated successfully. Oct 6 04:21:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 301abcbc-8a86-43b6-a4a2-9f0495ee8ac5. Oct 6 04:21:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:21:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.l0g9drhhmount_test with fs ext3 Oct 6 04:21:43 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:21:43 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e12b2846-620a-4935-8462-1443d80497a6 r/w with ordered data mode. Quota mode: none. Oct 6 04:21:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l0g9drhhmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:21:48 storageqe-109 systemd[1]: tmp-libblockdev.l0g9drhhmount_test.mount: Deactivated successfully. Oct 6 04:21:48 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e12b2846-620a-4935-8462-1443d80497a6. Oct 6 04:21:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:21:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p6779farmount_test with fs ext2 Oct 6 04:21:58 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:21:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 822bd8e9-a955-49cf-a062-e0448a6631a9 r/w without journal. Quota mode: none. Oct 6 04:21:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p6779farmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup open /dev/mapper/npo2linear URchgyJekD -q --disable-keyring Oct 6 04:22:03 storageqe-109 systemd[1]: tmp-libblockdev.p6779farmount_test.mount: Deactivated successfully. Oct 6 04:22:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 822bd8e9-a955-49cf-a062-e0448a6631a9. Oct 6 04:22:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:22:03 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:22:03 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:22:03 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q --disable-keyring Oct 6 04:22:03 storageqe-109 stratisd[4947]: [2025-10-06T08:22:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:22:03 storageqe-109 stratisd[4947]: [2025-10-06T08:22:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '1600000' resize URchgyJekD -q Oct 6 04:22:13 storageqe-109 journal: cryptsetup --size '1600000' resize URchgyJekD -q Oct 6 04:22:13 storageqe-109 stratisd[4947]: [2025-10-06T08:22:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:22:13 storageqe-109 stratisd[4947]: [2025-10-06T08:22:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:22:13 storageqe-109 stratisd[4947]: [2025-10-06T08:22:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:22:13 storageqe-109 stratisd[4947]: [2025-10-06T08:22:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:22:23 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:22:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.t4htu5u0mount_test with fs xfs Oct 6 04:22:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem d50edc77-8800-4969-be2e-800f720ff197 Oct 6 04:22:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:22:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t4htu5u0mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:22:48 storageqe-109 systemd[1]: tmp-libblockdev.t4htu5u0mount_test.mount: Deactivated successfully. Oct 6 04:22:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem d50edc77-8800-4969-be2e-800f720ff197 Oct 6 04:22:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:22:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.o70n27ocmount_test with fs ext4 Oct 6 04:22:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e6372d74-9b85-4de8-b388-30ceafc13cad r/w with ordered data mode. Quota mode: none. Oct 6 04:22:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.o70n27ocmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:23:03 storageqe-109 systemd[1]: tmp-libblockdev.o70n27ocmount_test.mount: Deactivated successfully. Oct 6 04:23:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e6372d74-9b85-4de8-b388-30ceafc13cad. Oct 6 04:23:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:23:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.sapq_1_lmount_test with fs ext3 Oct 6 04:23:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:23:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a44ce293-6553-4c50-ba1a-41d9797da69e r/w with ordered data mode. Quota mode: none. Oct 6 04:23:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sapq_1_lmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:23:18 storageqe-109 systemd[1]: tmp-libblockdev.sapq_1_lmount_test.mount: Deactivated successfully. Oct 6 04:23:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a44ce293-6553-4c50-ba1a-41d9797da69e. Oct 6 04:23:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:23:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ofqwoi9emount_test with fs ext2 Oct 6 04:23:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:23:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5ff4c942-49b5-4045-b85b-3af2277589e5 r/w without journal. Quota mode: none. Oct 6 04:23:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ofqwoi9emount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:23:33 storageqe-109 systemd[1]: tmp-libblockdev.ofqwoi9emount_test.mount: Deactivated successfully. Oct 6 04:23:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5ff4c942-49b5-4045-b85b-3af2277589e5. Oct 6 04:23:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:23:33 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:23:33 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:23:33 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:23:33 storageqe-109 stratisd[4947]: [2025-10-06T08:23:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:23:33 storageqe-109 stratisd[4947]: [2025-10-06T08:23:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '1600000' resize URchgyJekD -q --disable-keyring Oct 6 04:23:43 storageqe-109 journal: cryptsetup --size '1600000' resize URchgyJekD -q --disable-keyring INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:23:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.12u_hojgmount_test with fs xfs Oct 6 04:24:03 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f8829e65-b114-4ec5-bb3c-bc5bf169ee4b Oct 6 04:24:03 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:24:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.12u_hojgmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:24:08 storageqe-109 systemd[1]: tmp-libblockdev.12u_hojgmount_test.mount: Deactivated successfully. Oct 6 04:24:08 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f8829e65-b114-4ec5-bb3c-bc5bf169ee4b Oct 6 04:24:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:24:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z36bmczgmount_test with fs ext4 Oct 6 04:24:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5abc227d-7ca5-4f9d-ad95-adc6b15c6a4e r/w with ordered data mode. Quota mode: none. Oct 6 04:24:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z36bmczgmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:24:23 storageqe-109 systemd[1]: tmp-libblockdev.z36bmczgmount_test.mount: Deactivated successfully. Oct 6 04:24:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5abc227d-7ca5-4f9d-ad95-adc6b15c6a4e. Oct 6 04:24:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:24:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2qf0pbnrmount_test with fs ext3 Oct 6 04:24:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:24:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 19c66036-669b-424b-98d1-1bfbde06bad6 r/w with ordered data mode. Quota mode: none. Oct 6 04:24:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2qf0pbnrmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:24:38 storageqe-109 systemd[1]: tmp-libblockdev.2qf0pbnrmount_test.mount: Deactivated successfully. Oct 6 04:24:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 19c66036-669b-424b-98d1-1bfbde06bad6. Oct 6 04:24:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:24:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8_cwhyfymount_test with fs ext2 Oct 6 04:24:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:24:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 73e2ef36-ba30-4f17-a6cf-d9618e7ad4f1 r/w without journal. Quota mode: none. Oct 6 04:24:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8_cwhyfymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 04:24:53 storageqe-109 systemd[1]: tmp-libblockdev.8_cwhyfymount_test.mount: Deactivated successfully. Oct 6 04:24:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 73e2ef36-ba30-4f17-a6cf-d9618e7ad4f1. Oct 6 04:24:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:24:53 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:24:53 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:24:53 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 6 04:24:53 storageqe-109 stratisd[4947]: [2025-10-06T08:24:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:24:53 storageqe-109 stratisd[4947]: [2025-10-06T08:24:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:25:03 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:25:03 storageqe-109 stratisd[4947]: [2025-10-06T08:25:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:25:03 storageqe-109 stratisd[4947]: [2025-10-06T08:25:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --device-size '800M' resize URchgyJekD -q Oct 6 04:25:13 storageqe-109 journal: cryptsetup --device-size '800M' resize URchgyJekD -q Oct 6 04:25:13 storageqe-109 stratisd[4947]: [2025-10-06T08:25:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:25:13 storageqe-109 stratisd[4947]: [2025-10-06T08:25:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:25:13 storageqe-109 stratisd[4947]: [2025-10-06T08:25:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:25:13 storageqe-109 stratisd[4947]: [2025-10-06T08:25:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:25:23 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup --device-size '2049s' resize URchgyJekD -q Oct 6 04:25:33 storageqe-109 journal: cryptsetup --device-size '2049s' resize URchgyJekD -q Oct 6 04:25:33 storageqe-109 stratisd[4947]: [2025-10-06T08:25:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:25:33 storageqe-109 stratisd[4947]: [2025-10-06T08:25:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '2049' resize URchgyJekD -q Oct 6 04:25:43 storageqe-109 journal: cryptsetup --size '2049' resize URchgyJekD -q Oct 6 04:25:43 storageqe-109 stratisd[4947]: [2025-10-06T08:25:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:25:43 storageqe-109 stratisd[4947]: [2025-10-06T08:25:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:25:53 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup open /dev/mapper/npo2linear dummy2 -q Oct 6 04:26:03 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear dummy2 -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:26:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.366_a73omount_test with fs xfs Oct 6 04:26:23 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 7b6db4f1-cf14-4a5e-9307-4b771ca40984 Oct 6 04:26:23 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:26:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.366_a73omount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:26:28 storageqe-109 systemd[1]: tmp-libblockdev.366_a73omount_test.mount: Deactivated successfully. Oct 6 04:26:28 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 7b6db4f1-cf14-4a5e-9307-4b771ca40984 Oct 6 04:26:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:26:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2h0sqc7wmount_test with fs ext4 Oct 6 04:26:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 40e64e59-ffda-4dcd-b910-373cccefaf48 r/w with ordered data mode. Quota mode: none. Oct 6 04:26:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2h0sqc7wmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:26:43 storageqe-109 systemd[1]: tmp-libblockdev.2h0sqc7wmount_test.mount: Deactivated successfully. Oct 6 04:26:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 40e64e59-ffda-4dcd-b910-373cccefaf48. Oct 6 04:26:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:26:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9qjyli14mount_test with fs ext3 Oct 6 04:26:53 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:26:53 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f1b83301-7171-49b8-bcec-5bcb924bfd76 r/w with ordered data mode. Quota mode: none. Oct 6 04:26:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9qjyli14mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:26:58 storageqe-109 systemd[1]: tmp-libblockdev.9qjyli14mount_test.mount: Deactivated successfully. Oct 6 04:26:58 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f1b83301-7171-49b8-bcec-5bcb924bfd76. Oct 6 04:26:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:26:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zkgd9h8imount_test with fs ext2 Oct 6 04:27:08 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:27:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem de6773b2-12f8-41bf-bb9a-cbeb1aced695 r/w without journal. Quota mode: none. Oct 6 04:27:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zkgd9h8imount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:27:13 storageqe-109 systemd[1]: tmp-libblockdev.zkgd9h8imount_test.mount: Deactivated successfully. Oct 6 04:27:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem de6773b2-12f8-41bf-bb9a-cbeb1aced695. Oct 6 04:27:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:27:13 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:27:13 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:27:13 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:27:13 storageqe-109 stratisd[4947]: [2025-10-06T08:27:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:27:13 storageqe-109 stratisd[4947]: [2025-10-06T08:27:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:27:23 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:27:23 storageqe-109 stratisd[4947]: [2025-10-06T08:27:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:27:23 storageqe-109 stratisd[4947]: [2025-10-06T08:27:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:27:33 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:27:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.uv1y98n6mount_test with fs xfs Oct 6 04:27:53 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 117c8192-9fde-4c1e-8810-28ebeb0312c1 Oct 6 04:27:53 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:27:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uv1y98n6mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:27:58 storageqe-109 systemd[1]: tmp-libblockdev.uv1y98n6mount_test.mount: Deactivated successfully. Oct 6 04:27:58 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 117c8192-9fde-4c1e-8810-28ebeb0312c1 Oct 6 04:27:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:27:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._e4d7os2mount_test with fs ext4 Oct 6 04:28:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1273c1bd-e045-49f2-af84-1253c6c3ba91 r/w with ordered data mode. Quota mode: none. Oct 6 04:28:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev._e4d7os2mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:28:13 storageqe-109 systemd[1]: tmp-libblockdev._e4d7os2mount_test.mount: Deactivated successfully. Oct 6 04:28:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1273c1bd-e045-49f2-af84-1253c6c3ba91. Oct 6 04:28:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:28:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.k5t4ny8dmount_test with fs ext3 Oct 6 04:28:23 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:28:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e9db525a-a07e-4f93-b1a9-dd7c8a949916 r/w with ordered data mode. Quota mode: none. Oct 6 04:28:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k5t4ny8dmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:28:28 storageqe-109 systemd[1]: tmp-libblockdev.k5t4ny8dmount_test.mount: Deactivated successfully. Oct 6 04:28:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e9db525a-a07e-4f93-b1a9-dd7c8a949916. Oct 6 04:28:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:28:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xtnyq3qxmount_test with fs ext2 Oct 6 04:28:38 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:28:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4b7fe201-b426-416d-8b24-e04e26696122 r/w without journal. Quota mode: none. Oct 6 04:28:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xtnyq3qxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' luksFormat /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:28:43 storageqe-109 systemd[1]: tmp-libblockdev.xtnyq3qxmount_test.mount: Deactivated successfully. Oct 6 04:28:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4b7fe201-b426-416d-8b24-e04e26696122. Oct 6 04:28:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:28:43 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:28:43 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:28:43 storageqe-109 kernel: device-mapper: table: 253:4: adding target device dm-3 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=4096, alignment_offset=0, start=1024 Oct 6 04:28:43 storageqe-109 kernel: device-mapper: table: 253:4: start=2 not aligned to h/w logical block size 4096 of dm-3 Oct 6 04:28:43 storageqe-109 kernel: device-mapper: core: Cannot calculate initial queue limits Oct 6 04:28:43 storageqe-109 kernel: device-mapper: ioctl: unable to set up device queue for new table. Oct 6 04:28:43 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' luksFormat /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:28:43 storageqe-109 stratisd[4947]: [2025-10-06T08:28:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:28:43 storageqe-109 stratisd[4947]: [2025-10-06T08:28:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:28:53 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '0' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:29:03 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '0' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '-1' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:29:13 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '-1' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '14' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:29:23 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '14' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '1' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:29:33 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '1' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '-1' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:29:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '-1' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:29:53 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:29:53 storageqe-109 stratisd[4947]: [2025-10-06T08:29:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:29:53 storageqe-109 stratisd[4947]: [2025-10-06T08:29:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:30:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ewwq44p5mount_test with fs xfs Oct 6 04:30:13 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 462c11e3-0700-4c95-b019-e3944628346b Oct 6 04:30:13 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:30:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ewwq44p5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:30:18 storageqe-109 systemd[1]: tmp-libblockdev.ewwq44p5mount_test.mount: Deactivated successfully. Oct 6 04:30:18 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 462c11e3-0700-4c95-b019-e3944628346b Oct 6 04:30:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:30:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9zahzv9cmount_test with fs ext4 Oct 6 04:30:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5ddc5831-1e3a-4674-839e-b5d0f70db0c0 r/w with ordered data mode. Quota mode: none. Oct 6 04:30:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9zahzv9cmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:30:33 storageqe-109 systemd[1]: tmp-libblockdev.9zahzv9cmount_test.mount: Deactivated successfully. Oct 6 04:30:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5ddc5831-1e3a-4674-839e-b5d0f70db0c0. Oct 6 04:30:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:30:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hog_b7tkmount_test with fs ext3 Oct 6 04:30:43 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:30:43 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3044fb59-936a-48e6-ad55-c4bc13cdc08a r/w with ordered data mode. Quota mode: none. Oct 6 04:30:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hog_b7tkmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:30:48 storageqe-109 systemd[1]: tmp-libblockdev.hog_b7tkmount_test.mount: Deactivated successfully. Oct 6 04:30:48 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3044fb59-936a-48e6-ad55-c4bc13cdc08a. Oct 6 04:30:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:30:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jdatvg3omount_test with fs ext2 Oct 6 04:30:58 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:30:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 15884128-0cb0-47af-9daa-6b57be646f8d r/w without journal. Quota mode: none. Oct 6 04:30:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jdatvg3omount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:31:03 storageqe-109 systemd[1]: tmp-libblockdev.jdatvg3omount_test.mount: Deactivated successfully. Oct 6 04:31:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 15884128-0cb0-47af-9daa-6b57be646f8d. Oct 6 04:31:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:31:03 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:31:03 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:31:03 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '14' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:31:13 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '14' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '-1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:31:23 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '-1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:31:33 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileDxg cryptsetup --key-file '/tmp/testfileQzG' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:31:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '14' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:31:53 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '14' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:32:03 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:32:03 storageqe-109 stratisd[4947]: [2025-10-06T08:32:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:32:03 storageqe-109 stratisd[4947]: [2025-10-06T08:32:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileDxg' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q Oct 6 04:32:14 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileDxg' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q Oct 6 04:32:14 storageqe-109 stratisd[4947]: [2025-10-06T08:32:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:32:14 storageqe-109 stratisd[4947]: [2025-10-06T08:32:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --keyfile-size '11' luksRemoveKey /dev/mapper/npo2linear -q Oct 6 04:32:24 storageqe-109 journal: cryptsetup --keyfile-size '11' luksRemoveKey /dev/mapper/npo2linear -q cryptsetup --keyfile-size '12' luksRemoveKey /dev/mapper/npo2linear -q Oct 6 04:32:34 storageqe-109 journal: cryptsetup --keyfile-size '12' luksRemoveKey /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' --keyfile-offset '16' luksFormat /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:32:44 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' --keyfile-offset '16' luksFormat /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:32:44 storageqe-109 stratisd[4947]: [2025-10-06T08:32:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:32:44 storageqe-109 stratisd[4947]: [2025-10-06T08:32:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '15' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:32:54 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '15' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '16' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:33:04 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileQzG' --keyfile-size '13' --keyfile-offset '16' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:33:04 storageqe-109 stratisd[4947]: [2025-10-06T08:33:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:33:04 storageqe-109 stratisd[4947]: [2025-10-06T08:33:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:33:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.gkjibg0imount_test with fs xfs Oct 6 04:33:24 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 1fefbd32-9030-42c3-a5bd-232f8f9d008f Oct 6 04:33:24 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:33:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gkjibg0imount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:33:29 storageqe-109 systemd[1]: tmp-libblockdev.gkjibg0imount_test.mount: Deactivated successfully. Oct 6 04:33:29 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 1fefbd32-9030-42c3-a5bd-232f8f9d008f Oct 6 04:33:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:33:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9en37wzymount_test with fs ext4 Oct 6 04:33:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4dfbad36-2f96-4876-8164-1adc86069184 r/w with ordered data mode. Quota mode: none. Oct 6 04:33:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9en37wzymount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:33:44 storageqe-109 systemd[1]: tmp-libblockdev.9en37wzymount_test.mount: Deactivated successfully. Oct 6 04:33:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4dfbad36-2f96-4876-8164-1adc86069184. Oct 6 04:33:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:33:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4plb7goemount_test with fs ext3 Oct 6 04:33:54 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:33:54 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8c94d9ba-03b0-49c6-a6d1-00a0f4a05083 r/w with ordered data mode. Quota mode: none. Oct 6 04:33:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4plb7goemount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:33:59 storageqe-109 systemd[1]: tmp-libblockdev.4plb7goemount_test.mount: Deactivated successfully. Oct 6 04:33:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8c94d9ba-03b0-49c6-a6d1-00a0f4a05083. Oct 6 04:33:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:33:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1dh0ip9_mount_test with fs ext2 Oct 6 04:34:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:34:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3c932de9-77d7-4b9b-bcc3-9d0e758228c9 r/w without journal. Quota mode: none. Oct 6 04:34:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1dh0ip9_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileQzG' --pbkdf-force-iterations '1000' --keyfile-size '13' --keyfile-offset '16' --new-keyfile-offset '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:34:14 storageqe-109 systemd[1]: tmp-libblockdev.1dh0ip9_mount_test.mount: Deactivated successfully. Oct 6 04:34:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3c932de9-77d7-4b9b-bcc3-9d0e758228c9. Oct 6 04:34:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:34:14 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:34:14 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:34:14 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileQzG' --pbkdf-force-iterations '1000' --keyfile-size '13' --keyfile-offset '16' --new-keyfile-offset '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:34:14 storageqe-109 stratisd[4947]: [2025-10-06T08:34:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:34:14 storageqe-109 stratisd[4947]: [2025-10-06T08:34:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileDxg' --keyfile-offset '11' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:34:24 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileDxg' --keyfile-offset '11' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup --key-file '/tmp/testfileDxg' --keyfile-offset '1' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:34:34 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileDxg' --keyfile-offset '1' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:34:34 storageqe-109 stratisd[4947]: [2025-10-06T08:34:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:34:34 storageqe-109 stratisd[4947]: [2025-10-06T08:34:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:34:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.xncy3ekkmount_test with fs xfs Oct 6 04:34:54 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 4a219161-c8a5-48b9-8a9d-d522327d0246 Oct 6 04:34:54 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:34:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xncy3ekkmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:34:59 storageqe-109 systemd[1]: tmp-libblockdev.xncy3ekkmount_test.mount: Deactivated successfully. Oct 6 04:34:59 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 4a219161-c8a5-48b9-8a9d-d522327d0246 Oct 6 04:34:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:34:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.l6cr529_mount_test with fs ext4 Oct 6 04:35:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d13205e4-e439-4c36-9fda-3490491521ac r/w with ordered data mode. Quota mode: none. Oct 6 04:35:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l6cr529_mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:35:14 storageqe-109 systemd[1]: tmp-libblockdev.l6cr529_mount_test.mount: Deactivated successfully. Oct 6 04:35:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d13205e4-e439-4c36-9fda-3490491521ac. Oct 6 04:35:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:35:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.65bhbjlxmount_test with fs ext3 Oct 6 04:35:24 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:35:24 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6eafcd8e-f603-4c50-8dab-7c52f528fee1 r/w with ordered data mode. Quota mode: none. Oct 6 04:35:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.65bhbjlxmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:35:29 storageqe-109 systemd[1]: tmp-libblockdev.65bhbjlxmount_test.mount: Deactivated successfully. Oct 6 04:35:29 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6eafcd8e-f603-4c50-8dab-7c52f528fee1. Oct 6 04:35:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:35:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ys8dxu__mount_test with fs ext2 Oct 6 04:35:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:35:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f87da468-4d19-4c2d-8655-7f4aba2e8d4a r/w without journal. Quota mode: none. Oct 6 04:35:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ys8dxu__mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileDxg' --pbkdf-force-iterations '1000' --keyfile-offset '1' --new-keyfile-offset '0' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:35:44 storageqe-109 systemd[1]: tmp-libblockdev.ys8dxu__mount_test.mount: Deactivated successfully. Oct 6 04:35:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f87da468-4d19-4c2d-8655-7f4aba2e8d4a. Oct 6 04:35:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:35:44 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:35:44 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:35:44 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileDxg' --pbkdf-force-iterations '1000' --keyfile-offset '1' --new-keyfile-offset '0' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileDxg Oct 6 04:35:44 storageqe-109 stratisd[4947]: [2025-10-06T08:35:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:35:44 storageqe-109 stratisd[4947]: [2025-10-06T08:35:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileDxg' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:35:54 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileDxg' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:35:54 storageqe-109 stratisd[4947]: [2025-10-06T08:35:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:35:54 storageqe-109 stratisd[4947]: [2025-10-06T08:35:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:36:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.zkkrk91wmount_test with fs xfs Oct 6 04:36:14 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 182aef29-2d05-4227-968a-f78fa3cd8e13 Oct 6 04:36:14 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:36:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zkkrk91wmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:36:19 storageqe-109 systemd[1]: tmp-libblockdev.zkkrk91wmount_test.mount: Deactivated successfully. Oct 6 04:36:19 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 182aef29-2d05-4227-968a-f78fa3cd8e13 Oct 6 04:36:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:36:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rbsjcq_amount_test with fs ext4 Oct 6 04:36:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7c1287a0-977e-433d-a711-531f552da21b r/w with ordered data mode. Quota mode: none. Oct 6 04:36:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rbsjcq_amount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:36:34 storageqe-109 systemd[1]: tmp-libblockdev.rbsjcq_amount_test.mount: Deactivated successfully. Oct 6 04:36:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7c1287a0-977e-433d-a711-531f552da21b. Oct 6 04:36:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:36:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3l8tsvdpmount_test with fs ext3 Oct 6 04:36:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:36:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9653cbce-fd0f-4302-8eb0-6c3a343a65ee r/w with ordered data mode. Quota mode: none. Oct 6 04:36:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3l8tsvdpmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:36:49 storageqe-109 systemd[1]: tmp-libblockdev.3l8tsvdpmount_test.mount: Deactivated successfully. Oct 6 04:36:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9653cbce-fd0f-4302-8eb0-6c3a343a65ee. Oct 6 04:36:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:36:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jd2ohpxvmount_test with fs ext2 Oct 6 04:36:59 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:36:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6203b4a2-ed5f-4f98-9ec2-471545f740f0 r/w without journal. Quota mode: none. Oct 6 04:36:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jd2ohpxvmount_test with fs ext2 Oct 6 04:37:03 storageqe-109 systemd[1]: tmp-libblockdev.jd2ohpxvmount_test.mount: Deactivated successfully. Oct 6 04:37:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6203b4a2-ed5f-4f98-9ec2-471545f740f0. INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q Oct 6 04:37:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:37:04 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:37:04 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:37:04 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '1' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q Oct 6 04:37:14 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '1' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q Oct 6 04:37:24 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear /tmp/testheaderJdY -q Oct 6 04:37:34 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear /tmp/testheaderJdY -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 6 04:37:44 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' --sector-size '512' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderJdY' open wrong_device URchgyJekD -q Oct 6 04:37:54 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' open wrong_device URchgyJekD -q cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:38:04 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:38:04 storageqe-109 stratisd[4947]: [2025-10-06T08:38:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:38:04 storageqe-109 stratisd[4947]: [2025-10-06T08:38:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '1600000' --header '/tmp/testheaderJdY' resize URchgyJekD -q Oct 6 04:38:14 storageqe-109 journal: cryptsetup --size '1600000' --header '/tmp/testheaderJdY' resize URchgyJekD -q Oct 6 04:38:14 storageqe-109 stratisd[4947]: [2025-10-06T08:38:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:38:14 storageqe-109 stratisd[4947]: [2025-10-06T08:38:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:38:14 storageqe-109 stratisd[4947]: [2025-10-06T08:38:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:38:14 storageqe-109 stratisd[4947]: [2025-10-06T08:38:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --header '/tmp/testheaderJdY' status URchgyJekD -q Oct 6 04:38:24 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' status URchgyJekD -q cryptsetup --header '/tmp/testheaderJdY' luksSuspend URchgyJekD -q Oct 6 04:38:34 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksSuspend URchgyJekD -q cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q Oct 6 04:38:44 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q cryptsetup --header '/tmp/testheaderJdY' luksSuspend URchgyJekD -q Oct 6 04:38:54 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksSuspend URchgyJekD -q cryptsetup luksResume URchgyJekD -q Oct 6 04:39:04 storageqe-109 journal: cryptsetup luksResume URchgyJekD -q cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q Oct 6 04:39:14 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:39:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.njztefi7mount_test with fs xfs Oct 6 04:39:34 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 1674be80-b262-492c-88df-6edea6dac08a Oct 6 04:39:34 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:39:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.njztefi7mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:39:39 storageqe-109 systemd[1]: tmp-libblockdev.njztefi7mount_test.mount: Deactivated successfully. Oct 6 04:39:39 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 1674be80-b262-492c-88df-6edea6dac08a Oct 6 04:39:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:39:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.li_1c1symount_test with fs ext4 Oct 6 04:39:49 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 249c519e-ad06-4b4e-b182-57d5265d2fb6 r/w with ordered data mode. Quota mode: none. Oct 6 04:39:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.li_1c1symount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:39:54 storageqe-109 systemd[1]: tmp-libblockdev.li_1c1symount_test.mount: Deactivated successfully. Oct 6 04:39:54 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 249c519e-ad06-4b4e-b182-57d5265d2fb6. Oct 6 04:39:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:39:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.c_4bambkmount_test with fs ext3 Oct 6 04:40:04 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:40:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem db80d38d-d735-431f-8c02-8606fca51606 r/w with ordered data mode. Quota mode: none. Oct 6 04:40:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c_4bambkmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:40:09 storageqe-109 systemd[1]: tmp-libblockdev.c_4bambkmount_test.mount: Deactivated successfully. Oct 6 04:40:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem db80d38d-d735-431f-8c02-8606fca51606. Oct 6 04:40:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:40:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r7rv57o0mount_test with fs ext2 Oct 6 04:40:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:40:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a94018c3-2382-4097-8acd-5a7743b7b81b r/w without journal. Quota mode: none. Oct 6 04:40:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r7rv57o0mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD Oct 6 04:40:24 storageqe-109 systemd[1]: tmp-libblockdev.r7rv57o0mount_test.mount: Deactivated successfully. Oct 6 04:40:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a94018c3-2382-4097-8acd-5a7743b7b81b. Oct 6 04:40:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:40:24 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:40:24 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:40:24 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' --header '/tmp/testheaderJdY' luksAddKey _fakedev -q /tmp/testfileFVI cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' --header '/tmp/testheaderJdY' luksAddKey _fakedev -q /tmp/testfileFVI cryptsetup --header '/tmp/testheaderJdY' luksDump _fakedev -q Oct 6 04:40:34 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksDump _fakedev -q cryptsetup --header '/tmp/testheaderJdY' luksKillSlot _fakedev -q 5 Oct 6 04:40:44 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksKillSlot _fakedev -q 5 cryptsetup --header '/tmp/testheaderJdY' luksDump _fakedev -q Oct 6 04:40:54 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksDump _fakedev -q cryptsetup open --test-passphrase /tmp/testheaderJdY -q Oct 6 04:41:04 storageqe-109 journal: cryptsetup open --test-passphrase /tmp/testheaderJdY -q cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --type 'luks2' --header '/tmp/testheaderJdY' --luks2-keyslots-size '16352k' --luks2-metadata-size '16k' --offset '131072' luksFormat /dev/mapper/npo2linear -q Oct 6 04:41:14 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --type 'luks2' --header '/tmp/testheaderJdY' --luks2-keyslots-size '16352k' --luks2-metadata-size '16k' --offset '131072' luksFormat /dev/mapper/npo2linear -q cryptsetup luksDump /tmp/testheaderJdY -q Oct 6 04:41:24 storageqe-109 journal: cryptsetup luksDump /tmp/testheaderJdY -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI Oct 6 04:41:34 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileFVI' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:41:44 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileFVI' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileQzG cryptsetup luksDump /dev/mapper/npo2linear -q --dump-json-metadata Oct 6 04:41:54 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q --dump-json-metadata cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 6 04:42:04 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:42:14 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:42:24 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 04:42:34 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 04:42:34 storageqe-109 stratisd[4947]: [2025-10-06T08:42:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:42:34 storageqe-109 stratisd[4947]: [2025-10-06T08:42:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:42:45 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:42:55 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 6 04:43:05 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '512' --pbkdf-force-iterations '1000' --key-slot '0' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI Oct 6 04:43:15 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '512' --pbkdf-force-iterations '1000' --key-slot '0' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI Oct 6 04:43:15 storageqe-109 stratisd[4947]: [2025-10-06T08:43:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:43:15 storageqe-109 stratisd[4947]: [2025-10-06T08:43:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileFVI' --hash 'sha512' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:43:25 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileFVI' --hash 'sha512' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileQzG Oct 6 04:43:25 storageqe-109 stratisd[4947]: [2025-10-06T08:43:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:43:25 storageqe-109 stratisd[4947]: [2025-10-06T08:43:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 6 04:43:35 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear -q 1 Oct 6 04:43:45 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 1 cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 6 04:43:55 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:44:05 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-slot '0' --key-file '/tmp/testfileFVI' open /dev/mapper/npo2linear -q --test-passphrase Oct 6 04:44:15 storageqe-109 journal: cryptsetup --key-slot '0' --key-file '/tmp/testfileFVI' open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '1024' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI Oct 6 04:44:25 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '1024' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI Oct 6 04:44:25 storageqe-109 stratisd[4947]: [2025-10-06T08:44:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:44:25 storageqe-109 stratisd[4947]: [2025-10-06T08:44:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 6 04:44:35 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --align-payload '4097' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI Oct 6 04:44:45 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --align-payload '4097' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileFVI cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 04:44:55 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 6 04:44:55 storageqe-109 stratisd[4947]: [2025-10-06T08:44:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:44:55 storageqe-109 stratisd[4947]: [2025-10-06T08:44:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' isLuks /dev/mapper/npo2linear -q Oct 6 04:45:05 storageqe-109 journal: cryptsetup --type 'luks2' isLuks /dev/mapper/npo2linear -q cryptsetup --key-slot '0' --key-file '/tmp/testfileFVI' open /dev/mapper/npo2linear -q --test-passphrase Oct 6 04:45:15 storageqe-109 journal: cryptsetup --key-slot '0' --key-file '/tmp/testfileFVI' open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q Oct 6 04:45:25 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderJdY' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:45:35 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:45:35 storageqe-109 stratisd[4947]: [2025-10-06T08:45:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:45:35 storageqe-109 stratisd[4947]: [2025-10-06T08:45:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status URchgyJekD -q Oct 6 04:45:45 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 04:45:55 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:46:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.7t779zvsmount_test with fs xfs Oct 6 04:46:15 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b163b69e-a519-490f-88ac-bbbb04b6ca07 Oct 6 04:46:15 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:46:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7t779zvsmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:46:20 storageqe-109 systemd[1]: tmp-libblockdev.7t779zvsmount_test.mount: Deactivated successfully. Oct 6 04:46:20 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b163b69e-a519-490f-88ac-bbbb04b6ca07 Oct 6 04:46:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:46:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ck2jiwhpmount_test with fs ext4 Oct 6 04:46:30 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dd3dd1af-4120-4327-9071-125414fe89fe r/w with ordered data mode. Quota mode: none. Oct 6 04:46:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ck2jiwhpmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:46:35 storageqe-109 systemd[1]: tmp-libblockdev.ck2jiwhpmount_test.mount: Deactivated successfully. Oct 6 04:46:35 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dd3dd1af-4120-4327-9071-125414fe89fe. Oct 6 04:46:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:46:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.goz9rycpmount_test with fs ext3 Oct 6 04:46:45 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:46:45 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 10d2728f-706d-4e5e-af1c-f69e6650b6d0 r/w with ordered data mode. Quota mode: none. Oct 6 04:46:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.goz9rycpmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:46:50 storageqe-109 systemd[1]: tmp-libblockdev.goz9rycpmount_test.mount: Deactivated successfully. Oct 6 04:46:50 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 10d2728f-706d-4e5e-af1c-f69e6650b6d0. Oct 6 04:46:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:46:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._vhppb11mount_test with fs ext2 Oct 6 04:47:00 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:47:00 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a4468e3f-b4b0-4bd2-b669-107be1c42ba5 r/w without journal. Quota mode: none. Oct 6 04:47:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev._vhppb11mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:47:05 storageqe-109 systemd[1]: tmp-libblockdev._vhppb11mount_test.mount: Deactivated successfully. Oct 6 04:47:05 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a4468e3f-b4b0-4bd2-b669-107be1c42ba5. Oct 6 04:47:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:47:05 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:47:05 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:47:05 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 04:47:15 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:47:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.r2qc41v8mount_test with fs xfs Oct 6 04:47:35 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 83efae21-c8f4-481e-b659-399487ab9f9b Oct 6 04:47:35 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:47:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r2qc41v8mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:47:40 storageqe-109 systemd[1]: tmp-libblockdev.r2qc41v8mount_test.mount: Deactivated successfully. Oct 6 04:47:40 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 83efae21-c8f4-481e-b659-399487ab9f9b Oct 6 04:47:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:47:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ewkd8r25mount_test with fs ext4 Oct 6 04:47:50 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e3ec2af6-0cab-4a50-a38f-3c9a4ae18b8c r/w with ordered data mode. Quota mode: none. Oct 6 04:47:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ewkd8r25mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:47:55 storageqe-109 systemd[1]: tmp-libblockdev.ewkd8r25mount_test.mount: Deactivated successfully. Oct 6 04:47:55 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e3ec2af6-0cab-4a50-a38f-3c9a4ae18b8c. Oct 6 04:47:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:47:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1_5dzmexmount_test with fs ext3 Oct 6 04:48:05 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:48:05 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f0a224c3-f70b-4bab-960a-5467c4166552 r/w with ordered data mode. Quota mode: none. Oct 6 04:48:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1_5dzmexmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:48:10 storageqe-109 systemd[1]: tmp-libblockdev.1_5dzmexmount_test.mount: Deactivated successfully. Oct 6 04:48:10 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f0a224c3-f70b-4bab-960a-5467c4166552. Oct 6 04:48:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:48:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gmlgac35mount_test with fs ext2 Oct 6 04:48:20 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:48:20 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 863df753-4aae-444a-9391-1fbcf5d74b90 r/w without journal. Quota mode: none. Oct 6 04:48:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gmlgac35mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q --disable-keyring Oct 6 04:48:25 storageqe-109 systemd[1]: tmp-libblockdev.gmlgac35mount_test.mount: Deactivated successfully. Oct 6 04:48:25 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 863df753-4aae-444a-9391-1fbcf5d74b90. Oct 6 04:48:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:48:25 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:48:25 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:48:25 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q --disable-keyring cryptsetup status URchgyJekD -q Oct 6 04:48:35 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 04:48:45 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:48:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.3d68c2qnmount_test with fs xfs Oct 6 04:49:05 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 2dd2dca5-3117-40e5-a390-5e41699c1530 Oct 6 04:49:05 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:49:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3d68c2qnmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:49:10 storageqe-109 systemd[1]: tmp-libblockdev.3d68c2qnmount_test.mount: Deactivated successfully. Oct 6 04:49:10 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 2dd2dca5-3117-40e5-a390-5e41699c1530 Oct 6 04:49:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:49:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7ccyx7f0mount_test with fs ext4 Oct 6 04:49:20 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9a3eeaeb-5872-4410-8e1b-6980de1ce91f r/w with ordered data mode. Quota mode: none. Oct 6 04:49:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7ccyx7f0mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:49:25 storageqe-109 systemd[1]: tmp-libblockdev.7ccyx7f0mount_test.mount: Deactivated successfully. Oct 6 04:49:25 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9a3eeaeb-5872-4410-8e1b-6980de1ce91f. Oct 6 04:49:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:49:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1elb6p4vmount_test with fs ext3 Oct 6 04:49:35 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:49:35 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c3bcf800-171c-49c6-b3e1-2fa441ef9f83 r/w with ordered data mode. Quota mode: none. Oct 6 04:49:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1elb6p4vmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:49:40 storageqe-109 systemd[1]: tmp-libblockdev.1elb6p4vmount_test.mount: Deactivated successfully. Oct 6 04:49:40 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c3bcf800-171c-49c6-b3e1-2fa441ef9f83. Oct 6 04:49:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:49:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6nr2lbljmount_test with fs ext2 Oct 6 04:49:50 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:49:50 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9d50d1a1-be36-4ca8-9b56-d45954d041b6 r/w without journal. Quota mode: none. Oct 6 04:49:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6nr2lbljmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q --disable-keyring Oct 6 04:49:55 storageqe-109 systemd[1]: tmp-libblockdev.6nr2lbljmount_test.mount: Deactivated successfully. Oct 6 04:49:55 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9d50d1a1-be36-4ca8-9b56-d45954d041b6. Oct 6 04:49:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:49:55 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:49:55 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:49:55 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q --disable-keyring cryptsetup luksSuspend URchgyJekD -q Oct 6 04:50:05 storageqe-109 journal: cryptsetup luksSuspend URchgyJekD -q cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q Oct 6 04:50:15 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 04:50:25 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 04:50:35 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:50:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8hgdruw5mount_test with fs xfs Oct 6 04:50:55 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 86876699-96b6-4952-a5af-99a3f973086a Oct 6 04:50:55 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:50:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8hgdruw5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:51:00 storageqe-109 systemd[1]: tmp-libblockdev.8hgdruw5mount_test.mount: Deactivated successfully. Oct 6 04:51:00 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 86876699-96b6-4952-a5af-99a3f973086a Oct 6 04:51:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:51:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q4u9nm4zmount_test with fs ext4 Oct 6 04:51:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 272cb7b4-a02a-4f10-9986-c6a6481a69ae r/w with ordered data mode. Quota mode: none. Oct 6 04:51:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q4u9nm4zmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:51:15 storageqe-109 systemd[1]: tmp-libblockdev.q4u9nm4zmount_test.mount: Deactivated successfully. Oct 6 04:51:15 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 272cb7b4-a02a-4f10-9986-c6a6481a69ae. Oct 6 04:51:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:51:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pfrcrsj7mount_test with fs ext3 Oct 6 04:51:25 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:51:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 01687af4-f177-4bef-9abb-6c0be47f7a51 r/w with ordered data mode. Quota mode: none. Oct 6 04:51:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pfrcrsj7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:51:30 storageqe-109 systemd[1]: tmp-libblockdev.pfrcrsj7mount_test.mount: Deactivated successfully. Oct 6 04:51:30 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 01687af4-f177-4bef-9abb-6c0be47f7a51. Oct 6 04:51:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:51:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vcskflvumount_test with fs ext2 Oct 6 04:51:40 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:51:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 90b4dfb3-55c2-415e-a905-8221c9ae99fb r/w without journal. Quota mode: none. Oct 6 04:51:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vcskflvumount_test with fs ext2 Oct 6 04:51:45 storageqe-109 systemd[1]: tmp-libblockdev.vcskflvumount_test.mount: Deactivated successfully. Oct 6 04:51:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 90b4dfb3-55c2-415e-a905-8221c9ae99fb. INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q Oct 6 04:51:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:51:45 storageqe-109 INFO: remove crypt device URchgyJekD Oct 6 04:51:45 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:51:45 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' open /dev/mapper/npo2linear URchgyJekD -q cryptsetup luksSuspend URchgyJekD -q Oct 6 04:51:55 storageqe-109 journal: cryptsetup luksSuspend URchgyJekD -q cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q --disable-keyring Oct 6 04:52:05 storageqe-109 journal: cryptsetup --header '/tmp/testheaderJdY' luksResume URchgyJekD -q --disable-keyring cryptsetup status URchgyJekD -q Oct 6 04:52:15 storageqe-109 journal: cryptsetup status URchgyJekD -q cryptsetup status URchgyJekD -q Oct 6 04:52:25 storageqe-109 journal: cryptsetup status URchgyJekD -q INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:52:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.30hjoqalmount_test with fs xfs Oct 6 04:52:45 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f17d4b7a-fc07-4a39-8f44-c236b56e62f7 Oct 6 04:52:45 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 04:52:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.30hjoqalmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:52:50 storageqe-109 systemd[1]: tmp-libblockdev.30hjoqalmount_test.mount: Deactivated successfully. Oct 6 04:52:50 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f17d4b7a-fc07-4a39-8f44-c236b56e62f7 Oct 6 04:52:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs xfs in remove_crypt Oct 6 04:52:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.goxhrhbcmount_test with fs ext4 Oct 6 04:53:00 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a875b707-feff-43d6-8dc6-7129f0c67330 r/w with ordered data mode. Quota mode: none. Oct 6 04:53:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.goxhrhbcmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:53:05 storageqe-109 systemd[1]: tmp-libblockdev.goxhrhbcmount_test.mount: Deactivated successfully. Oct 6 04:53:05 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a875b707-feff-43d6-8dc6-7129f0c67330. Oct 6 04:53:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext4 in remove_crypt Oct 6 04:53:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mblthh88mount_test with fs ext3 Oct 6 04:53:15 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 04:53:15 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2b5647f4-6a9a-498d-9491-4b1d2093b0fa r/w with ordered data mode. Quota mode: none. Oct 6 04:53:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mblthh88mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:53:20 storageqe-109 systemd[1]: tmp-libblockdev.mblthh88mount_test.mount: Deactivated successfully. Oct 6 04:53:20 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 04:53:20 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2b5647f4-6a9a-498d-9491-4b1d2093b0fa. Oct 6 04:53:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext3 in remove_crypt Oct 6 04:53:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:53:20 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 04:53:20 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: will run io in dir /tmp/libblockdev.kco9dwr6mount_test with fs ext2 Oct 6 04:53:30 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 04:53:30 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 60cfa9f3-0af7-4b64-b94d-af4c289d3503 r/w without journal. Quota mode: none. Oct 6 04:53:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kco9dwr6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt INFO: remove crypt device URchgyJekD Oct 6 04:53:35 storageqe-109 systemd[1]: tmp-libblockdev.kco9dwr6mount_test.mount: Deactivated successfully. Oct 6 04:53:35 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 60cfa9f3-0af7-4b64-b94d-af4c289d3503. Oct 6 04:53:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/URchgyJekD and fs ext2 in remove_crypt Oct 6 04:53:35 storageqe-109 INFO: remove crypt device URchgyJekD INFO: finishe the remove crypt device URchgyJekD cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:53:35 storageqe-109 INFO: finishe the remove crypt device URchgyJekD Oct 6 04:53:35 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 6 04:53:35 storageqe-109 stratisd[4947]: [2025-10-06T08:53:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:53:35 storageqe-109 stratisd[4947]: [2025-10-06T08:53:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'keydesc0' --token-id '3' token add /dev/mapper/npo2linear -q Oct 6 04:53:45 storageqe-109 journal: cryptsetup --key-description 'keydesc0' --token-id '3' token add /dev/mapper/npo2linear -q Oct 6 04:53:45 storageqe-109 stratisd[4947]: [2025-10-06T08:53:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:53:45 storageqe-109 stratisd[4947]: [2025-10-06T08:53:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 6 04:53:55 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-description 'keydesc1' --key-slot '5' token add /dev/mapper/npo2linear -q Oct 6 04:54:05 storageqe-109 journal: cryptsetup --key-description 'keydesc1' --key-slot '5' token add /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear -q --token-only --test-passphrase Oct 6 04:54:15 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear -q --token-only --test-passphrase cryptsetup open /dev/mapper/npo2linear URchgyJekD -q --token-only --test-passphrase Oct 6 04:54:25 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear URchgyJekD -q --token-only --test-passphrase INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_compat_test2[npo2_linear] #### Oct 6 04:54:30 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 04:54:30 storageqe-109 INFO: #### END test_compat_test2[npo2_linear] #### Oct 6 04:54:30 storageqe-109 stratisd[4947]: [2025-10-06T08:54:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:54:30 storageqe-109 stratisd[4947]: [2025-10-06T08:54:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:54:31 storageqe-109 stratisd[4947]: [2025-10-06T08:54:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:54:31 storageqe-109 stratisd[4947]: [2025-10-06T08:54:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:54:32 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_verify_lock_range ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 04:54:32 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 04:54:32 storageqe-109 INFO: #### will start test_verify_lock_range ##### Oct 6 04:54:32 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:54:38 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 04:54:39 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 04:54:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:54:49 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:54:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal --debug Oct 6 04:55:00 storageqe-109 kernel: nvme0n1: Oct 6 04:55:00 storageqe-109 kernel: nvme0n1: p1 Oct 6 04:55:00 storageqe-109 kernel: nvme0n1: p1 p2 Oct 6 04:55:00 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal --debug Oct 6 04:55:10 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:10 storageqe-109 stratisd[4947]: [2025-10-06T08:55:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:55:10 storageqe-109 stratisd[4947]: [2025-10-06T08:55:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 04:55:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:20 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 04:55:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:55:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:55:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 04:55:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 04:55:21 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 04:55:30 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup erase /dev/nvme0n1p1 -q Oct 6 04:55:31 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p1 -q cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 04:55:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:55:51 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 04:55:51 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 04:55:51 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 04:56:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q INFO: finishe the remove crypt device None Oct 6 04:56:13 storageqe-109 INFO: finishe the remove crypt device None cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:56:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:56:27 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:56:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_verify_lock_range #### INFO: #### will start test_hw_opal ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 04:56:43 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 04:56:43 storageqe-109 INFO: #### END test_verify_lock_range #### Oct 6 04:56:43 storageqe-109 INFO: #### will start test_hw_opal ##### Oct 6 04:56:43 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:56:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:56:59 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 04:57:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 04:57:10 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 04:57:20 storageqe-109 kernel: nvme_log_error: 5 callbacks suppressed Oct 6 04:57:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:20 storageqe-109 kernel: blk_print_req_error: 5 callbacks suppressed Oct 6 04:57:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 04:57:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 04:57:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 04:57:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 04:57:21 storageqe-109 stratisd[4947]: [2025-10-06T08:57:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:57:21 storageqe-109 stratisd[4947]: [2025-10-06T08:57:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 AdGx -q Oct 6 04:57:31 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 AdGx -q Oct 6 04:57:33 storageqe-109 stratisd[4947]: [2025-10-06T08:57:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:57:33 storageqe-109 stratisd[4947]: [2025-10-06T08:57:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 04:57:40 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.1jbf3v1ymount_test with fs xfs Oct 6 04:57:53 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 57174f1f-fbc5-4627-9798-550abdccc8d1 Oct 6 04:57:53 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 04:57:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1jbf3v1ymount_test with fs xfs Oct 6 04:57:59 storageqe-109 systemd[1]: tmp-libblockdev.1jbf3v1ymount_test.mount: Deactivated successfully. Oct 6 04:57:59 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 57174f1f-fbc5-4627-9798-550abdccc8d1 Oct 6 04:58:19 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.ytzvzz6zmount_test with fs ext2 Oct 6 04:58:19 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3ef3629b-a9bf-48c0-9a5d-116a5ca11c17 r/w without journal. Quota mode: none. Oct 6 04:58:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ytzvzz6zmount_test with fs ext2 Oct 6 04:58:24 storageqe-109 systemd[1]: tmp-libblockdev.ytzvzz6zmount_test.mount: Deactivated successfully. Oct 6 04:58:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3ef3629b-a9bf-48c0-9a5d-116a5ca11c17. INFO: will run io in dir /tmp/libblockdev.y4xxhuj1mount_test with fs ext3 Oct 6 04:58:45 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 04:58:46 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b8ed4fc2-ca1f-4b77-8a12-3560aa161cb2 r/w with ordered data mode. Quota mode: none. Oct 6 04:58:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y4xxhuj1mount_test with fs ext3 Oct 6 04:58:50 storageqe-109 systemd[1]: tmp-libblockdev.y4xxhuj1mount_test.mount: Deactivated successfully. Oct 6 04:58:50 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b8ed4fc2-ca1f-4b77-8a12-3560aa161cb2. INFO: will run io in dir /tmp/libblockdev.4mi8wm2fmount_test with fs ext4 Oct 6 04:59:01 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 67ec36c6-889e-4ea0-82d0-785fae34d646 r/w with ordered data mode. Quota mode: none. Oct 6 04:59:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4mi8wm2fmount_test with fs ext4 Oct 6 04:59:06 storageqe-109 systemd[1]: tmp-libblockdev.4mi8wm2fmount_test.mount: Deactivated successfully. Oct 6 04:59:07 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 67ec36c6-889e-4ea0-82d0-785fae34d646. INFO: will run io in dir /tmp/libblockdev.2_uwg4kcmount_test with fs xfs Oct 6 04:59:17 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 4241b873-1e4c-400d-acb0-a79c751eb64c Oct 6 04:59:17 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 04:59:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2_uwg4kcmount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/AdGx and fs xfs in remove_crypt Oct 6 04:59:22 storageqe-109 systemd[1]: tmp-libblockdev.2_uwg4kcmount_test.mount: Deactivated successfully. Oct 6 04:59:22 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 4241b873-1e4c-400d-acb0-a79c751eb64c Oct 6 04:59:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AdGx and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.c8ujbq9ymount_test with fs xfs Oct 6 04:59:32 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 410b3e5f-5278-488c-85e0-e9573ca3aab4 Oct 6 04:59:32 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 04:59:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c8ujbq9ymount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/AdGx and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/AdGx and fs ext4 in remove_crypt Oct 6 04:59:37 storageqe-109 systemd[1]: tmp-libblockdev.c8ujbq9ymount_test.mount: Deactivated successfully. Oct 6 04:59:37 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 410b3e5f-5278-488c-85e0-e9573ca3aab4 Oct 6 04:59:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AdGx and fs xfs in remove_crypt Oct 6 04:59:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AdGx and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5fx9vxxpmount_test with fs ext4 Oct 6 04:59:47 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3288200c-ac3d-4066-91d5-2231452c892a r/w with ordered data mode. Quota mode: none. Oct 6 04:59:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5fx9vxxpmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/AdGx and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/AdGx and fs ext3 in remove_crypt Oct 6 04:59:52 storageqe-109 systemd[1]: tmp-libblockdev.5fx9vxxpmount_test.mount: Deactivated successfully. Oct 6 04:59:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3288200c-ac3d-4066-91d5-2231452c892a. Oct 6 04:59:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AdGx and fs ext4 in remove_crypt Oct 6 04:59:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AdGx and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.awrs70wbmount_test with fs ext3 Oct 6 05:00:13 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:00:13 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 65af33f7-8713-4cb8-9fb8-86d528c6ea8b r/w with ordered data mode. Quota mode: none. Oct 6 05:00:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.awrs70wbmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/AdGx and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/AdGx and fs ext2 in remove_crypt Oct 6 05:00:18 storageqe-109 systemd[1]: tmp-libblockdev.awrs70wbmount_test.mount: Deactivated successfully. Oct 6 05:00:18 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 65af33f7-8713-4cb8-9fb8-86d528c6ea8b. Oct 6 05:00:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AdGx and fs ext3 in remove_crypt Oct 6 05:00:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AdGx and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e61ichzzmount_test with fs ext2 Oct 6 05:00:38 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:00:38 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8145ee59-01b9-4783-8d6b-a0ea59f31d02 r/w without journal. Quota mode: none. Oct 6 05:00:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e61ichzzmount_test with fs ext2 Oct 6 05:00:43 storageqe-109 systemd[1]: tmp-libblockdev.e61ichzzmount_test.mount: Deactivated successfully. Oct 6 05:00:43 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8145ee59-01b9-4783-8d6b-a0ea59f31d02. INFO: End IO testing with the luks device /dev/mapper/AdGx and fs ext2 in remove_crypt INFO: remove crypt device AdGx Oct 6 05:00:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AdGx and fs ext2 in remove_crypt Oct 6 05:00:43 storageqe-109 INFO: remove crypt device AdGx cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:00:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 05:00:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:01:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:01:16 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:01:16 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:01:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:01:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device AdGx cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:01:37 storageqe-109 INFO: finishe the remove crypt device AdGx Oct 6 05:01:38 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:01:49 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:01:49 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:01:49 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:01:49 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:01:50 storageqe-109 stratisd[4947]: [2025-10-06T09:01:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:01:50 storageqe-109 stratisd[4947]: [2025-10-06T09:01:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 WCaL -q Oct 6 05:01:59 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 WCaL -q Oct 6 05:02:02 storageqe-109 stratisd[4947]: [2025-10-06T09:02:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:02:02 storageqe-109 stratisd[4947]: [2025-10-06T09:02:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:02:08 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.dhvtbsewmount_test with fs xfs Oct 6 05:02:23 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem e6cde744-7a12-4507-ae18-91c0550cc490 Oct 6 05:02:23 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:02:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dhvtbsewmount_test with fs xfs Oct 6 05:02:28 storageqe-109 systemd[1]: tmp-libblockdev.dhvtbsewmount_test.mount: Deactivated successfully. Oct 6 05:02:28 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem e6cde744-7a12-4507-ae18-91c0550cc490 INFO: will run io in dir /tmp/libblockdev.l8b0dgf7mount_test with fs ext2 Oct 6 05:02:49 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:02:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d250807b-7d33-44bd-b815-184a0b7416ae r/w without journal. Quota mode: none. Oct 6 05:02:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l8b0dgf7mount_test with fs ext2 Oct 6 05:02:54 storageqe-109 systemd[1]: tmp-libblockdev.l8b0dgf7mount_test.mount: Deactivated successfully. Oct 6 05:02:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d250807b-7d33-44bd-b815-184a0b7416ae. INFO: will run io in dir /tmp/libblockdev.b57wiim5mount_test with fs ext3 Oct 6 05:03:16 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:03:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 54b24191-e368-43dd-a559-0045c8e81e20 r/w with ordered data mode. Quota mode: none. Oct 6 05:03:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b57wiim5mount_test with fs ext3 Oct 6 05:03:21 storageqe-109 systemd[1]: tmp-libblockdev.b57wiim5mount_test.mount: Deactivated successfully. Oct 6 05:03:21 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 54b24191-e368-43dd-a559-0045c8e81e20. INFO: will run io in dir /tmp/libblockdev.yrxxgsnjmount_test with fs ext4 Oct 6 05:03:32 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 678679d4-04e6-41d7-96c5-996f72b331ee r/w with ordered data mode. Quota mode: none. Oct 6 05:03:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yrxxgsnjmount_test with fs ext4 Oct 6 05:03:38 storageqe-109 systemd[1]: tmp-libblockdev.yrxxgsnjmount_test.mount: Deactivated successfully. Oct 6 05:03:38 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 678679d4-04e6-41d7-96c5-996f72b331ee. INFO: will run io in dir /tmp/libblockdev.kzhafjzymount_test with fs xfs Oct 6 05:03:49 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 03918cc9-04bd-4a73-9200-11fff8348436 Oct 6 05:03:49 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:03:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kzhafjzymount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/WCaL and fs xfs in remove_crypt Oct 6 05:03:54 storageqe-109 systemd[1]: tmp-libblockdev.kzhafjzymount_test.mount: Deactivated successfully. Oct 6 05:03:54 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 03918cc9-04bd-4a73-9200-11fff8348436 Oct 6 05:03:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WCaL and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.rlw_unwdmount_test with fs xfs Oct 6 05:04:05 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem d7052106-0948-41e6-aedd-b769a27c5d00 Oct 6 05:04:05 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:04:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rlw_unwdmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/WCaL and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WCaL and fs ext4 in remove_crypt Oct 6 05:04:10 storageqe-109 systemd[1]: tmp-libblockdev.rlw_unwdmount_test.mount: Deactivated successfully. Oct 6 05:04:10 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem d7052106-0948-41e6-aedd-b769a27c5d00 Oct 6 05:04:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WCaL and fs xfs in remove_crypt Oct 6 05:04:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WCaL and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cu8iv099mount_test with fs ext4 Oct 6 05:04:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b7ea03d6-6f87-4a0c-a3a0-e3644dfcc572 r/w with ordered data mode. Quota mode: none. Oct 6 05:04:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cu8iv099mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/WCaL and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WCaL and fs ext3 in remove_crypt Oct 6 05:04:26 storageqe-109 systemd[1]: tmp-libblockdev.cu8iv099mount_test.mount: Deactivated successfully. Oct 6 05:04:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b7ea03d6-6f87-4a0c-a3a0-e3644dfcc572. Oct 6 05:04:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WCaL and fs ext4 in remove_crypt Oct 6 05:04:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WCaL and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.o5r4a8gymount_test with fs ext3 Oct 6 05:04:48 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:04:48 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 580c8d3a-07cd-41d4-8015-c3b244325e4e r/w with ordered data mode. Quota mode: none. Oct 6 05:04:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.o5r4a8gymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/WCaL and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WCaL and fs ext2 in remove_crypt Oct 6 05:04:53 storageqe-109 systemd[1]: tmp-libblockdev.o5r4a8gymount_test.mount: Deactivated successfully. Oct 6 05:04:53 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 580c8d3a-07cd-41d4-8015-c3b244325e4e. Oct 6 05:04:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WCaL and fs ext3 in remove_crypt Oct 6 05:04:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WCaL and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.w6y6472mmount_test with fs ext2 Oct 6 05:05:15 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:05:15 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 44c2ceb2-3a6a-4e9f-8312-01710438a2ae r/w without journal. Quota mode: none. Oct 6 05:05:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.w6y6472mmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/WCaL and fs ext2 in remove_crypt INFO: remove crypt device WCaL Oct 6 05:05:20 storageqe-109 systemd[1]: tmp-libblockdev.w6y6472mmount_test.mount: Deactivated successfully. Oct 6 05:05:20 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 44c2ceb2-3a6a-4e9f-8312-01710438a2ae. Oct 6 05:05:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WCaL and fs ext2 in remove_crypt Oct 6 05:05:20 storageqe-109 INFO: remove crypt device WCaL cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:05:20 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 05:05:30 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:05:42 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:05:52 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:05:52 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:05:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:06:04 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device WCaL Oct 6 05:06:14 storageqe-109 INFO: finishe the remove crypt device WCaL cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:06:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:06:25 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:06:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hw_opal #### INFO: #### will start test_hw_rw ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:06:41 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:06:41 storageqe-109 INFO: #### END test_hw_opal #### Oct 6 05:06:41 storageqe-109 INFO: #### will start test_hw_rw ##### Oct 6 05:06:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:06:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:06:58 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:06:59 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:07:09 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:07:19 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:07:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:07:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:07:20 storageqe-109 stratisd[4947]: [2025-10-06T09:07:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:07:20 storageqe-109 stratisd[4947]: [2025-10-06T09:07:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 DjCz -q --allow-discards Oct 6 05:07:29 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 DjCz -q --allow-discards Oct 6 05:07:32 storageqe-109 stratisd[4947]: [2025-10-06T09:07:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:07:32 storageqe-109 stratisd[4947]: [2025-10-06T09:07:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:07:39 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup luksSuspend DjCz -q Oct 6 05:07:42 storageqe-109 journal: cryptsetup luksSuspend DjCz -q cryptsetup close DjCz -q Oct 6 05:07:52 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32528, 256 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32528 op 0x0:(READ) flags 0x2080700 phys_seg 16 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32784, 256 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32784 op 0x0:(READ) flags 0x2080700 phys_seg 16 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32768, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32768 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32768, async page read Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32769, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32769 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32769, async page read Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32770, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32770 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32770, async page read Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32771, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32771 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32771, async page read Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32772, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32772 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32772, async page read Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32773, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32773 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32773, async page read Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32774, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32774 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32774, async page read Oct 6 05:07:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32775, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:07:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32775 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:07:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32775, async page read Oct 6 05:07:52 storageqe-109 journal: cryptsetup close DjCz -q Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32760, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32760 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32760, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32761, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32762, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32763, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32764, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32765, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32766, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32767, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32768, lost async page write Oct 6 05:08:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32769, lost async page write Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32793, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32793 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32794, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32794 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32919, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32795, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32919 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32795 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32920, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32796, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32920 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32796 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32953, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32797, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32953 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32797 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32954, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32798 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: nvme_log_error: 3804 callbacks suppressed Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51838, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: blk_print_req_error: 3804 callbacks suppressed Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51838 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: buffer_io_error: 19068 callbacks suppressed Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51838, lost async page write Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51839, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51839 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51839, lost async page write Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51840, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51840 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51840, lost async page write Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51841, lost async page write Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51842, lost async page write Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51843, lost async page write Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51844, lost async page write Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51845, lost async page write Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51846, lost async page write Oct 6 05:08:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51847, lost async page write Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51873, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51873 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51874, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51874 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51875, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51875 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51876, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51876 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51877, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51877 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51878, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51878 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51879, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51879 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: nvme_log_error: 4131 callbacks suppressed Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72555, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: blk_print_req_error: 4131 callbacks suppressed Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72555 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: buffer_io_error: 20707 callbacks suppressed Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72555, lost async page write Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72556, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72556 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72556, lost async page write Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72557, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72557 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72557, lost async page write Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72558, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72558 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72558, lost async page write Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72559, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72559 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72559, lost async page write Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72560, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72560 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72560, lost async page write Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72561, lost async page write Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72562, lost async page write Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72563, lost async page write Oct 6 05:08:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72564, lost async page write Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72593, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72593 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72594, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72594 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72595, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72595 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72596, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72596 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: nvme_log_error: 4133 callbacks suppressed Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93274, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: blk_print_req_error: 4133 callbacks suppressed Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93274 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: buffer_io_error: 20709 callbacks suppressed Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93274, lost async page write Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93275, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93275 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93275, lost async page write Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93276, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93276 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93276, lost async page write Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93277, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93277 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93277, lost async page write Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93278, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93278 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93278, lost async page write Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93279, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93279 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93279, lost async page write Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93280, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93280 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93280, lost async page write Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93281, lost async page write Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93282, lost async page write Oct 6 05:08:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93283, lost async page write Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93313, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93313 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93314, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93314 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93315, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93315 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme_log_error: 4131 callbacks suppressed Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113959, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: blk_print_req_error: 4131 callbacks suppressed Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113959 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: buffer_io_error: 20675 callbacks suppressed Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113959, lost async page write Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113960, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113960 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113960, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113961, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113962, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113963, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113964, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113965, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113966, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113967, lost async page write Oct 6 05:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 113968, lost async page write Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113993, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113993 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113994, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113994 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113995, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113995 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113996, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113996 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113997, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113997 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113998, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113998 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 113999, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 113999 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114000, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114000 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: nvme_log_error: 4132 callbacks suppressed Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134677, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: blk_print_req_error: 4132 callbacks suppressed Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134677 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: buffer_io_error: 20708 callbacks suppressed Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134677, lost async page write Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134678, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134678 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134678, lost async page write Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134679, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134679 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134679, lost async page write Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134680, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134680 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134680, lost async page write Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134681, lost async page write Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134682, lost async page write Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134683, lost async page write Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134684, lost async page write Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134685, lost async page write Oct 6 05:08:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134686, lost async page write Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134713, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134713 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134714, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134714 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134715, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134715 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134716, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134716 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134717, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134717 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134718, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134718 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme_log_error: 4129 callbacks suppressed Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155360, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: blk_print_req_error: 4129 callbacks suppressed Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155360 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: buffer_io_error: 20673 callbacks suppressed Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155360, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155361, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155362, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155363, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155364, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155365, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155366, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155367, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155368, lost async page write Oct 6 05:08:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155369, lost async page write Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155393 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155394 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155395 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155396 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155397 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155398 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155399 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155400, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155400 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155433, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155433 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: nvme_log_error: 4382 callbacks suppressed Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 177616, 32 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: blk_print_req_error: 4382 callbacks suppressed Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 177616 op 0x1:(WRITE) flags 0x2100000 phys_seg 32 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: buffer_io_error: 22246 callbacks suppressed Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 177616, lost async page write Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 177648, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 177617, lost async page write Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178152, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178152 op 0x1:(WRITE) flags 0x2104000 phys_seg 33 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178152, lost async page write Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178153, lost async page write Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178154, lost async page write Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178155, lost async page write Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178156, lost async page write Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178157, lost async page write Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178158, lost async page write Oct 6 05:08:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178159, lost async page write Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178185, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178185 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178186, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178186 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178187, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178187 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178188, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178188 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178189, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178189 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 177648 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178190, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178190 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178191, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178191 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: nvme_log_error: 4235 callbacks suppressed Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199369, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199200, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199370, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: blk_print_req_error: 4236 callbacks suppressed Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199200 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199370 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: buffer_io_error: 21648 callbacks suppressed Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199200, lost async page write Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199370, lost async page write Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199201, lost async page write Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199371, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199202, lost async page write Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199371 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199203, lost async page write Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199371, lost async page write Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199204, lost async page write Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199372, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199205, lost async page write Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199372 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199206, lost async page write Oct 6 05:08:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 199372, lost async page write Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199233, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199373, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199233 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199373 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199234, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199374, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199234 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 199374 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 199235, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 200408 op 0x1:(WRITE) flags 0x2104000 phys_seg 33 prio class 0 Oct 6 05:08:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 200441 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:08:46 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:08:46 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:08:47 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:08:59 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:09:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hw_rw #### INFO: #### will start test_hw_opal_header ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:09:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:09:15 storageqe-109 INFO: #### END test_hw_rw #### Oct 6 05:09:15 storageqe-109 INFO: #### will start test_hw_opal_header ##### Oct 6 05:09:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:09:21 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:09:31 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:09:32 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' --header '/tmp/testheaderIJU' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:09:42 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderIJU' luksFormat /dev/nvme0n1 -q --hw-opal cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q Oct 6 05:10:03 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q Oct 6 05:10:12 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderIJU' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:10:13 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderIJU' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:10:13 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:10:13 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:10:13 storageqe-109 kernel: nvme_log_error: 1444 callbacks suppressed Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: blk_print_req_error: 1443 callbacks suppressed Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: buffer_io_error: 5908 callbacks suppressed Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 0, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 1, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 1 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 1, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 2, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 2 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 2, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 4, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 4 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 4, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 5, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 5 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 5, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 6, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 6 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 6, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 7, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 7 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 7, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 0, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 1, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 1 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 1, async page read Oct 6 05:10:13 storageqe-109 kernel: nvme0n1: unable to read partition table cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q Oct 6 05:10:27 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderIJU' --sector-size '512' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:10:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderIJU' --sector-size '512' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:10:37 storageqe-109 kernel: nvme_log_error: 1412 callbacks suppressed Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: blk_print_req_error: 1412 callbacks suppressed Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: buffer_io_error: 1398 callbacks suppressed Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:10:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:10:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:10:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q Oct 6 05:10:50 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q cryptsetup --header '/tmp/testheaderIJU' open /dev/nvme0n1 NRcj -q Oct 6 05:11:00 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' open /dev/nvme0n1 NRcj -q Oct 6 05:11:07 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --header '/tmp/testheaderIJU' luksSuspend NRcj -q Oct 6 05:11:11 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksSuspend NRcj -q cryptsetup --header '/tmp/testheaderIJU' luksResume NRcj -q Oct 6 05:11:21 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksResume NRcj -q cryptsetup --header '/tmp/testheaderIJU' luksSuspend NRcj -q Oct 6 05:11:32 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksSuspend NRcj -q cryptsetup luksResume NRcj -q Oct 6 05:11:42 storageqe-109 journal: cryptsetup luksResume NRcj -q Oct 6 05:11:42 storageqe-109 kernel: nvme_log_error: 149 callbacks suppressed Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: blk_print_req_error: 149 callbacks suppressed Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 64, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 64 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 128, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 128 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 256, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 256 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 512, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 512 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 1024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 1024 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 2048, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 2048 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 6 05:11:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 4096, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:11:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 4096 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 cryptsetup --header '/tmp/testheaderIJU' luksResume NRcj -q Oct 6 05:11:53 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksResume NRcj -q INFO: start IO testing with the luks device /dev/mapper/NRcj and fs xfs in remove_crypt Oct 6 05:12:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NRcj and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.6v23y7_gmount_test with fs xfs Oct 6 05:12:13 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f1cb32b1-2f48-4d44-a520-0820dde10476 Oct 6 05:12:13 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:12:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6v23y7_gmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/NRcj and fs xfs in remove_crypt Oct 6 05:12:18 storageqe-109 systemd[1]: tmp-libblockdev.6v23y7_gmount_test.mount: Deactivated successfully. Oct 6 05:12:18 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f1cb32b1-2f48-4d44-a520-0820dde10476 Oct 6 05:12:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NRcj and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NRcj and fs ext4 in remove_crypt Oct 6 05:12:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NRcj and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ezg_47t7mount_test with fs ext4 Oct 6 05:12:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2124a64c-d265-479e-adda-13892f290c9f r/w with ordered data mode. Quota mode: none. Oct 6 05:12:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ezg_47t7mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/NRcj and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NRcj and fs ext3 in remove_crypt Oct 6 05:12:34 storageqe-109 systemd[1]: tmp-libblockdev.ezg_47t7mount_test.mount: Deactivated successfully. Oct 6 05:12:34 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2124a64c-d265-479e-adda-13892f290c9f. Oct 6 05:12:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NRcj and fs ext4 in remove_crypt Oct 6 05:12:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NRcj and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ayqlhuy8mount_test with fs ext3 Oct 6 05:12:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:12:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ff4acd07-91b2-4b15-829a-0b4908a7d044 r/w with ordered data mode. Quota mode: none. Oct 6 05:12:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ayqlhuy8mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/NRcj and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NRcj and fs ext2 in remove_crypt Oct 6 05:13:00 storageqe-109 systemd[1]: tmp-libblockdev.ayqlhuy8mount_test.mount: Deactivated successfully. Oct 6 05:13:00 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ff4acd07-91b2-4b15-829a-0b4908a7d044. Oct 6 05:13:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NRcj and fs ext3 in remove_crypt Oct 6 05:13:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NRcj and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.sowvd9rhmount_test with fs ext2 Oct 6 05:13:21 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:13:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 36d56735-ffeb-4223-98bf-f127bc0f3f9b r/w without journal. Quota mode: none. Oct 6 05:13:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sowvd9rhmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/NRcj and fs ext2 in remove_crypt INFO: remove crypt device NRcj Oct 6 05:13:26 storageqe-109 systemd[1]: tmp-libblockdev.sowvd9rhmount_test.mount: Deactivated successfully. Oct 6 05:13:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 36d56735-ffeb-4223-98bf-f127bc0f3f9b. Oct 6 05:13:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NRcj and fs ext2 in remove_crypt Oct 6 05:13:26 storageqe-109 INFO: remove crypt device NRcj cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q Oct 6 05:13:26 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q cryptsetup --header '/tmp/testheaderIJU' erase /dev/nvme0n1 -q Oct 6 05:13:36 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' erase /dev/nvme0n1 -q cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q Oct 6 05:13:48 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:13:58 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:13:58 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:13:58 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q Oct 6 05:14:10 storageqe-109 journal: cryptsetup --header '/tmp/testheaderIJU' luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device NRcj Oct 6 05:14:20 storageqe-109 INFO: finishe the remove crypt device NRcj cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:14:21 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:14:31 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:14:32 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hw_opal_header #### INFO: #### will start test_partitions_in_same_disk ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:14:47 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:14:47 storageqe-109 INFO: #### END test_hw_opal_header #### Oct 6 05:14:47 storageqe-109 INFO: #### will start test_partitions_in_same_disk ##### Oct 6 05:14:47 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:14:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:15:04 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:15:05 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 05:15:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:15:05 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 05:15:05 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 05:15:15 storageqe-109 kernel: nvme0n1: Oct 6 05:15:15 storageqe-109 kernel: nvme0n1: p1 Oct 6 05:15:15 storageqe-109 kernel: nvme0n1: p1 p2 p3 Oct 6 05:15:15 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 Oct 6 05:15:15 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 Oct 6 05:15:16 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 p7 Oct 6 05:15:16 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal Oct 6 05:15:25 storageqe-109 kernel: nvme_log_error: 1 callbacks suppressed Oct 6 05:15:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:25 storageqe-109 kernel: blk_print_req_error: 1 callbacks suppressed Oct 6 05:15:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:25 storageqe-109 kernel: buffer_io_error: 142 callbacks suppressed Oct 6 05:15:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 05:15:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 05:15:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:15:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 6 05:15:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:15:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:15:26 storageqe-109 stratisd[4947]: [2025-10-06T09:15:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:15:26 storageqe-109 stratisd[4947]: [2025-10-06T09:15:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 05:15:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 6 05:15:36 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 6 05:15:45 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310464, async page read Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:15:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:15:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:15:45 storageqe-109 stratisd[4947]: [2025-10-06T09:15:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:15:45 storageqe-109 stratisd[4947]: [2025-10-06T09:15:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 6 05:15:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 6 05:15:55 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 6 05:16:04 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:16:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:04 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:16:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:04 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:16:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 6 05:16:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 6 05:16:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:16:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310464, async page read Oct 6 05:16:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:16:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:16:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:16:05 storageqe-109 stratisd[4947]: [2025-10-06T09:16:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:16:05 storageqe-109 stratisd[4947]: [2025-10-06T09:16:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:16:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 6 05:16:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 6 05:16:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 6 05:16:15 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 6 05:16:24 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310464, async page read Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:16:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:16:24 storageqe-109 stratisd[4947]: [2025-10-06T09:16:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:16:24 storageqe-109 stratisd[4947]: [2025-10-06T09:16:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 6 05:16:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 6 05:16:34 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 6 05:16:43 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:16:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:43 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:16:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:43 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:16:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310464, async page read Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:16:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:16:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:16:44 storageqe-109 stratisd[4947]: [2025-10-06T09:16:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:16:44 storageqe-109 stratisd[4947]: [2025-10-06T09:16:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 6 05:16:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 6 05:16:54 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 6 05:17:03 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310464, async page read Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:17:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:17:03 storageqe-109 stratisd[4947]: [2025-10-06T09:17:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:17:03 storageqe-109 stratisd[4947]: [2025-10-06T09:17:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 6 05:17:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 6 05:17:13 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 6 05:17:23 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310464, async page read Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:17:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:17:23 storageqe-109 stratisd[4947]: [2025-10-06T09:17:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:17:23 storageqe-109 stratisd[4947]: [2025-10-06T09:17:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 6 05:17:23 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 6 05:17:33 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 6 05:17:42 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310464, async page read Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:17:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:17:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:17:42 storageqe-109 stratisd[4947]: [2025-10-06T09:17:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:17:42 storageqe-109 stratisd[4947]: [2025-10-06T09:17:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 6 05:17:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 05:17:52 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q cryptsetup erase /dev/nvme0n1p1 -q Oct 6 05:18:02 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p1 -q Oct 6 05:18:03 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 05:18:13 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p2 -q Oct 6 05:18:23 storageqe-109 INFO: finishe the remove crypt device None Oct 6 05:18:23 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q cryptsetup erase /dev/nvme0n1p2 -q Oct 6 05:18:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p2 -q cryptsetup luksDump /dev/nvme0n1p2 -q Oct 6 05:18:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p3 -q Oct 6 05:18:54 storageqe-109 INFO: finishe the remove crypt device None Oct 6 05:18:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q cryptsetup erase /dev/nvme0n1p3 -q Oct 6 05:19:04 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p3 -q cryptsetup luksDump /dev/nvme0n1p3 -q Oct 6 05:19:15 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p4 -q Oct 6 05:19:25 storageqe-109 INFO: finishe the remove crypt device None Oct 6 05:19:25 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q cryptsetup erase /dev/nvme0n1p4 -q Oct 6 05:19:35 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p4 -q cryptsetup luksDump /dev/nvme0n1p4 -q Oct 6 05:19:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q INFO: finishe the remove crypt device None Oct 6 05:19:56 storageqe-109 INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p5 -q Oct 6 05:19:56 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q cryptsetup erase /dev/nvme0n1p5 -q Oct 6 05:20:06 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p5 -q cryptsetup luksDump /dev/nvme0n1p5 -q Oct 6 05:20:17 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p6 -q Oct 6 05:20:27 storageqe-109 INFO: finishe the remove crypt device None Oct 6 05:20:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q cryptsetup erase /dev/nvme0n1p6 -q Oct 6 05:20:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p6 -q cryptsetup luksDump /dev/nvme0n1p6 -q Oct 6 05:20:47 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q INFO: finishe the remove crypt device None Oct 6 05:20:57 storageqe-109 INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p7 -q Oct 6 05:20:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q cryptsetup erase /dev/nvme0n1p7 -q Oct 6 05:21:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p7 -q cryptsetup luksDump /dev/nvme0n1p7 -q Oct 6 05:21:18 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p8 -q Oct 6 05:21:28 storageqe-109 INFO: finishe the remove crypt device None Oct 6 05:21:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q cryptsetup erase /dev/nvme0n1p8 -q Oct 6 05:21:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p8 -q cryptsetup luksDump /dev/nvme0n1p8 -q Oct 6 05:21:49 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q INFO: finishe the remove crypt device None Oct 6 05:21:59 storageqe-109 INFO: finishe the remove crypt device None Oct 6 05:22:00 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 6 05:22:02 storageqe-109 kernel: nvme0n1: p3 p4 p5 p6 p7 p8 Oct 6 05:22:03 storageqe-109 kernel: nvme0n1: p4 p5 p6 p7 p8 Oct 6 05:22:04 storageqe-109 kernel: nvme0n1: p5 p6 p7 p8 Oct 6 05:22:05 storageqe-109 kernel: nvme0n1: p6 p7 p8 Oct 6 05:22:06 storageqe-109 kernel: nvme0n1: p7 p8 Oct 6 05:22:07 storageqe-109 kernel: nvme0n1: p7 p8 cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:22:08 storageqe-109 kernel: nvme0n1: p7 Oct 6 05:22:08 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:22:08 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:22:08 storageqe-109 kernel: nvme0n1: p7 Oct 6 05:22:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:22:21 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:22:32 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:22:32 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_partitions_in_same_disk #### INFO: #### will start test_upstream_opal_test ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:22:47 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:22:48 storageqe-109 INFO: #### END test_partitions_in_same_disk #### Oct 6 05:22:48 storageqe-109 INFO: #### will start test_upstream_opal_test ##### Oct 6 05:22:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:22:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:23:04 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:23:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:23:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:23:27 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:23:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_upstream_opal_test #### INFO: #### will start test_hw_opal_tang ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:23:42 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:23:42 storageqe-109 INFO: #### END test_upstream_opal_test #### Oct 6 05:23:42 storageqe-109 INFO: #### will start test_hw_opal_tang ##### Oct 6 05:23:42 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:23:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:23:59 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:24:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:24:10 storageqe-109 systemd[1]: Reload requested from client PID 549016 ('systemctl') (unit session-4.scope)... Oct 6 05:24:10 storageqe-109 systemd[1]: Reloading... Oct 6 05:24:10 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 6 05:24:10 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 05:24:10 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 05:24:10 storageqe-109 systemd[1]: Reloading finished in 159 ms. Oct 6 05:24:10 storageqe-109 kernel: nvme0n1: Oct 6 05:24:10 storageqe-109 kernel: nvme0n1: p1 Oct 6 05:24:10 storageqe-109 kernel: nvme0n1: p1 p2 Oct 6 05:24:11 storageqe-109 kernel: nvme0n1: p1 p2 p3 Oct 6 05:24:11 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal Oct 6 05:24:11 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 Oct 6 05:24:11 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 Oct 6 05:24:11 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 p7 Oct 6 05:24:11 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8 Oct 6 05:24:11 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal Oct 6 05:24:21 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:21 storageqe-109 stratisd[4947]: [2025-10-06T09:24:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:21 storageqe-109 stratisd[4947]: [2025-10-06T09:24:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 05:24:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:33 storageqe-109 systemd[1]: Created slice system-tangd.slice - Slice /system/tangd. Oct 6 05:24:33 storageqe-109 systemd[1]: Started tangd@0-10.73.194.89:80-10.73.194.89:33830.service - Tang Server (10.73.194.89:33830). Oct 6 05:24:33 storageqe-109 tangd[550166]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:24:33 storageqe-109 systemd[1]: tangd@0-10.73.194.89:80-10.73.194.89:33830.service: Deactivated successfully. Oct 6 05:24:37 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:24:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:37 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:24:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:37 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:24:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 05:24:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 05:24:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 6 05:24:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:38 storageqe-109 systemd[1]: Started tangd@1-10.73.194.89:80-10.73.194.89:57944.service - Tang Server (10.73.194.89:57944). Oct 6 05:24:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 6 05:24:38 storageqe-109 stratisd[4947]: [2025-10-06T09:24:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:38 storageqe-109 stratisd[4947]: [2025-10-06T09:24:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 6 05:24:38 storageqe-109 tangd[550662]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:24:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 6 05:24:38 storageqe-109 systemd[1]: tangd@1-10.73.194.89:80-10.73.194.89:57944.service: Deactivated successfully. Oct 6 05:24:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 6 05:24:40 storageqe-109 stratisd[4947]: [2025-10-06T09:24:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:40 storageqe-109 stratisd[4947]: [2025-10-06T09:24:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:40 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 6 05:24:50 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310464, async page read Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:24:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:24:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:24:50 storageqe-109 stratisd[4947]: [2025-10-06T09:24:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:50 storageqe-109 stratisd[4947]: [2025-10-06T09:24:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 6 05:24:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:25:02 storageqe-109 systemd[1]: Started tangd@2-10.73.194.89:80-10.73.194.89:41254.service - Tang Server (10.73.194.89:41254). Oct 6 05:25:02 storageqe-109 tangd[551927]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:25:02 storageqe-109 systemd[1]: tangd@2-10.73.194.89:80-10.73.194.89:41254.service: Deactivated successfully. Oct 6 05:25:06 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310464, async page read Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:25:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:25:06 storageqe-109 stratisd[4947]: [2025-10-06T09:25:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:06 storageqe-109 stratisd[4947]: [2025-10-06T09:25:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 6 05:25:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 6 05:25:06 storageqe-109 systemd[1]: Started tangd@3-10.73.194.89:80-10.73.194.89:41546.service - Tang Server (10.73.194.89:41546). Oct 6 05:25:06 storageqe-109 tangd[552423]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:25:06 storageqe-109 systemd[1]: tangd@3-10.73.194.89:80-10.73.194.89:41546.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 6 05:25:09 storageqe-109 stratisd[4947]: [2025-10-06T09:25:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:09 storageqe-109 stratisd[4947]: [2025-10-06T09:25:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:09 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 6 05:25:18 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:25:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310464, async page read Oct 6 05:25:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:19 storageqe-109 stratisd[4947]: [2025-10-06T09:25:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:19 storageqe-109 stratisd[4947]: [2025-10-06T09:25:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 6 05:25:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 6 05:25:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:31 storageqe-109 systemd[1]: Started tangd@4-10.73.194.89:80-10.73.194.89:60816.service - Tang Server (10.73.194.89:60816). Oct 6 05:25:31 storageqe-109 tangd[553670]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:25:31 storageqe-109 systemd[1]: tangd@4-10.73.194.89:80-10.73.194.89:60816.service: Deactivated successfully. Oct 6 05:25:35 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310464, async page read Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:35 storageqe-109 stratisd[4947]: [2025-10-06T09:25:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:35 storageqe-109 stratisd[4947]: [2025-10-06T09:25:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 6 05:25:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 6 05:25:35 storageqe-109 systemd[1]: Started tangd@5-10.73.194.89:80-10.73.194.89:60826.service - Tang Server (10.73.194.89:60826). Oct 6 05:25:35 storageqe-109 tangd[554166]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:25:35 storageqe-109 systemd[1]: tangd@5-10.73.194.89:80-10.73.194.89:60826.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 6 05:25:38 storageqe-109 stratisd[4947]: [2025-10-06T09:25:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:38 storageqe-109 stratisd[4947]: [2025-10-06T09:25:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:38 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 6 05:25:47 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310464, async page read Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:25:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:25:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:25:47 storageqe-109 stratisd[4947]: [2025-10-06T09:25:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:47 storageqe-109 stratisd[4947]: [2025-10-06T09:25:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 6 05:25:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:25:59 storageqe-109 systemd[1]: Started tangd@6-10.73.194.89:80-10.73.194.89:45338.service - Tang Server (10.73.194.89:45338). Oct 6 05:25:59 storageqe-109 tangd[555413]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:25:59 storageqe-109 systemd[1]: tangd@6-10.73.194.89:80-10.73.194.89:45338.service: Deactivated successfully. Oct 6 05:26:03 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:26:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:03 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:26:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310464, async page read Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:26:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:26:04 storageqe-109 stratisd[4947]: [2025-10-06T09:26:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:04 storageqe-109 stratisd[4947]: [2025-10-06T09:26:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 6 05:26:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 6 05:26:04 storageqe-109 systemd[1]: Started tangd@7-10.73.194.89:80-10.73.194.89:45348.service - Tang Server (10.73.194.89:45348). Oct 6 05:26:04 storageqe-109 tangd[555910]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:26:04 storageqe-109 systemd[1]: tangd@7-10.73.194.89:80-10.73.194.89:45348.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 6 05:26:06 storageqe-109 stratisd[4947]: [2025-10-06T09:26:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:06 storageqe-109 stratisd[4947]: [2025-10-06T09:26:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:07 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 6 05:26:16 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310464, async page read Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:16 storageqe-109 stratisd[4947]: [2025-10-06T09:26:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:16 storageqe-109 stratisd[4947]: [2025-10-06T09:26:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 6 05:26:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:28 storageqe-109 systemd[1]: Started tangd@8-10.73.194.89:80-10.73.194.89:55174.service - Tang Server (10.73.194.89:55174). Oct 6 05:26:28 storageqe-109 tangd[557159]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:26:28 storageqe-109 systemd[1]: tangd@8-10.73.194.89:80-10.73.194.89:55174.service: Deactivated successfully. Oct 6 05:26:32 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310464, async page read Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:32 storageqe-109 stratisd[4947]: [2025-10-06T09:26:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:32 storageqe-109 stratisd[4947]: [2025-10-06T09:26:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 6 05:26:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 6 05:26:32 storageqe-109 systemd[1]: Started tangd@9-10.73.194.89:80-10.73.194.89:55186.service - Tang Server (10.73.194.89:55186). Oct 6 05:26:32 storageqe-109 tangd[557657]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:26:32 storageqe-109 systemd[1]: tangd@9-10.73.194.89:80-10.73.194.89:55186.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 6 05:26:35 storageqe-109 stratisd[4947]: [2025-10-06T09:26:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:35 storageqe-109 stratisd[4947]: [2025-10-06T09:26:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:35 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 6 05:26:44 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:26:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:44 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:26:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:44 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:26:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310464, async page read Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:26:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:26:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:26:45 storageqe-109 stratisd[4947]: [2025-10-06T09:26:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:45 storageqe-109 stratisd[4947]: [2025-10-06T09:26:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 6 05:26:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:26:57 storageqe-109 systemd[1]: Started tangd@10-10.73.194.89:80-10.73.194.89:52764.service - Tang Server (10.73.194.89:52764). Oct 6 05:26:57 storageqe-109 tangd[558919]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:26:57 storageqe-109 systemd[1]: tangd@10-10.73.194.89:80-10.73.194.89:52764.service: Deactivated successfully. Oct 6 05:27:01 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310464, async page read Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:27:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:27:01 storageqe-109 stratisd[4947]: [2025-10-06T09:27:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:01 storageqe-109 stratisd[4947]: [2025-10-06T09:27:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 6 05:27:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 6 05:27:01 storageqe-109 systemd[1]: Started tangd@11-10.73.194.89:80-10.73.194.89:52770.service - Tang Server (10.73.194.89:52770). Oct 6 05:27:01 storageqe-109 tangd[559416]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:27:01 storageqe-109 systemd[1]: tangd@11-10.73.194.89:80-10.73.194.89:52770.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 6 05:27:04 storageqe-109 stratisd[4947]: [2025-10-06T09:27:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:04 storageqe-109 stratisd[4947]: [2025-10-06T09:27:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:04 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 6 05:27:13 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310464, async page read Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:13 storageqe-109 stratisd[4947]: [2025-10-06T09:27:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:13 storageqe-109 stratisd[4947]: [2025-10-06T09:27:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 6 05:27:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:25 storageqe-109 systemd[1]: Started tangd@12-10.73.194.89:80-10.73.194.89:35114.service - Tang Server (10.73.194.89:35114). Oct 6 05:27:25 storageqe-109 tangd[560662]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:27:25 storageqe-109 systemd[1]: tangd@12-10.73.194.89:80-10.73.194.89:35114.service: Deactivated successfully. Oct 6 05:27:29 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:27:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:29 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:27:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310464, async page read Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:30 storageqe-109 stratisd[4947]: [2025-10-06T09:27:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:30 storageqe-109 stratisd[4947]: [2025-10-06T09:27:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 6 05:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 6 05:27:30 storageqe-109 systemd[1]: Started tangd@13-10.73.194.89:80-10.73.194.89:35122.service - Tang Server (10.73.194.89:35122). Oct 6 05:27:30 storageqe-109 tangd[561158]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:27:30 storageqe-109 systemd[1]: tangd@13-10.73.194.89:80-10.73.194.89:35122.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 6 05:27:32 storageqe-109 stratisd[4947]: [2025-10-06T09:27:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:32 storageqe-109 stratisd[4947]: [2025-10-06T09:27:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:33 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 6 05:27:42 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310464, async page read Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:42 storageqe-109 stratisd[4947]: [2025-10-06T09:27:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:42 storageqe-109 stratisd[4947]: [2025-10-06T09:27:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 6 05:27:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:54 storageqe-109 systemd[1]: Started tangd@14-10.73.194.89:80-10.73.194.89:52248.service - Tang Server (10.73.194.89:52248). Oct 6 05:27:54 storageqe-109 tangd[562421]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 6 05:27:54 storageqe-109 systemd[1]: tangd@14-10.73.194.89:80-10.73.194.89:52248.service: Deactivated successfully. Oct 6 05:27:58 storageqe-109 kernel: nvme_log_error: 8 callbacks suppressed Oct 6 05:27:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:58 storageqe-109 kernel: blk_print_req_error: 8 callbacks suppressed Oct 6 05:27:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:58 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:27:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 6 05:27:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 6 05:27:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310464, async page read Oct 6 05:27:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:27:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:59 storageqe-109 stratisd[4947]: [2025-10-06T09:27:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:59 storageqe-109 stratisd[4947]: [2025-10-06T09:27:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 6 05:27:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 6 05:27:59 storageqe-109 systemd[1]: Started tangd@15-10.73.194.89:80-10.73.194.89:39314.service - Tang Server (10.73.194.89:39314). Oct 6 05:27:59 storageqe-109 tangd[562917]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 6 05:27:59 storageqe-109 systemd[1]: tangd@15-10.73.194.89:80-10.73.194.89:39314.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs xfs in remove_crypt Oct 6 05:28:01 storageqe-109 stratisd[4947]: [2025-10-06T09:28:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:28:01 storageqe-109 stratisd[4947]: [2025-10-06T09:28:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:28:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs xfs in remove_crypt Oct 6 05:28:03 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.fzpk2oj_mount_test with fs xfs Oct 6 05:28:12 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem e8b12cd5-e352-4b14-a51e-08666e23c0c8 Oct 6 05:28:12 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:28:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fzpk2oj_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs ext4 in remove_crypt Oct 6 05:28:17 storageqe-109 systemd[1]: tmp-libblockdev.fzpk2oj_mount_test.mount: Deactivated successfully. Oct 6 05:28:17 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem e8b12cd5-e352-4b14-a51e-08666e23c0c8 Oct 6 05:28:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs xfs in remove_crypt Oct 6 05:28:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ifdg4b2emount_test with fs ext4 Oct 6 05:28:27 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ce0f6efc-9d10-4177-a0cf-6c0d1e313e4b r/w with ordered data mode. Quota mode: none. Oct 6 05:28:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ifdg4b2emount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs ext3 in remove_crypt Oct 6 05:28:32 storageqe-109 systemd[1]: tmp-libblockdev.ifdg4b2emount_test.mount: Deactivated successfully. Oct 6 05:28:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ce0f6efc-9d10-4177-a0cf-6c0d1e313e4b. Oct 6 05:28:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs ext4 in remove_crypt Oct 6 05:28:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7okbijl4mount_test with fs ext3 Oct 6 05:28:42 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:28:42 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 03e89a03-5c8c-4b55-976d-2a94be218245 r/w with ordered data mode. Quota mode: none. Oct 6 05:28:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7okbijl4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs ext2 in remove_crypt Oct 6 05:28:47 storageqe-109 systemd[1]: tmp-libblockdev.7okbijl4mount_test.mount: Deactivated successfully. Oct 6 05:28:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 03e89a03-5c8c-4b55-976d-2a94be218245. Oct 6 05:28:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs ext3 in remove_crypt Oct 6 05:28:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FDVJ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p15ylc1tmount_test with fs ext2 Oct 6 05:28:57 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:28:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8676b7c8-74e7-454f-94db-29c265f413d9 r/w without journal. Quota mode: none. Oct 6 05:28:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p15ylc1tmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs ext2 in remove_crypt INFO: remove crypt device FDVJ Oct 6 05:29:02 storageqe-109 systemd[1]: tmp-libblockdev.p15ylc1tmount_test.mount: Deactivated successfully. Oct 6 05:29:02 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8676b7c8-74e7-454f-94db-29c265f413d9. Oct 6 05:29:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FDVJ and fs ext2 in remove_crypt Oct 6 05:29:02 storageqe-109 INFO: remove crypt device FDVJ cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 05:29:02 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q cryptsetup erase /dev/nvme0n1p1 -q Oct 6 05:29:12 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p1 -q cryptsetup luksDump /dev/nvme0n1p1 -q Oct 6 05:29:23 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q INFO: finishe the remove crypt device FDVJ INFO: start IO testing with the luks device /dev/mapper/ITNr and fs xfs in remove_crypt Oct 6 05:29:33 storageqe-109 INFO: finishe the remove crypt device FDVJ Oct 6 05:29:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ITNr and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.cl98qacemount_test with fs xfs Oct 6 05:29:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 6ecae9fb-b47e-4b0b-a439-6294976dbe59 Oct 6 05:29:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 05:29:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cl98qacemount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ITNr and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ITNr and fs ext4 in remove_crypt Oct 6 05:29:48 storageqe-109 systemd[1]: tmp-libblockdev.cl98qacemount_test.mount: Deactivated successfully. Oct 6 05:29:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 6ecae9fb-b47e-4b0b-a439-6294976dbe59 Oct 6 05:29:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ITNr and fs xfs in remove_crypt Oct 6 05:29:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ITNr and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9vt5zwiomount_test with fs ext4 Oct 6 05:29:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ae3f4fe4-e910-4139-84b7-19c5761abe40 r/w with ordered data mode. Quota mode: none. Oct 6 05:29:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9vt5zwiomount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ITNr and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ITNr and fs ext3 in remove_crypt Oct 6 05:30:03 storageqe-109 systemd[1]: tmp-libblockdev.9vt5zwiomount_test.mount: Deactivated successfully. Oct 6 05:30:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ae3f4fe4-e910-4139-84b7-19c5761abe40. Oct 6 05:30:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ITNr and fs ext4 in remove_crypt Oct 6 05:30:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ITNr and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.co9wjmtkmount_test with fs ext3 Oct 6 05:30:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 05:30:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ae57b78b-b14e-42c7-b69a-349c4b8fce56 r/w with ordered data mode. Quota mode: none. Oct 6 05:30:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.co9wjmtkmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ITNr and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ITNr and fs ext2 in remove_crypt Oct 6 05:30:18 storageqe-109 systemd[1]: tmp-libblockdev.co9wjmtkmount_test.mount: Deactivated successfully. Oct 6 05:30:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ae57b78b-b14e-42c7-b69a-349c4b8fce56. Oct 6 05:30:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ITNr and fs ext3 in remove_crypt Oct 6 05:30:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ITNr and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._1ginddpmount_test with fs ext2 Oct 6 05:30:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 05:30:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem be5706ea-2807-47b0-9c34-341e6a1ab4d5 r/w without journal. Quota mode: none. Oct 6 05:30:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev._1ginddpmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ITNr and fs ext2 in remove_crypt INFO: remove crypt device ITNr Oct 6 05:30:33 storageqe-109 systemd[1]: tmp-libblockdev._1ginddpmount_test.mount: Deactivated successfully. Oct 6 05:30:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem be5706ea-2807-47b0-9c34-341e6a1ab4d5. Oct 6 05:30:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ITNr and fs ext2 in remove_crypt Oct 6 05:30:33 storageqe-109 INFO: remove crypt device ITNr cryptsetup luksDump /dev/nvme0n1p2 -q Oct 6 05:30:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q cryptsetup erase /dev/nvme0n1p2 -q Oct 6 05:30:44 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p2 -q cryptsetup luksDump /dev/nvme0n1p2 -q Oct 6 05:30:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q INFO: finishe the remove crypt device ITNr INFO: start IO testing with the luks device /dev/mapper/etOV and fs xfs in remove_crypt Oct 6 05:31:04 storageqe-109 INFO: finishe the remove crypt device ITNr Oct 6 05:31:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/etOV and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.as9t5wydmount_test with fs xfs Oct 6 05:31:15 storageqe-109 kernel: XFS (dm-5): Mounting V5 Filesystem 6c5e93d9-d3d9-454b-99bb-9ba5d1648cde Oct 6 05:31:15 storageqe-109 kernel: XFS (dm-5): Ending clean mount Oct 6 05:31:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.as9t5wydmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/etOV and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/etOV and fs ext4 in remove_crypt Oct 6 05:31:19 storageqe-109 systemd[1]: tmp-libblockdev.as9t5wydmount_test.mount: Deactivated successfully. Oct 6 05:31:19 storageqe-109 kernel: XFS (dm-5): Unmounting Filesystem 6c5e93d9-d3d9-454b-99bb-9ba5d1648cde Oct 6 05:31:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/etOV and fs xfs in remove_crypt Oct 6 05:31:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/etOV and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8qov1sewmount_test with fs ext4 Oct 6 05:31:29 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem b120573c-1eee-45b9-9680-2bf30b035c84 r/w with ordered data mode. Quota mode: none. Oct 6 05:31:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8qov1sewmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/etOV and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/etOV and fs ext3 in remove_crypt Oct 6 05:31:34 storageqe-109 systemd[1]: tmp-libblockdev.8qov1sewmount_test.mount: Deactivated successfully. Oct 6 05:31:34 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem b120573c-1eee-45b9-9680-2bf30b035c84. Oct 6 05:31:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/etOV and fs ext4 in remove_crypt Oct 6 05:31:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/etOV and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ioh838mvmount_test with fs ext3 Oct 6 05:31:44 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext3 file system using the ext4 subsystem Oct 6 05:31:44 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 1feabd2b-bc4d-4eaa-beb9-bfe562c75034 r/w with ordered data mode. Quota mode: none. Oct 6 05:31:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ioh838mvmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/etOV and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/etOV and fs ext2 in remove_crypt Oct 6 05:31:49 storageqe-109 systemd[1]: tmp-libblockdev.ioh838mvmount_test.mount: Deactivated successfully. Oct 6 05:31:49 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 1feabd2b-bc4d-4eaa-beb9-bfe562c75034. Oct 6 05:31:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/etOV and fs ext3 in remove_crypt Oct 6 05:31:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/etOV and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x5jr1py6mount_test with fs ext2 Oct 6 05:31:59 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext2 file system using the ext4 subsystem Oct 6 05:31:59 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem c64f1378-e7c0-474b-bd73-97b7b12bb55f r/w without journal. Quota mode: none. Oct 6 05:31:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x5jr1py6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/etOV and fs ext2 in remove_crypt INFO: remove crypt device etOV Oct 6 05:32:04 storageqe-109 systemd[1]: tmp-libblockdev.x5jr1py6mount_test.mount: Deactivated successfully. Oct 6 05:32:04 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem c64f1378-e7c0-474b-bd73-97b7b12bb55f. Oct 6 05:32:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/etOV and fs ext2 in remove_crypt Oct 6 05:32:04 storageqe-109 INFO: remove crypt device etOV cryptsetup luksDump /dev/nvme0n1p3 -q Oct 6 05:32:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q cryptsetup erase /dev/nvme0n1p3 -q Oct 6 05:32:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p3 -q cryptsetup luksDump /dev/nvme0n1p3 -q Oct 6 05:32:26 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q INFO: finishe the remove crypt device etOV INFO: start IO testing with the luks device /dev/mapper/aZxL and fs xfs in remove_crypt Oct 6 05:32:36 storageqe-109 INFO: finishe the remove crypt device etOV Oct 6 05:32:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aZxL and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.auyosceimount_test with fs xfs Oct 6 05:32:46 storageqe-109 kernel: XFS (dm-6): Mounting V5 Filesystem 86ff9b0e-2ca5-455f-930c-dc3f17df7622 Oct 6 05:32:46 storageqe-109 kernel: XFS (dm-6): Ending clean mount Oct 6 05:32:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.auyosceimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/aZxL and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/aZxL and fs ext4 in remove_crypt Oct 6 05:32:51 storageqe-109 systemd[1]: tmp-libblockdev.auyosceimount_test.mount: Deactivated successfully. Oct 6 05:32:51 storageqe-109 kernel: XFS (dm-6): Unmounting Filesystem 86ff9b0e-2ca5-455f-930c-dc3f17df7622 Oct 6 05:32:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aZxL and fs xfs in remove_crypt Oct 6 05:32:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aZxL and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.s1qifc7hmount_test with fs ext4 Oct 6 05:33:01 storageqe-109 kernel: EXT4-fs (dm-6): mounted filesystem a0471f31-b20c-43a3-8760-6d76306d4f29 r/w with ordered data mode. Quota mode: none. Oct 6 05:33:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s1qifc7hmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/aZxL and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/aZxL and fs ext3 in remove_crypt Oct 6 05:33:06 storageqe-109 systemd[1]: tmp-libblockdev.s1qifc7hmount_test.mount: Deactivated successfully. Oct 6 05:33:06 storageqe-109 kernel: EXT4-fs (dm-6): unmounting filesystem a0471f31-b20c-43a3-8760-6d76306d4f29. Oct 6 05:33:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aZxL and fs ext4 in remove_crypt Oct 6 05:33:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aZxL and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.edj0y16xmount_test with fs ext3 Oct 6 05:33:16 storageqe-109 kernel: EXT4-fs (dm-6): mounting ext3 file system using the ext4 subsystem Oct 6 05:33:16 storageqe-109 kernel: EXT4-fs (dm-6): mounted filesystem 4b551b1b-12d3-4dd7-91ed-b90f7898fc80 r/w with ordered data mode. Quota mode: none. Oct 6 05:33:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.edj0y16xmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/aZxL and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/aZxL and fs ext2 in remove_crypt Oct 6 05:33:21 storageqe-109 systemd[1]: tmp-libblockdev.edj0y16xmount_test.mount: Deactivated successfully. Oct 6 05:33:21 storageqe-109 kernel: EXT4-fs (dm-6): unmounting filesystem 4b551b1b-12d3-4dd7-91ed-b90f7898fc80. Oct 6 05:33:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aZxL and fs ext3 in remove_crypt Oct 6 05:33:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aZxL and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._y4hqr8omount_test with fs ext2 Oct 6 05:33:31 storageqe-109 kernel: EXT4-fs (dm-6): mounting ext2 file system using the ext4 subsystem Oct 6 05:33:31 storageqe-109 kernel: EXT4-fs (dm-6): mounted filesystem 40cab2d7-1e23-46e1-a975-ae2d5774486c r/w without journal. Quota mode: none. Oct 6 05:33:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev._y4hqr8omount_test with fs ext2 Oct 6 05:33:35 storageqe-109 systemd[1]: tmp-libblockdev._y4hqr8omount_test.mount: Deactivated successfully. Oct 6 05:33:35 storageqe-109 kernel: EXT4-fs (dm-6): unmounting filesystem 40cab2d7-1e23-46e1-a975-ae2d5774486c. INFO: End IO testing with the luks device /dev/mapper/aZxL and fs ext2 in remove_crypt INFO: remove crypt device aZxL Oct 6 05:33:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aZxL and fs ext2 in remove_crypt Oct 6 05:33:36 storageqe-109 INFO: remove crypt device aZxL cryptsetup luksDump /dev/nvme0n1p4 -q Oct 6 05:33:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q cryptsetup erase /dev/nvme0n1p4 -q Oct 6 05:33:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p4 -q cryptsetup luksDump /dev/nvme0n1p4 -q Oct 6 05:33:57 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q INFO: finishe the remove crypt device aZxL INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs xfs in remove_crypt Oct 6 05:34:07 storageqe-109 INFO: finishe the remove crypt device aZxL Oct 6 05:34:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._va03uiamount_test with fs xfs Oct 6 05:34:17 storageqe-109 kernel: XFS (dm-7): Mounting V5 Filesystem 278a39c7-ab78-4a90-902d-aeb1cb173c8e Oct 6 05:34:17 storageqe-109 kernel: XFS (dm-7): Ending clean mount Oct 6 05:34:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev._va03uiamount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs ext4 in remove_crypt Oct 6 05:34:22 storageqe-109 systemd[1]: tmp-libblockdev._va03uiamount_test.mount: Deactivated successfully. Oct 6 05:34:22 storageqe-109 kernel: XFS (dm-7): Unmounting Filesystem 278a39c7-ab78-4a90-902d-aeb1cb173c8e Oct 6 05:34:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs xfs in remove_crypt Oct 6 05:34:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8hrzyc_5mount_test with fs ext4 Oct 6 05:34:32 storageqe-109 kernel: EXT4-fs (dm-7): mounted filesystem bb95ff48-3125-4ed0-9eeb-707c395d0ce0 r/w with ordered data mode. Quota mode: none. Oct 6 05:34:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8hrzyc_5mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs ext3 in remove_crypt Oct 6 05:34:37 storageqe-109 systemd[1]: tmp-libblockdev.8hrzyc_5mount_test.mount: Deactivated successfully. Oct 6 05:34:37 storageqe-109 kernel: EXT4-fs (dm-7): unmounting filesystem bb95ff48-3125-4ed0-9eeb-707c395d0ce0. Oct 6 05:34:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs ext4 in remove_crypt Oct 6 05:34:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rl2sebpbmount_test with fs ext3 Oct 6 05:34:47 storageqe-109 kernel: EXT4-fs (dm-7): mounting ext3 file system using the ext4 subsystem Oct 6 05:34:47 storageqe-109 kernel: EXT4-fs (dm-7): mounted filesystem c53f1072-5b5c-49b0-8d35-88e90aa8e027 r/w with ordered data mode. Quota mode: none. Oct 6 05:34:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rl2sebpbmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs ext2 in remove_crypt Oct 6 05:34:52 storageqe-109 systemd[1]: tmp-libblockdev.rl2sebpbmount_test.mount: Deactivated successfully. Oct 6 05:34:52 storageqe-109 kernel: EXT4-fs (dm-7): unmounting filesystem c53f1072-5b5c-49b0-8d35-88e90aa8e027. Oct 6 05:34:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs ext3 in remove_crypt Oct 6 05:34:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xLGQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z_ckhs87mount_test with fs ext2 Oct 6 05:35:02 storageqe-109 kernel: EXT4-fs (dm-7): mounting ext2 file system using the ext4 subsystem Oct 6 05:35:02 storageqe-109 kernel: EXT4-fs (dm-7): mounted filesystem 21ab708a-b4e6-4f78-9e4f-24eeb7817fcc r/w without journal. Quota mode: none. Oct 6 05:35:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z_ckhs87mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs ext2 in remove_crypt INFO: remove crypt device xLGQ Oct 6 05:35:07 storageqe-109 systemd[1]: tmp-libblockdev.z_ckhs87mount_test.mount: Deactivated successfully. Oct 6 05:35:07 storageqe-109 kernel: EXT4-fs (dm-7): unmounting filesystem 21ab708a-b4e6-4f78-9e4f-24eeb7817fcc. Oct 6 05:35:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xLGQ and fs ext2 in remove_crypt Oct 6 05:35:07 storageqe-109 INFO: remove crypt device xLGQ cryptsetup luksDump /dev/nvme0n1p5 -q Oct 6 05:35:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q cryptsetup erase /dev/nvme0n1p5 -q Oct 6 05:35:17 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p5 -q cryptsetup luksDump /dev/nvme0n1p5 -q Oct 6 05:35:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q INFO: finishe the remove crypt device xLGQ INFO: start IO testing with the luks device /dev/mapper/psMK and fs xfs in remove_crypt Oct 6 05:35:38 storageqe-109 INFO: finishe the remove crypt device xLGQ Oct 6 05:35:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/psMK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.vunqzsw8mount_test with fs xfs Oct 6 05:35:48 storageqe-109 kernel: XFS (dm-8): Mounting V5 Filesystem b49c8a40-9401-47d8-8407-c84af6286ab7 Oct 6 05:35:48 storageqe-109 kernel: XFS (dm-8): Ending clean mount Oct 6 05:35:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vunqzsw8mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/psMK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/psMK and fs ext4 in remove_crypt Oct 6 05:35:53 storageqe-109 systemd[1]: tmp-libblockdev.vunqzsw8mount_test.mount: Deactivated successfully. Oct 6 05:35:53 storageqe-109 kernel: XFS (dm-8): Unmounting Filesystem b49c8a40-9401-47d8-8407-c84af6286ab7 Oct 6 05:35:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/psMK and fs xfs in remove_crypt Oct 6 05:35:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/psMK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1iv5xqvnmount_test with fs ext4 Oct 6 05:36:03 storageqe-109 kernel: EXT4-fs (dm-8): mounted filesystem c3055e1e-3162-4bd3-927a-8f9eccfeb696 r/w with ordered data mode. Quota mode: none. Oct 6 05:36:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1iv5xqvnmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/psMK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/psMK and fs ext3 in remove_crypt Oct 6 05:36:08 storageqe-109 systemd[1]: tmp-libblockdev.1iv5xqvnmount_test.mount: Deactivated successfully. Oct 6 05:36:08 storageqe-109 kernel: EXT4-fs (dm-8): unmounting filesystem c3055e1e-3162-4bd3-927a-8f9eccfeb696. Oct 6 05:36:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/psMK and fs ext4 in remove_crypt Oct 6 05:36:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/psMK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._tvrrczbmount_test with fs ext3 Oct 6 05:36:18 storageqe-109 kernel: EXT4-fs (dm-8): mounting ext3 file system using the ext4 subsystem Oct 6 05:36:18 storageqe-109 kernel: EXT4-fs (dm-8): mounted filesystem 5c5f9fd9-4c26-43e5-a8e2-49928cb8ee95 r/w with ordered data mode. Quota mode: none. Oct 6 05:36:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev._tvrrczbmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/psMK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/psMK and fs ext2 in remove_crypt Oct 6 05:36:23 storageqe-109 systemd[1]: tmp-libblockdev._tvrrczbmount_test.mount: Deactivated successfully. Oct 6 05:36:23 storageqe-109 kernel: EXT4-fs (dm-8): unmounting filesystem 5c5f9fd9-4c26-43e5-a8e2-49928cb8ee95. Oct 6 05:36:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/psMK and fs ext3 in remove_crypt Oct 6 05:36:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/psMK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.a3_b0eqpmount_test with fs ext2 Oct 6 05:36:33 storageqe-109 kernel: EXT4-fs (dm-8): mounting ext2 file system using the ext4 subsystem Oct 6 05:36:33 storageqe-109 kernel: EXT4-fs (dm-8): mounted filesystem 34e1f980-e226-496b-8f74-d40bc049bb27 r/w without journal. Quota mode: none. Oct 6 05:36:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a3_b0eqpmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/psMK and fs ext2 in remove_crypt Oct 6 05:36:38 storageqe-109 systemd[1]: tmp-libblockdev.a3_b0eqpmount_test.mount: Deactivated successfully. Oct 6 05:36:38 storageqe-109 kernel: EXT4-fs (dm-8): unmounting filesystem 34e1f980-e226-496b-8f74-d40bc049bb27. Oct 6 05:36:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/psMK and fs ext2 in remove_crypt INFO: remove crypt device psMK Oct 6 05:36:38 storageqe-109 INFO: remove crypt device psMK cryptsetup luksDump /dev/nvme0n1p6 -q Oct 6 05:36:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q cryptsetup erase /dev/nvme0n1p6 -q Oct 6 05:36:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p6 -q cryptsetup luksDump /dev/nvme0n1p6 -q Oct 6 05:36:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q INFO: finishe the remove crypt device psMK INFO: start IO testing with the luks device /dev/mapper/yFOM and fs xfs in remove_crypt Oct 6 05:37:09 storageqe-109 INFO: finishe the remove crypt device psMK Oct 6 05:37:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yFOM and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.6iyqms82mount_test with fs xfs Oct 6 05:37:19 storageqe-109 kernel: XFS (dm-9): Mounting V5 Filesystem ecad5468-5879-4453-819c-f253adbbb618 Oct 6 05:37:19 storageqe-109 kernel: XFS (dm-9): Ending clean mount Oct 6 05:37:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6iyqms82mount_test with fs xfs Oct 6 05:37:24 storageqe-109 systemd[1]: tmp-libblockdev.6iyqms82mount_test.mount: Deactivated successfully. Oct 6 05:37:24 storageqe-109 kernel: XFS (dm-9): Unmounting Filesystem ecad5468-5879-4453-819c-f253adbbb618 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yFOM and fs ext4 in remove_crypt Oct 6 05:37:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs xfs in remove_crypt Oct 6 05:37:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yFOM and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2y9bqjcwmount_test with fs ext4 Oct 6 05:37:34 storageqe-109 kernel: EXT4-fs (dm-9): mounted filesystem e51076a3-4565-40a5-96d5-dcf5e025995b r/w with ordered data mode. Quota mode: none. Oct 6 05:37:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2y9bqjcwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yFOM and fs ext3 in remove_crypt Oct 6 05:37:39 storageqe-109 systemd[1]: tmp-libblockdev.2y9bqjcwmount_test.mount: Deactivated successfully. Oct 6 05:37:39 storageqe-109 kernel: EXT4-fs (dm-9): unmounting filesystem e51076a3-4565-40a5-96d5-dcf5e025995b. Oct 6 05:37:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs ext4 in remove_crypt Oct 6 05:37:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yFOM and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gbo7la7bmount_test with fs ext3 Oct 6 05:37:49 storageqe-109 kernel: EXT4-fs (dm-9): mounting ext3 file system using the ext4 subsystem Oct 6 05:37:49 storageqe-109 kernel: EXT4-fs (dm-9): mounted filesystem a2af817a-008f-4c22-820e-bba4b40cafb5 r/w with ordered data mode. Quota mode: none. Oct 6 05:37:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gbo7la7bmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yFOM and fs ext2 in remove_crypt Oct 6 05:37:54 storageqe-109 systemd[1]: tmp-libblockdev.gbo7la7bmount_test.mount: Deactivated successfully. Oct 6 05:37:54 storageqe-109 kernel: EXT4-fs (dm-9): unmounting filesystem a2af817a-008f-4c22-820e-bba4b40cafb5. Oct 6 05:37:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs ext3 in remove_crypt Oct 6 05:37:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yFOM and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3f0eib4pmount_test with fs ext2 Oct 6 05:38:04 storageqe-109 kernel: EXT4-fs (dm-9): mounting ext2 file system using the ext4 subsystem Oct 6 05:38:04 storageqe-109 kernel: EXT4-fs (dm-9): mounted filesystem ce84a534-0300-4b3a-91cc-7c4d65f13a15 r/w without journal. Quota mode: none. Oct 6 05:38:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3f0eib4pmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs ext2 in remove_crypt INFO: remove crypt device yFOM Oct 6 05:38:09 storageqe-109 systemd[1]: tmp-libblockdev.3f0eib4pmount_test.mount: Deactivated successfully. Oct 6 05:38:09 storageqe-109 kernel: EXT4-fs (dm-9): unmounting filesystem ce84a534-0300-4b3a-91cc-7c4d65f13a15. Oct 6 05:38:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yFOM and fs ext2 in remove_crypt Oct 6 05:38:09 storageqe-109 INFO: remove crypt device yFOM cryptsetup luksDump /dev/nvme0n1p7 -q Oct 6 05:38:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q cryptsetup erase /dev/nvme0n1p7 -q Oct 6 05:38:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p7 -q cryptsetup luksDump /dev/nvme0n1p7 -q Oct 6 05:38:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q INFO: finishe the remove crypt device yFOM INFO: start IO testing with the luks device /dev/mapper/ARkK and fs xfs in remove_crypt Oct 6 05:38:40 storageqe-109 INFO: finishe the remove crypt device yFOM Oct 6 05:38:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ARkK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.83je3nozmount_test with fs xfs Oct 6 05:38:50 storageqe-109 kernel: XFS (dm-10): Mounting V5 Filesystem 036c14cc-58a0-4227-9d18-30370baa93f5 Oct 6 05:38:50 storageqe-109 kernel: XFS (dm-10): Ending clean mount Oct 6 05:38:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.83je3nozmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ARkK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ARkK and fs ext4 in remove_crypt Oct 6 05:38:55 storageqe-109 systemd[1]: tmp-libblockdev.83je3nozmount_test.mount: Deactivated successfully. Oct 6 05:38:55 storageqe-109 kernel: XFS (dm-10): Unmounting Filesystem 036c14cc-58a0-4227-9d18-30370baa93f5 Oct 6 05:38:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ARkK and fs xfs in remove_crypt Oct 6 05:38:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ARkK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j01xakmwmount_test with fs ext4 Oct 6 05:39:05 storageqe-109 kernel: EXT4-fs (dm-10): mounted filesystem 541941dc-eee2-4a8d-a891-5a6f381244f2 r/w with ordered data mode. Quota mode: none. Oct 6 05:39:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j01xakmwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ARkK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ARkK and fs ext3 in remove_crypt Oct 6 05:39:10 storageqe-109 systemd[1]: tmp-libblockdev.j01xakmwmount_test.mount: Deactivated successfully. Oct 6 05:39:10 storageqe-109 kernel: EXT4-fs (dm-10): unmounting filesystem 541941dc-eee2-4a8d-a891-5a6f381244f2. Oct 6 05:39:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ARkK and fs ext4 in remove_crypt Oct 6 05:39:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ARkK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j4m2cyjbmount_test with fs ext3 Oct 6 05:39:20 storageqe-109 kernel: EXT4-fs (dm-10): mounting ext3 file system using the ext4 subsystem Oct 6 05:39:20 storageqe-109 kernel: EXT4-fs (dm-10): mounted filesystem 667529f5-e97e-474d-8b17-13c6200cf634 r/w with ordered data mode. Quota mode: none. Oct 6 05:39:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j4m2cyjbmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ARkK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ARkK and fs ext2 in remove_crypt Oct 6 05:39:25 storageqe-109 systemd[1]: tmp-libblockdev.j4m2cyjbmount_test.mount: Deactivated successfully. Oct 6 05:39:25 storageqe-109 kernel: EXT4-fs (dm-10): unmounting filesystem 667529f5-e97e-474d-8b17-13c6200cf634. Oct 6 05:39:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ARkK and fs ext3 in remove_crypt Oct 6 05:39:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ARkK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3oyl96komount_test with fs ext2 Oct 6 05:39:35 storageqe-109 kernel: EXT4-fs (dm-10): mounting ext2 file system using the ext4 subsystem Oct 6 05:39:35 storageqe-109 kernel: EXT4-fs (dm-10): mounted filesystem 1da804c1-c5fd-4f2d-9e0d-a99d9e7d32f0 r/w without journal. Quota mode: none. Oct 6 05:39:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3oyl96komount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ARkK and fs ext2 in remove_crypt Oct 6 05:39:40 storageqe-109 systemd[1]: tmp-libblockdev.3oyl96komount_test.mount: Deactivated successfully. Oct 6 05:39:40 storageqe-109 kernel: EXT4-fs (dm-10): unmounting filesystem 1da804c1-c5fd-4f2d-9e0d-a99d9e7d32f0. Oct 6 05:39:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ARkK and fs ext2 in remove_crypt INFO: remove crypt device ARkK Oct 6 05:39:40 storageqe-109 INFO: remove crypt device ARkK cryptsetup luksDump /dev/nvme0n1p8 -q Oct 6 05:39:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q cryptsetup erase /dev/nvme0n1p8 -q Oct 6 05:39:51 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p8 -q cryptsetup luksDump /dev/nvme0n1p8 -q Oct 6 05:40:01 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q INFO: finishe the remove crypt device ARkK Oct 6 05:40:11 storageqe-109 INFO: finishe the remove crypt device ARkK Oct 6 05:40:13 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 6 05:40:14 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 6 05:40:14 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 6 05:40:15 storageqe-109 kernel: nvme0n1: p2 p4 p5 p6 p7 p8 Oct 6 05:40:16 storageqe-109 kernel: nvme0n1: p2 p5 p6 p7 p8 Oct 6 05:40:17 storageqe-109 kernel: nvme0n1: p2 p6 p7 p8 Oct 6 05:40:18 storageqe-109 kernel: nvme0n1: p2 p7 p8 Oct 6 05:40:19 storageqe-109 kernel: nvme0n1: p2 p8 Oct 6 05:40:20 storageqe-109 kernel: nvme0n1: p2 cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:40:22 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:40:22 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:40:22 storageqe-109 kernel: nvme0n1: p2 Oct 6 05:40:22 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hw_opal_tang #### INFO: #### will start test_hw_luks_paramter ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:40:39 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 05:40:39 storageqe-109 INFO: #### END test_hw_opal_tang #### Oct 6 05:40:39 storageqe-109 INFO: #### will start test_hw_luks_paramter ##### Oct 6 05:40:39 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:40:45 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:40:55 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:40:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:41:06 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:41:11 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 6 05:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:11 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 6 05:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:41:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:41:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:41:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:41:12 storageqe-109 stratisd[4947]: [2025-10-06T09:41:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:41:12 storageqe-109 stratisd[4947]: [2025-10-06T09:41:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:41:22 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:41:22 storageqe-109 stratisd[4947]: [2025-10-06T09:41:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:41:22 storageqe-109 stratisd[4947]: [2025-10-06T09:41:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:41:28 storageqe-109 chronyd[999]: Selected source 10.2.32.38 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:41:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:41:36 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.0kms_dpwmount_test with fs xfs Oct 6 05:41:44 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 55b9e0b1-d937-4e38-82af-118c6fcebcb0 Oct 6 05:41:44 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:41:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0kms_dpwmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:41:49 storageqe-109 systemd[1]: tmp-libblockdev.0kms_dpwmount_test.mount: Deactivated successfully. Oct 6 05:41:49 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 55b9e0b1-d937-4e38-82af-118c6fcebcb0 Oct 6 05:41:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:41:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mgy9_9rkmount_test with fs ext4 Oct 6 05:42:00 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem add5dcd2-2bf9-42af-837e-c7a6a95c21eb r/w with ordered data mode. Quota mode: none. Oct 6 05:42:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mgy9_9rkmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:42:06 storageqe-109 systemd[1]: tmp-libblockdev.mgy9_9rkmount_test.mount: Deactivated successfully. Oct 6 05:42:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem add5dcd2-2bf9-42af-837e-c7a6a95c21eb. Oct 6 05:42:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:42:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.t4uudljdmount_test with fs ext3 Oct 6 05:42:28 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:42:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem af1e3c23-9234-40ba-83f5-0ee5d2f54193 r/w with ordered data mode. Quota mode: none. Oct 6 05:42:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t4uudljdmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:42:34 storageqe-109 systemd[1]: tmp-libblockdev.t4uudljdmount_test.mount: Deactivated successfully. Oct 6 05:42:34 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem af1e3c23-9234-40ba-83f5-0ee5d2f54193. Oct 6 05:42:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:42:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4pq25st8mount_test with fs ext2 Oct 6 05:42:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:42:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c976d9c6-092f-436f-9627-8878474e890d r/w without journal. Quota mode: none. Oct 6 05:42:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4pq25st8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 05:43:01 storageqe-109 systemd[1]: tmp-libblockdev.4pq25st8mount_test.mount: Deactivated successfully. Oct 6 05:43:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c976d9c6-092f-436f-9627-8878474e890d. Oct 6 05:43:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:43:01 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:43:01 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 05:43:11 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:43:23 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:43:33 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:43:33 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:43:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:43:45 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:43:55 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 05:43:55 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:44:00 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:44:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:00 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:44:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:44:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:44:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:44:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:44:01 storageqe-109 stratisd[4947]: [2025-10-06T09:44:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:44:01 storageqe-109 stratisd[4947]: [2025-10-06T09:44:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:44:10 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:44:11 storageqe-109 stratisd[4947]: [2025-10-06T09:44:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:44:11 storageqe-109 stratisd[4947]: [2025-10-06T09:44:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:44:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:44:25 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.ij40a5r6mount_test with fs xfs Oct 6 05:44:33 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 2b68be2c-4db3-477b-8c7f-2aee196166dd Oct 6 05:44:33 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:44:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ij40a5r6mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:44:37 storageqe-109 systemd[1]: tmp-libblockdev.ij40a5r6mount_test.mount: Deactivated successfully. Oct 6 05:44:37 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 2b68be2c-4db3-477b-8c7f-2aee196166dd Oct 6 05:44:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:44:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m38o2fdfmount_test with fs ext4 Oct 6 05:44:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 739d84d5-7102-4f43-af2b-39b70be586a8 r/w with ordered data mode. Quota mode: none. Oct 6 05:44:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m38o2fdfmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:44:54 storageqe-109 systemd[1]: tmp-libblockdev.m38o2fdfmount_test.mount: Deactivated successfully. Oct 6 05:44:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 739d84d5-7102-4f43-af2b-39b70be586a8. Oct 6 05:44:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:44:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r0n6bb0kmount_test with fs ext3 Oct 6 05:45:16 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:45:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 661bc12a-d7e8-43cb-b230-41cb597c994b r/w with ordered data mode. Quota mode: none. Oct 6 05:45:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r0n6bb0kmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:45:21 storageqe-109 systemd[1]: tmp-libblockdev.r0n6bb0kmount_test.mount: Deactivated successfully. Oct 6 05:45:21 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 661bc12a-d7e8-43cb-b230-41cb597c994b. Oct 6 05:45:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:45:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q1g3k713mount_test with fs ext2 Oct 6 05:45:42 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:45:42 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem df98f7e4-71bd-40a1-b6a5-538f64720ac1 r/w without journal. Quota mode: none. Oct 6 05:45:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q1g3k713mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 05:45:47 storageqe-109 systemd[1]: tmp-libblockdev.q1g3k713mount_test.mount: Deactivated successfully. Oct 6 05:45:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem df98f7e4-71bd-40a1-b6a5-538f64720ac1. Oct 6 05:45:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:45:47 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:45:48 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 05:45:58 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:46:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:46:19 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:46:19 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:46:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:46:31 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:46:41 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 05:46:41 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:46:47 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:46:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:46:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:46:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:46:47 storageqe-109 stratisd[4947]: [2025-10-06T09:46:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:46:47 storageqe-109 stratisd[4947]: [2025-10-06T09:46:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:46:57 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:46:58 storageqe-109 stratisd[4947]: [2025-10-06T09:46:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:46:58 storageqe-109 stratisd[4947]: [2025-10-06T09:46:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:47:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:47:11 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.1o6m3wgdmount_test with fs xfs Oct 6 05:47:19 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 564d882d-4b20-4054-beec-3c4520923834 Oct 6 05:47:19 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:47:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1o6m3wgdmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:47:24 storageqe-109 systemd[1]: tmp-libblockdev.1o6m3wgdmount_test.mount: Deactivated successfully. Oct 6 05:47:24 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 564d882d-4b20-4054-beec-3c4520923834 Oct 6 05:47:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:47:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vh4mhai3mount_test with fs ext4 Oct 6 05:47:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7ec6cdd3-1b0e-4384-b663-9b6805271bab r/w with ordered data mode. Quota mode: none. Oct 6 05:47:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vh4mhai3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:47:41 storageqe-109 systemd[1]: tmp-libblockdev.vh4mhai3mount_test.mount: Deactivated successfully. Oct 6 05:47:41 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7ec6cdd3-1b0e-4384-b663-9b6805271bab. Oct 6 05:47:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:47:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.t9598k7wmount_test with fs ext3 Oct 6 05:48:04 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 05:48:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1a16b31b-c9da-4295-98a6-5c63a9f1d7b8 r/w with ordered data mode. Quota mode: none. Oct 6 05:48:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t9598k7wmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:48:09 storageqe-109 systemd[1]: tmp-libblockdev.t9598k7wmount_test.mount: Deactivated successfully. Oct 6 05:48:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1a16b31b-c9da-4295-98a6-5c63a9f1d7b8. Oct 6 05:48:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:48:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nrmdiig8mount_test with fs ext2 Oct 6 05:48:30 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:48:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9d3a6cdb-90fe-4e5b-bb63-ae5d75831ff3 r/w without journal. Quota mode: none. Oct 6 05:48:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nrmdiig8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 05:48:36 storageqe-109 systemd[1]: tmp-libblockdev.nrmdiig8mount_test.mount: Deactivated successfully. Oct 6 05:48:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9d3a6cdb-90fe-4e5b-bb63-ae5d75831ff3. Oct 6 05:48:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:48:36 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:48:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 05:48:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:48:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:49:08 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:49:08 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:49:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:49:20 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:49:30 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 05:49:30 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:49:35 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:49:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:35 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:49:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:49:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:49:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:49:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:49:36 storageqe-109 stratisd[4947]: [2025-10-06T09:49:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:49:36 storageqe-109 stratisd[4947]: [2025-10-06T09:49:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:49:46 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:49:47 storageqe-109 stratisd[4947]: [2025-10-06T09:49:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:49:47 storageqe-109 stratisd[4947]: [2025-10-06T09:49:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:49:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:50:00 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.us6epd4nmount_test with fs xfs Oct 6 05:50:08 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 06dd5c27-8140-4c21-867f-353c8a1a63c8 Oct 6 05:50:08 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:50:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.us6epd4nmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:50:13 storageqe-109 systemd[1]: tmp-libblockdev.us6epd4nmount_test.mount: Deactivated successfully. Oct 6 05:50:13 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 06dd5c27-8140-4c21-867f-353c8a1a63c8 Oct 6 05:50:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:50:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.43q_z8brmount_test with fs ext4 Oct 6 05:50:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2b6a2bb3-0764-4c32-8fdd-50b3af831add r/w with ordered data mode. Quota mode: none. Oct 6 05:50:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.43q_z8brmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:50:29 storageqe-109 systemd[1]: tmp-libblockdev.43q_z8brmount_test.mount: Deactivated successfully. Oct 6 05:50:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2b6a2bb3-0764-4c32-8fdd-50b3af831add. Oct 6 05:50:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:50:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:50:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.p811jhvbmount_test with fs ext3 Oct 6 05:50:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c6051186-6cc2-46ed-b279-95a46d539a4c r/w with ordered data mode. Quota mode: none. Oct 6 05:50:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p811jhvbmount_test with fs ext3 Oct 6 05:50:56 storageqe-109 systemd[1]: tmp-libblockdev.p811jhvbmount_test.mount: Deactivated successfully. Oct 6 05:50:56 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c6051186-6cc2-46ed-b279-95a46d539a4c. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:50:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:50:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j2r20kkkmount_test with fs ext2 Oct 6 05:51:18 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:51:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 376c27c0-6617-46e4-b6b5-6ab71df99092 r/w without journal. Quota mode: none. Oct 6 05:51:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j2r20kkkmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 05:51:23 storageqe-109 systemd[1]: tmp-libblockdev.j2r20kkkmount_test.mount: Deactivated successfully. Oct 6 05:51:23 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 376c27c0-6617-46e4-b6b5-6ab71df99092. Oct 6 05:51:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:51:23 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:51:23 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 05:51:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:51:45 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:51:55 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:51:55 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:51:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:52:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:52:17 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 05:52:17 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 05:52:47 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 05:53:45 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:53:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:53:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:53:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:53:45 storageqe-109 stratisd[4947]: [2025-10-06T09:53:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:53:45 storageqe-109 stratisd[4947]: [2025-10-06T09:53:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:53:55 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:54:25 storageqe-109 stratisd[4947]: [2025-10-06T09:54:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:54:25 storageqe-109 stratisd[4947]: [2025-10-06T09:54:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:54:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.e5uq2n88mount_test with fs xfs Oct 6 05:54:46 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem b626a0de-2a44-4fb2-a5d8-9bd6007dfeca Oct 6 05:54:46 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:54:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e5uq2n88mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:54:52 storageqe-109 systemd[1]: tmp-libblockdev.e5uq2n88mount_test.mount: Deactivated successfully. Oct 6 05:54:52 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem b626a0de-2a44-4fb2-a5d8-9bd6007dfeca Oct 6 05:54:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:54:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cujkb48fmount_test with fs ext4 Oct 6 05:55:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem efd47dba-7ded-4050-a96a-b4acc9c6766d r/w with ordered data mode. Quota mode: none. Oct 6 05:55:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cujkb48fmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:55:09 storageqe-109 systemd[1]: tmp-libblockdev.cujkb48fmount_test.mount: Deactivated successfully. Oct 6 05:55:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem efd47dba-7ded-4050-a96a-b4acc9c6766d. Oct 6 05:55:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:55:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:55:31 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.hb3cswasmount_test with fs ext3 Oct 6 05:55:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem dffe27d4-fe17-47c8-a523-54775f3de71e r/w with ordered data mode. Quota mode: none. Oct 6 05:55:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hb3cswasmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:55:36 storageqe-109 systemd[1]: tmp-libblockdev.hb3cswasmount_test.mount: Deactivated successfully. Oct 6 05:55:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem dffe27d4-fe17-47c8-a523-54775f3de71e. Oct 6 05:55:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:55:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2cmjsaf8mount_test with fs ext2 Oct 6 05:55:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 05:55:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6d2a746d-0ee3-4836-a053-9884034a45d1 r/w without journal. Quota mode: none. Oct 6 05:55:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2cmjsaf8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 05:56:03 storageqe-109 systemd[1]: tmp-libblockdev.2cmjsaf8mount_test.mount: Deactivated successfully. Oct 6 05:56:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6d2a746d-0ee3-4836-a053-9884034a45d1. Oct 6 05:56:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 05:56:03 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:56:04 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 05:56:14 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:56:26 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 05:56:36 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 05:56:36 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 05:56:36 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 05:56:47 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:56:57 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 05:56:57 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 05:57:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 05:58:25 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 05:58:26 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 dnf[592012]: Updating Subscription Management repositories. Oct 6 05:58:26 storageqe-109 dnf[592012]: Unable to read consumer identity Oct 6 05:58:26 storageqe-109 dnf[592012]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-AppStream 279 kB/s | 2.8 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-AppStream-debuginfo 238 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-BaseOS 334 kB/s | 2.7 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-BaseOS-debuginfo 169 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-CRB 274 kB/s | 2.7 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-CRB-debuginfo 194 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-HighAvailability 457 kB/s | 2.8 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-HighAvailability-debuginfo 503 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-NFV 181 kB/s | 2.7 kB 00:00 Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 05:58:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 05:58:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-NFV-debuginfo 67 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-RT 659 kB/s | 2.7 kB 00:00 Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 05:58:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-RT-debuginfo 109 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-SAP 412 kB/s | 2.7 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-SAP-debuginfo 414 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-SAPHANA 334 kB/s | 2.7 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-SAPHANA-debuginfo 260 kB/s | 1.5 kB 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 6 05:58:26 storageqe-109 dnf[592012]: Errors during downloading metadata for repository 'beaker-client': Oct 6 05:58:26 storageqe-109 dnf[592012]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 6 05:58:26 storageqe-109 dnf[592012]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 6 05:58:26 storageqe-109 stratisd[4947]: [2025-10-06T09:58:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:58:26 storageqe-109 stratisd[4947]: [2025-10-06T09:58:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:58:26 storageqe-109 dnf[592012]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 6 05:58:27 storageqe-109 dnf[592012]: Google Cloud CLI 4.1 kB/s | 1.4 kB 00:00 Oct 6 05:58:28 storageqe-109 dnf[592012]: Copr repo for python-ssh2-python312 owned by mh 2.0 kB/s | 1.5 kB 00:00 Oct 6 05:58:28 storageqe-109 dnf[592012]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 6 05:58:29 storageqe-109 dnf[592012]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 6 05:58:29 storageqe-109 dnf[592012]: Ignoring repositories: beaker-client Oct 6 05:58:29 storageqe-109 dnf[592012]: Metadata cache created. Oct 6 05:58:29 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 05:58:29 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:58:36 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 05:59:06 storageqe-109 stratisd[4947]: [2025-10-06T09:59:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 05:59:06 storageqe-109 stratisd[4947]: [2025-10-06T09:59:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:59:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.bm6pwlr3mount_test with fs xfs Oct 6 05:59:27 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 1a0bd09a-8939-4109-89e6-3dd9410e2f75 Oct 6 05:59:27 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 05:59:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bm6pwlr3mount_test with fs xfs Oct 6 05:59:32 storageqe-109 systemd[1]: tmp-libblockdev.bm6pwlr3mount_test.mount: Deactivated successfully. Oct 6 05:59:32 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 1a0bd09a-8939-4109-89e6-3dd9410e2f75 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:59:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 05:59:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.by832u08mount_test with fs ext4 Oct 6 05:59:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a9aa5d34-bce1-4ce9-a8e1-fbb7e0c5c5fb r/w with ordered data mode. Quota mode: none. Oct 6 05:59:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.by832u08mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 05:59:49 storageqe-109 systemd[1]: tmp-libblockdev.by832u08mount_test.mount: Deactivated successfully. Oct 6 05:59:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a9aa5d34-bce1-4ce9-a8e1-fbb7e0c5c5fb. Oct 6 05:59:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 05:59:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.t8qzjjermount_test with fs ext3 Oct 6 06:00:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:00:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5e72b37c-9c1d-45f3-97df-8c325a704ce1 r/w with ordered data mode. Quota mode: none. Oct 6 06:00:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t8qzjjermount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:00:16 storageqe-109 systemd[1]: tmp-libblockdev.t8qzjjermount_test.mount: Deactivated successfully. Oct 6 06:00:16 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5e72b37c-9c1d-45f3-97df-8c325a704ce1. Oct 6 06:00:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:00:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.aasdpjtfmount_test with fs ext2 Oct 6 06:00:37 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:00:37 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 10c16517-e132-45bc-ae2d-efb624a9f8f1 r/w without journal. Quota mode: none. Oct 6 06:00:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.aasdpjtfmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:00:42 storageqe-109 systemd[1]: tmp-libblockdev.aasdpjtfmount_test.mount: Deactivated successfully. Oct 6 06:00:42 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 10c16517-e132-45bc-ae2d-efb624a9f8f1. Oct 6 06:00:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:00:42 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:00:42 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:00:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:01:04 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:01:14 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:01:14 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:01:14 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:01:26 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:01:36 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:01:36 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:02:06 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:03:04 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:03:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:04 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:03:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:03:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:03:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:03:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:03:05 storageqe-109 stratisd[4947]: [2025-10-06T10:03:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:03:05 storageqe-109 stratisd[4947]: [2025-10-06T10:03:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:03:15 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:03:45 storageqe-109 stratisd[4947]: [2025-10-06T10:03:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:03:45 storageqe-109 stratisd[4947]: [2025-10-06T10:03:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:03:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.p6pz74pumount_test with fs xfs Oct 6 06:04:07 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 6ba90953-ee86-420e-a33f-06ff96b26075 Oct 6 06:04:07 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:04:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p6pz74pumount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:04:12 storageqe-109 systemd[1]: tmp-libblockdev.p6pz74pumount_test.mount: Deactivated successfully. Oct 6 06:04:12 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 6ba90953-ee86-420e-a33f-06ff96b26075 Oct 6 06:04:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:04:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lljajatdmount_test with fs ext4 Oct 6 06:04:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c006a543-d0e8-4761-bb7e-ae1e5ef8d114 r/w with ordered data mode. Quota mode: none. Oct 6 06:04:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lljajatdmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:04:29 storageqe-109 systemd[1]: tmp-libblockdev.lljajatdmount_test.mount: Deactivated successfully. Oct 6 06:04:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c006a543-d0e8-4761-bb7e-ae1e5ef8d114. Oct 6 06:04:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:04:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2h55qtfymount_test with fs ext3 Oct 6 06:04:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:04:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4a44bf10-d31a-4873-93a5-7e485f33d3d6 r/w with ordered data mode. Quota mode: none. Oct 6 06:04:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2h55qtfymount_test with fs ext3 Oct 6 06:04:56 storageqe-109 systemd[1]: tmp-libblockdev.2h55qtfymount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:04:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4a44bf10-d31a-4873-93a5-7e485f33d3d6. Oct 6 06:04:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:04:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.iau157b3mount_test with fs ext2 Oct 6 06:05:18 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:05:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 966d2907-1905-4150-8d2f-b8d99771b397 r/w without journal. Quota mode: none. Oct 6 06:05:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iau157b3mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:05:23 storageqe-109 systemd[1]: tmp-libblockdev.iau157b3mount_test.mount: Deactivated successfully. Oct 6 06:05:23 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 966d2907-1905-4150-8d2f-b8d99771b397. Oct 6 06:05:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:05:23 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:05:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:05:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:05:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:05:56 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:05:56 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:05:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:06:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:06:17 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:06:17 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:06:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:07:46 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:07:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:07:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:07:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:07:46 storageqe-109 stratisd[4947]: [2025-10-06T10:07:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:07:46 storageqe-109 stratisd[4947]: [2025-10-06T10:07:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:07:56 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:08:27 storageqe-109 stratisd[4947]: [2025-10-06T10:08:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:08:27 storageqe-109 stratisd[4947]: [2025-10-06T10:08:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:08:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.r4zostojmount_test with fs xfs Oct 6 06:08:48 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem a7783648-209e-41d1-a0f6-239c142376da Oct 6 06:08:48 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:08:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r4zostojmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:08:53 storageqe-109 systemd[1]: tmp-libblockdev.r4zostojmount_test.mount: Deactivated successfully. Oct 6 06:08:53 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem a7783648-209e-41d1-a0f6-239c142376da Oct 6 06:08:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:08:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g4xhf17jmount_test with fs ext4 Oct 6 06:09:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 73bf7bbd-45f3-4ee6-8079-db5fec52f6f3 r/w with ordered data mode. Quota mode: none. Oct 6 06:09:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g4xhf17jmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:09:09 storageqe-109 systemd[1]: tmp-libblockdev.g4xhf17jmount_test.mount: Deactivated successfully. Oct 6 06:09:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 73bf7bbd-45f3-4ee6-8079-db5fec52f6f3. Oct 6 06:09:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:09:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8k12plijmount_test with fs ext3 Oct 6 06:09:31 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:09:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 135a1707-77db-469a-9d0d-bb227d61b817 r/w with ordered data mode. Quota mode: none. Oct 6 06:09:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8k12plijmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:09:36 storageqe-109 systemd[1]: tmp-libblockdev.8k12plijmount_test.mount: Deactivated successfully. Oct 6 06:09:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 135a1707-77db-469a-9d0d-bb227d61b817. Oct 6 06:09:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:09:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.patkrz9ymount_test with fs ext2 Oct 6 06:09:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:09:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 21f9a04e-412d-40b9-a5cb-fedacc6fb770 r/w without journal. Quota mode: none. Oct 6 06:09:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.patkrz9ymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:10:02 storageqe-109 systemd[1]: tmp-libblockdev.patkrz9ymount_test.mount: Deactivated successfully. Oct 6 06:10:02 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 21f9a04e-412d-40b9-a5cb-fedacc6fb770. Oct 6 06:10:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:10:02 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:10:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:10:13 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:10:25 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:10:35 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:10:35 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:10:35 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:10:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:10:56 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:10:57 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:11:02 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:11:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:11:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:11:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:11:02 storageqe-109 stratisd[4947]: [2025-10-06T10:11:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:11:02 storageqe-109 stratisd[4947]: [2025-10-06T10:11:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:11:06 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 06:11:06 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 06:11:06 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:11:12 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:11:13 storageqe-109 stratisd[4947]: [2025-10-06T10:11:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:11:13 storageqe-109 stratisd[4947]: [2025-10-06T10:11:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:11:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:11:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.nk5qn3wgmount_test with fs xfs Oct 6 06:11:34 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 09ca4345-9333-4c91-84d8-369d2a2cb6d6 Oct 6 06:11:34 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:11:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nk5qn3wgmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:11:39 storageqe-109 systemd[1]: tmp-libblockdev.nk5qn3wgmount_test.mount: Deactivated successfully. Oct 6 06:11:39 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 09ca4345-9333-4c91-84d8-369d2a2cb6d6 Oct 6 06:11:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:11:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2ossgjf4mount_test with fs ext4 Oct 6 06:11:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem bb86f6b7-de2d-45ba-a920-eae772cbafbe r/w with ordered data mode. Quota mode: none. Oct 6 06:11:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2ossgjf4mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:11:56 storageqe-109 systemd[1]: tmp-libblockdev.2ossgjf4mount_test.mount: Deactivated successfully. Oct 6 06:11:56 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem bb86f6b7-de2d-45ba-a920-eae772cbafbe. Oct 6 06:11:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:11:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:12:18 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.t7wcyk0tmount_test with fs ext3 Oct 6 06:12:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 88f583ec-ef20-46ae-b3f7-1ec197de4023 r/w with ordered data mode. Quota mode: none. Oct 6 06:12:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t7wcyk0tmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:12:24 storageqe-109 systemd[1]: tmp-libblockdev.t7wcyk0tmount_test.mount: Deactivated successfully. Oct 6 06:12:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 88f583ec-ef20-46ae-b3f7-1ec197de4023. Oct 6 06:12:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:12:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fws_oj6lmount_test with fs ext2 Oct 6 06:12:45 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:12:45 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 43a2566d-82e1-477d-ace9-732b6335c789 r/w without journal. Quota mode: none. Oct 6 06:12:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fws_oj6lmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:12:50 storageqe-109 systemd[1]: tmp-libblockdev.fws_oj6lmount_test.mount: Deactivated successfully. Oct 6 06:12:50 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 43a2566d-82e1-477d-ace9-732b6335c789. Oct 6 06:12:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:12:50 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:12:51 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:13:01 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:13:13 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:13:23 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:13:23 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:13:23 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:13:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:13:45 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:13:45 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:13:50 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:13:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:13:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:13:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:13:50 storageqe-109 stratisd[4947]: [2025-10-06T10:13:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:13:50 storageqe-109 stratisd[4947]: [2025-10-06T10:13:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:14:00 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:14:01 storageqe-109 stratisd[4947]: [2025-10-06T10:14:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:14:01 storageqe-109 stratisd[4947]: [2025-10-06T10:14:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:14:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:14:15 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.opm_j3bpmount_test with fs xfs Oct 6 06:14:22 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 6eac0081-f7b9-4839-944b-de87ed40afde Oct 6 06:14:22 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:14:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.opm_j3bpmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:14:27 storageqe-109 systemd[1]: tmp-libblockdev.opm_j3bpmount_test.mount: Deactivated successfully. Oct 6 06:14:27 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 6eac0081-f7b9-4839-944b-de87ed40afde Oct 6 06:14:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:14:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fgjx7wdymount_test with fs ext4 Oct 6 06:14:38 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5220b742-9d5c-4ab2-8523-1955f3850559 r/w with ordered data mode. Quota mode: none. Oct 6 06:14:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fgjx7wdymount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:14:44 storageqe-109 systemd[1]: tmp-libblockdev.fgjx7wdymount_test.mount: Deactivated successfully. Oct 6 06:14:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5220b742-9d5c-4ab2-8523-1955f3850559. Oct 6 06:14:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:14:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:15:06 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.dw0oi9zgmount_test with fs ext3 Oct 6 06:15:06 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4846069b-46f6-47d4-b283-eca9ef2143a9 r/w with ordered data mode. Quota mode: none. Oct 6 06:15:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dw0oi9zgmount_test with fs ext3 Oct 6 06:15:11 storageqe-109 systemd[1]: tmp-libblockdev.dw0oi9zgmount_test.mount: Deactivated successfully. Oct 6 06:15:11 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4846069b-46f6-47d4-b283-eca9ef2143a9. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:15:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:15:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9wfi3417mount_test with fs ext2 Oct 6 06:15:32 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:15:32 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c44e92b8-85fb-4f24-8758-37473019c716 r/w without journal. Quota mode: none. Oct 6 06:15:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9wfi3417mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:15:37 storageqe-109 systemd[1]: tmp-libblockdev.9wfi3417mount_test.mount: Deactivated successfully. Oct 6 06:15:37 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c44e92b8-85fb-4f24-8758-37473019c716. Oct 6 06:15:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:15:37 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:15:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:15:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:16:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:16:10 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:16:10 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:16:10 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:16:21 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:16:31 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:16:32 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:16:37 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:16:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:16:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:16:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:16:37 storageqe-109 stratisd[4947]: [2025-10-06T10:16:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:16:37 storageqe-109 stratisd[4947]: [2025-10-06T10:16:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:16:47 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:16:48 storageqe-109 stratisd[4947]: [2025-10-06T10:16:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:16:48 storageqe-109 stratisd[4947]: [2025-10-06T10:16:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:16:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:17:02 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.op0c0arkmount_test with fs xfs Oct 6 06:17:09 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem c226b3a8-6024-4ef7-901e-147d41a6a110 Oct 6 06:17:09 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:17:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.op0c0arkmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:17:15 storageqe-109 systemd[1]: tmp-libblockdev.op0c0arkmount_test.mount: Deactivated successfully. Oct 6 06:17:15 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem c226b3a8-6024-4ef7-901e-147d41a6a110 Oct 6 06:17:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:17:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.v3r2oyismount_test with fs ext4 Oct 6 06:17:26 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8d30852c-bc35-4d5f-bff2-3936e8f1d307 r/w with ordered data mode. Quota mode: none. Oct 6 06:17:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v3r2oyismount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:17:32 storageqe-109 systemd[1]: tmp-libblockdev.v3r2oyismount_test.mount: Deactivated successfully. Oct 6 06:17:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8d30852c-bc35-4d5f-bff2-3936e8f1d307. Oct 6 06:17:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:17:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.d1cym61bmount_test with fs ext3 Oct 6 06:17:54 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:17:54 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 61acf6dd-8d20-4ee0-a843-d5075db4a4b2 r/w with ordered data mode. Quota mode: none. Oct 6 06:17:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d1cym61bmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:17:59 storageqe-109 systemd[1]: tmp-libblockdev.d1cym61bmount_test.mount: Deactivated successfully. Oct 6 06:17:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 61acf6dd-8d20-4ee0-a843-d5075db4a4b2. Oct 6 06:17:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:17:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ohqcoa76mount_test with fs ext2 Oct 6 06:18:21 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:18:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f54722d1-2ef9-4ca1-9aee-4223a69b1018 r/w without journal. Quota mode: none. Oct 6 06:18:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ohqcoa76mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:18:26 storageqe-109 systemd[1]: tmp-libblockdev.ohqcoa76mount_test.mount: Deactivated successfully. Oct 6 06:18:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f54722d1-2ef9-4ca1-9aee-4223a69b1018. Oct 6 06:18:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:18:26 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:18:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:18:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:18:48 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:18:58 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:18:58 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:18:58 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:19:10 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:19:20 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:19:20 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:19:26 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:19:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:19:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:19:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:19:26 storageqe-109 stratisd[4947]: [2025-10-06T10:19:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:19:26 storageqe-109 stratisd[4947]: [2025-10-06T10:19:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:19:36 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:19:37 storageqe-109 stratisd[4947]: [2025-10-06T10:19:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:19:37 storageqe-109 stratisd[4947]: [2025-10-06T10:19:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:19:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:19:50 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.1tcjftgkmount_test with fs xfs Oct 6 06:19:58 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem e4e34c33-3049-46ba-a112-65732f34c4f4 Oct 6 06:19:58 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:19:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1tcjftgkmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:20:03 storageqe-109 systemd[1]: tmp-libblockdev.1tcjftgkmount_test.mount: Deactivated successfully. Oct 6 06:20:03 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem e4e34c33-3049-46ba-a112-65732f34c4f4 Oct 6 06:20:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:20:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ml6bkdicmount_test with fs ext4 Oct 6 06:20:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d176768d-b18a-453e-a442-0a17ea98d309 r/w with ordered data mode. Quota mode: none. Oct 6 06:20:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ml6bkdicmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:20:19 storageqe-109 systemd[1]: tmp-libblockdev.ml6bkdicmount_test.mount: Deactivated successfully. Oct 6 06:20:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d176768d-b18a-453e-a442-0a17ea98d309. Oct 6 06:20:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:20:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:20:41 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.w0gil9nhmount_test with fs ext3 Oct 6 06:20:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5f18bf57-1b17-4dbc-a913-c74d37445ecf r/w with ordered data mode. Quota mode: none. Oct 6 06:20:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.w0gil9nhmount_test with fs ext3 Oct 6 06:20:46 storageqe-109 systemd[1]: tmp-libblockdev.w0gil9nhmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:20:46 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5f18bf57-1b17-4dbc-a913-c74d37445ecf. Oct 6 06:20:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:20:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.17aqkko9mount_test with fs ext2 Oct 6 06:21:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:21:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b0e90111-5f5c-49bf-8aa7-41dfe85e3ad5 r/w without journal. Quota mode: none. Oct 6 06:21:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.17aqkko9mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:21:12 storageqe-109 systemd[1]: tmp-libblockdev.17aqkko9mount_test.mount: Deactivated successfully. Oct 6 06:21:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b0e90111-5f5c-49bf-8aa7-41dfe85e3ad5. Oct 6 06:21:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:21:12 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:21:13 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:21:23 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:21:35 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:21:45 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:21:45 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:21:45 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:21:57 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:22:07 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:22:07 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:22:37 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:23:35 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:23:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:23:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:23:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:23:35 storageqe-109 stratisd[4947]: [2025-10-06T10:23:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:23:35 storageqe-109 stratisd[4947]: [2025-10-06T10:23:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:23:45 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:24:16 storageqe-109 stratisd[4947]: [2025-10-06T10:24:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:24:16 storageqe-109 stratisd[4947]: [2025-10-06T10:24:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:24:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.4k8r19bomount_test with fs xfs Oct 6 06:24:37 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem de135b9b-880f-4c27-84e1-70c45bf194ec Oct 6 06:24:37 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:24:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4k8r19bomount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:24:42 storageqe-109 systemd[1]: tmp-libblockdev.4k8r19bomount_test.mount: Deactivated successfully. Oct 6 06:24:42 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem de135b9b-880f-4c27-84e1-70c45bf194ec Oct 6 06:24:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:24:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ko7d17rnmount_test with fs ext4 Oct 6 06:24:54 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 18fbc3e2-fa96-48f5-a8ff-339922b10f61 r/w with ordered data mode. Quota mode: none. Oct 6 06:24:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ko7d17rnmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:24:59 storageqe-109 systemd[1]: tmp-libblockdev.ko7d17rnmount_test.mount: Deactivated successfully. Oct 6 06:24:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 18fbc3e2-fa96-48f5-a8ff-339922b10f61. Oct 6 06:24:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:24:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._ycfey_gmount_test with fs ext3 Oct 6 06:25:21 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:25:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a6808518-76b7-4257-b403-5ee1d9743f05 r/w with ordered data mode. Quota mode: none. Oct 6 06:25:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev._ycfey_gmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:25:27 storageqe-109 systemd[1]: tmp-libblockdev._ycfey_gmount_test.mount: Deactivated successfully. Oct 6 06:25:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a6808518-76b7-4257-b403-5ee1d9743f05. Oct 6 06:25:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:25:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8wp468c8mount_test with fs ext2 Oct 6 06:25:48 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:25:48 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6121e5ff-88b2-4627-802a-3af9b5470eb5 r/w without journal. Quota mode: none. Oct 6 06:25:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8wp468c8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:25:54 storageqe-109 systemd[1]: tmp-libblockdev.8wp468c8mount_test.mount: Deactivated successfully. Oct 6 06:25:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6121e5ff-88b2-4627-802a-3af9b5470eb5. Oct 6 06:25:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:25:54 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:25:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:26:04 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:26:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:26:26 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:26:26 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:26:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:26:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:26:48 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:26:48 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:27:18 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:28:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:28:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:28:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:28:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:28:17 storageqe-109 stratisd[4947]: [2025-10-06T10:28:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:28:17 storageqe-109 stratisd[4947]: [2025-10-06T10:28:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:28:26 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:28:57 storageqe-109 stratisd[4947]: [2025-10-06T10:28:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:28:57 storageqe-109 stratisd[4947]: [2025-10-06T10:28:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:29:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.c_x7ftwsmount_test with fs xfs Oct 6 06:29:18 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 9c8b5622-a936-4a96-aba2-15ffcbb45081 Oct 6 06:29:18 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:29:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c_x7ftwsmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:29:23 storageqe-109 systemd[1]: tmp-libblockdev.c_x7ftwsmount_test.mount: Deactivated successfully. Oct 6 06:29:23 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 9c8b5622-a936-4a96-aba2-15ffcbb45081 Oct 6 06:29:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:29:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.42b38hdcmount_test with fs ext4 Oct 6 06:29:34 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem cd02f00d-baa1-43e2-8279-5a1b29a70ba3 r/w with ordered data mode. Quota mode: none. Oct 6 06:29:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.42b38hdcmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:29:39 storageqe-109 systemd[1]: tmp-libblockdev.42b38hdcmount_test.mount: Deactivated successfully. Oct 6 06:29:39 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem cd02f00d-baa1-43e2-8279-5a1b29a70ba3. Oct 6 06:29:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:29:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3ijlzlm_mount_test with fs ext3 Oct 6 06:30:01 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:30:01 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5812ca97-fd7b-48d5-8fe7-9dac0417ef59 r/w with ordered data mode. Quota mode: none. Oct 6 06:30:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3ijlzlm_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:30:06 storageqe-109 systemd[1]: tmp-libblockdev.3ijlzlm_mount_test.mount: Deactivated successfully. Oct 6 06:30:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5812ca97-fd7b-48d5-8fe7-9dac0417ef59. Oct 6 06:30:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:30:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cwgqaytsmount_test with fs ext2 Oct 6 06:30:27 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:30:27 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f8866f12-764f-4920-978d-5b2f563e9f7b r/w without journal. Quota mode: none. Oct 6 06:30:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cwgqaytsmount_test with fs ext2 Oct 6 06:30:32 storageqe-109 systemd[1]: tmp-libblockdev.cwgqaytsmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:30:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f8866f12-764f-4920-978d-5b2f563e9f7b. Oct 6 06:30:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:30:32 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:30:33 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:30:43 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:30:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:31:05 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:31:05 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:31:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:31:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:31:26 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:31:26 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:31:56 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:32:54 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:32:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:54 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:32:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:32:55 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:32:55 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:32:55 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:32:55 storageqe-109 stratisd[4947]: [2025-10-06T10:32:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:32:55 storageqe-109 stratisd[4947]: [2025-10-06T10:32:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:33:05 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:33:35 storageqe-109 stratisd[4947]: [2025-10-06T10:33:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:33:35 storageqe-109 stratisd[4947]: [2025-10-06T10:33:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:33:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._xpm53cgmount_test with fs xfs Oct 6 06:33:57 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 2f871361-330e-4dc6-a296-ad5df3c077e5 Oct 6 06:33:57 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:33:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev._xpm53cgmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:34:02 storageqe-109 systemd[1]: tmp-libblockdev._xpm53cgmount_test.mount: Deactivated successfully. Oct 6 06:34:02 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 2f871361-330e-4dc6-a296-ad5df3c077e5 Oct 6 06:34:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:34:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fb8yn1yumount_test with fs ext4 Oct 6 06:34:13 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c66b8ec2-cc3e-4b70-b64e-b9b3978128d2 r/w with ordered data mode. Quota mode: none. Oct 6 06:34:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fb8yn1yumount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:34:19 storageqe-109 systemd[1]: tmp-libblockdev.fb8yn1yumount_test.mount: Deactivated successfully. Oct 6 06:34:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c66b8ec2-cc3e-4b70-b64e-b9b3978128d2. Oct 6 06:34:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:34:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fvbqaj7zmount_test with fs ext3 Oct 6 06:34:41 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:34:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3cb19c7b-869b-4408-b1cd-bdac456eff4a r/w with ordered data mode. Quota mode: none. Oct 6 06:34:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fvbqaj7zmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:34:47 storageqe-109 systemd[1]: tmp-libblockdev.fvbqaj7zmount_test.mount: Deactivated successfully. Oct 6 06:34:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3cb19c7b-869b-4408-b1cd-bdac456eff4a. Oct 6 06:34:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:34:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.v42g5ve_mount_test with fs ext2 Oct 6 06:35:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:35:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6449dadd-a0c7-4eec-b96e-099bb3bf5f6e r/w without journal. Quota mode: none. Oct 6 06:35:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v42g5ve_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:35:14 storageqe-109 systemd[1]: tmp-libblockdev.v42g5ve_mount_test.mount: Deactivated successfully. Oct 6 06:35:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6449dadd-a0c7-4eec-b96e-099bb3bf5f6e. Oct 6 06:35:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:35:14 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:35:14 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:35:24 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:35:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:35:46 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:35:46 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:35:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:35:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:36:08 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:36:08 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:36:38 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:37:36 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:37:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:37:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:37:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:37:36 storageqe-109 stratisd[4947]: [2025-10-06T10:37:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:37:36 storageqe-109 stratisd[4947]: [2025-10-06T10:37:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:37:46 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:38:17 storageqe-109 stratisd[4947]: [2025-10-06T10:38:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:38:17 storageqe-109 stratisd[4947]: [2025-10-06T10:38:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:38:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.z7fsaeh_mount_test with fs xfs Oct 6 06:38:38 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 4c9b9578-a99c-4062-b261-73d31cb5ec48 Oct 6 06:38:38 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:38:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z7fsaeh_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:38:43 storageqe-109 systemd[1]: tmp-libblockdev.z7fsaeh_mount_test.mount: Deactivated successfully. Oct 6 06:38:43 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 4c9b9578-a99c-4062-b261-73d31cb5ec48 Oct 6 06:38:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:38:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.clf8dtvbmount_test with fs ext4 Oct 6 06:38:54 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c6319a5a-3c15-4697-b158-b10746f5edc0 r/w with ordered data mode. Quota mode: none. Oct 6 06:38:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.clf8dtvbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:39:00 storageqe-109 systemd[1]: tmp-libblockdev.clf8dtvbmount_test.mount: Deactivated successfully. Oct 6 06:39:00 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c6319a5a-3c15-4697-b158-b10746f5edc0. Oct 6 06:39:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:39:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:39:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.ab_5b115mount_test with fs ext3 Oct 6 06:39:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 23790fe1-f9f3-436f-bfd6-545b3e155b0b r/w with ordered data mode. Quota mode: none. Oct 6 06:39:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ab_5b115mount_test with fs ext3 Oct 6 06:39:26 storageqe-109 systemd[1]: tmp-libblockdev.ab_5b115mount_test.mount: Deactivated successfully. Oct 6 06:39:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 23790fe1-f9f3-436f-bfd6-545b3e155b0b. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:39:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:39:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mni83um3mount_test with fs ext2 Oct 6 06:39:48 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:39:48 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 59795d88-dec5-44d9-9030-b02ac621d488 r/w without journal. Quota mode: none. Oct 6 06:39:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mni83um3mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:39:53 storageqe-109 systemd[1]: tmp-libblockdev.mni83um3mount_test.mount: Deactivated successfully. Oct 6 06:39:53 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 59795d88-dec5-44d9-9030-b02ac621d488. Oct 6 06:39:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:39:53 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:39:53 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:40:03 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:40:15 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:40:25 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:40:25 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:40:25 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:40:37 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:40:47 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:40:47 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:40:52 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:40:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:52 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:40:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:40:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:40:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:40:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:40:53 storageqe-109 stratisd[4947]: [2025-10-06T10:40:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:40:53 storageqe-109 stratisd[4947]: [2025-10-06T10:40:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:41:02 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:41:03 storageqe-109 stratisd[4947]: [2025-10-06T10:41:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:41:03 storageqe-109 stratisd[4947]: [2025-10-06T10:41:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:41:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:41:17 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.maf9lvyumount_test with fs xfs Oct 6 06:41:24 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 77573d40-1355-4a45-92b8-95de9195b28c Oct 6 06:41:24 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:41:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.maf9lvyumount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:41:30 storageqe-109 systemd[1]: tmp-libblockdev.maf9lvyumount_test.mount: Deactivated successfully. Oct 6 06:41:30 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 77573d40-1355-4a45-92b8-95de9195b28c Oct 6 06:41:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:41:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.py0zscr9mount_test with fs ext4 Oct 6 06:41:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 54133bcc-4ddd-40bf-b798-fb055e6752da r/w with ordered data mode. Quota mode: none. Oct 6 06:41:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.py0zscr9mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:41:47 storageqe-109 systemd[1]: tmp-libblockdev.py0zscr9mount_test.mount: Deactivated successfully. Oct 6 06:41:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 54133bcc-4ddd-40bf-b798-fb055e6752da. Oct 6 06:41:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:41:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:42:09 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:42:09 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f1a0e025-3142-4a0e-a289-97886d0197ba r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.cvl5e3jlmount_test with fs ext3 Oct 6 06:42:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cvl5e3jlmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:42:14 storageqe-109 systemd[1]: tmp-libblockdev.cvl5e3jlmount_test.mount: Deactivated successfully. Oct 6 06:42:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f1a0e025-3142-4a0e-a289-97886d0197ba. Oct 6 06:42:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:42:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.il0oye_kmount_test with fs ext2 Oct 6 06:42:36 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:42:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 77d0aa6c-53fa-48ee-9a6c-07719a029b66 r/w without journal. Quota mode: none. Oct 6 06:42:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.il0oye_kmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:42:41 storageqe-109 systemd[1]: tmp-libblockdev.il0oye_kmount_test.mount: Deactivated successfully. Oct 6 06:42:41 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 77d0aa6c-53fa-48ee-9a6c-07719a029b66. Oct 6 06:42:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:42:41 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:42:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:42:51 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:43:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:43:13 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:43:13 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:43:13 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:43:25 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:43:35 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:43:35 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:43:40 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:43:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:40 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:43:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:43:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:43:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:43:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:43:41 storageqe-109 stratisd[4947]: [2025-10-06T10:43:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:43:41 storageqe-109 stratisd[4947]: [2025-10-06T10:43:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:43:51 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:43:52 storageqe-109 stratisd[4947]: [2025-10-06T10:43:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:43:52 storageqe-109 stratisd[4947]: [2025-10-06T10:43:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:44:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:44:05 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.a0qxgvnomount_test with fs xfs Oct 6 06:44:13 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 591fe954-d590-48f8-ba89-5a8706c36e34 Oct 6 06:44:13 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:44:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a0qxgvnomount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:44:18 storageqe-109 systemd[1]: tmp-libblockdev.a0qxgvnomount_test.mount: Deactivated successfully. Oct 6 06:44:18 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 591fe954-d590-48f8-ba89-5a8706c36e34 Oct 6 06:44:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:44:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.oa0o1007mount_test with fs ext4 Oct 6 06:44:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a1c18331-4665-49db-9e4c-271a51ffb450 r/w with ordered data mode. Quota mode: none. Oct 6 06:44:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.oa0o1007mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:44:34 storageqe-109 systemd[1]: tmp-libblockdev.oa0o1007mount_test.mount: Deactivated successfully. Oct 6 06:44:34 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a1c18331-4665-49db-9e4c-271a51ffb450. Oct 6 06:44:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:44:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vetccg7jmount_test with fs ext3 Oct 6 06:44:56 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:44:56 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4c505ffa-2ca2-478f-860e-77869161baf4 r/w with ordered data mode. Quota mode: none. Oct 6 06:44:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vetccg7jmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:45:01 storageqe-109 systemd[1]: tmp-libblockdev.vetccg7jmount_test.mount: Deactivated successfully. Oct 6 06:45:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4c505ffa-2ca2-478f-860e-77869161baf4. Oct 6 06:45:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:45:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qd_wukuomount_test with fs ext2 Oct 6 06:45:23 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:45:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6fa37e01-9849-4f62-8db9-493ae5e1143c r/w without journal. Quota mode: none. Oct 6 06:45:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qd_wukuomount_test with fs ext2 Oct 6 06:45:27 storageqe-109 systemd[1]: tmp-libblockdev.qd_wukuomount_test.mount: Deactivated successfully. Oct 6 06:45:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6fa37e01-9849-4f62-8db9-493ae5e1143c. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:45:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:45:28 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:45:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:45:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:45:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:46:00 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:46:00 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:46:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:46:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:46:22 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:46:22 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:46:27 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:46:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:46:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:46:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:46:27 storageqe-109 stratisd[4947]: [2025-10-06T10:46:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:46:27 storageqe-109 stratisd[4947]: [2025-10-06T10:46:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:46:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:46:38 storageqe-109 stratisd[4947]: [2025-10-06T10:46:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:46:38 storageqe-109 stratisd[4947]: [2025-10-06T10:46:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:46:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:46:52 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.fm_dyvqfmount_test with fs xfs Oct 6 06:46:59 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 4c5a3445-002c-402a-9dac-a8855ebe539b Oct 6 06:46:59 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:46:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fm_dyvqfmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:47:05 storageqe-109 systemd[1]: tmp-libblockdev.fm_dyvqfmount_test.mount: Deactivated successfully. Oct 6 06:47:05 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 4c5a3445-002c-402a-9dac-a8855ebe539b Oct 6 06:47:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:47:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hdlakkiemount_test with fs ext4 Oct 6 06:47:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d22c2eb8-f008-4a12-9dc7-2be6a78d6f10 r/w with ordered data mode. Quota mode: none. Oct 6 06:47:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hdlakkiemount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:47:22 storageqe-109 systemd[1]: tmp-libblockdev.hdlakkiemount_test.mount: Deactivated successfully. Oct 6 06:47:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d22c2eb8-f008-4a12-9dc7-2be6a78d6f10. Oct 6 06:47:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:47:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jl03ql_tmount_test with fs ext3 Oct 6 06:47:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:47:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e772210a-5290-4c21-b9bc-7cecb3de4e17 r/w with ordered data mode. Quota mode: none. Oct 6 06:47:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jl03ql_tmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:47:49 storageqe-109 systemd[1]: tmp-libblockdev.jl03ql_tmount_test.mount: Deactivated successfully. Oct 6 06:47:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e772210a-5290-4c21-b9bc-7cecb3de4e17. Oct 6 06:47:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:47:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._a0et1i4mount_test with fs ext2 Oct 6 06:48:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:48:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 06654dd5-1205-4024-92ea-39bc628001fd r/w without journal. Quota mode: none. Oct 6 06:48:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev._a0et1i4mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:48:16 storageqe-109 systemd[1]: tmp-libblockdev._a0et1i4mount_test.mount: Deactivated successfully. Oct 6 06:48:16 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 06654dd5-1205-4024-92ea-39bc628001fd. Oct 6 06:48:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:48:16 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:48:17 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:48:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:48:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:48:48 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:48:48 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:48:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:49:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:49:10 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:49:10 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:49:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:49:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:49:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:49:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:49:16 storageqe-109 stratisd[4947]: [2025-10-06T10:49:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:49:16 storageqe-109 stratisd[4947]: [2025-10-06T10:49:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:49:26 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:49:27 storageqe-109 stratisd[4947]: [2025-10-06T10:49:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:49:27 storageqe-109 stratisd[4947]: [2025-10-06T10:49:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:49:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:49:40 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.52yxt_ylmount_test with fs xfs Oct 6 06:49:48 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 625d11e4-b453-4a23-b858-bedcd56ed244 Oct 6 06:49:48 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:49:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.52yxt_ylmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:49:53 storageqe-109 systemd[1]: tmp-libblockdev.52yxt_ylmount_test.mount: Deactivated successfully. Oct 6 06:49:53 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 625d11e4-b453-4a23-b858-bedcd56ed244 Oct 6 06:49:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:49:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3g38ekolmount_test with fs ext4 Oct 6 06:50:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3895a883-31d7-4e51-b7c1-a207bd695d04 r/w with ordered data mode. Quota mode: none. Oct 6 06:50:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3g38ekolmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:50:09 storageqe-109 systemd[1]: tmp-libblockdev.3g38ekolmount_test.mount: Deactivated successfully. Oct 6 06:50:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3895a883-31d7-4e51-b7c1-a207bd695d04. Oct 6 06:50:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:50:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0qke3ml2mount_test with fs ext3 Oct 6 06:50:31 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:50:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c0279cff-58e9-438e-a8e0-4dbed17b67f3 r/w with ordered data mode. Quota mode: none. Oct 6 06:50:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0qke3ml2mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:50:36 storageqe-109 systemd[1]: tmp-libblockdev.0qke3ml2mount_test.mount: Deactivated successfully. Oct 6 06:50:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c0279cff-58e9-438e-a8e0-4dbed17b67f3. Oct 6 06:50:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:50:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.eysarhalmount_test with fs ext2 Oct 6 06:50:57 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:50:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 55432cb6-562a-4c7d-b7d9-a4803f211a8d r/w without journal. Quota mode: none. Oct 6 06:50:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.eysarhalmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:51:02 storageqe-109 systemd[1]: tmp-libblockdev.eysarhalmount_test.mount: Deactivated successfully. Oct 6 06:51:02 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 55432cb6-562a-4c7d-b7d9-a4803f211a8d. Oct 6 06:51:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:51:02 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:51:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:51:13 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:51:25 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:51:35 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:51:35 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:51:35 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:51:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:51:56 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:51:57 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 06:52:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:53:25 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:53:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:53:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:53:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:53:25 storageqe-109 stratisd[4947]: [2025-10-06T10:53:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:53:25 storageqe-109 stratisd[4947]: [2025-10-06T10:53:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:53:35 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:54:05 storageqe-109 stratisd[4947]: [2025-10-06T10:54:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:54:05 storageqe-109 stratisd[4947]: [2025-10-06T10:54:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:54:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.gcv41n9emount_test with fs xfs Oct 6 06:54:27 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 6498b196-3dd0-47a9-9e89-6de63d54e821 Oct 6 06:54:27 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:54:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gcv41n9emount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:54:32 storageqe-109 systemd[1]: tmp-libblockdev.gcv41n9emount_test.mount: Deactivated successfully. Oct 6 06:54:32 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 6498b196-3dd0-47a9-9e89-6de63d54e821 Oct 6 06:54:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:54:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jfm_avftmount_test with fs ext4 Oct 6 06:54:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 02840d1a-c570-429e-97a5-43b356d8fea3 r/w with ordered data mode. Quota mode: none. Oct 6 06:54:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jfm_avftmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:54:49 storageqe-109 systemd[1]: tmp-libblockdev.jfm_avftmount_test.mount: Deactivated successfully. Oct 6 06:54:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 02840d1a-c570-429e-97a5-43b356d8fea3. Oct 6 06:54:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:54:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vyj3dhivmount_test with fs ext3 Oct 6 06:55:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:55:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b4d9ba53-d872-45a8-9601-4305baa3dbe4 r/w with ordered data mode. Quota mode: none. Oct 6 06:55:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vyj3dhivmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:55:17 storageqe-109 systemd[1]: tmp-libblockdev.vyj3dhivmount_test.mount: Deactivated successfully. Oct 6 06:55:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b4d9ba53-d872-45a8-9601-4305baa3dbe4. Oct 6 06:55:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:55:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.36dkc6o5mount_test with fs ext2 Oct 6 06:55:38 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 06:55:38 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 047d9811-46a0-49cf-8459-7e9ef02bb0ec r/w without journal. Quota mode: none. Oct 6 06:55:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.36dkc6o5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 06:55:44 storageqe-109 systemd[1]: tmp-libblockdev.36dkc6o5mount_test.mount: Deactivated successfully. Oct 6 06:55:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 047d9811-46a0-49cf-8459-7e9ef02bb0ec. Oct 6 06:55:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:55:44 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:55:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 06:55:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:56:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 06:56:16 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 06:56:16 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 06:56:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 06:56:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:56:38 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 06:56:38 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 06:57:08 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 06:58:06 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 06:58:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 06:58:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 06:58:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 06:58:06 storageqe-109 stratisd[4947]: [2025-10-06T10:58:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:58:06 storageqe-109 stratisd[4947]: [2025-10-06T10:58:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:58:16 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 06:58:46 storageqe-109 stratisd[4947]: [2025-10-06T10:58:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 06:58:46 storageqe-109 stratisd[4947]: [2025-10-06T10:58:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:58:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.v_luv8ovmount_test with fs xfs Oct 6 06:59:08 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem a7387193-030a-4ad6-8fba-513fcef52f5c Oct 6 06:59:08 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 06:59:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v_luv8ovmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:59:12 storageqe-109 systemd[1]: tmp-libblockdev.v_luv8ovmount_test.mount: Deactivated successfully. Oct 6 06:59:12 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem a7387193-030a-4ad6-8fba-513fcef52f5c Oct 6 06:59:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 06:59:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fmgh4scsmount_test with fs ext4 Oct 6 06:59:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c3436fde-d81b-4de0-a0fb-db62015f98eb r/w with ordered data mode. Quota mode: none. Oct 6 06:59:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fmgh4scsmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:59:29 storageqe-109 systemd[1]: tmp-libblockdev.fmgh4scsmount_test.mount: Deactivated successfully. Oct 6 06:59:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c3436fde-d81b-4de0-a0fb-db62015f98eb. Oct 6 06:59:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 06:59:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.og7fn8q4mount_test with fs ext3 Oct 6 06:59:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 06:59:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 99fde53d-a10b-4779-a186-4c8904d07b5a r/w with ordered data mode. Quota mode: none. Oct 6 06:59:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.og7fn8q4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 06:59:56 storageqe-109 systemd[1]: tmp-libblockdev.og7fn8q4mount_test.mount: Deactivated successfully. Oct 6 06:59:56 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 99fde53d-a10b-4779-a186-4c8904d07b5a. Oct 6 06:59:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 06:59:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2jud9g5dmount_test with fs ext2 Oct 6 07:00:18 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:00:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 346f359d-b082-4406-a726-761d6bcd37ca r/w without journal. Quota mode: none. Oct 6 07:00:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2jud9g5dmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:00:22 storageqe-109 systemd[1]: tmp-libblockdev.2jud9g5dmount_test.mount: Deactivated successfully. Oct 6 07:00:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 346f359d-b082-4406-a726-761d6bcd37ca. Oct 6 07:00:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:00:22 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:00:23 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:00:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:00:45 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:00:55 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:00:55 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:00:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:01:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:01:17 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:01:17 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:01:47 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:02:45 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:02:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:02:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:02:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:02:45 storageqe-109 stratisd[4947]: [2025-10-06T11:02:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:02:45 storageqe-109 stratisd[4947]: [2025-10-06T11:02:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:02:55 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:03:26 storageqe-109 stratisd[4947]: [2025-10-06T11:03:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:03:26 storageqe-109 stratisd[4947]: [2025-10-06T11:03:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:03:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.sy0tn7utmount_test with fs xfs Oct 6 07:03:47 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem e12d1563-46a9-4523-ad54-3e9a1f9ffb97 Oct 6 07:03:47 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:03:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sy0tn7utmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:03:53 storageqe-109 systemd[1]: tmp-libblockdev.sy0tn7utmount_test.mount: Deactivated successfully. Oct 6 07:03:53 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem e12d1563-46a9-4523-ad54-3e9a1f9ffb97 Oct 6 07:03:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:03:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.yr6gwiqkmount_test with fs ext4 Oct 6 07:04:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7fe382b5-2e99-4277-b4a0-af248b9f9340 r/w with ordered data mode. Quota mode: none. Oct 6 07:04:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yr6gwiqkmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:04:10 storageqe-109 systemd[1]: tmp-libblockdev.yr6gwiqkmount_test.mount: Deactivated successfully. Oct 6 07:04:10 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7fe382b5-2e99-4277-b4a0-af248b9f9340. Oct 6 07:04:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:04:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vbvqivd4mount_test with fs ext3 Oct 6 07:04:32 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:04:32 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d5e61785-ebb8-4b7a-a8b8-bb5bf7b3bcfe r/w with ordered data mode. Quota mode: none. Oct 6 07:04:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vbvqivd4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:04:38 storageqe-109 systemd[1]: tmp-libblockdev.vbvqivd4mount_test.mount: Deactivated successfully. Oct 6 07:04:38 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d5e61785-ebb8-4b7a-a8b8-bb5bf7b3bcfe. Oct 6 07:04:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:04:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mcyqtfpxmount_test with fs ext2 Oct 6 07:04:59 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:04:59 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7417cf4e-1ba1-433f-b5b9-17978899575d r/w without journal. Quota mode: none. Oct 6 07:04:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mcyqtfpxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:05:04 storageqe-109 systemd[1]: tmp-libblockdev.mcyqtfpxmount_test.mount: Deactivated successfully. Oct 6 07:05:04 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7417cf4e-1ba1-433f-b5b9-17978899575d. Oct 6 07:05:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:05:05 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:05:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:05:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:05:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:05:37 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:05:37 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:05:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:05:49 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:05:59 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:05:59 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:06:29 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:07:27 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:07:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:07:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:07:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:07:27 storageqe-109 stratisd[4947]: [2025-10-06T11:07:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:07:27 storageqe-109 stratisd[4947]: [2025-10-06T11:07:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:07:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:08:08 storageqe-109 stratisd[4947]: [2025-10-06T11:08:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:08:08 storageqe-109 stratisd[4947]: [2025-10-06T11:08:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:08:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.c0mrldi5mount_test with fs xfs Oct 6 07:08:29 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f2df8619-8013-43d0-89d7-c43bf998562c Oct 6 07:08:29 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:08:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c0mrldi5mount_test with fs xfs Oct 6 07:08:34 storageqe-109 systemd[1]: tmp-libblockdev.c0mrldi5mount_test.mount: Deactivated successfully. Oct 6 07:08:34 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f2df8619-8013-43d0-89d7-c43bf998562c INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:08:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:08:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8zjtwhicmount_test with fs ext4 Oct 6 07:08:45 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f2bf80f4-f0c4-4da0-ac73-c27393fab4d2 r/w with ordered data mode. Quota mode: none. Oct 6 07:08:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8zjtwhicmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:08:51 storageqe-109 systemd[1]: tmp-libblockdev.8zjtwhicmount_test.mount: Deactivated successfully. Oct 6 07:08:51 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f2bf80f4-f0c4-4da0-ac73-c27393fab4d2. Oct 6 07:08:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:08:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ae7w6qbimount_test with fs ext3 Oct 6 07:09:13 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:09:13 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 13b4115b-8011-4778-afb9-91636a4fee8f r/w with ordered data mode. Quota mode: none. Oct 6 07:09:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ae7w6qbimount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:09:18 storageqe-109 systemd[1]: tmp-libblockdev.ae7w6qbimount_test.mount: Deactivated successfully. Oct 6 07:09:18 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 13b4115b-8011-4778-afb9-91636a4fee8f. Oct 6 07:09:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:09:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bplc7qewmount_test with fs ext2 Oct 6 07:09:39 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:09:39 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 12fd687f-575e-47c4-ac37-e2d2d653b383 r/w without journal. Quota mode: none. Oct 6 07:09:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bplc7qewmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:09:44 storageqe-109 systemd[1]: tmp-libblockdev.bplc7qewmount_test.mount: Deactivated successfully. Oct 6 07:09:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 12fd687f-575e-47c4-ac37-e2d2d653b383. Oct 6 07:09:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:09:44 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:09:45 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:09:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:10:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:10:16 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:10:16 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:10:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:10:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:10:38 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:10:38 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:10:43 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:10:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:43 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:10:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:10:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:10:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:10:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627554, async page read Oct 6 07:10:44 storageqe-109 stratisd[4947]: [2025-10-06T11:10:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:10:44 storageqe-109 stratisd[4947]: [2025-10-06T11:10:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:10:54 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:10:55 storageqe-109 stratisd[4947]: [2025-10-06T11:10:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:10:55 storageqe-109 stratisd[4947]: [2025-10-06T11:10:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:11:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:11:08 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.w3kzx4o4mount_test with fs xfs Oct 6 07:11:16 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 21aea9b3-1c23-4ae2-a220-4c6d91236d6d Oct 6 07:11:16 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:11:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.w3kzx4o4mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:11:22 storageqe-109 systemd[1]: tmp-libblockdev.w3kzx4o4mount_test.mount: Deactivated successfully. Oct 6 07:11:22 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 21aea9b3-1c23-4ae2-a220-4c6d91236d6d Oct 6 07:11:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:11:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vmkfwpatmount_test with fs ext4 Oct 6 07:11:33 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 34c34f90-175d-4b38-9722-a4d925c0567c r/w with ordered data mode. Quota mode: none. Oct 6 07:11:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vmkfwpatmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:11:39 storageqe-109 systemd[1]: tmp-libblockdev.vmkfwpatmount_test.mount: Deactivated successfully. Oct 6 07:11:39 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 34c34f90-175d-4b38-9722-a4d925c0567c. Oct 6 07:11:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:11:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i9iiu9u3mount_test with fs ext3 Oct 6 07:12:04 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:12:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3af3a6d3-9315-4353-91e8-4eab2573ab03 r/w with ordered data mode. Quota mode: none. Oct 6 07:12:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i9iiu9u3mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:12:10 storageqe-109 systemd[1]: tmp-libblockdev.i9iiu9u3mount_test.mount: Deactivated successfully. Oct 6 07:12:10 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3af3a6d3-9315-4353-91e8-4eab2573ab03. Oct 6 07:12:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:12:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f20eqpw_mount_test with fs ext2 Oct 6 07:12:34 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:12:34 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e071a69a-164d-41bb-98c8-bbfdc4f4d8ce r/w without journal. Quota mode: none. Oct 6 07:12:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f20eqpw_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:12:40 storageqe-109 systemd[1]: tmp-libblockdev.f20eqpw_mount_test.mount: Deactivated successfully. Oct 6 07:12:40 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e071a69a-164d-41bb-98c8-bbfdc4f4d8ce. Oct 6 07:12:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:12:40 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:12:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:12:51 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:13:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:13:13 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:13:13 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:13:13 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:13:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:13:34 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:13:35 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:13:40 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:13:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:13:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:13:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:13:40 storageqe-109 stratisd[4947]: [2025-10-06T11:13:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:13:40 storageqe-109 stratisd[4947]: [2025-10-06T11:13:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:13:50 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:13:51 storageqe-109 stratisd[4947]: [2025-10-06T11:13:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:13:51 storageqe-109 stratisd[4947]: [2025-10-06T11:13:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:14:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:14:05 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.9m80b24dmount_test with fs xfs Oct 6 07:14:12 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 860078db-213a-4c6f-b9ef-cbbf1773ccd6 Oct 6 07:14:12 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:14:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9m80b24dmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:14:17 storageqe-109 systemd[1]: tmp-libblockdev.9m80b24dmount_test.mount: Deactivated successfully. Oct 6 07:14:17 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 860078db-213a-4c6f-b9ef-cbbf1773ccd6 Oct 6 07:14:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:14:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bqwqk1vimount_test with fs ext4 Oct 6 07:14:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem fe7a45fe-e55d-46b7-978d-df6cb7f5c156 r/w with ordered data mode. Quota mode: none. Oct 6 07:14:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bqwqk1vimount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:14:34 storageqe-109 systemd[1]: tmp-libblockdev.bqwqk1vimount_test.mount: Deactivated successfully. Oct 6 07:14:34 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem fe7a45fe-e55d-46b7-978d-df6cb7f5c156. Oct 6 07:14:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:14:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.d444s0unmount_test with fs ext3 Oct 6 07:14:56 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:14:56 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 93a922ae-4b76-4396-bef8-ff192223830b r/w with ordered data mode. Quota mode: none. Oct 6 07:14:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d444s0unmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:15:01 storageqe-109 systemd[1]: tmp-libblockdev.d444s0unmount_test.mount: Deactivated successfully. Oct 6 07:15:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 93a922ae-4b76-4396-bef8-ff192223830b. Oct 6 07:15:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:15:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i3y_ti0bmount_test with fs ext2 Oct 6 07:15:23 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:15:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4da8f68a-ce94-4c11-8b78-26a0f681a2ca r/w without journal. Quota mode: none. Oct 6 07:15:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i3y_ti0bmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:15:28 storageqe-109 systemd[1]: tmp-libblockdev.i3y_ti0bmount_test.mount: Deactivated successfully. Oct 6 07:15:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4da8f68a-ce94-4c11-8b78-26a0f681a2ca. Oct 6 07:15:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:15:28 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:15:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:15:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:15:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:16:00 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:16:00 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:16:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:16:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:16:22 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:16:22 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:16:27 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:16:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:16:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:16:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:16:28 storageqe-109 stratisd[4947]: [2025-10-06T11:16:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:16:28 storageqe-109 stratisd[4947]: [2025-10-06T11:16:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:16:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:16:38 storageqe-109 stratisd[4947]: [2025-10-06T11:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:16:38 storageqe-109 stratisd[4947]: [2025-10-06T11:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:16:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:16:52 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.n58mk8grmount_test with fs xfs Oct 6 07:16:59 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem c5a004e1-3cc3-40a3-b499-587172ee05e7 Oct 6 07:16:59 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:16:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n58mk8grmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:17:05 storageqe-109 systemd[1]: tmp-libblockdev.n58mk8grmount_test.mount: Deactivated successfully. Oct 6 07:17:05 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem c5a004e1-3cc3-40a3-b499-587172ee05e7 Oct 6 07:17:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:17:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6cdcx1nxmount_test with fs ext4 Oct 6 07:17:17 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ddc47f7d-1aa0-4f73-809e-362c72d9c6a7 r/w with ordered data mode. Quota mode: none. Oct 6 07:17:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6cdcx1nxmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:17:23 storageqe-109 systemd[1]: tmp-libblockdev.6cdcx1nxmount_test.mount: Deactivated successfully. Oct 6 07:17:23 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ddc47f7d-1aa0-4f73-809e-362c72d9c6a7. Oct 6 07:17:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:17:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.astqbxuqmount_test with fs ext3 Oct 6 07:17:48 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:17:48 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 94d84daf-4495-47ce-8769-26b1e37711b1 r/w with ordered data mode. Quota mode: none. Oct 6 07:17:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.astqbxuqmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:17:54 storageqe-109 systemd[1]: tmp-libblockdev.astqbxuqmount_test.mount: Deactivated successfully. Oct 6 07:17:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 94d84daf-4495-47ce-8769-26b1e37711b1. Oct 6 07:17:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:17:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uq3kvmmomount_test with fs ext2 Oct 6 07:18:18 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:18:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ac9d4841-2dd3-452a-9ffc-e8b7328cd81c r/w without journal. Quota mode: none. Oct 6 07:18:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uq3kvmmomount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:18:24 storageqe-109 systemd[1]: tmp-libblockdev.uq3kvmmomount_test.mount: Deactivated successfully. Oct 6 07:18:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ac9d4841-2dd3-452a-9ffc-e8b7328cd81c. Oct 6 07:18:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:18:24 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:18:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:18:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:18:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:18:56 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:18:56 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:18:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:19:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:19:18 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:19:18 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:19:23 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:19:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:23 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:19:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:19:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:19:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:19:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:19:24 storageqe-109 stratisd[4947]: [2025-10-06T11:19:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:19:24 storageqe-109 stratisd[4947]: [2025-10-06T11:19:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:19:33 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:19:34 storageqe-109 stratisd[4947]: [2025-10-06T11:19:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:19:34 storageqe-109 stratisd[4947]: [2025-10-06T11:19:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:19:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:19:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.binwnt7cmount_test with fs xfs Oct 6 07:19:56 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem c3c1de61-f26c-4ed5-b4e4-d1b1d599cc17 Oct 6 07:19:56 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:19:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.binwnt7cmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:20:00 storageqe-109 systemd[1]: tmp-libblockdev.binwnt7cmount_test.mount: Deactivated successfully. Oct 6 07:20:00 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem c3c1de61-f26c-4ed5-b4e4-d1b1d599cc17 Oct 6 07:20:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:20:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fc2w2ik3mount_test with fs ext4 Oct 6 07:20:12 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f15c4f8b-9d06-48be-ae07-281e7f9aa741 r/w with ordered data mode. Quota mode: none. Oct 6 07:20:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fc2w2ik3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:20:17 storageqe-109 systemd[1]: tmp-libblockdev.fc2w2ik3mount_test.mount: Deactivated successfully. Oct 6 07:20:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f15c4f8b-9d06-48be-ae07-281e7f9aa741. Oct 6 07:20:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:20:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:20:39 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.ms2yat68mount_test with fs ext3 Oct 6 07:20:39 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c526adf2-5c91-47c6-88d3-c157efaa6a9b r/w with ordered data mode. Quota mode: none. Oct 6 07:20:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ms2yat68mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:20:44 storageqe-109 systemd[1]: tmp-libblockdev.ms2yat68mount_test.mount: Deactivated successfully. Oct 6 07:20:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c526adf2-5c91-47c6-88d3-c157efaa6a9b. Oct 6 07:20:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:20:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g25lk2i_mount_test with fs ext2 Oct 6 07:21:05 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:21:05 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a80dcba6-763e-4dd5-9cb2-775c196e08e8 r/w without journal. Quota mode: none. Oct 6 07:21:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g25lk2i_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:21:10 storageqe-109 systemd[1]: tmp-libblockdev.g25lk2i_mount_test.mount: Deactivated successfully. Oct 6 07:21:10 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a80dcba6-763e-4dd5-9cb2-775c196e08e8. Oct 6 07:21:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:21:10 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:21:11 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:21:21 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:21:32 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:21:43 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:21:43 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:21:43 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:21:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:22:04 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:22:04 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:22:34 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:23:32 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:23:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:32 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:23:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:23:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:23:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:23:33 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:23:33 storageqe-109 stratisd[4947]: [2025-10-06T11:23:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:23:33 storageqe-109 stratisd[4947]: [2025-10-06T11:23:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:23:43 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:24:13 storageqe-109 stratisd[4947]: [2025-10-06T11:24:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:24:13 storageqe-109 stratisd[4947]: [2025-10-06T11:24:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:24:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.tc_qmnbqmount_test with fs xfs Oct 6 07:24:34 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 2bb4478c-bfae-43f5-b957-eec639c04f81 Oct 6 07:24:34 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:24:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tc_qmnbqmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:24:40 storageqe-109 systemd[1]: tmp-libblockdev.tc_qmnbqmount_test.mount: Deactivated successfully. Oct 6 07:24:40 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 2bb4478c-bfae-43f5-b957-eec639c04f81 Oct 6 07:24:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:24:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.we_42scgmount_test with fs ext4 Oct 6 07:24:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem fafef0f0-12f6-43c3-9e39-cdc1acbd22e1 r/w with ordered data mode. Quota mode: none. Oct 6 07:24:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.we_42scgmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:24:58 storageqe-109 systemd[1]: tmp-libblockdev.we_42scgmount_test.mount: Deactivated successfully. Oct 6 07:24:58 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem fafef0f0-12f6-43c3-9e39-cdc1acbd22e1. Oct 6 07:24:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:24:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fpygcxq4mount_test with fs ext3 Oct 6 07:25:23 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:25:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f31829e4-7e3b-4666-af68-59da8d6dccb5 r/w with ordered data mode. Quota mode: none. Oct 6 07:25:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fpygcxq4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:25:29 storageqe-109 systemd[1]: tmp-libblockdev.fpygcxq4mount_test.mount: Deactivated successfully. Oct 6 07:25:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f31829e4-7e3b-4666-af68-59da8d6dccb5. Oct 6 07:25:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:25:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.85je7tkemount_test with fs ext2 Oct 6 07:25:53 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:25:53 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1e0bf183-fa4b-4180-8d84-83fba7d6de5e r/w without journal. Quota mode: none. Oct 6 07:25:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.85je7tkemount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:25:59 storageqe-109 systemd[1]: tmp-libblockdev.85je7tkemount_test.mount: Deactivated successfully. Oct 6 07:25:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1e0bf183-fa4b-4180-8d84-83fba7d6de5e. Oct 6 07:25:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:25:59 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:25:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:26:09 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:26:21 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:26:31 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:26:31 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:26:31 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:26:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:26:53 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:26:53 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:27:23 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:28:21 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:28:21 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:28:21 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:28:21 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:28:21 storageqe-109 stratisd[4947]: [2025-10-06T11:28:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:28:21 storageqe-109 stratisd[4947]: [2025-10-06T11:28:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:28:31 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:29:02 storageqe-109 stratisd[4947]: [2025-10-06T11:29:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:29:02 storageqe-109 stratisd[4947]: [2025-10-06T11:29:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:29:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.om23lh9lmount_test with fs xfs Oct 6 07:29:23 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 3192a610-afc2-4184-a778-9de35bd390e1 Oct 6 07:29:23 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:29:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.om23lh9lmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:29:28 storageqe-109 systemd[1]: tmp-libblockdev.om23lh9lmount_test.mount: Deactivated successfully. Oct 6 07:29:28 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 3192a610-afc2-4184-a778-9de35bd390e1 Oct 6 07:29:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:29:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.knsclz7bmount_test with fs ext4 Oct 6 07:29:39 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 361d1c03-f073-4a5d-b213-ae9d9712920e r/w with ordered data mode. Quota mode: none. Oct 6 07:29:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.knsclz7bmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:29:45 storageqe-109 systemd[1]: tmp-libblockdev.knsclz7bmount_test.mount: Deactivated successfully. Oct 6 07:29:45 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 361d1c03-f073-4a5d-b213-ae9d9712920e. Oct 6 07:29:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:29:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:30:07 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.tu7zu6t5mount_test with fs ext3 Oct 6 07:30:07 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d7fedf91-4d85-4072-8bb0-aacc894488dd r/w with ordered data mode. Quota mode: none. Oct 6 07:30:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tu7zu6t5mount_test with fs ext3 Oct 6 07:30:11 storageqe-109 systemd[1]: tmp-libblockdev.tu7zu6t5mount_test.mount: Deactivated successfully. Oct 6 07:30:11 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d7fedf91-4d85-4072-8bb0-aacc894488dd. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:30:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:30:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wgpyubknmount_test with fs ext2 Oct 6 07:30:33 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:30:33 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1b3458b7-f0d9-4a2e-933a-591218ab9d07 r/w without journal. Quota mode: none. Oct 6 07:30:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wgpyubknmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:30:38 storageqe-109 systemd[1]: tmp-libblockdev.wgpyubknmount_test.mount: Deactivated successfully. Oct 6 07:30:38 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1b3458b7-f0d9-4a2e-933a-591218ab9d07. Oct 6 07:30:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:30:38 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:30:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:30:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:31:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:31:10 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:31:10 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:31:10 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:31:22 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:31:32 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:31:32 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:32:02 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:33:00 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:33:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:00 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:33:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:33:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:33:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:33:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:33:01 storageqe-109 stratisd[4947]: [2025-10-06T11:33:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:33:01 storageqe-109 stratisd[4947]: [2025-10-06T11:33:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:33:11 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:33:42 storageqe-109 stratisd[4947]: [2025-10-06T11:33:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:33:42 storageqe-109 stratisd[4947]: [2025-10-06T11:33:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:33:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ckjcc0qjmount_test with fs xfs Oct 6 07:34:03 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 70c36d08-c580-47a5-a2a7-5f855335419c Oct 6 07:34:03 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:34:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ckjcc0qjmount_test with fs xfs Oct 6 07:34:09 storageqe-109 systemd[1]: tmp-libblockdev.ckjcc0qjmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:34:09 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 70c36d08-c580-47a5-a2a7-5f855335419c Oct 6 07:34:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:34:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4tg5hs24mount_test with fs ext4 Oct 6 07:34:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 49c6d3d4-535e-463b-bd6d-d4515445d904 r/w with ordered data mode. Quota mode: none. Oct 6 07:34:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4tg5hs24mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:34:26 storageqe-109 systemd[1]: tmp-libblockdev.4tg5hs24mount_test.mount: Deactivated successfully. Oct 6 07:34:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 49c6d3d4-535e-463b-bd6d-d4515445d904. Oct 6 07:34:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:34:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mnj0cnkfmount_test with fs ext3 Oct 6 07:34:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:34:52 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 669af0a8-ab11-40cd-a75d-1454edef532c r/w with ordered data mode. Quota mode: none. Oct 6 07:34:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mnj0cnkfmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:34:57 storageqe-109 systemd[1]: tmp-libblockdev.mnj0cnkfmount_test.mount: Deactivated successfully. Oct 6 07:34:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 669af0a8-ab11-40cd-a75d-1454edef532c. Oct 6 07:34:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:34:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lqw4yd1wmount_test with fs ext2 Oct 6 07:35:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:35:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 78e1e5bc-3cd4-43f1-b309-45084381b00f r/w without journal. Quota mode: none. Oct 6 07:35:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lqw4yd1wmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:35:28 storageqe-109 systemd[1]: tmp-libblockdev.lqw4yd1wmount_test.mount: Deactivated successfully. Oct 6 07:35:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 78e1e5bc-3cd4-43f1-b309-45084381b00f. Oct 6 07:35:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:35:28 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:35:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:35:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:35:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:36:00 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:36:00 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:36:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:36:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:36:22 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:36:22 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:36:52 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:37:50 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:37:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:37:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:37:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:37:51 storageqe-109 stratisd[4947]: [2025-10-06T11:37:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:37:51 storageqe-109 stratisd[4947]: [2025-10-06T11:37:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:38:00 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:38:31 storageqe-109 stratisd[4947]: [2025-10-06T11:38:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:38:31 storageqe-109 stratisd[4947]: [2025-10-06T11:38:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:38:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.60a572yrmount_test with fs xfs Oct 6 07:38:52 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem d4769462-f301-44d3-9572-68c86384084d Oct 6 07:38:52 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:38:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.60a572yrmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:38:57 storageqe-109 systemd[1]: tmp-libblockdev.60a572yrmount_test.mount: Deactivated successfully. Oct 6 07:38:57 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem d4769462-f301-44d3-9572-68c86384084d Oct 6 07:38:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:38:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1i3n0lvqmount_test with fs ext4 Oct 6 07:39:09 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 98a2b79a-1158-43c5-8350-3f7f23dd82db r/w with ordered data mode. Quota mode: none. Oct 6 07:39:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1i3n0lvqmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:39:14 storageqe-109 systemd[1]: tmp-libblockdev.1i3n0lvqmount_test.mount: Deactivated successfully. Oct 6 07:39:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 98a2b79a-1158-43c5-8350-3f7f23dd82db. Oct 6 07:39:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:39:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.yu3ohp5zmount_test with fs ext3 Oct 6 07:39:36 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:39:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 780b943c-aba8-4057-b7b7-a8ee48eba263 r/w with ordered data mode. Quota mode: none. Oct 6 07:39:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yu3ohp5zmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:39:41 storageqe-109 systemd[1]: tmp-libblockdev.yu3ohp5zmount_test.mount: Deactivated successfully. Oct 6 07:39:41 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 780b943c-aba8-4057-b7b7-a8ee48eba263. Oct 6 07:39:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:39:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zf4jf45lmount_test with fs ext2 Oct 6 07:40:03 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:40:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8d94b211-b8ad-4185-ba5c-5fe5680d004f r/w without journal. Quota mode: none. Oct 6 07:40:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zf4jf45lmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:40:08 storageqe-109 systemd[1]: tmp-libblockdev.zf4jf45lmount_test.mount: Deactivated successfully. Oct 6 07:40:08 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8d94b211-b8ad-4185-ba5c-5fe5680d004f. Oct 6 07:40:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:40:08 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:40:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:40:18 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:40:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:40:40 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:40:40 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:40:40 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:40:52 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:41:02 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:41:02 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:41:07 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:41:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:41:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:41:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:41:07 storageqe-109 stratisd[4947]: [2025-10-06T11:41:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:41:07 storageqe-109 stratisd[4947]: [2025-10-06T11:41:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:41:17 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:41:18 storageqe-109 stratisd[4947]: [2025-10-06T11:41:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:41:18 storageqe-109 stratisd[4947]: [2025-10-06T11:41:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:41:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:41:32 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.ryb2rlbomount_test with fs xfs Oct 6 07:41:41 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f1b5b8b9-8f66-4b62-ab8f-6d041af717b7 Oct 6 07:41:41 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:41:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ryb2rlbomount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:41:47 storageqe-109 systemd[1]: tmp-libblockdev.ryb2rlbomount_test.mount: Deactivated successfully. Oct 6 07:41:47 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f1b5b8b9-8f66-4b62-ab8f-6d041af717b7 Oct 6 07:41:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:41:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dtneeinwmount_test with fs ext4 Oct 6 07:42:00 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e9cfa017-307d-4545-8ba0-746e19eefc02 r/w with ordered data mode. Quota mode: none. Oct 6 07:42:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dtneeinwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:42:07 storageqe-109 systemd[1]: tmp-libblockdev.dtneeinwmount_test.mount: Deactivated successfully. Oct 6 07:42:07 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e9cfa017-307d-4545-8ba0-746e19eefc02. Oct 6 07:42:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:42:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r18954p9mount_test with fs ext3 Oct 6 07:43:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:43:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 62cb8468-73aa-4fae-9cf7-e6f4c58da1e2 r/w with ordered data mode. Quota mode: none. Oct 6 07:43:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r18954p9mount_test with fs ext3 Oct 6 07:43:18 storageqe-109 systemd[1]: tmp-libblockdev.r18954p9mount_test.mount: Deactivated successfully. Oct 6 07:43:18 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 62cb8468-73aa-4fae-9cf7-e6f4c58da1e2. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:43:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:43:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fnjzj4s8mount_test with fs ext2 Oct 6 07:44:20 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:44:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6b1f10ef-2674-46bd-889a-18e51a0c9d53 r/w without journal. Quota mode: none. Oct 6 07:44:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fnjzj4s8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:44:26 storageqe-109 systemd[1]: tmp-libblockdev.fnjzj4s8mount_test.mount: Deactivated successfully. Oct 6 07:44:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6b1f10ef-2674-46bd-889a-18e51a0c9d53. Oct 6 07:44:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:44:26 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:44:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:44:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:44:49 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:44:59 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:44:59 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:44:59 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:45:11 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:45:21 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:45:21 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:45:26 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:45:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:45:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:45:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:45:26 storageqe-109 stratisd[4947]: [2025-10-06T11:45:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:45:26 storageqe-109 stratisd[4947]: [2025-10-06T11:45:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:45:36 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:45:37 storageqe-109 stratisd[4947]: [2025-10-06T11:45:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:45:37 storageqe-109 stratisd[4947]: [2025-10-06T11:45:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:45:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:45:51 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:45:58 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem abfcf5b9-ff50-419b-8e7b-eba495cd970a Oct 6 07:45:58 storageqe-109 kernel: XFS (dm-3): Ending clean mount INFO: will run io in dir /tmp/libblockdev.y6w4etwimount_test with fs xfs Oct 6 07:45:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y6w4etwimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:46:03 storageqe-109 systemd[1]: tmp-libblockdev.y6w4etwimount_test.mount: Deactivated successfully. Oct 6 07:46:03 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem abfcf5b9-ff50-419b-8e7b-eba495cd970a Oct 6 07:46:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:46:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vt4d7ll6mount_test with fs ext4 Oct 6 07:46:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6b200f4d-860f-40df-9f69-cb30a78755e1 r/w with ordered data mode. Quota mode: none. Oct 6 07:46:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vt4d7ll6mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:46:19 storageqe-109 systemd[1]: tmp-libblockdev.vt4d7ll6mount_test.mount: Deactivated successfully. Oct 6 07:46:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6b200f4d-860f-40df-9f69-cb30a78755e1. Oct 6 07:46:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:46:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7en0g89emount_test with fs ext3 Oct 6 07:46:41 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:46:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 18755525-893a-4c68-9b12-65406dac3834 r/w with ordered data mode. Quota mode: none. Oct 6 07:46:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7en0g89emount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:46:46 storageqe-109 systemd[1]: tmp-libblockdev.7en0g89emount_test.mount: Deactivated successfully. Oct 6 07:46:46 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 18755525-893a-4c68-9b12-65406dac3834. Oct 6 07:46:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:46:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.20f0df37mount_test with fs ext2 Oct 6 07:47:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:47:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ed755097-6d85-4c7c-9dfd-9e8394f0047a r/w without journal. Quota mode: none. Oct 6 07:47:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.20f0df37mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:47:12 storageqe-109 systemd[1]: tmp-libblockdev.20f0df37mount_test.mount: Deactivated successfully. Oct 6 07:47:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ed755097-6d85-4c7c-9dfd-9e8394f0047a. Oct 6 07:47:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:47:12 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:47:13 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:47:23 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:47:35 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:47:45 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:47:45 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:47:45 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:47:57 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:48:07 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:48:07 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:48:12 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:48:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:48:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:48:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:48:12 storageqe-109 stratisd[4947]: [2025-10-06T11:48:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:48:12 storageqe-109 stratisd[4947]: [2025-10-06T11:48:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:48:22 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:48:23 storageqe-109 stratisd[4947]: [2025-10-06T11:48:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:48:23 storageqe-109 stratisd[4947]: [2025-10-06T11:48:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:48:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:48:37 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.01s7vj_2mount_test with fs xfs Oct 6 07:48:46 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 5014d128-ff01-4779-940f-3db93c28d6a5 Oct 6 07:48:46 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:48:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.01s7vj_2mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:48:52 storageqe-109 systemd[1]: tmp-libblockdev.01s7vj_2mount_test.mount: Deactivated successfully. Oct 6 07:48:52 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 5014d128-ff01-4779-940f-3db93c28d6a5 Oct 6 07:48:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:48:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m82ft7h6mount_test with fs ext4 Oct 6 07:49:05 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7be98f28-dc86-49e2-bf7d-d018e18f1cfc r/w with ordered data mode. Quota mode: none. Oct 6 07:49:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m82ft7h6mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:49:12 storageqe-109 systemd[1]: tmp-libblockdev.m82ft7h6mount_test.mount: Deactivated successfully. Oct 6 07:49:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7be98f28-dc86-49e2-bf7d-d018e18f1cfc. Oct 6 07:49:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:49:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7xsgbs62mount_test with fs ext3 Oct 6 07:50:17 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:50:17 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8b2190fb-47fc-4a31-8f1f-e3249ae7522e r/w with ordered data mode. Quota mode: none. Oct 6 07:50:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7xsgbs62mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:50:23 storageqe-109 systemd[1]: tmp-libblockdev.7xsgbs62mount_test.mount: Deactivated successfully. Oct 6 07:50:23 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8b2190fb-47fc-4a31-8f1f-e3249ae7522e. Oct 6 07:50:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:50:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:50:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 07:50:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 07:50:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: will run io in dir /tmp/libblockdev.bm4w07swmount_test with fs ext2 Oct 6 07:51:25 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:51:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d1c08565-6325-4d62-b74a-1d2ccaa6af62 r/w without journal. Quota mode: none. Oct 6 07:51:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bm4w07swmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:51:32 storageqe-109 systemd[1]: tmp-libblockdev.bm4w07swmount_test.mount: Deactivated successfully. Oct 6 07:51:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d1c08565-6325-4d62-b74a-1d2ccaa6af62. Oct 6 07:51:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:51:32 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:51:32 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:51:43 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:51:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:52:04 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:52:04 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:52:04 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:52:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:52:26 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:52:26 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 07:52:31 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:52:31 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:31 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:52:31 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:52:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:52:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:52:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:52:32 storageqe-109 stratisd[4947]: [2025-10-06T11:52:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:52:32 storageqe-109 stratisd[4947]: [2025-10-06T11:52:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:52:42 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:52:43 storageqe-109 stratisd[4947]: [2025-10-06T11:52:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:52:43 storageqe-109 stratisd[4947]: [2025-10-06T11:52:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:52:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:52:56 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.1y5nfw3smount_test with fs xfs Oct 6 07:53:04 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 9d7bbe11-64df-437b-9ff9-3fae256441bd Oct 6 07:53:04 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:53:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1y5nfw3smount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:53:09 storageqe-109 systemd[1]: tmp-libblockdev.1y5nfw3smount_test.mount: Deactivated successfully. Oct 6 07:53:09 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 9d7bbe11-64df-437b-9ff9-3fae256441bd Oct 6 07:53:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:53:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1g2bdnw9mount_test with fs ext4 Oct 6 07:53:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7b96a578-410f-428f-af0d-1a22ee55fcc6 r/w with ordered data mode. Quota mode: none. Oct 6 07:53:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1g2bdnw9mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:53:26 storageqe-109 systemd[1]: tmp-libblockdev.1g2bdnw9mount_test.mount: Deactivated successfully. Oct 6 07:53:26 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 07:53:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7b96a578-410f-428f-af0d-1a22ee55fcc6. Oct 6 07:53:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:53:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:53:26 storageqe-109 dnf[785751]: Updating Subscription Management repositories. Oct 6 07:53:26 storageqe-109 dnf[785751]: Unable to read consumer identity Oct 6 07:53:26 storageqe-109 dnf[785751]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 07:53:26 storageqe-109 dnf[785751]: Metadata cache refreshed recently. Oct 6 07:53:26 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 07:53:26 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. INFO: will run io in dir /tmp/libblockdev.at1qsw8smount_test with fs ext3 Oct 6 07:53:48 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:53:48 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 964caa5b-c560-45eb-8760-c461934c1315 r/w with ordered data mode. Quota mode: none. Oct 6 07:53:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.at1qsw8smount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:53:53 storageqe-109 systemd[1]: tmp-libblockdev.at1qsw8smount_test.mount: Deactivated successfully. Oct 6 07:53:53 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 964caa5b-c560-45eb-8760-c461934c1315. Oct 6 07:53:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:53:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hpxl35hcmount_test with fs ext2 Oct 6 07:54:15 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 07:54:15 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 660430fc-c05a-448e-977c-8eb52e734225 r/w without journal. Quota mode: none. Oct 6 07:54:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hpxl35hcmount_test with fs ext2 Oct 6 07:54:19 storageqe-109 systemd[1]: tmp-libblockdev.hpxl35hcmount_test.mount: Deactivated successfully. Oct 6 07:54:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 660430fc-c05a-448e-977c-8eb52e734225. INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 07:54:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:54:20 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:54:20 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 07:54:30 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:54:42 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 07:54:52 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 07:54:52 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 07:54:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 07:55:04 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:55:14 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 07:55:14 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 07:55:44 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 07:56:42 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 07:56:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 07:56:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 07:56:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 07:56:43 storageqe-109 stratisd[4947]: [2025-10-06T11:56:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:56:43 storageqe-109 stratisd[4947]: [2025-10-06T11:56:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:56:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 07:57:23 storageqe-109 stratisd[4947]: [2025-10-06T11:57:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 07:57:23 storageqe-109 stratisd[4947]: [2025-10-06T11:57:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:57:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.tf2lyclhmount_test with fs xfs Oct 6 07:57:46 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 90eb5168-0e43-44b7-8649-b06b5292200f Oct 6 07:57:46 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 07:57:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tf2lyclhmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:57:52 storageqe-109 systemd[1]: tmp-libblockdev.tf2lyclhmount_test.mount: Deactivated successfully. Oct 6 07:57:52 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 90eb5168-0e43-44b7-8649-b06b5292200f Oct 6 07:57:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 07:57:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p8itqp8hmount_test with fs ext4 Oct 6 07:58:05 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem eb1bf41e-d2f8-4484-bd73-e06f60bf23b6 r/w with ordered data mode. Quota mode: none. Oct 6 07:58:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p8itqp8hmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:58:12 storageqe-109 systemd[1]: tmp-libblockdev.p8itqp8hmount_test.mount: Deactivated successfully. Oct 6 07:58:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem eb1bf41e-d2f8-4484-bd73-e06f60bf23b6. Oct 6 07:58:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 07:58:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:59:16 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 07:59:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 049ea990-ab9a-40c6-b3f0-ba5550b2b1cc r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.lmz0l4ywmount_test with fs ext3 Oct 6 07:59:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lmz0l4ywmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 07:59:23 storageqe-109 systemd[1]: tmp-libblockdev.lmz0l4ywmount_test.mount: Deactivated successfully. Oct 6 07:59:23 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 049ea990-ab9a-40c6-b3f0-ba5550b2b1cc. Oct 6 07:59:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 07:59:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bba71dgymount_test with fs ext2 Oct 6 08:00:25 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:00:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 41e2444f-69c5-4f78-9769-0e3984809f93 r/w without journal. Quota mode: none. Oct 6 08:00:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bba71dgymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:00:32 storageqe-109 systemd[1]: tmp-libblockdev.bba71dgymount_test.mount: Deactivated successfully. Oct 6 08:00:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 41e2444f-69c5-4f78-9769-0e3984809f93. Oct 6 08:00:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:00:32 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:00:32 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:00:42 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:00:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:01:04 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:01:04 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:01:04 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:01:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:01:26 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:01:26 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:01:56 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 08:02:54 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:02:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:02:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:02:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:02:55 storageqe-109 stratisd[4947]: [2025-10-06T12:02:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:02:55 storageqe-109 stratisd[4947]: [2025-10-06T12:02:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:03:04 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:03:35 storageqe-109 stratisd[4947]: [2025-10-06T12:03:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:03:35 storageqe-109 stratisd[4947]: [2025-10-06T12:03:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:03:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.41mgjjv_mount_test with fs xfs Oct 6 08:03:56 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 77ad8503-6f30-4757-834d-3a628189e471 Oct 6 08:03:56 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:03:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.41mgjjv_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:04:01 storageqe-109 systemd[1]: tmp-libblockdev.41mgjjv_mount_test.mount: Deactivated successfully. Oct 6 08:04:01 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 77ad8503-6f30-4757-834d-3a628189e471 Oct 6 08:04:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:04:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lulonzplmount_test with fs ext4 Oct 6 08:04:12 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 68ad7a71-252e-4feb-96c3-4c5689443b7d r/w with ordered data mode. Quota mode: none. Oct 6 08:04:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lulonzplmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:04:18 storageqe-109 systemd[1]: tmp-libblockdev.lulonzplmount_test.mount: Deactivated successfully. Oct 6 08:04:18 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 68ad7a71-252e-4feb-96c3-4c5689443b7d. Oct 6 08:04:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:04:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p2izad6ymount_test with fs ext3 Oct 6 08:04:40 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:04:40 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b8e90d40-77ae-417d-bcd5-4c2581adfccb r/w with ordered data mode. Quota mode: none. Oct 6 08:04:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p2izad6ymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:04:44 storageqe-109 systemd[1]: tmp-libblockdev.p2izad6ymount_test.mount: Deactivated successfully. Oct 6 08:04:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b8e90d40-77ae-417d-bcd5-4c2581adfccb. Oct 6 08:04:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:04:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.56zofmacmount_test with fs ext2 Oct 6 08:05:06 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:05:06 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e42ceb0d-59f7-4906-9697-766914e1d057 r/w without journal. Quota mode: none. Oct 6 08:05:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.56zofmacmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:05:11 storageqe-109 systemd[1]: tmp-libblockdev.56zofmacmount_test.mount: Deactivated successfully. Oct 6 08:05:11 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e42ceb0d-59f7-4906-9697-766914e1d057. Oct 6 08:05:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:05:11 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:05:11 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:05:21 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:05:33 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:05:43 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:05:43 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:05:43 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:05:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:06:05 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:06:05 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:06:35 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 08:07:33 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:07:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:33 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:07:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:07:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:07:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:07:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:07:34 storageqe-109 stratisd[4947]: [2025-10-06T12:07:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:07:34 storageqe-109 stratisd[4947]: [2025-10-06T12:07:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:07:44 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:08:15 storageqe-109 stratisd[4947]: [2025-10-06T12:08:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:08:15 storageqe-109 stratisd[4947]: [2025-10-06T12:08:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:08:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8vv8_susmount_test with fs xfs Oct 6 08:08:37 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem fd2489cf-1c95-4f8c-a375-03ab53944fe1 Oct 6 08:08:37 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:08:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8vv8_susmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:08:43 storageqe-109 systemd[1]: tmp-libblockdev.8vv8_susmount_test.mount: Deactivated successfully. Oct 6 08:08:43 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem fd2489cf-1c95-4f8c-a375-03ab53944fe1 Oct 6 08:08:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:08:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.a84o4k2emount_test with fs ext4 Oct 6 08:08:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem eced4265-5ca8-49f9-a9c7-4110d00b82eb r/w with ordered data mode. Quota mode: none. Oct 6 08:08:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a84o4k2emount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:09:04 storageqe-109 systemd[1]: tmp-libblockdev.a84o4k2emount_test.mount: Deactivated successfully. Oct 6 08:09:04 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem eced4265-5ca8-49f9-a9c7-4110d00b82eb. Oct 6 08:09:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:09:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.592f1x74mount_test with fs ext3 Oct 6 08:10:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:10:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 581510f5-6ab3-4d7f-8483-0155c905c5f4 r/w with ordered data mode. Quota mode: none. Oct 6 08:10:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.592f1x74mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:10:15 storageqe-109 systemd[1]: tmp-libblockdev.592f1x74mount_test.mount: Deactivated successfully. Oct 6 08:10:15 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 581510f5-6ab3-4d7f-8483-0155c905c5f4. Oct 6 08:10:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:10:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.391wc3mtmount_test with fs ext2 Oct 6 08:11:17 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:11:17 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem eafa72ed-7702-49de-9ca4-39f59e94c36e r/w without journal. Quota mode: none. Oct 6 08:11:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.391wc3mtmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:11:23 storageqe-109 systemd[1]: tmp-libblockdev.391wc3mtmount_test.mount: Deactivated successfully. Oct 6 08:11:23 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem eafa72ed-7702-49de-9ca4-39f59e94c36e. Oct 6 08:11:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:11:23 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:11:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:11:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:11:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:11:56 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:11:56 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:11:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:12:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:12:18 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:12:18 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:12:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 08:13:45 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:13:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:45 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:13:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:13:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:13:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:13:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:13:46 storageqe-109 stratisd[4947]: [2025-10-06T12:13:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:13:46 storageqe-109 stratisd[4947]: [2025-10-06T12:13:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:13:56 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:14:26 storageqe-109 stratisd[4947]: [2025-10-06T12:14:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:14:26 storageqe-109 stratisd[4947]: [2025-10-06T12:14:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:14:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._j_t7z1lmount_test with fs xfs Oct 6 08:14:47 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 11a600fb-c4ed-4364-90e6-696e0b3d5976 Oct 6 08:14:47 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:14:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev._j_t7z1lmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:14:52 storageqe-109 systemd[1]: tmp-libblockdev._j_t7z1lmount_test.mount: Deactivated successfully. Oct 6 08:14:52 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 11a600fb-c4ed-4364-90e6-696e0b3d5976 Oct 6 08:14:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:14:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lenzmy5vmount_test with fs ext4 Oct 6 08:15:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 33805fc2-28e3-43c9-9677-15c261ccabcb r/w with ordered data mode. Quota mode: none. Oct 6 08:15:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lenzmy5vmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:15:08 storageqe-109 systemd[1]: tmp-libblockdev.lenzmy5vmount_test.mount: Deactivated successfully. Oct 6 08:15:08 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 33805fc2-28e3-43c9-9677-15c261ccabcb. Oct 6 08:15:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:15:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.602ib80jmount_test with fs ext3 Oct 6 08:15:30 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:15:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e3570222-c91b-4c19-9e66-92f62687c212 r/w with ordered data mode. Quota mode: none. Oct 6 08:15:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.602ib80jmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:15:35 storageqe-109 systemd[1]: tmp-libblockdev.602ib80jmount_test.mount: Deactivated successfully. Oct 6 08:15:35 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e3570222-c91b-4c19-9e66-92f62687c212. Oct 6 08:15:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:15:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1cdcwc22mount_test with fs ext2 Oct 6 08:15:57 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:15:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 983ebe4d-c67a-441f-8c8e-1602b17c06f5 r/w without journal. Quota mode: none. Oct 6 08:15:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1cdcwc22mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:16:02 storageqe-109 systemd[1]: tmp-libblockdev.1cdcwc22mount_test.mount: Deactivated successfully. Oct 6 08:16:02 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 983ebe4d-c67a-441f-8c8e-1602b17c06f5. Oct 6 08:16:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:16:02 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:16:02 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:16:12 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:16:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:16:34 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:16:34 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:16:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:16:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:16:56 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:16:56 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:17:01 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:17:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:17:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:17:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:17:01 storageqe-109 stratisd[4947]: [2025-10-06T12:17:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:17:01 storageqe-109 stratisd[4947]: [2025-10-06T12:17:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:17:11 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:17:12 storageqe-109 stratisd[4947]: [2025-10-06T12:17:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:17:12 storageqe-109 stratisd[4947]: [2025-10-06T12:17:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:17:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:17:26 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.49ycrtgbmount_test with fs xfs Oct 6 08:17:33 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 0cea0ecb-a30f-4064-a1a7-067f25379c4b Oct 6 08:17:33 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:17:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.49ycrtgbmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:17:39 storageqe-109 systemd[1]: tmp-libblockdev.49ycrtgbmount_test.mount: Deactivated successfully. Oct 6 08:17:39 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 0cea0ecb-a30f-4064-a1a7-067f25379c4b Oct 6 08:17:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:17:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.aeus2x2kmount_test with fs ext4 Oct 6 08:17:50 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0f87415f-26e6-430e-90cd-6046e300a5f3 r/w with ordered data mode. Quota mode: none. Oct 6 08:17:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.aeus2x2kmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:17:56 storageqe-109 systemd[1]: tmp-libblockdev.aeus2x2kmount_test.mount: Deactivated successfully. Oct 6 08:17:56 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0f87415f-26e6-430e-90cd-6046e300a5f3. Oct 6 08:17:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:17:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1ir6ks22mount_test with fs ext3 Oct 6 08:18:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:18:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 87f94126-86e8-492e-a0a7-c89e1876868a r/w with ordered data mode. Quota mode: none. Oct 6 08:18:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1ir6ks22mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:18:28 storageqe-109 systemd[1]: tmp-libblockdev.1ir6ks22mount_test.mount: Deactivated successfully. Oct 6 08:18:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 87f94126-86e8-492e-a0a7-c89e1876868a. Oct 6 08:18:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:18:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rq8d9i3rmount_test with fs ext2 Oct 6 08:18:53 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:18:53 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9bf21d11-34c1-4025-b5c8-aad59b1d6599 r/w without journal. Quota mode: none. Oct 6 08:18:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rq8d9i3rmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:18:59 storageqe-109 systemd[1]: tmp-libblockdev.rq8d9i3rmount_test.mount: Deactivated successfully. Oct 6 08:18:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9bf21d11-34c1-4025-b5c8-aad59b1d6599. Oct 6 08:18:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:18:59 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:18:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:19:10 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:19:21 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:19:31 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:19:31 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:19:31 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:19:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:19:53 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:19:53 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:19:58 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:58 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:19:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:19:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:19:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:19:59 storageqe-109 stratisd[4947]: [2025-10-06T12:19:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:19:59 storageqe-109 stratisd[4947]: [2025-10-06T12:19:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:20:09 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:20:09 storageqe-109 stratisd[4947]: [2025-10-06T12:20:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:20:09 storageqe-109 stratisd[4947]: [2025-10-06T12:20:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:20:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:20:23 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.x2z1dl0nmount_test with fs xfs Oct 6 08:20:31 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f0aa7f46-77e5-4adb-8816-9f43b8c9caa6 Oct 6 08:20:31 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:20:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x2z1dl0nmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:20:35 storageqe-109 systemd[1]: tmp-libblockdev.x2z1dl0nmount_test.mount: Deactivated successfully. Oct 6 08:20:35 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f0aa7f46-77e5-4adb-8816-9f43b8c9caa6 Oct 6 08:20:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:20:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g4015fdvmount_test with fs ext4 Oct 6 08:20:47 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 51e21738-77de-482a-8d4e-f27b6aaf0ce9 r/w with ordered data mode. Quota mode: none. Oct 6 08:20:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g4015fdvmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:20:52 storageqe-109 systemd[1]: tmp-libblockdev.g4015fdvmount_test.mount: Deactivated successfully. Oct 6 08:20:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 51e21738-77de-482a-8d4e-f27b6aaf0ce9. Oct 6 08:20:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:20:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i7tbkvq8mount_test with fs ext3 Oct 6 08:21:14 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:21:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e243972d-85cb-43bc-bdec-521473fec804 r/w with ordered data mode. Quota mode: none. Oct 6 08:21:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i7tbkvq8mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:21:19 storageqe-109 systemd[1]: tmp-libblockdev.i7tbkvq8mount_test.mount: Deactivated successfully. Oct 6 08:21:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e243972d-85cb-43bc-bdec-521473fec804. Oct 6 08:21:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:21:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.oz0i6ixxmount_test with fs ext2 Oct 6 08:21:40 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:21:40 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ae6d2903-aea6-4e30-907d-71df0f11a910 r/w without journal. Quota mode: none. Oct 6 08:21:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.oz0i6ixxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:21:45 storageqe-109 systemd[1]: tmp-libblockdev.oz0i6ixxmount_test.mount: Deactivated successfully. Oct 6 08:21:45 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ae6d2903-aea6-4e30-907d-71df0f11a910. Oct 6 08:21:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:21:45 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:21:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:21:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:22:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:22:17 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:22:18 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:22:18 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:22:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:22:39 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:22:39 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:22:45 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:22:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:22:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:22:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:22:45 storageqe-109 stratisd[4947]: [2025-10-06T12:22:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:22:45 storageqe-109 stratisd[4947]: [2025-10-06T12:22:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:22:55 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:22:56 storageqe-109 stratisd[4947]: [2025-10-06T12:22:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:22:56 storageqe-109 stratisd[4947]: [2025-10-06T12:22:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:23:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:23:09 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.mp1tyu0omount_test with fs xfs Oct 6 08:23:17 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 685a74c9-f6b0-4758-a2f4-7dbe4e75bfda Oct 6 08:23:17 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:23:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mp1tyu0omount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:23:23 storageqe-109 systemd[1]: tmp-libblockdev.mp1tyu0omount_test.mount: Deactivated successfully. Oct 6 08:23:23 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 685a74c9-f6b0-4758-a2f4-7dbe4e75bfda Oct 6 08:23:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:23:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5wzgrdgvmount_test with fs ext4 Oct 6 08:23:34 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8e24dec9-02aa-410a-b9b9-bd700f61e6c3 r/w with ordered data mode. Quota mode: none. Oct 6 08:23:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5wzgrdgvmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:23:40 storageqe-109 systemd[1]: tmp-libblockdev.5wzgrdgvmount_test.mount: Deactivated successfully. Oct 6 08:23:40 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8e24dec9-02aa-410a-b9b9-bd700f61e6c3. Oct 6 08:23:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:23:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._nhdrap1mount_test with fs ext3 Oct 6 08:24:06 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:24:06 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3c82c8bf-004a-456a-af9e-95d958c31ee8 r/w with ordered data mode. Quota mode: none. Oct 6 08:24:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev._nhdrap1mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:24:12 storageqe-109 systemd[1]: tmp-libblockdev._nhdrap1mount_test.mount: Deactivated successfully. Oct 6 08:24:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3c82c8bf-004a-456a-af9e-95d958c31ee8. Oct 6 08:24:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:24:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.b7rd7m24mount_test with fs ext2 Oct 6 08:24:37 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:24:37 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1294c062-20b1-43bc-ac3f-1c6b40dda18d r/w without journal. Quota mode: none. Oct 6 08:24:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b7rd7m24mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:24:43 storageqe-109 systemd[1]: tmp-libblockdev.b7rd7m24mount_test.mount: Deactivated successfully. Oct 6 08:24:43 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1294c062-20b1-43bc-ac3f-1c6b40dda18d. Oct 6 08:24:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:24:43 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:24:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:24:53 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:25:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:25:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:25:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:25:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:25:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:25:37 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:25:37 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:25:42 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:25:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:42 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:25:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:25:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:25:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:25:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:25:43 storageqe-109 stratisd[4947]: [2025-10-06T12:25:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:25:43 storageqe-109 stratisd[4947]: [2025-10-06T12:25:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:25:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:25:53 storageqe-109 stratisd[4947]: [2025-10-06T12:25:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:25:53 storageqe-109 stratisd[4947]: [2025-10-06T12:25:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:26:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:26:07 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.1hi9ccromount_test with fs xfs Oct 6 08:26:15 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem dcd59575-78a4-4594-89a8-116be9c7569d Oct 6 08:26:15 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:26:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1hi9ccromount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:26:19 storageqe-109 systemd[1]: tmp-libblockdev.1hi9ccromount_test.mount: Deactivated successfully. Oct 6 08:26:19 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem dcd59575-78a4-4594-89a8-116be9c7569d Oct 6 08:26:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:26:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9jgsviromount_test with fs ext4 Oct 6 08:26:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5ec63952-98ed-4e14-b546-e579c9df367d r/w with ordered data mode. Quota mode: none. Oct 6 08:26:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9jgsviromount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:26:36 storageqe-109 systemd[1]: tmp-libblockdev.9jgsviromount_test.mount: Deactivated successfully. Oct 6 08:26:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5ec63952-98ed-4e14-b546-e579c9df367d. Oct 6 08:26:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:26:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.a0oat1c4mount_test with fs ext3 Oct 6 08:26:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:26:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c2621d6b-4b24-4734-a7e4-53e325f6cc39 r/w with ordered data mode. Quota mode: none. Oct 6 08:26:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a0oat1c4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:27:03 storageqe-109 systemd[1]: tmp-libblockdev.a0oat1c4mount_test.mount: Deactivated successfully. Oct 6 08:27:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c2621d6b-4b24-4734-a7e4-53e325f6cc39. Oct 6 08:27:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:27:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xxav4d37mount_test with fs ext2 Oct 6 08:27:25 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:27:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 603021f8-74d0-467c-9984-a113e3395419 r/w without journal. Quota mode: none. Oct 6 08:27:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xxav4d37mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:27:30 storageqe-109 systemd[1]: tmp-libblockdev.xxav4d37mount_test.mount: Deactivated successfully. Oct 6 08:27:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 603021f8-74d0-467c-9984-a113e3395419. Oct 6 08:27:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:27:30 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:27:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:27:40 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:27:52 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:28:02 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:28:02 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:28:02 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:28:14 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:28:24 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:28:24 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:28:54 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 08:29:52 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:29:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:29:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:29:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:29:52 storageqe-109 stratisd[4947]: [2025-10-06T12:29:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:29:52 storageqe-109 stratisd[4947]: [2025-10-06T12:29:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:30:02 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:30:32 storageqe-109 stratisd[4947]: [2025-10-06T12:30:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:30:32 storageqe-109 stratisd[4947]: [2025-10-06T12:30:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:30:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.p8ybyclkmount_test with fs xfs Oct 6 08:30:54 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 18416660-cb3a-4ece-bf86-5392bb752285 Oct 6 08:30:54 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:30:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p8ybyclkmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:30:59 storageqe-109 systemd[1]: tmp-libblockdev.p8ybyclkmount_test.mount: Deactivated successfully. Oct 6 08:30:59 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 18416660-cb3a-4ece-bf86-5392bb752285 Oct 6 08:30:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:30:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.if9uaemsmount_test with fs ext4 Oct 6 08:31:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ec147dda-476b-4efe-817c-473a327343fa r/w with ordered data mode. Quota mode: none. Oct 6 08:31:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.if9uaemsmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:31:17 storageqe-109 systemd[1]: tmp-libblockdev.if9uaemsmount_test.mount: Deactivated successfully. Oct 6 08:31:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ec147dda-476b-4efe-817c-473a327343fa. Oct 6 08:31:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:31:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.diht3jczmount_test with fs ext3 Oct 6 08:31:43 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:31:43 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e71e8f10-f94f-4ae9-a481-9764336cb3fc r/w with ordered data mode. Quota mode: none. Oct 6 08:31:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.diht3jczmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:31:49 storageqe-109 systemd[1]: tmp-libblockdev.diht3jczmount_test.mount: Deactivated successfully. Oct 6 08:31:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e71e8f10-f94f-4ae9-a481-9764336cb3fc. Oct 6 08:31:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:31:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cms6l26kmount_test with fs ext2 Oct 6 08:32:14 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:32:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4ba93639-8785-4025-8306-a9c83087cf61 r/w without journal. Quota mode: none. Oct 6 08:32:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cms6l26kmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:32:20 storageqe-109 systemd[1]: tmp-libblockdev.cms6l26kmount_test.mount: Deactivated successfully. Oct 6 08:32:20 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4ba93639-8785-4025-8306-a9c83087cf61. Oct 6 08:32:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:32:20 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:32:20 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:32:30 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:32:42 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:32:52 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:32:52 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:32:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:33:04 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:33:14 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:33:14 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:33:44 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 08:34:42 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:34:42 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:34:42 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:34:42 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627558, async page read Oct 6 08:34:42 storageqe-109 stratisd[4947]: [2025-10-06T12:34:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:34:42 storageqe-109 stratisd[4947]: [2025-10-06T12:34:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:34:52 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:35:23 storageqe-109 stratisd[4947]: [2025-10-06T12:35:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:35:23 storageqe-109 stratisd[4947]: [2025-10-06T12:35:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:35:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:35:44 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem fd257f92-f0f1-427c-b422-b4084579655e INFO: will run io in dir /tmp/libblockdev.8_lf0wgkmount_test with fs xfs Oct 6 08:35:44 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:35:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8_lf0wgkmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:35:49 storageqe-109 systemd[1]: tmp-libblockdev.8_lf0wgkmount_test.mount: Deactivated successfully. Oct 6 08:35:49 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem fd257f92-f0f1-427c-b422-b4084579655e Oct 6 08:35:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:35:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4e5a15u3mount_test with fs ext4 Oct 6 08:36:00 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5d251268-818e-4780-93ae-7cd89243527f r/w with ordered data mode. Quota mode: none. Oct 6 08:36:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4e5a15u3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:36:06 storageqe-109 systemd[1]: tmp-libblockdev.4e5a15u3mount_test.mount: Deactivated successfully. Oct 6 08:36:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5d251268-818e-4780-93ae-7cd89243527f. Oct 6 08:36:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:36:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jit7q9dmmount_test with fs ext3 Oct 6 08:36:28 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:36:28 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 656863f4-a101-4a22-8fe3-508be98a7a9b r/w with ordered data mode. Quota mode: none. Oct 6 08:36:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jit7q9dmmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:36:33 storageqe-109 systemd[1]: tmp-libblockdev.jit7q9dmmount_test.mount: Deactivated successfully. Oct 6 08:36:33 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 656863f4-a101-4a22-8fe3-508be98a7a9b. Oct 6 08:36:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:36:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tij9m9hlmount_test with fs ext2 Oct 6 08:36:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:36:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7416a726-2d08-4c2c-bac0-b5c26d4dc132 r/w without journal. Quota mode: none. Oct 6 08:36:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tij9m9hlmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:36:59 storageqe-109 systemd[1]: tmp-libblockdev.tij9m9hlmount_test.mount: Deactivated successfully. Oct 6 08:36:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7416a726-2d08-4c2c-bac0-b5c26d4dc132. Oct 6 08:36:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:36:59 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:37:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:37:10 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:37:22 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:37:31 storageqe-109 NetworkManager[995]: [1759754251.6784] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 6 08:37:31 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 6 08:37:31 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:37:32 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:37:32 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:37:32 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:37:41 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:37:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:37:54 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:37:54 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:38:24 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 08:39:22 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:39:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:39:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:39:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:39:22 storageqe-109 stratisd[4947]: [2025-10-06T12:39:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:39:22 storageqe-109 stratisd[4947]: [2025-10-06T12:39:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:39:32 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:40:02 storageqe-109 stratisd[4947]: [2025-10-06T12:40:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:40:02 storageqe-109 stratisd[4947]: [2025-10-06T12:40:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:40:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.0ulb86xjmount_test with fs xfs Oct 6 08:40:24 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 0844175a-b855-43a4-bd47-deba9a038aee Oct 6 08:40:24 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:40:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0ulb86xjmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:40:29 storageqe-109 systemd[1]: tmp-libblockdev.0ulb86xjmount_test.mount: Deactivated successfully. Oct 6 08:40:29 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 0844175a-b855-43a4-bd47-deba9a038aee Oct 6 08:40:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:40:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wljrv6ckmount_test with fs ext4 Oct 6 08:40:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f4cae34c-9d3d-4219-8923-78e7051ae1bd r/w with ordered data mode. Quota mode: none. Oct 6 08:40:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wljrv6ckmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:40:47 storageqe-109 systemd[1]: tmp-libblockdev.wljrv6ckmount_test.mount: Deactivated successfully. Oct 6 08:40:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f4cae34c-9d3d-4219-8923-78e7051ae1bd. Oct 6 08:40:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:40:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4lhblkpumount_test with fs ext3 Oct 6 08:41:13 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:41:13 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 99b2c9f5-d5e8-4397-866b-13d6dbb8fdeb r/w with ordered data mode. Quota mode: none. Oct 6 08:41:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4lhblkpumount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:41:19 storageqe-109 systemd[1]: tmp-libblockdev.4lhblkpumount_test.mount: Deactivated successfully. Oct 6 08:41:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 99b2c9f5-d5e8-4397-866b-13d6dbb8fdeb. Oct 6 08:41:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:41:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wj3l3daimount_test with fs ext2 Oct 6 08:41:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:41:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f4a86ebc-bc66-4e63-950b-3820bc7feab2 r/w without journal. Quota mode: none. Oct 6 08:41:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wj3l3daimount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:41:50 storageqe-109 systemd[1]: tmp-libblockdev.wj3l3daimount_test.mount: Deactivated successfully. Oct 6 08:41:50 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f4a86ebc-bc66-4e63-950b-3820bc7feab2. Oct 6 08:41:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:41:50 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:41:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:42:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:42:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:42:22 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:42:22 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:42:22 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:42:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:42:44 storageqe-109 INFO: finishe the remove crypt device Xzst Oct 6 08:42:44 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 6 08:43:14 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 08:44:12 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:44:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:12 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:44:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:44:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:44:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:44:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:44:13 storageqe-109 stratisd[4947]: [2025-10-06T12:44:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:44:13 storageqe-109 stratisd[4947]: [2025-10-06T12:44:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:44:23 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Xzst -q --allow-discards Oct 6 08:44:54 storageqe-109 stratisd[4947]: [2025-10-06T12:44:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:44:54 storageqe-109 stratisd[4947]: [2025-10-06T12:44:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:45:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.z3pevh75mount_test with fs xfs Oct 6 08:45:15 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 28eaaaa1-a9f8-41bb-aa59-8ac51cce8356 Oct 6 08:45:15 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:45:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z3pevh75mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt Oct 6 08:45:20 storageqe-109 systemd[1]: tmp-libblockdev.z3pevh75mount_test.mount: Deactivated successfully. Oct 6 08:45:20 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 28eaaaa1-a9f8-41bb-aa59-8ac51cce8356 Oct 6 08:45:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:45:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ql9r1q2umount_test with fs ext4 Oct 6 08:45:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 75e3bf01-f1fb-4275-89b8-32f65224a972 r/w with ordered data mode. Quota mode: none. Oct 6 08:45:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ql9r1q2umount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:45:36 storageqe-109 systemd[1]: tmp-libblockdev.ql9r1q2umount_test.mount: Deactivated successfully. Oct 6 08:45:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 75e3bf01-f1fb-4275-89b8-32f65224a972. Oct 6 08:45:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext4 in remove_crypt Oct 6 08:45:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r_7lsfhlmount_test with fs ext3 Oct 6 08:45:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:45:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9f0dfb3f-f5b9-414e-802e-14c18a485d6f r/w with ordered data mode. Quota mode: none. Oct 6 08:45:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r_7lsfhlmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:46:03 storageqe-109 systemd[1]: tmp-libblockdev.r_7lsfhlmount_test.mount: Deactivated successfully. Oct 6 08:46:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9f0dfb3f-f5b9-414e-802e-14c18a485d6f. Oct 6 08:46:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext3 in remove_crypt Oct 6 08:46:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j9o18xj1mount_test with fs ext2 Oct 6 08:46:25 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:46:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem db781278-b6a4-498a-82d2-e66d400ce8bb r/w without journal. Quota mode: none. Oct 6 08:46:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j9o18xj1mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt INFO: remove crypt device Xzst Oct 6 08:46:30 storageqe-109 systemd[1]: tmp-libblockdev.j9o18xj1mount_test.mount: Deactivated successfully. Oct 6 08:46:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem db781278-b6a4-498a-82d2-e66d400ce8bb. Oct 6 08:46:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Xzst and fs ext2 in remove_crypt Oct 6 08:46:30 storageqe-109 INFO: remove crypt device Xzst cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:46:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:46:40 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:46:52 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:47:02 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:47:02 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:47:02 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:47:14 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device Xzst Oct 6 08:47:24 storageqe-109 INFO: finishe the remove crypt device Xzst cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:47:25 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:47:35 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:47:36 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hw_luks_paramter #### INFO: #### will start test_hw_luks_bz1750680 ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 08:47:51 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 08:47:51 storageqe-109 INFO: #### END test_hw_luks_paramter #### Oct 6 08:47:51 storageqe-109 INFO: #### will start test_hw_luks_bz1750680 ##### Oct 6 08:47:51 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:47:58 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:48:08 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:48:09 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:48:19 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:48:29 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:48:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:29 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:48:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:48:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:48:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:48:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:48:30 storageqe-109 stratisd[4947]: [2025-10-06T12:48:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:48:30 storageqe-109 stratisd[4947]: [2025-10-06T12:48:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 VwGB -q --disable-keyring Oct 6 08:48:40 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 VwGB -q --disable-keyring Oct 6 08:48:42 storageqe-109 stratisd[4947]: [2025-10-06T12:48:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:48:42 storageqe-109 stratisd[4947]: [2025-10-06T12:48:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:48:49 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/VwGB and fs xfs in remove_crypt Oct 6 08:48:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/VwGB and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.hsvzai1ymount_test with fs xfs Oct 6 08:49:03 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem e27896a4-a45a-4eb0-8309-ff77b221a608 Oct 6 08:49:03 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 08:49:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hsvzai1ymount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/VwGB and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/VwGB and fs ext4 in remove_crypt Oct 6 08:49:08 storageqe-109 systemd[1]: tmp-libblockdev.hsvzai1ymount_test.mount: Deactivated successfully. Oct 6 08:49:08 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem e27896a4-a45a-4eb0-8309-ff77b221a608 Oct 6 08:49:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/VwGB and fs xfs in remove_crypt Oct 6 08:49:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/VwGB and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9flso7f7mount_test with fs ext4 Oct 6 08:49:19 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6a04aac9-e028-460a-98d2-ab8417217510 r/w with ordered data mode. Quota mode: none. Oct 6 08:49:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9flso7f7mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/VwGB and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/VwGB and fs ext3 in remove_crypt Oct 6 08:49:25 storageqe-109 systemd[1]: tmp-libblockdev.9flso7f7mount_test.mount: Deactivated successfully. Oct 6 08:49:25 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6a04aac9-e028-460a-98d2-ab8417217510. Oct 6 08:49:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/VwGB and fs ext4 in remove_crypt Oct 6 08:49:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/VwGB and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pqrwyolqmount_test with fs ext3 Oct 6 08:49:46 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 08:49:46 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9a2ae295-c7b5-4d6d-8321-a76e26dbb331 r/w with ordered data mode. Quota mode: none. Oct 6 08:49:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pqrwyolqmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/VwGB and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/VwGB and fs ext2 in remove_crypt Oct 6 08:49:51 storageqe-109 systemd[1]: tmp-libblockdev.pqrwyolqmount_test.mount: Deactivated successfully. Oct 6 08:49:51 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9a2ae295-c7b5-4d6d-8321-a76e26dbb331. Oct 6 08:49:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/VwGB and fs ext3 in remove_crypt Oct 6 08:49:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/VwGB and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y195jslpmount_test with fs ext2 Oct 6 08:50:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 08:50:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c1158790-4edd-45a8-a239-42be68884b53 r/w without journal. Quota mode: none. Oct 6 08:50:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y195jslpmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/VwGB and fs ext2 in remove_crypt INFO: remove crypt device VwGB Oct 6 08:50:16 storageqe-109 systemd[1]: tmp-libblockdev.y195jslpmount_test.mount: Deactivated successfully. Oct 6 08:50:16 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c1158790-4edd-45a8-a239-42be68884b53. Oct 6 08:50:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/VwGB and fs ext2 in remove_crypt Oct 6 08:50:16 storageqe-109 INFO: remove crypt device VwGB cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:50:17 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 08:50:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:50:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:50:48 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:50:48 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:50:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 08:51:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device VwGB Oct 6 08:51:10 storageqe-109 INFO: finishe the remove crypt device VwGB cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:51:12 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:51:22 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:51:23 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hw_luks_bz1750680 #### INFO: #### will start test_hw_luks_bz1862173 ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 08:51:38 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 08:51:38 storageqe-109 INFO: #### END test_hw_luks_bz1750680 #### Oct 6 08:51:38 storageqe-109 INFO: #### will start test_hw_luks_bz1862173 ##### Oct 6 08:51:38 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:51:44 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:51:54 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:51:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:52:05 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 08:52:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:52:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:52:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:52:16 storageqe-109 stratisd[4947]: [2025-10-06T12:52:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:52:16 storageqe-109 stratisd[4947]: [2025-10-06T12:52:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' token add /dev/nvme0n1 -q Oct 6 08:52:26 storageqe-109 journal: cryptsetup --key-description 'mykey' token add /dev/nvme0n1 -q Oct 6 08:52:26 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:52:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:52:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:52:26 storageqe-109 stratisd[4947]: [2025-10-06T12:52:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:52:26 storageqe-109 stratisd[4947]: [2025-10-06T12:52:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:52:35 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --type 'luks2' open /dev/nvme0n1 Hqsv -q --allow-discards --token-only Oct 6 08:52:36 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Hqsv -q --allow-discards --token-only Oct 6 08:52:36 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 08:52:36 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:36 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:36 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 08:52:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 08:52:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627553, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 08:52:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627553 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 08:52:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 08:52:37 storageqe-109 stratisd[4947]: [2025-10-06T12:52:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:52:37 storageqe-109 stratisd[4947]: [2025-10-06T12:52:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:52:37 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 08:52:37 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 08:52:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:52:40 storageqe-109 udisksd[5174]: Error getting '/dev/nvme0n1' metadata_size: Failed to initialize device: No such device (g-bd-crypto-error-quark, 1) Oct 6 08:52:50 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 08:52:50 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_hw_luks_bz1862173 #### INFO: #### will start test_libaio_vs_io_uring_comparison ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 08:53:06 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 08:53:06 storageqe-109 INFO: #### END test_hw_luks_bz1862173 #### Oct 6 08:53:06 storageqe-109 INFO: #### will start test_libaio_vs_io_uring_comparison ##### Oct 6 08:53:06 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 08:53:11 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 08:53:11 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 08:53:11 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 08:53:12 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 08:53:19 storageqe-109 stratisd[4947]: [2025-10-06T12:53:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:53:19 storageqe-109 stratisd[4947]: [2025-10-06T12:53:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:53:20 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/nvme0n1 AzgvGe -q --allow-discards Oct 6 08:53:30 storageqe-109 journal: cryptsetup open /dev/nvme0n1 AzgvGe -q --allow-discards Oct 6 08:53:32 storageqe-109 stratisd[4947]: [2025-10-06T12:53:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 08:53:32 storageqe-109 stratisd[4947]: [2025-10-06T12:53:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs xfs in remove_crypt Oct 6 09:10:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._57n8fqmmount_test with fs xfs Oct 6 09:10:50 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 0d4361f7-b48c-4338-ae05-bdc6766f83bd Oct 6 09:10:50 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 09:10:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev._57n8fqmmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs ext4 in remove_crypt Oct 6 09:10:57 storageqe-109 systemd[1]: tmp-libblockdev._57n8fqmmount_test.mount: Deactivated successfully. Oct 6 09:10:57 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 0d4361f7-b48c-4338-ae05-bdc6766f83bd Oct 6 09:10:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs xfs in remove_crypt Oct 6 09:10:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._tvc6x9emount_test with fs ext4 Oct 6 09:11:09 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 52701c34-ac7f-4199-976f-cb18bb89d40b r/w with ordered data mode. Quota mode: none. Oct 6 09:11:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev._tvc6x9emount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs ext3 in remove_crypt Oct 6 09:11:14 storageqe-109 systemd[1]: tmp-libblockdev._tvc6x9emount_test.mount: Deactivated successfully. Oct 6 09:11:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 52701c34-ac7f-4199-976f-cb18bb89d40b. Oct 6 09:11:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs ext4 in remove_crypt Oct 6 09:11:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.paw7_3b8mount_test with fs ext3 Oct 6 09:11:36 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 09:11:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 90853a87-00cf-4712-8bf2-9e6dd179766c r/w with ordered data mode. Quota mode: none. Oct 6 09:11:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.paw7_3b8mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs ext2 in remove_crypt Oct 6 09:11:42 storageqe-109 systemd[1]: tmp-libblockdev.paw7_3b8mount_test.mount: Deactivated successfully. Oct 6 09:11:42 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 90853a87-00cf-4712-8bf2-9e6dd179766c. Oct 6 09:11:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs ext3 in remove_crypt Oct 6 09:11:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/AzgvGe and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.04rnzz77mount_test with fs ext2 Oct 6 09:12:03 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 09:12:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5209c7de-a6db-4547-984a-316fe66dfb14 r/w without journal. Quota mode: none. Oct 6 09:12:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.04rnzz77mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs ext2 in remove_crypt INFO: remove crypt device AzgvGe cryptsetup luksDump /dev/nvme0n1 -q Oct 6 09:12:09 storageqe-109 systemd[1]: tmp-libblockdev.04rnzz77mount_test.mount: Deactivated successfully. Oct 6 09:12:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5209c7de-a6db-4547-984a-316fe66dfb14. Oct 6 09:12:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/AzgvGe and fs ext2 in remove_crypt Oct 6 09:12:09 storageqe-109 INFO: remove crypt device AzgvGe Oct 6 09:12:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 09:12:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q Oct 6 09:12:19 storageqe-109 stratisd[4947]: [2025-10-06T13:12:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:12:19 storageqe-109 stratisd[4947]: [2025-10-06T13:12:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/nvme0n1 -q Oct 6 09:12:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 09:12:39 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 09:12:39 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 09:12:39 storageqe-109 stratisd[4947]: [2025-10-06T13:12:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:12:39 storageqe-109 stratisd[4947]: [2025-10-06T13:12:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:12:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 09:12:49 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device AzgvGe Oct 6 09:12:59 storageqe-109 INFO: finishe the remove crypt device AzgvGe Oct 6 09:12:59 storageqe-109 stratisd[4947]: [2025-10-06T13:12:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:12:59 storageqe-109 stratisd[4947]: [2025-10-06T13:12:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_libaio_vs_io_uring_comparison #### INFO: #### will start test_luks_hardware_vs_software_performance ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:13:05 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:13:05 storageqe-109 INFO: #### END test_libaio_vs_io_uring_comparison #### Oct 6 09:13:05 storageqe-109 INFO: #### will start test_luks_hardware_vs_software_performance ##### Oct 6 09:13:05 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:13:09 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 09:13:10 storageqe-109 stratisd[4947]: [2025-10-06T13:13:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:13:10 storageqe-109 stratisd[4947]: [2025-10-06T13:13:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 09:13:11 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 09:13:19 storageqe-109 stratisd[4947]: [2025-10-06T13:13:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:13:19 storageqe-109 stratisd[4947]: [2025-10-06T13:13:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 obYrWt -q --allow-discards Oct 6 09:13:29 storageqe-109 journal: cryptsetup open /dev/nvme0n1 obYrWt -q --allow-discards Oct 6 09:13:31 storageqe-109 stratisd[4947]: [2025-10-06T13:13:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:13:31 storageqe-109 stratisd[4947]: [2025-10-06T13:13:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs xfs in remove_crypt Oct 6 09:14:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.inv0dorpmount_test with fs xfs Oct 6 09:15:03 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 42223fa2-7104-47fc-90bb-3e0e7bdf2fdb Oct 6 09:15:03 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 09:15:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.inv0dorpmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs ext4 in remove_crypt Oct 6 09:15:10 storageqe-109 systemd[1]: tmp-libblockdev.inv0dorpmount_test.mount: Deactivated successfully. Oct 6 09:15:10 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 42223fa2-7104-47fc-90bb-3e0e7bdf2fdb Oct 6 09:15:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs xfs in remove_crypt Oct 6 09:15:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tae73_n6mount_test with fs ext4 Oct 6 09:15:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3e79af22-9ac7-4785-a697-0dd372c5e0c8 r/w with ordered data mode. Quota mode: none. Oct 6 09:15:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tae73_n6mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs ext3 in remove_crypt Oct 6 09:15:27 storageqe-109 systemd[1]: tmp-libblockdev.tae73_n6mount_test.mount: Deactivated successfully. Oct 6 09:15:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3e79af22-9ac7-4785-a697-0dd372c5e0c8. Oct 6 09:15:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs ext4 in remove_crypt Oct 6 09:15:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kljskv1fmount_test with fs ext3 Oct 6 09:15:49 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 09:15:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0f3bf9fb-3297-43fa-8f4e-7b0d86e3b8b4 r/w with ordered data mode. Quota mode: none. Oct 6 09:15:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kljskv1fmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs ext2 in remove_crypt Oct 6 09:15:54 storageqe-109 systemd[1]: tmp-libblockdev.kljskv1fmount_test.mount: Deactivated successfully. Oct 6 09:15:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0f3bf9fb-3297-43fa-8f4e-7b0d86e3b8b4. Oct 6 09:15:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs ext3 in remove_crypt Oct 6 09:15:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/obYrWt and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r5s55xihmount_test with fs ext2 Oct 6 09:16:16 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 09:16:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 65a9218c-9f4b-4a27-a8bc-04060334f375 r/w without journal. Quota mode: none. Oct 6 09:16:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r5s55xihmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs ext2 in remove_crypt INFO: remove crypt device obYrWt INFO: finishe the remove crypt device obYrWt cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 09:16:21 storageqe-109 systemd[1]: tmp-libblockdev.r5s55xihmount_test.mount: Deactivated successfully. Oct 6 09:16:21 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 65a9218c-9f4b-4a27-a8bc-04060334f375. Oct 6 09:16:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/obYrWt and fs ext2 in remove_crypt Oct 6 09:16:21 storageqe-109 INFO: remove crypt device obYrWt Oct 6 09:16:21 storageqe-109 INFO: finishe the remove crypt device obYrWt Oct 6 09:16:21 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 6 09:16:21 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 09:16:21 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 09:16:21 storageqe-109 stratisd[4947]: [2025-10-06T13:16:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:16:21 storageqe-109 stratisd[4947]: [2025-10-06T13:16:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:16:32 storageqe-109 kernel: nvme_log_error: 364 callbacks suppressed Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: blk_print_req_error: 364 callbacks suppressed Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: buffer_io_error: 358 callbacks suppressed Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 6 09:16:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 6 09:16:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 6 09:16:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 6 09:16:32 storageqe-109 stratisd[4947]: [2025-10-06T13:16:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:16:32 storageqe-109 stratisd[4947]: [2025-10-06T13:16:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 TQtyGp -q --allow-discards Oct 6 09:16:42 storageqe-109 journal: cryptsetup open /dev/nvme0n1 TQtyGp -q --allow-discards Oct 6 09:16:45 storageqe-109 stratisd[4947]: [2025-10-06T13:16:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:16:45 storageqe-109 stratisd[4947]: [2025-10-06T13:16:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:16:51 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs xfs in remove_crypt Oct 6 09:18:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.d1uhhmezmount_test with fs xfs Oct 6 09:18:16 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 9f5b17a1-8e0c-4907-872d-e6fc996a7581 Oct 6 09:18:16 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 09:18:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d1uhhmezmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs ext4 in remove_crypt Oct 6 09:18:23 storageqe-109 systemd[1]: tmp-libblockdev.d1uhhmezmount_test.mount: Deactivated successfully. Oct 6 09:18:23 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 9f5b17a1-8e0c-4907-872d-e6fc996a7581 Oct 6 09:18:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs xfs in remove_crypt Oct 6 09:18:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kwepp82bmount_test with fs ext4 Oct 6 09:18:34 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 232ba784-9730-4478-8110-964223f9228a r/w with ordered data mode. Quota mode: none. Oct 6 09:18:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kwepp82bmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs ext3 in remove_crypt Oct 6 09:18:40 storageqe-109 systemd[1]: tmp-libblockdev.kwepp82bmount_test.mount: Deactivated successfully. Oct 6 09:18:40 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 232ba784-9730-4478-8110-964223f9228a. Oct 6 09:18:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs ext4 in remove_crypt Oct 6 09:18:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7allj9m9mount_test with fs ext3 Oct 6 09:19:02 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 09:19:02 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 94520b30-7e88-43f5-8756-d4b26fb52634 r/w with ordered data mode. Quota mode: none. Oct 6 09:19:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7allj9m9mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs ext2 in remove_crypt Oct 6 09:19:07 storageqe-109 systemd[1]: tmp-libblockdev.7allj9m9mount_test.mount: Deactivated successfully. Oct 6 09:19:07 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 94520b30-7e88-43f5-8756-d4b26fb52634. Oct 6 09:19:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs ext3 in remove_crypt Oct 6 09:19:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TQtyGp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vz_hlc55mount_test with fs ext2 Oct 6 09:19:29 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 09:19:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c5e6ce5a-11ce-4aa9-8fe6-3fcf0de60e6e r/w without journal. Quota mode: none. Oct 6 09:19:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vz_hlc55mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs ext2 in remove_crypt INFO: remove crypt device TQtyGp Oct 6 09:19:34 storageqe-109 systemd[1]: tmp-libblockdev.vz_hlc55mount_test.mount: Deactivated successfully. Oct 6 09:19:34 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c5e6ce5a-11ce-4aa9-8fe6-3fcf0de60e6e. Oct 6 09:19:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TQtyGp and fs ext2 in remove_crypt Oct 6 09:19:34 storageqe-109 INFO: remove crypt device TQtyGp cryptsetup luksDump /dev/nvme0n1 -q Oct 6 09:19:35 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 6 09:19:45 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 6 09:19:57 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 09:20:07 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 09:20:07 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 09:20:07 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 6 09:20:18 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device TQtyGp Oct 6 09:20:28 storageqe-109 INFO: finishe the remove crypt device TQtyGp Oct 6 09:20:37 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_hardware_vs_software_performance #### INFO: #### will start test_luks_block_size_optimization ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:21:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:21:45 storageqe-109 INFO: #### END test_luks_hardware_vs_software_performance #### Oct 6 09:21:45 storageqe-109 INFO: #### will start test_luks_block_size_optimization ##### Oct 6 09:21:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 09:21:51 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 09:21:58 storageqe-109 stratisd[4947]: [2025-10-06T13:21:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:21:58 storageqe-109 stratisd[4947]: [2025-10-06T13:21:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 GrSxTc -q --allow-discards Oct 6 09:22:09 storageqe-109 journal: cryptsetup open /dev/nvme0n1 GrSxTc -q --allow-discards Oct 6 09:22:11 storageqe-109 stratisd[4947]: [2025-10-06T13:22:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:22:11 storageqe-109 stratisd[4947]: [2025-10-06T13:22:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:22:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 09:22:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 09:22:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs xfs in remove_crypt Oct 6 09:29:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2oiu8we1mount_test with fs xfs Oct 6 09:30:08 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 6ac97036-73b2-4349-b4b8-b4de61cc2fe7 Oct 6 09:30:08 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 09:30:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2oiu8we1mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs ext4 in remove_crypt Oct 6 09:30:15 storageqe-109 systemd[1]: tmp-libblockdev.2oiu8we1mount_test.mount: Deactivated successfully. Oct 6 09:30:15 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 6ac97036-73b2-4349-b4b8-b4de61cc2fe7 Oct 6 09:30:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs xfs in remove_crypt Oct 6 09:30:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xheejuq4mount_test with fs ext4 Oct 6 09:30:27 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 84661956-f41c-480c-a710-637fcb9c5c73 r/w with ordered data mode. Quota mode: none. Oct 6 09:30:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xheejuq4mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs ext3 in remove_crypt Oct 6 09:30:33 storageqe-109 systemd[1]: tmp-libblockdev.xheejuq4mount_test.mount: Deactivated successfully. Oct 6 09:30:33 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 84661956-f41c-480c-a710-637fcb9c5c73. Oct 6 09:30:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs ext4 in remove_crypt Oct 6 09:30:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hb15k04lmount_test with fs ext3 Oct 6 09:30:54 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 09:30:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 10e71c5d-f334-406c-b390-735b3febe16e r/w with ordered data mode. Quota mode: none. Oct 6 09:30:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hb15k04lmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs ext2 in remove_crypt Oct 6 09:31:00 storageqe-109 systemd[1]: tmp-libblockdev.hb15k04lmount_test.mount: Deactivated successfully. Oct 6 09:31:00 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 10e71c5d-f334-406c-b390-735b3febe16e. Oct 6 09:31:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs ext3 in remove_crypt Oct 6 09:31:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GrSxTc and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.sssu5f4jmount_test with fs ext2 Oct 6 09:31:21 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 09:31:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem fd0f983d-48c5-4cf6-9c15-93d32428e1aa r/w without journal. Quota mode: none. Oct 6 09:31:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sssu5f4jmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs ext2 in remove_crypt INFO: remove crypt device GrSxTc INFO: finishe the remove crypt device GrSxTc Oct 6 09:31:27 storageqe-109 systemd[1]: tmp-libblockdev.sssu5f4jmount_test.mount: Deactivated successfully. Oct 6 09:31:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem fd0f983d-48c5-4cf6-9c15-93d32428e1aa. Oct 6 09:31:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GrSxTc and fs ext2 in remove_crypt Oct 6 09:31:27 storageqe-109 INFO: remove crypt device GrSxTc Oct 6 09:31:27 storageqe-109 INFO: finishe the remove crypt device GrSxTc Oct 6 09:31:27 storageqe-109 stratisd[4947]: [2025-10-06T13:31:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:31:27 storageqe-109 stratisd[4947]: [2025-10-06T13:31:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_block_size_optimization #### INFO: #### will start test_luks_cpu_utilization_analysis ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:31:33 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:31:33 storageqe-109 INFO: #### END test_luks_block_size_optimization #### Oct 6 09:31:33 storageqe-109 INFO: #### will start test_luks_cpu_utilization_analysis ##### Oct 6 09:31:33 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:31:38 storageqe-109 stratisd[4947]: [2025-10-06T13:31:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:31:38 storageqe-109 stratisd[4947]: [2025-10-06T13:31:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 09:31:39 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 6 09:31:47 storageqe-109 stratisd[4947]: [2025-10-06T13:31:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:31:47 storageqe-109 stratisd[4947]: [2025-10-06T13:31:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 nBUTik -q --allow-discards Oct 6 09:31:57 storageqe-109 journal: cryptsetup open /dev/nvme0n1 nBUTik -q --allow-discards Oct 6 09:31:59 storageqe-109 stratisd[4947]: [2025-10-06T13:31:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:31:59 storageqe-109 stratisd[4947]: [2025-10-06T13:31:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:32:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 09:32:53 storageqe-109 dnf[904784]: Updating Subscription Management repositories. Oct 6 09:32:53 storageqe-109 dnf[904784]: Unable to read consumer identity Oct 6 09:32:53 storageqe-109 dnf[904784]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 09:32:53 storageqe-109 dnf[904784]: beaker-AppStream 449 kB/s | 2.8 kB 00:00 Oct 6 09:32:53 storageqe-109 dnf[904784]: beaker-AppStream-debuginfo 371 kB/s | 1.5 kB 00:00 Oct 6 09:32:53 storageqe-109 dnf[904784]: beaker-BaseOS 672 kB/s | 2.7 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-BaseOS-debuginfo 428 kB/s | 1.5 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-CRB 657 kB/s | 2.7 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-CRB-debuginfo 479 kB/s | 1.5 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-HighAvailability 742 kB/s | 2.8 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-HighAvailability-debuginfo 614 kB/s | 1.5 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-NFV 643 kB/s | 2.7 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-NFV-debuginfo 409 kB/s | 1.5 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-RT 878 kB/s | 2.7 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-RT-debuginfo 447 kB/s | 1.5 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-SAP 712 kB/s | 2.7 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-SAP-debuginfo 437 kB/s | 1.5 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-SAPHANA 652 kB/s | 2.7 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-SAPHANA-debuginfo 459 kB/s | 1.5 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: Beaker Client - RedHatEnterpriseLinux10 0.0 B/s | 0 B 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: Errors during downloading metadata for repository 'beaker-client': Oct 6 09:32:54 storageqe-109 dnf[904784]: - Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 6 09:32:54 storageqe-109 dnf[904784]: Error: Failed to download metadata for repo 'beaker-client': Cannot download repomd.xml: Curl error (6): Could not resolve hostname for http://download.eng.bos.redhat.com/beakerrepos/client/RedHatEnterpriseLinux10/repodata/repomd.xml [Could not resolve host: download.eng.bos.redhat.com] Oct 6 09:32:54 storageqe-109 dnf[904784]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 6 09:32:54 storageqe-109 dnf[904784]: Google Cloud CLI 4.2 kB/s | 1.4 kB 00:00 Oct 6 09:32:55 storageqe-109 dnf[904784]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 6 09:32:56 storageqe-109 dnf[904784]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 6 09:32:57 storageqe-109 dnf[904784]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 6 09:32:57 storageqe-109 dnf[904784]: Ignoring repositories: beaker-client Oct 6 09:32:57 storageqe-109 dnf[904784]: Metadata cache created. Oct 6 09:32:57 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 09:32:57 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs xfs in remove_crypt Oct 6 09:33:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._wqk0z03mount_test with fs xfs Oct 6 09:34:09 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem bc0f6e4b-a846-448d-89a6-ec5a8d73676e Oct 6 09:34:09 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 6 09:34:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev._wqk0z03mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs ext4 in remove_crypt Oct 6 09:34:14 storageqe-109 systemd[1]: tmp-libblockdev._wqk0z03mount_test.mount: Deactivated successfully. Oct 6 09:34:14 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem bc0f6e4b-a846-448d-89a6-ec5a8d73676e Oct 6 09:34:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs xfs in remove_crypt Oct 6 09:34:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h_otku53mount_test with fs ext4 Oct 6 09:34:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4265ba97-5bc7-424c-bd69-b677f9ce486d r/w with ordered data mode. Quota mode: none. Oct 6 09:34:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h_otku53mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs ext3 in remove_crypt Oct 6 09:34:31 storageqe-109 systemd[1]: tmp-libblockdev.h_otku53mount_test.mount: Deactivated successfully. Oct 6 09:34:31 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4265ba97-5bc7-424c-bd69-b677f9ce486d. Oct 6 09:34:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs ext4 in remove_crypt Oct 6 09:34:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lzvle_ymmount_test with fs ext3 Oct 6 09:34:53 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 6 09:34:53 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem db306b1c-ec50-4371-94f4-0d5cfe40f99b r/w with ordered data mode. Quota mode: none. Oct 6 09:34:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lzvle_ymmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs ext2 in remove_crypt Oct 6 09:34:58 storageqe-109 systemd[1]: tmp-libblockdev.lzvle_ymmount_test.mount: Deactivated successfully. Oct 6 09:34:58 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem db306b1c-ec50-4371-94f4-0d5cfe40f99b. Oct 6 09:34:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs ext3 in remove_crypt Oct 6 09:34:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nBUTik and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.oyh3lactmount_test with fs ext2 Oct 6 09:35:19 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 6 09:35:19 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 874a2f49-78a0-4fd4-86d4-72377947009b r/w without journal. Quota mode: none. Oct 6 09:35:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.oyh3lactmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs ext2 in remove_crypt INFO: remove crypt device nBUTik INFO: finishe the remove crypt device nBUTik Oct 6 09:35:25 storageqe-109 systemd[1]: tmp-libblockdev.oyh3lactmount_test.mount: Deactivated successfully. Oct 6 09:35:25 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 874a2f49-78a0-4fd4-86d4-72377947009b. Oct 6 09:35:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nBUTik and fs ext2 in remove_crypt Oct 6 09:35:25 storageqe-109 INFO: remove crypt device nBUTik Oct 6 09:35:25 storageqe-109 INFO: finishe the remove crypt device nBUTik Oct 6 09:35:25 storageqe-109 stratisd[4947]: [2025-10-06T13:35:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:35:25 storageqe-109 stratisd[4947]: [2025-10-06T13:35:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_cpu_utilization_analysis #### Oct 6 09:35:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:35:31 storageqe-109 INFO: #### END test_luks_cpu_utilization_analysis #### Oct 6 09:35:31 storageqe-109 stratisd[4947]: [2025-10-06T13:35:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:35:31 storageqe-109 stratisd[4947]: [2025-10-06T13:35:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 09:35:32 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 09:35:32 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 09:35:32 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 09:35:42 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_reencrypt_token_tpm2_import[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:35:48 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:35:48 storageqe-109 INFO: #### will start test_reencrypt_token_tpm2_import[npo2_linear] ##### Oct 6 09:35:48 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:36:02 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 09:36:16 storageqe-109 systemd[1]: Started run-p906297-i906597.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:16 storageqe-109 systemd[1]: Starting man-db-cache-update.service... Oct 6 09:36:17 storageqe-109 systemd[1]: man-db-cache-update.service: Deactivated successfully. Oct 6 09:36:17 storageqe-109 systemd[1]: Finished man-db-cache-update.service. Oct 6 09:36:17 storageqe-109 systemd[1]: man-db-cache-update.service: Consumed 485ms CPU time, 69.7M memory peak. Oct 6 09:36:17 storageqe-109 systemd[1]: run-p906297-i906597.service: Deactivated successfully. Oct 6 09:36:26 storageqe-109 dbus-broker-launch[989]: Noticed file-system modification, trigger reload. Oct 6 09:36:26 storageqe-109 dbus-broker-launch[989]: Noticed file-system modification, trigger reload. Oct 6 09:36:26 storageqe-109 systemd[1]: Started run-p906372-i906672.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:26 storageqe-109 systemd[1]: Reload requested from client PID 906376 ('systemctl') (unit session-4.scope)... Oct 6 09:36:26 storageqe-109 systemd[1]: Reloading... Oct 6 09:36:26 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 6 09:36:26 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 09:36:26 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 09:36:26 storageqe-109 systemd[1]: Reloading finished in 141 ms. Oct 6 09:36:26 storageqe-109 systemd[1]: Queuing reload/restart jobs for marked units… Oct 6 09:36:26 storageqe-109 systemd[1]: Starting man-db-cache-update.service... Oct 6 09:36:28 storageqe-109 systemd[1]: man-db-cache-update.service: Deactivated successfully. Oct 6 09:36:28 storageqe-109 systemd[1]: Finished man-db-cache-update.service. Oct 6 09:36:28 storageqe-109 systemd[1]: man-db-cache-update.service: Consumed 1.506s CPU time, 51.5M memory peak. Oct 6 09:36:28 storageqe-109 systemd[1]: run-p906372-i906672.service: Deactivated successfully. Oct 6 09:36:31 storageqe-109 systemd[1]: Started run-p906447-i906747.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:31 storageqe-109 systemd[1]: Starting man-db-cache-update.service... Oct 6 09:36:32 storageqe-109 systemd[1]: Started unbound-anchor.timer - daily update of the root trust anchor for DNSSEC. Oct 6 09:36:32 storageqe-109 systemd[1]: Started run-p906496-i906796.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:32 storageqe-109 systemd[1]: Reload requested from client PID 906500 ('systemctl') (unit session-4.scope)... Oct 6 09:36:32 storageqe-109 systemd[1]: Reloading... Oct 6 09:36:32 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 6 09:36:32 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 09:36:32 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 09:36:33 storageqe-109 systemd[1]: Reloading finished in 149 ms. Oct 6 09:36:33 storageqe-109 systemd[1]: Queuing reload/restart jobs for marked units… Oct 6 09:36:34 storageqe-109 systemd[1]: man-db-cache-update.service: Deactivated successfully. Oct 6 09:36:34 storageqe-109 systemd[1]: Finished man-db-cache-update.service. Oct 6 09:36:34 storageqe-109 systemd[1]: man-db-cache-update.service: Consumed 3.015s CPU time, 143.5M memory peak. Oct 6 09:36:34 storageqe-109 systemd[1]: run-p906447-i906747.service: Deactivated successfully. Oct 6 09:36:34 storageqe-109 systemd[1]: run-p906496-i906796.service: Deactivated successfully. Oct 6 09:36:34 storageqe-109 systemd[1]: Started run-p906572-i906872.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:34 storageqe-109 systemd[1]: Starting man-db-cache-update.service... Oct 6 09:36:37 storageqe-109 systemd[1]: Started run-p906622-i906922.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:37 storageqe-109 systemd[1]: man-db-cache-update.service: Deactivated successfully. Oct 6 09:36:37 storageqe-109 systemd[1]: Finished man-db-cache-update.service. Oct 6 09:36:37 storageqe-109 systemd[1]: man-db-cache-update.service: Consumed 2.705s CPU time, 55.2M memory peak. Oct 6 09:36:37 storageqe-109 systemd[1]: run-p906572-i906872.service: Deactivated successfully. Oct 6 09:36:37 storageqe-109 systemd[1]: run-p906622-i906922.service: Deactivated successfully. Oct 6 09:36:39 storageqe-109 systemd[1]: Started run-p906643-i906943.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:39 storageqe-109 systemd[1]: Starting man-db-cache-update.service... Oct 6 09:36:40 storageqe-109 systemd[1]: Started run-p906673-i906973.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:40 storageqe-109 systemd[1]: man-db-cache-update.service: Deactivated successfully. Oct 6 09:36:40 storageqe-109 systemd[1]: Finished man-db-cache-update.service. Oct 6 09:36:40 storageqe-109 systemd[1]: man-db-cache-update.service: Consumed 1.655s CPU time, 48.2M memory peak. Oct 6 09:36:40 storageqe-109 systemd[1]: run-p906643-i906943.service: Deactivated successfully. Oct 6 09:36:40 storageqe-109 systemd[1]: run-p906673-i906973.service: Deactivated successfully. Oct 6 09:36:42 storageqe-109 systemd[1]: Started run-p906694-i906994.service - [systemd-run] /usr/bin/systemctl start man-db-cache-update. Oct 6 09:36:42 storageqe-109 systemd[1]: Starting man-db-cache-update.service... Oct 6 09:36:42 storageqe-109 systemd[1]: Starting tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daemon... Oct 6 09:36:42 storageqe-109 systemd[1]: Started tpm2-abrmd.service - TPM2 Access Broker and Resource Management Daemon. Oct 6 09:36:44 storageqe-109 systemd[1]: man-db-cache-update.service: Deactivated successfully. Oct 6 09:36:44 storageqe-109 systemd[1]: Finished man-db-cache-update.service. Oct 6 09:36:44 storageqe-109 systemd[1]: man-db-cache-update.service: Consumed 2.694s CPU time, 55.7M memory peak. Oct 6 09:36:44 storageqe-109 systemd[1]: run-p906694-i906994.service: Deactivated successfully. cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:36:49 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:36:50 storageqe-109 stratisd[4947]: [2025-10-06T13:36:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:36:50 storageqe-109 stratisd[4947]: [2025-10-06T13:36:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:37:00 storageqe-109 stratisd[4947]: [2025-10-06T13:37:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:37:00 storageqe-109 stratisd[4947]: [2025-10-06T13:37:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --token-id '1' --token-type 'systemd-tpm2' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q Oct 6 09:37:01 storageqe-109 stratisd[4947]: [2025-10-06T13:37:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:01 storageqe-109 stratisd[4947]: [2025-10-06T13:37:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:01 storageqe-109 journal: cryptsetup --token-id '1' --token-type 'systemd-tpm2' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q Oct 6 09:37:03 storageqe-109 stratisd[4947]: [2025-10-06T13:37:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:03 storageqe-109 stratisd[4947]: [2025-10-06T13:37:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:03 storageqe-109 stratisd[4947]: [2025-10-06T13:37:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:03 storageqe-109 stratisd[4947]: [2025-10-06T13:37:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:16 storageqe-109 stratisd[4947]: [2025-10-06T13:37:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:16 storageqe-109 stratisd[4947]: [2025-10-06T13:37:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 6 09:37:26 storageqe-109 journal: cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 6 09:37:33 storageqe-109 stratisd[4947]: [2025-10-06T13:37:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 6 09:37:33 storageqe-109 stratisd[4947]: [2025-10-06T13:37:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_tpm2_import[npo2_linear] #### INFO: #### will start test_reencrypt_token_tpm2_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:37:48 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:37:48 storageqe-109 INFO: #### END test_reencrypt_token_tpm2_import[npo2_linear] #### Oct 6 09:37:48 storageqe-109 INFO: #### will start test_reencrypt_token_tpm2_header[npo2_linear] ##### Oct 6 09:37:48 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderovW' luksFormat /dev/mapper/npo2linear -q Oct 6 09:37:57 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderovW' luksFormat /dev/mapper/npo2linear -q cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderovW' reencrypt /dev/mapper/npo2linear -q Oct 6 09:38:07 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderovW' reencrypt /dev/mapper/npo2linear -q cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' --header '/tmp/testheaderovW' reencrypt /dev/mapper/npo2linear -q --token-only Oct 6 09:38:29 storageqe-109 journal: cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' --header '/tmp/testheaderovW' reencrypt /dev/mapper/npo2linear -q --token-only cryptsetup --header '/tmp/testheaderovW' luksAddKey /dev/mapper/npo2linear -q --token-only Oct 6 09:38:52 storageqe-109 journal: cryptsetup --header '/tmp/testheaderovW' luksAddKey /dev/mapper/npo2linear -q --token-only cryptsetup --key-description 'mykey' --token-id '1' --header '/tmp/testheaderovW' token add /dev/mapper/npo2linear -q Oct 6 09:39:10 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '1' --header '/tmp/testheaderovW' token add /dev/mapper/npo2linear -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_tpm2_header[npo2_linear] #### INFO: #### will start test_reencrypt_token_tpm2[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:39:25 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:39:25 storageqe-109 INFO: #### END test_reencrypt_token_tpm2_header[npo2_linear] #### Oct 6 09:39:25 storageqe-109 INFO: #### will start test_reencrypt_token_tpm2[npo2_linear] ##### Oct 6 09:39:25 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:39:39 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:39:39 storageqe-109 stratisd[4947]: [2025-10-06T13:39:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:39:39 storageqe-109 stratisd[4947]: [2025-10-06T13:39:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:39:49 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:39:49 storageqe-109 stratisd[4947]: [2025-10-06T13:39:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:39:49 storageqe-109 stratisd[4947]: [2025-10-06T13:39:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:39:49 storageqe-109 stratisd[4947]: [2025-10-06T13:39:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:39:49 storageqe-109 stratisd[4947]: [2025-10-06T13:39:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:00 storageqe-109 stratisd[4947]: [2025-10-06T13:40:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:00 storageqe-109 stratisd[4947]: [2025-10-06T13:40:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' reencrypt /dev/mapper/npo2linear -q --token-only Oct 6 09:40:11 storageqe-109 stratisd[4947]: [2025-10-06T13:40:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:11 storageqe-109 stratisd[4947]: [2025-10-06T13:40:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:11 storageqe-109 journal: cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' reencrypt /dev/mapper/npo2linear -q --token-only Oct 6 09:40:14 storageqe-109 stratisd[4947]: [2025-10-06T13:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:14 storageqe-109 stratisd[4947]: [2025-10-06T13:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:14 storageqe-109 stratisd[4947]: [2025-10-06T13:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:14 storageqe-109 stratisd[4947]: [2025-10-06T13:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:24 storageqe-109 stratisd[4947]: [2025-10-06T13:40:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:24 storageqe-109 stratisd[4947]: [2025-10-06T13:40:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 6 09:40:34 storageqe-109 journal: cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 6 09:40:41 storageqe-109 stratisd[4947]: [2025-10-06T13:40:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:41 storageqe-109 stratisd[4947]: [2025-10-06T13:40:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear BARmXNILqF -q --allow-discards --token-only Oct 6 09:40:51 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear BARmXNILqF -q --allow-discards --token-only Oct 6 09:40:52 storageqe-109 stratisd[4947]: [2025-10-06T13:40:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:40:52 storageqe-109 stratisd[4947]: [2025-10-06T13:40:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 6 09:41:04 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 6 09:41:04 storageqe-109 stratisd[4947]: [2025-10-06T13:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"keyslots":["2"],"tpm2-blob":"AJ4AIOuESWJUX5OBTFtvnCiO+3oUiaV66U8+sk2d9cPY4NcSABBSulYnWOUKJ2bcg9QpvaJYl8i2Gq4hJLpFI9Hev2ElyMBH1Q825VxOXi83BU+kVWM1iEbLXWIrK1oq1WPy5voxn8Dgks7b7PgSz/RWG2j94AX2LNdlWmca1GyO9SF+yFajkiNFozhIF059bEcMRKv/2IudBBAwsUIV2gBOAAgACwAABBIAIDxT1KyvQs/XyV+t0nEVczfsRr/qjkdbjx+nkJrT42X8ABAAIM9Ch2g0GBwNnwZGxoNLgKB0DzeTV1c5u9l1j8AqUa+O","tpm2-pcr-bank":"sha256","tpm2-pcrs":[7],"tpm2-policy-hash":"3c53d4acaf42cfd7c95fadd271157337ec46bfea8e475b8f1fa7909ad3e365fc","tpm2_srk":"gQAAAQAiAAshqczdWisdANJ7SSOokuIrXVG4PLC1ScexDuI3EQSqowAAAAEAWgAjAAsAAwRyAAAABgCAAEMAEAADABAAILDNyHzGsS2PmO6sGgf6oi4Yf7ehkYXkXomAPiYPoPeiACA3slVZeZnPwaOy2Vusbio9mJZZzJQeCTYL6AJGJRPlXw==","type":"systemd-tpm2"} Oct 6 09:41:04 storageqe-109 stratisd[4947]: [2025-10-06T13:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key tpm2-blob. Oct 6 09:41:04 storageqe-109 stratisd[4947]: [2025-10-06T13:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 6 09:41:04 storageqe-109 stratisd[4947]: [2025-10-06T13:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"keyslots":["2"],"tpm2-blob":"AJ4AIOuESWJUX5OBTFtvnCiO+3oUiaV66U8+sk2d9cPY4NcSABBSulYnWOUKJ2bcg9QpvaJYl8i2Gq4hJLpFI9Hev2ElyMBH1Q825VxOXi83BU+kVWM1iEbLXWIrK1oq1WPy5voxn8Dgks7b7PgSz/RWG2j94AX2LNdlWmca1GyO9SF+yFajkiNFozhIF059bEcMRKv/2IudBBAwsUIV2gBOAAgACwAABBIAIDxT1KyvQs/XyV+t0nEVczfsRr/qjkdbjx+nkJrT42X8ABAAIM9Ch2g0GBwNnwZGxoNLgKB0DzeTV1c5u9l1j8AqUa+O","tpm2-pcr-bank":"sha256","tpm2-pcrs":[7],"tpm2-policy-hash":"3c53d4acaf42cfd7c95fadd271157337ec46bfea8e475b8f1fa7909ad3e365fc","tpm2_srk":"gQAAAQAiAAshqczdWisdANJ7SSOokuIrXVG4PLC1ScexDuI3EQSqowAAAAEAWgAjAAsAAwRyAAAABgCAAEMAEAADABAAILDNyHzGsS2PmO6sGgf6oi4Yf7ehkYXkXomAPiYPoPeiACA3slVZeZnPwaOy2Vusbio9mJZZzJQeCTYL6AJGJRPlXw==","type":"systemd-tpm2"} Oct 6 09:41:04 storageqe-109 stratisd[4947]: [2025-10-06T13:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key tpm2-blob. Oct 6 09:41:04 storageqe-109 stratisd[4947]: [2025-10-06T13:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs xfs in remove_crypt Oct 6 09:41:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.gggx61twmount_test with fs xfs Oct 6 09:41:25 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 1a3fcbba-80c3-48a5-910c-53d33c13e1ad Oct 6 09:41:25 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 09:41:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gggx61twmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext4 in remove_crypt Oct 6 09:41:30 storageqe-109 systemd[1]: tmp-libblockdev.gggx61twmount_test.mount: Deactivated successfully. Oct 6 09:41:30 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 1a3fcbba-80c3-48a5-910c-53d33c13e1ad Oct 6 09:41:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs xfs in remove_crypt Oct 6 09:41:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.k0sx92hbmount_test with fs ext4 Oct 6 09:41:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fd3089e1-a32e-4190-b4f3-b5ca7175431a r/w with ordered data mode. Quota mode: none. Oct 6 09:41:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k0sx92hbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext3 in remove_crypt Oct 6 09:41:45 storageqe-109 systemd[1]: tmp-libblockdev.k0sx92hbmount_test.mount: Deactivated successfully. Oct 6 09:41:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fd3089e1-a32e-4190-b4f3-b5ca7175431a. Oct 6 09:41:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext4 in remove_crypt Oct 6 09:41:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bbm2b_gcmount_test with fs ext3 Oct 6 09:41:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 09:41:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 005a2b70-4a7d-417b-beeb-1b21111609c1 r/w with ordered data mode. Quota mode: none. Oct 6 09:41:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bbm2b_gcmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext2 in remove_crypt Oct 6 09:42:00 storageqe-109 systemd[1]: tmp-libblockdev.bbm2b_gcmount_test.mount: Deactivated successfully. Oct 6 09:42:00 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 005a2b70-4a7d-417b-beeb-1b21111609c1. Oct 6 09:42:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext3 in remove_crypt Oct 6 09:42:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lpvzmbpymount_test with fs ext2 Oct 6 09:42:10 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 09:42:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 925be86d-ddc5-45eb-9830-67fa5f5bd56e r/w without journal. Quota mode: none. Oct 6 09:42:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lpvzmbpymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext2 in remove_crypt INFO: remove crypt device BARmXNILqF INFO: finishe the remove crypt device BARmXNILqF Oct 6 09:42:15 storageqe-109 systemd[1]: tmp-libblockdev.lpvzmbpymount_test.mount: Deactivated successfully. Oct 6 09:42:15 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 925be86d-ddc5-45eb-9830-67fa5f5bd56e. Oct 6 09:42:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BARmXNILqF and fs ext2 in remove_crypt Oct 6 09:42:15 storageqe-109 INFO: remove crypt device BARmXNILqF Oct 6 09:42:15 storageqe-109 INFO: finishe the remove crypt device BARmXNILqF INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_tpm2[npo2_linear] #### INFO: #### will start test_reencrypt_token_keyring_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:42:20 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:42:20 storageqe-109 INFO: #### END test_reencrypt_token_tpm2[npo2_linear] #### Oct 6 09:42:20 storageqe-109 INFO: #### will start test_reencrypt_token_keyring_header[npo2_linear] ##### Oct 6 09:42:20 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderEKz' luksFormat /dev/mapper/npo2linear -q Oct 6 09:42:25 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderEKz' luksFormat /dev/mapper/npo2linear -q cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderEKz' reencrypt /dev/mapper/npo2linear -q Oct 6 09:42:35 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderEKz' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --header '/tmp/testheaderEKz' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:42:57 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --header '/tmp/testheaderEKz' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderEKz' token add /dev/mapper/npo2linear -q Oct 6 09:43:18 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderEKz' token add /dev/mapper/npo2linear -q cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '10' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderEKz' reencrypt /dev/mapper/npo2linear -q --token-only Oct 6 09:43:28 storageqe-109 journal: cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '10' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderEKz' reencrypt /dev/mapper/npo2linear -q --token-only INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_keyring_header[npo2_linear] #### INFO: #### will start test_reencrypt_token_keyring[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:43:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:43:33 storageqe-109 INFO: #### END test_reencrypt_token_keyring_header[npo2_linear] #### Oct 6 09:43:33 storageqe-109 INFO: #### will start test_reencrypt_token_keyring[npo2_linear] ##### Oct 6 09:43:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:43:38 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:43:38 storageqe-109 stratisd[4947]: [2025-10-06T13:43:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:43:38 storageqe-109 stratisd[4947]: [2025-10-06T13:43:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:43:48 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:43:49 storageqe-109 stratisd[4947]: [2025-10-06T13:43:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:43:49 storageqe-109 stratisd[4947]: [2025-10-06T13:43:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:43:49 storageqe-109 stratisd[4947]: [2025-10-06T13:43:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:43:49 storageqe-109 stratisd[4947]: [2025-10-06T13:43:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:43:59 storageqe-109 stratisd[4947]: [2025-10-06T13:43:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:43:59 storageqe-109 stratisd[4947]: [2025-10-06T13:43:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:44:09 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:44:09 storageqe-109 stratisd[4947]: [2025-10-06T13:44:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:44:09 storageqe-109 stratisd[4947]: [2025-10-06T13:44:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:44:09 storageqe-109 stratisd[4947]: [2025-10-06T13:44:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:44:09 storageqe-109 stratisd[4947]: [2025-10-06T13:44:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:44:20 storageqe-109 stratisd[4947]: [2025-10-06T13:44:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:44:20 storageqe-109 stratisd[4947]: [2025-10-06T13:44:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 6 09:44:30 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 6 09:44:30 storageqe-109 stratisd[4947]: [2025-10-06T13:44:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:44:30 storageqe-109 stratisd[4947]: [2025-10-06T13:44:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '1' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --token-only Oct 6 09:44:40 storageqe-109 journal: cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '1' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --token-only INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_keyring[npo2_linear] #### INFO: #### will start test_reencrypt[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:44:45 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:44:45 storageqe-109 INFO: #### END test_reencrypt_token_keyring[npo2_linear] #### Oct 6 09:44:45 storageqe-109 INFO: #### will start test_reencrypt[npo2_linear] ##### Oct 6 09:44:45 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:44:50 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 09:44:50 storageqe-109 stratisd[4947]: [2025-10-06T13:44:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:44:50 storageqe-109 stratisd[4947]: [2025-10-06T13:44:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksOpen /dev/mapper/npo2linear fzrwXATgMy -q Oct 6 09:45:00 storageqe-109 journal: cryptsetup luksOpen /dev/mapper/npo2linear fzrwXATgMy -q Oct 6 09:45:00 storageqe-109 stratisd[4947]: [2025-10-06T13:45:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:45:00 storageqe-109 stratisd[4947]: [2025-10-06T13:45:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt Oct 6 09:45:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ju9z0j38mount_test with fs xfs Oct 6 09:45:20 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem dee6be27-6703-472b-9fda-32a43c833f58 Oct 6 09:45:20 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 09:45:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ju9z0j38mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt Oct 6 09:45:25 storageqe-109 systemd[1]: tmp-libblockdev.ju9z0j38mount_test.mount: Deactivated successfully. Oct 6 09:45:25 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem dee6be27-6703-472b-9fda-32a43c833f58 Oct 6 09:45:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt Oct 6 09:45:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ssf4foanmount_test with fs ext4 Oct 6 09:45:35 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d30160f9-d215-41d1-8354-1698f636b354 r/w with ordered data mode. Quota mode: none. Oct 6 09:45:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ssf4foanmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt Oct 6 09:45:40 storageqe-109 systemd[1]: tmp-libblockdev.ssf4foanmount_test.mount: Deactivated successfully. Oct 6 09:45:40 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d30160f9-d215-41d1-8354-1698f636b354. Oct 6 09:45:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt Oct 6 09:45:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.casr24f4mount_test with fs ext3 Oct 6 09:45:50 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 09:45:50 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e0986268-fe29-4cd1-a138-3a6565e1103a r/w with ordered data mode. Quota mode: none. Oct 6 09:45:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.casr24f4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt Oct 6 09:45:55 storageqe-109 systemd[1]: tmp-libblockdev.casr24f4mount_test.mount: Deactivated successfully. Oct 6 09:45:55 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e0986268-fe29-4cd1-a138-3a6565e1103a. Oct 6 09:45:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt Oct 6 09:45:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.__f60jqvmount_test with fs ext2 Oct 6 09:46:05 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 09:46:05 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2b81bfca-cd83-4ee9-9fe0-fb3d4060adc7 r/w without journal. Quota mode: none. Oct 6 09:46:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.__f60jqvmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt INFO: remove crypt device fzrwXATgMy Oct 6 09:46:10 storageqe-109 systemd[1]: tmp-libblockdev.__f60jqvmount_test.mount: Deactivated successfully. Oct 6 09:46:10 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2b81bfca-cd83-4ee9-9fe0-fb3d4060adc7. Oct 6 09:46:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt Oct 6 09:46:10 storageqe-109 INFO: remove crypt device fzrwXATgMy INFO: finishe the remove crypt device fzrwXATgMy cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:46:10 storageqe-109 INFO: finishe the remove crypt device fzrwXATgMy Oct 6 09:46:10 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:46:10 storageqe-109 stratisd[4947]: [2025-10-06T13:46:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:10 storageqe-109 stratisd[4947]: [2025-10-06T13:46:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:10 storageqe-109 stratisd[4947]: [2025-10-06T13:46:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:10 storageqe-109 stratisd[4947]: [2025-10-06T13:46:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:21 storageqe-109 stratisd[4947]: [2025-10-06T13:46:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:21 storageqe-109 stratisd[4947]: [2025-10-06T13:46:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '256' --cipher 'twofish-cbc-essiv:sha256' --resilience 'journal' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:46:31 storageqe-109 journal: cryptsetup --key-size '256' --cipher 'twofish-cbc-essiv:sha256' --resilience 'journal' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:46:31 storageqe-109 stratisd[4947]: [2025-10-06T13:46:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:31 storageqe-109 stratisd[4947]: [2025-10-06T13:46:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:31 storageqe-109 stratisd[4947]: [2025-10-06T13:46:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:31 storageqe-109 stratisd[4947]: [2025-10-06T13:46:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:31 storageqe-109 kernel: alg: No test for essiv(cbc(twofish),sha256) (essiv(cbc-twofish-avx,sha256-ni)) Oct 6 09:46:43 storageqe-109 stratisd[4947]: [2025-10-06T13:46:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:43 storageqe-109 stratisd[4947]: [2025-10-06T13:46:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:46:53 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:46:53 storageqe-109 stratisd[4947]: [2025-10-06T13:46:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:53 storageqe-109 stratisd[4947]: [2025-10-06T13:46:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:53 storageqe-109 stratisd[4947]: [2025-10-06T13:46:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:46:53 storageqe-109 stratisd[4947]: [2025-10-06T13:46:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:07 storageqe-109 stratisd[4947]: [2025-10-06T13:47:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:07 storageqe-109 stratisd[4947]: [2025-10-06T13:47:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --cipher 'aes-xts-plain64' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --init-only Oct 6 09:47:17 storageqe-109 journal: cryptsetup --cipher 'aes-xts-plain64' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --init-only Oct 6 09:47:17 storageqe-109 stratisd[4947]: [2025-10-06T13:47:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:17 storageqe-109 stratisd[4947]: [2025-10-06T13:47:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:17 storageqe-109 stratisd[4947]: [2025-10-06T13:47:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:17 storageqe-109 stratisd[4947]: [2025-10-06T13:47:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:47:27 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:47:27 storageqe-109 stratisd[4947]: [2025-10-06T13:47:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:27 storageqe-109 stratisd[4947]: [2025-10-06T13:47:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:35 storageqe-109 stratisd[4947]: [2025-10-06T13:47:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:35 storageqe-109 stratisd[4947]: [2025-10-06T13:47:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --sector-size '512' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:47:45 storageqe-109 journal: cryptsetup --sector-size '512' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 09:47:45 storageqe-109 stratisd[4947]: [2025-10-06T13:47:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:45 storageqe-109 stratisd[4947]: [2025-10-06T13:47:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:45 storageqe-109 stratisd[4947]: [2025-10-06T13:47:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:45 storageqe-109 stratisd[4947]: [2025-10-06T13:47:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:58 storageqe-109 stratisd[4947]: [2025-10-06T13:47:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:47:58 storageqe-109 stratisd[4947]: [2025-10-06T13:47:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear fzrwXATgMy -q Oct 6 09:48:08 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear fzrwXATgMy -q Oct 6 09:48:08 storageqe-109 stratisd[4947]: [2025-10-06T13:48:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:08 storageqe-109 stratisd[4947]: [2025-10-06T13:48:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --active-name '/dev/mapper/fzrwXATgMy' --resilience 'none' reencrypt -q Oct 6 09:48:18 storageqe-109 journal: cryptsetup --active-name '/dev/mapper/fzrwXATgMy' --resilience 'none' reencrypt -q Oct 6 09:48:18 storageqe-109 stratisd[4947]: [2025-10-06T13:48:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:18 storageqe-109 stratisd[4947]: [2025-10-06T13:48:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:18 storageqe-109 stratisd[4947]: [2025-10-06T13:48:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:18 storageqe-109 stratisd[4947]: [2025-10-06T13:48:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:18 storageqe-109 stratisd[4947]: [2025-10-06T13:48:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:18 storageqe-109 stratisd[4947]: [2025-10-06T13:48:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:23 storageqe-109 auditd[957]: Audit daemon rotating log files Oct 6 09:48:32 storageqe-109 stratisd[4947]: [2025-10-06T13:48:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:32 storageqe-109 stratisd[4947]: [2025-10-06T13:48:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:32 storageqe-109 stratisd[4947]: [2025-10-06T13:48:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:48:32 storageqe-109 stratisd[4947]: [2025-10-06T13:48:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status fzrwXATgMy -q Oct 6 09:48:42 storageqe-109 journal: cryptsetup status fzrwXATgMy -q INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt Oct 6 09:48:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.yb4s1ef4mount_test with fs xfs Oct 6 09:49:02 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem d27462d1-232a-4d37-97eb-0127eaa14870 Oct 6 09:49:02 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 09:49:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yb4s1ef4mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt Oct 6 09:49:07 storageqe-109 systemd[1]: tmp-libblockdev.yb4s1ef4mount_test.mount: Deactivated successfully. Oct 6 09:49:07 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem d27462d1-232a-4d37-97eb-0127eaa14870 Oct 6 09:49:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs xfs in remove_crypt Oct 6 09:49:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hhwbibcrmount_test with fs ext4 Oct 6 09:49:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6372332e-ddba-45b9-a6d6-be9c3a40f5f1 r/w with ordered data mode. Quota mode: none. Oct 6 09:49:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hhwbibcrmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt Oct 6 09:49:23 storageqe-109 systemd[1]: tmp-libblockdev.hhwbibcrmount_test.mount: Deactivated successfully. Oct 6 09:49:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6372332e-ddba-45b9-a6d6-be9c3a40f5f1. Oct 6 09:49:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext4 in remove_crypt Oct 6 09:49:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.770jzqudmount_test with fs ext3 Oct 6 09:49:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 09:49:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ec6b1f4b-bdee-42ab-8454-b0f6fcc40aca r/w with ordered data mode. Quota mode: none. Oct 6 09:49:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.770jzqudmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt Oct 6 09:49:38 storageqe-109 systemd[1]: tmp-libblockdev.770jzqudmount_test.mount: Deactivated successfully. Oct 6 09:49:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ec6b1f4b-bdee-42ab-8454-b0f6fcc40aca. Oct 6 09:49:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext3 in remove_crypt Oct 6 09:49:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p3c5e0x_mount_test with fs ext2 Oct 6 09:49:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 09:49:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b90ce805-ad07-40af-9abb-7ed90387a9c1 r/w without journal. Quota mode: none. Oct 6 09:49:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p3c5e0x_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt INFO: remove crypt device fzrwXATgMy INFO: finishe the remove crypt device fzrwXATgMy Oct 6 09:49:53 storageqe-109 systemd[1]: tmp-libblockdev.p3c5e0x_mount_test.mount: Deactivated successfully. Oct 6 09:49:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b90ce805-ad07-40af-9abb-7ed90387a9c1. Oct 6 09:49:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fzrwXATgMy and fs ext2 in remove_crypt Oct 6 09:49:53 storageqe-109 INFO: remove crypt device fzrwXATgMy Oct 6 09:49:53 storageqe-109 INFO: finishe the remove crypt device fzrwXATgMy INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt[npo2_linear] #### INFO: #### will start test_reencrypt_data_shift[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:49:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:49:58 storageqe-109 INFO: #### END test_reencrypt[npo2_linear] #### Oct 6 09:49:58 storageqe-109 INFO: #### will start test_reencrypt_data_shift[npo2_linear] ##### Oct 6 09:49:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --key-size '128' --reduce-device-size '8M' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:03 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:03 storageqe-109 stratisd[4947]: [2025-10-06T13:50:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:03 storageqe-109 stratisd[4947]: [2025-10-06T13:50:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:12 storageqe-109 stratisd[4947]: [2025-10-06T13:50:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:12 storageqe-109 stratisd[4947]: [2025-10-06T13:50:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '21M' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:22 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '21M' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:22 storageqe-109 stratisd[4947]: [2025-10-06T13:50:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:22 storageqe-109 stratisd[4947]: [2025-10-06T13:50:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:30 storageqe-109 stratisd[4947]: [2025-10-06T13:50:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:30 storageqe-109 stratisd[4947]: [2025-10-06T13:50:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '30M' --offset '21504' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:40 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '30M' --offset '21504' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:40 storageqe-109 stratisd[4947]: [2025-10-06T13:50:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:40 storageqe-109 stratisd[4947]: [2025-10-06T13:50:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:49 storageqe-109 stratisd[4947]: [2025-10-06T13:50:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:49 storageqe-109 stratisd[4947]: [2025-10-06T13:50:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '33M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:59 storageqe-109 journal: cryptsetup --reduce-device-size '33M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:50:59 storageqe-109 stratisd[4947]: [2025-10-06T13:50:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:50:59 storageqe-109 stratisd[4947]: [2025-10-06T13:50:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:51:04 storageqe-109 stratisd[4947]: [2025-10-06T13:51:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:51:04 storageqe-109 stratisd[4947]: [2025-10-06T13:51:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '64M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:51:14 storageqe-109 journal: cryptsetup --reduce-device-size '64M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:51:14 storageqe-109 stratisd[4947]: [2025-10-06T13:51:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:51:14 storageqe-109 stratisd[4947]: [2025-10-06T13:51:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:51:19 storageqe-109 stratisd[4947]: [2025-10-06T13:51:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:51:19 storageqe-109 stratisd[4947]: [2025-10-06T13:51:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '8M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 6 09:51:29 storageqe-109 journal: cryptsetup --reduce-device-size '8M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 6 09:51:29 storageqe-109 stratisd[4947]: [2025-10-06T13:51:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:51:29 storageqe-109 stratisd[4947]: [2025-10-06T13:51:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '8M' --offset '32760' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 6 09:51:39 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --offset '32760' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --reduce-device-size '21M' --offset '43008' --header '/tmp/testheaderLmt' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:51:49 storageqe-109 journal: cryptsetup --reduce-device-size '21M' --offset '43008' --header '/tmp/testheaderLmt' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only ZUBqCmLyTs Oct 6 09:52:04 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only ZUBqCmLyTs Oct 6 09:52:04 storageqe-109 stratisd[4947]: [2025-10-06T13:52:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:04 storageqe-109 stratisd[4947]: [2025-10-06T13:52:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:04 storageqe-109 stratisd[4947]: [2025-10-06T13:52:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:04 storageqe-109 stratisd[4947]: [2025-10-06T13:52:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:04 storageqe-109 stratisd[4947]: [2025-10-06T13:52:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:04 storageqe-109 stratisd[4947]: [2025-10-06T13:52:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup reencrypt /dev/mapper/npo2linear -q --resume-only Oct 6 09:52:14 storageqe-109 journal: cryptsetup reencrypt /dev/mapper/npo2linear -q --resume-only Oct 6 09:52:14 storageqe-109 stratisd[4947]: [2025-10-06T13:52:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:14 storageqe-109 stratisd[4947]: [2025-10-06T13:52:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:14 storageqe-109 stratisd[4947]: [2025-10-06T13:52:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:14 storageqe-109 stratisd[4947]: [2025-10-06T13:52:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:14 storageqe-109 stratisd[4947]: [2025-10-06T13:52:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:14 storageqe-109 stratisd[4947]: [2025-10-06T13:52:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:43 storageqe-109 stratisd[4947]: [2025-10-06T13:52:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:43 storageqe-109 stratisd[4947]: [2025-10-06T13:52:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:43 storageqe-109 stratisd[4947]: [2025-10-06T13:52:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:52:43 storageqe-109 stratisd[4947]: [2025-10-06T13:52:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only ZUBqCmLyTs Oct 6 09:52:53 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only ZUBqCmLyTs INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt Oct 6 09:53:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.g91yg219mount_test with fs xfs Oct 6 09:53:13 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem afd08d75-dc1a-4e19-9f9c-eeabc4c9b619 Oct 6 09:53:13 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 09:53:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g91yg219mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt Oct 6 09:53:18 storageqe-109 systemd[1]: tmp-libblockdev.g91yg219mount_test.mount: Deactivated successfully. Oct 6 09:53:18 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem afd08d75-dc1a-4e19-9f9c-eeabc4c9b619 Oct 6 09:53:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt Oct 6 09:53:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rb0pgajfmount_test with fs ext4 Oct 6 09:53:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 789b41ad-d2a0-4214-9409-ecc8c5c85a1b r/w with ordered data mode. Quota mode: none. Oct 6 09:53:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rb0pgajfmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt Oct 6 09:53:33 storageqe-109 systemd[1]: tmp-libblockdev.rb0pgajfmount_test.mount: Deactivated successfully. Oct 6 09:53:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 789b41ad-d2a0-4214-9409-ecc8c5c85a1b. Oct 6 09:53:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt Oct 6 09:53:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ypuwoyb1mount_test with fs ext3 Oct 6 09:53:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 09:53:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8fab78d6-3bad-4bcd-b48e-7561592b0f5c r/w with ordered data mode. Quota mode: none. Oct 6 09:53:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ypuwoyb1mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt Oct 6 09:53:49 storageqe-109 systemd[1]: tmp-libblockdev.ypuwoyb1mount_test.mount: Deactivated successfully. Oct 6 09:53:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8fab78d6-3bad-4bcd-b48e-7561592b0f5c. Oct 6 09:53:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt Oct 6 09:53:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.b0wyih5mmount_test with fs ext2 Oct 6 09:53:59 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 09:53:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 18741ac2-857c-417b-8803-90ea76f4d47e r/w without journal. Quota mode: none. Oct 6 09:53:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b0wyih5mmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt INFO: remove crypt device ZUBqCmLyTs INFO: finishe the remove crypt device ZUBqCmLyTs cryptsetup --key-size '128' --reduce-device-size '8M' --key-file '/tmp/testfileiye' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only ZUBqCmLyTs Oct 6 09:54:04 storageqe-109 systemd[1]: tmp-libblockdev.b0wyih5mmount_test.mount: Deactivated successfully. Oct 6 09:54:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 18741ac2-857c-417b-8803-90ea76f4d47e. Oct 6 09:54:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt Oct 6 09:54:04 storageqe-109 INFO: remove crypt device ZUBqCmLyTs Oct 6 09:54:04 storageqe-109 INFO: finishe the remove crypt device ZUBqCmLyTs Oct 6 09:54:04 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --key-file '/tmp/testfileiye' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only ZUBqCmLyTs Oct 6 09:54:04 storageqe-109 stratisd[4947]: [2025-10-06T13:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:54:04 storageqe-109 stratisd[4947]: [2025-10-06T13:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:54:04 storageqe-109 stratisd[4947]: [2025-10-06T13:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:54:04 storageqe-109 stratisd[4947]: [2025-10-06T13:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:54:04 storageqe-109 stratisd[4947]: [2025-10-06T13:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 09:54:04 storageqe-109 stratisd[4947]: [2025-10-06T13:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt Oct 6 09:54:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.gre27pgimount_test with fs xfs Oct 6 09:54:24 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem a0f186b6-e248-401c-aa2b-a68216081ebe Oct 6 09:54:24 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 09:54:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gre27pgimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt Oct 6 09:54:30 storageqe-109 systemd[1]: tmp-libblockdev.gre27pgimount_test.mount: Deactivated successfully. Oct 6 09:54:30 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem a0f186b6-e248-401c-aa2b-a68216081ebe Oct 6 09:54:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs xfs in remove_crypt Oct 6 09:54:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.yt8ylv0hmount_test with fs ext4 Oct 6 09:54:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7e8aeaae-ad3c-414e-a5a8-20e2b37a7fd3 r/w with ordered data mode. Quota mode: none. Oct 6 09:54:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yt8ylv0hmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt Oct 6 09:54:44 storageqe-109 systemd[1]: tmp-libblockdev.yt8ylv0hmount_test.mount: Deactivated successfully. Oct 6 09:54:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7e8aeaae-ad3c-414e-a5a8-20e2b37a7fd3. Oct 6 09:54:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext4 in remove_crypt Oct 6 09:54:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dbsn9n6jmount_test with fs ext3 Oct 6 09:54:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 09:54:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a619ed6e-f8ad-420a-aad0-83f0c6222c78 r/w with ordered data mode. Quota mode: none. Oct 6 09:54:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dbsn9n6jmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt Oct 6 09:54:59 storageqe-109 systemd[1]: tmp-libblockdev.dbsn9n6jmount_test.mount: Deactivated successfully. Oct 6 09:54:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a619ed6e-f8ad-420a-aad0-83f0c6222c78. Oct 6 09:54:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt Oct 6 09:55:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.iutugryamount_test with fs ext2 Oct 6 09:55:10 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 09:55:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3ee6bc96-d264-4605-a230-fec4febf8b36 r/w without journal. Quota mode: none. Oct 6 09:55:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iutugryamount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt INFO: remove crypt device ZUBqCmLyTs INFO: finishe the remove crypt device ZUBqCmLyTs cryptsetup open /dev/mapper/npo2linear ZUBqCmLyTs -q --test-passphrase Oct 6 09:55:14 storageqe-109 systemd[1]: tmp-libblockdev.iutugryamount_test.mount: Deactivated successfully. Oct 6 09:55:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3ee6bc96-d264-4605-a230-fec4febf8b36. Oct 6 09:55:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ZUBqCmLyTs and fs ext2 in remove_crypt Oct 6 09:55:14 storageqe-109 INFO: remove crypt device ZUBqCmLyTs Oct 6 09:55:14 storageqe-109 INFO: finishe the remove crypt device ZUBqCmLyTs Oct 6 09:55:14 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear ZUBqCmLyTs -q --test-passphrase INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_data_shift[npo2_linear] #### INFO: #### will start test_reencrypt_with_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:55:30 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 09:55:30 storageqe-109 INFO: #### END test_reencrypt_data_shift[npo2_linear] #### Oct 6 09:55:30 storageqe-109 INFO: #### will start test_reencrypt_with_header[npo2_linear] ##### Oct 6 09:55:30 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --key-size '128' --header '/tmp/testheaderiDX' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:55:35 storageqe-109 journal: cryptsetup --key-size '128' --header '/tmp/testheaderiDX' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --header '/tmp/testheadervwF' --resilience 'none' --cipher 'twofish-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:55:57 storageqe-109 journal: cryptsetup --header '/tmp/testheadervwF' --resilience 'none' --cipher 'twofish-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --header '/tmp/testheaderdyc' --resilience 'checksum' --cipher 'serpent-xts-plain' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:56:15 storageqe-109 journal: cryptsetup --header '/tmp/testheaderdyc' --resilience 'checksum' --cipher 'serpent-xts-plain' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --header '/tmp/testheaderLqC' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt fPawOAYWum Oct 6 09:56:32 storageqe-109 journal: cryptsetup --header '/tmp/testheaderLqC' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt fPawOAYWum cryptsetup --header '/tmp/testheaderLqC' status fPawOAYWum -q Oct 6 09:56:53 storageqe-109 journal: cryptsetup --header '/tmp/testheaderLqC' status fPawOAYWum -q cryptsetup --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt fPawOAYWum Oct 6 09:57:03 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt fPawOAYWum INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 09:57:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.gjzx0dwhmount_test with fs xfs Oct 6 09:57:23 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 91ccb487-8713-403a-8058-5a0732ed2db8 Oct 6 09:57:24 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 09:57:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gjzx0dwhmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 09:57:28 storageqe-109 systemd[1]: tmp-libblockdev.gjzx0dwhmount_test.mount: Deactivated successfully. Oct 6 09:57:28 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 91ccb487-8713-403a-8058-5a0732ed2db8 Oct 6 09:57:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 09:57:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e65nyotamount_test with fs ext4 Oct 6 09:57:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b913f11d-284b-402b-b958-e07edd7183c1 r/w with ordered data mode. Quota mode: none. Oct 6 09:57:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e65nyotamount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 09:57:44 storageqe-109 systemd[1]: tmp-libblockdev.e65nyotamount_test.mount: Deactivated successfully. Oct 6 09:57:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b913f11d-284b-402b-b958-e07edd7183c1. Oct 6 09:57:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 09:57:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1uomxs5cmount_test with fs ext3 Oct 6 09:57:54 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 09:57:54 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ef59e74a-10f8-4082-a407-3eb435ec5e3f r/w with ordered data mode. Quota mode: none. Oct 6 09:57:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1uomxs5cmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 09:57:59 storageqe-109 systemd[1]: tmp-libblockdev.1uomxs5cmount_test.mount: Deactivated successfully. Oct 6 09:57:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ef59e74a-10f8-4082-a407-3eb435ec5e3f. Oct 6 09:57:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 09:57:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.yeei6axhmount_test with fs ext2 Oct 6 09:58:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 09:58:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e6a39351-d11d-435a-bad0-d1a1db9f7d42 r/w without journal. Quota mode: none. Oct 6 09:58:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yeei6axhmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum Oct 6 09:58:14 storageqe-109 systemd[1]: tmp-libblockdev.yeei6axhmount_test.mount: Deactivated successfully. Oct 6 09:58:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e6a39351-d11d-435a-bad0-d1a1db9f7d42. Oct 6 09:58:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 09:58:14 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 09:58:14 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum cryptsetup --offset '32768' --header '/tmp/testheaderCuc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 6 09:58:14 storageqe-109 journal: cryptsetup --offset '32768' --header '/tmp/testheaderCuc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --key-size '128' --offset '32768' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --key-file '/tmp/testfileIYW' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only fPawOAYWum Oct 6 09:58:33 storageqe-109 journal: cryptsetup --key-size '128' --offset '32768' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --key-file '/tmp/testfileIYW' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only fPawOAYWum cryptsetup --header '/tmp/testheaderuRc' status fPawOAYWum -q Oct 6 09:58:43 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' status fPawOAYWum -q INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 09:58:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.wqpjc4wimount_test with fs xfs Oct 6 09:59:03 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 944baf62-7183-4c2e-a3f7-90a712afa770 Oct 6 09:59:03 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 09:59:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wqpjc4wimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 09:59:08 storageqe-109 systemd[1]: tmp-libblockdev.wqpjc4wimount_test.mount: Deactivated successfully. Oct 6 09:59:08 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 944baf62-7183-4c2e-a3f7-90a712afa770 Oct 6 09:59:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 09:59:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.soqr6524mount_test with fs ext4 Oct 6 09:59:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 90bdc6eb-8b5c-43d5-bd42-76d6a5c878c1 r/w with ordered data mode. Quota mode: none. Oct 6 09:59:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.soqr6524mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 09:59:23 storageqe-109 systemd[1]: tmp-libblockdev.soqr6524mount_test.mount: Deactivated successfully. Oct 6 09:59:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 90bdc6eb-8b5c-43d5-bd42-76d6a5c878c1. Oct 6 09:59:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 09:59:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i6pz60shmount_test with fs ext3 Oct 6 09:59:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 09:59:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 663aa273-6f98-4ae8-9db4-87c9593ece71 r/w with ordered data mode. Quota mode: none. Oct 6 09:59:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i6pz60shmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 09:59:38 storageqe-109 systemd[1]: tmp-libblockdev.i6pz60shmount_test.mount: Deactivated successfully. Oct 6 09:59:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 663aa273-6f98-4ae8-9db4-87c9593ece71. Oct 6 09:59:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 09:59:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ogc8op3qmount_test with fs ext2 Oct 6 09:59:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 09:59:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 16a584ca-ab29-471f-8a1e-a0dcb10c26fa r/w without journal. Quota mode: none. Oct 6 09:59:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ogc8op3qmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum cryptsetup --header '/tmp/testheaderuRc' open /dev/mapper/npo2linear --test-passphrase -q Oct 6 09:59:53 storageqe-109 systemd[1]: tmp-libblockdev.ogc8op3qmount_test.mount: Deactivated successfully. Oct 6 09:59:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 16a584ca-ab29-471f-8a1e-a0dcb10c26fa. Oct 6 09:59:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 09:59:53 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 09:59:53 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum Oct 6 09:59:53 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:00:03 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:00:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.lt5vm8b4mount_test with fs xfs Oct 6 10:00:23 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem a06149e4-25ea-4d46-a91f-c68c2f5aaed0 Oct 6 10:00:23 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 10:00:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lt5vm8b4mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:00:28 storageqe-109 systemd[1]: tmp-libblockdev.lt5vm8b4mount_test.mount: Deactivated successfully. Oct 6 10:00:28 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem a06149e4-25ea-4d46-a91f-c68c2f5aaed0 Oct 6 10:00:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:00:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.u0i1vednmount_test with fs ext4 Oct 6 10:00:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 66694155-1b31-431c-9cfe-b54def7c3f9f r/w with ordered data mode. Quota mode: none. Oct 6 10:00:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u0i1vednmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:00:43 storageqe-109 systemd[1]: tmp-libblockdev.u0i1vednmount_test.mount: Deactivated successfully. Oct 6 10:00:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 66694155-1b31-431c-9cfe-b54def7c3f9f. Oct 6 10:00:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:00:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vwzc4f6lmount_test with fs ext3 Oct 6 10:00:53 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 10:00:53 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6d52afd0-8741-4db7-872f-1b84bd9c86a9 r/w with ordered data mode. Quota mode: none. Oct 6 10:00:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vwzc4f6lmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:00:58 storageqe-109 systemd[1]: tmp-libblockdev.vwzc4f6lmount_test.mount: Deactivated successfully. Oct 6 10:00:58 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6d52afd0-8741-4db7-872f-1b84bd9c86a9. Oct 6 10:00:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:00:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.iubcmtivmount_test with fs ext2 Oct 6 10:01:08 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 10:01:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 38df7cbc-c0d5-4ae2-946b-472997bdf889 r/w without journal. Quota mode: none. Oct 6 10:01:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iubcmtivmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum cryptsetup --key-size '128' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 10:01:13 storageqe-109 systemd[1]: tmp-libblockdev.iubcmtivmount_test.mount: Deactivated successfully. Oct 6 10:01:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 38df7cbc-c0d5-4ae2-946b-472997bdf889. Oct 6 10:01:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:01:13 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 10:01:13 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum Oct 6 10:01:13 storageqe-109 journal: cryptsetup --key-size '128' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --resilience 'journal' --header '/tmp/testheaderuRc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 10:01:36 storageqe-109 journal: cryptsetup --resilience 'journal' --header '/tmp/testheaderuRc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-size '128' --resilience 'none' --header '/tmp/testheaderuRc' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 10:01:57 storageqe-109 journal: cryptsetup --key-size '128' --resilience 'none' --header '/tmp/testheaderuRc' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --resilience 'checksum' --header '/tmp/testheaderuRc' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 6 10:02:17 storageqe-109 journal: cryptsetup --resilience 'checksum' --header '/tmp/testheaderuRc' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-size '128' --type 'luks2' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:02:37 storageqe-109 journal: cryptsetup --key-size '128' --type 'luks2' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderuRc' open /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:02:48 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' open /dev/mapper/npo2linear fPawOAYWum -q cryptsetup --active-name 'fPawOAYWum' --header '/tmp/testheaderuRc' reencrypt /dev/mapper/npo2linear -q Oct 6 10:02:58 storageqe-109 journal: cryptsetup --active-name 'fPawOAYWum' --header '/tmp/testheaderuRc' reencrypt /dev/mapper/npo2linear -q INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:03:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.fa4en_jomount_test with fs xfs Oct 6 10:03:28 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 524b9af3-75cc-466a-a41e-daa06d60dd79 Oct 6 10:03:28 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 10:03:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fa4en_jomount_test with fs xfs Oct 6 10:03:33 storageqe-109 systemd[1]: tmp-libblockdev.fa4en_jomount_test.mount: Deactivated successfully. Oct 6 10:03:33 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 524b9af3-75cc-466a-a41e-daa06d60dd79 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:03:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:03:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tqsdr3uimount_test with fs ext4 Oct 6 10:03:43 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 69e85d20-3dd2-4e12-b61a-7e620b572adf r/w with ordered data mode. Quota mode: none. Oct 6 10:03:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tqsdr3uimount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:03:48 storageqe-109 systemd[1]: tmp-libblockdev.tqsdr3uimount_test.mount: Deactivated successfully. Oct 6 10:03:48 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 69e85d20-3dd2-4e12-b61a-7e620b572adf. Oct 6 10:03:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:03:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.00rxeb8hmount_test with fs ext3 Oct 6 10:03:59 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 10:03:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 071f1622-3749-448c-ba0c-71c3c0fff567 r/w with ordered data mode. Quota mode: none. Oct 6 10:03:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.00rxeb8hmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:04:04 storageqe-109 systemd[1]: tmp-libblockdev.00rxeb8hmount_test.mount: Deactivated successfully. Oct 6 10:04:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 071f1622-3749-448c-ba0c-71c3c0fff567. Oct 6 10:04:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:04:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cy94irjamount_test with fs ext2 Oct 6 10:04:14 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 10:04:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 14ea4e0d-dfd4-4746-bfd8-0c089f4e020b r/w without journal. Quota mode: none. Oct 6 10:04:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cy94irjamount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum cryptsetup --key-size '128' --type 'luks2' --sector-size '512' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:04:19 storageqe-109 systemd[1]: tmp-libblockdev.cy94irjamount_test.mount: Deactivated successfully. Oct 6 10:04:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 14ea4e0d-dfd4-4746-bfd8-0c089f4e020b. Oct 6 10:04:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:04:19 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 10:04:19 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum Oct 6 10:04:19 storageqe-109 journal: cryptsetup --key-size '128' --type 'luks2' --sector-size '512' --header '/tmp/testheaderuRc' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:04:29 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:04:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.qgjofp3lmount_test with fs xfs Oct 6 10:04:49 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3144884f-b7ae-4d6e-b648-2eb017ff8ee8 Oct 6 10:04:49 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 10:04:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qgjofp3lmount_test with fs xfs Oct 6 10:04:54 storageqe-109 systemd[1]: tmp-libblockdev.qgjofp3lmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:04:54 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3144884f-b7ae-4d6e-b648-2eb017ff8ee8 Oct 6 10:04:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:04:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z2mj_anamount_test with fs ext4 Oct 6 10:05:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7608bd7c-526c-4d5a-b055-ec37472f7d7c r/w with ordered data mode. Quota mode: none. Oct 6 10:05:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z2mj_anamount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:05:09 storageqe-109 systemd[1]: tmp-libblockdev.z2mj_anamount_test.mount: Deactivated successfully. Oct 6 10:05:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7608bd7c-526c-4d5a-b055-ec37472f7d7c. Oct 6 10:05:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:05:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qatnxfatmount_test with fs ext3 Oct 6 10:05:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 10:05:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c022ab81-cd0d-444d-86a6-ee25b01b9d2d r/w with ordered data mode. Quota mode: none. Oct 6 10:05:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qatnxfatmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:05:25 storageqe-109 systemd[1]: tmp-libblockdev.qatnxfatmount_test.mount: Deactivated successfully. Oct 6 10:05:25 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c022ab81-cd0d-444d-86a6-ee25b01b9d2d. Oct 6 10:05:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:05:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9o3hv5uxmount_test with fs ext2 Oct 6 10:05:35 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 10:05:35 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 331eb38c-f218-4a71-85d3-8ae42deffd18 r/w without journal. Quota mode: none. Oct 6 10:05:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9o3hv5uxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum cryptsetup --header '/tmp/testheaderuRc' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 6 10:05:40 storageqe-109 systemd[1]: tmp-libblockdev.9o3hv5uxmount_test.mount: Deactivated successfully. Oct 6 10:05:40 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 331eb38c-f218-4a71-85d3-8ae42deffd18. Oct 6 10:05:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:05:40 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 10:05:40 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum Oct 6 10:05:40 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --header '/tmp/testheaderuRc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:05:59 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderuRc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:06:09 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:06:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.e3oz_ym5mount_test with fs xfs Oct 6 10:06:29 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem eb23cef7-8957-4e09-8ad5-f1a6ed738b9b Oct 6 10:06:30 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 10:06:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e3oz_ym5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:06:34 storageqe-109 systemd[1]: tmp-libblockdev.e3oz_ym5mount_test.mount: Deactivated successfully. Oct 6 10:06:34 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem eb23cef7-8957-4e09-8ad5-f1a6ed738b9b Oct 6 10:06:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:06:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xixy55hbmount_test with fs ext4 Oct 6 10:06:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 058bd3c4-b22e-459a-970d-8deee08441e8 r/w with ordered data mode. Quota mode: none. Oct 6 10:06:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xixy55hbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:06:49 storageqe-109 systemd[1]: tmp-libblockdev.xixy55hbmount_test.mount: Deactivated successfully. Oct 6 10:06:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 058bd3c4-b22e-459a-970d-8deee08441e8. Oct 6 10:06:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:06:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dkm8fzcgmount_test with fs ext3 Oct 6 10:06:59 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 10:06:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 860d0d3a-0b01-4c01-be3d-ea872d010277 r/w with ordered data mode. Quota mode: none. Oct 6 10:06:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dkm8fzcgmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:07:04 storageqe-109 systemd[1]: tmp-libblockdev.dkm8fzcgmount_test.mount: Deactivated successfully. Oct 6 10:07:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 860d0d3a-0b01-4c01-be3d-ea872d010277. Oct 6 10:07:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:07:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q_hna4yemount_test with fs ext2 Oct 6 10:07:14 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 10:07:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9e7dfc41-e97e-4aa7-aea3-06b688c78a71 r/w without journal. Quota mode: none. Oct 6 10:07:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q_hna4yemount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum Oct 6 10:07:19 storageqe-109 systemd[1]: tmp-libblockdev.q_hna4yemount_test.mount: Deactivated successfully. Oct 6 10:07:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9e7dfc41-e97e-4aa7-aea3-06b688c78a71. Oct 6 10:07:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:07:19 storageqe-109 INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum cryptsetup --header '/tmp/testheaderuRc' --resilience 'journal' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 6 10:07:19 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum Oct 6 10:07:19 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' --resilience 'journal' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --key-size '128' --header '/tmp/testheaderuRc' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:07:36 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --header '/tmp/testheaderuRc' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:07:46 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:07:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.x9knys5fmount_test with fs xfs Oct 6 10:08:06 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 60f821ae-7866-4f25-8faa-cf6b147ef020 Oct 6 10:08:06 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 10:08:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x9knys5fmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:08:12 storageqe-109 systemd[1]: tmp-libblockdev.x9knys5fmount_test.mount: Deactivated successfully. Oct 6 10:08:12 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 60f821ae-7866-4f25-8faa-cf6b147ef020 Oct 6 10:08:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:08:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ro55h6wgmount_test with fs ext4 Oct 6 10:08:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 79fc1446-7187-4a14-b104-3972a5e3924d r/w with ordered data mode. Quota mode: none. Oct 6 10:08:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ro55h6wgmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:08:28 storageqe-109 systemd[1]: tmp-libblockdev.ro55h6wgmount_test.mount: Deactivated successfully. Oct 6 10:08:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 79fc1446-7187-4a14-b104-3972a5e3924d. Oct 6 10:08:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:08:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ot27wvh9mount_test with fs ext3 Oct 6 10:08:38 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 10:08:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ec6dbf55-cc15-4594-9f51-4aa193e833ac r/w with ordered data mode. Quota mode: none. Oct 6 10:08:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ot27wvh9mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:08:44 storageqe-109 systemd[1]: tmp-libblockdev.ot27wvh9mount_test.mount: Deactivated successfully. Oct 6 10:08:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ec6dbf55-cc15-4594-9f51-4aa193e833ac. Oct 6 10:08:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:08:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.w_9p0h3cmount_test with fs ext2 Oct 6 10:08:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 10:08:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c46abe78-2915-49a8-abcb-37ff14ea1360 r/w without journal. Quota mode: none. Oct 6 10:08:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.w_9p0h3cmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum cryptsetup --header '/tmp/testheaderuRc' --resilience 'none' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 6 10:09:00 storageqe-109 systemd[1]: tmp-libblockdev.w_9p0h3cmount_test.mount: Deactivated successfully. Oct 6 10:09:00 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c46abe78-2915-49a8-abcb-37ff14ea1360. Oct 6 10:09:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:09:01 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 10:09:01 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum Oct 6 10:09:01 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' --resilience 'none' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderuRc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:09:18 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderuRc' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:09:28 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:09:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.qjcc_3mkmount_test with fs xfs Oct 6 10:09:48 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 546babcd-f145-461d-ab79-0756971db595 Oct 6 10:09:48 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 10:09:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qjcc_3mkmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:09:54 storageqe-109 systemd[1]: tmp-libblockdev.qjcc_3mkmount_test.mount: Deactivated successfully. Oct 6 10:09:54 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 546babcd-f145-461d-ab79-0756971db595 Oct 6 10:09:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:09:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xkhzc2c7mount_test with fs ext4 Oct 6 10:10:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 146b4bb5-9da7-4875-bb9b-de16a583bbc8 r/w with ordered data mode. Quota mode: none. Oct 6 10:10:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xkhzc2c7mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:10:09 storageqe-109 systemd[1]: tmp-libblockdev.xkhzc2c7mount_test.mount: Deactivated successfully. Oct 6 10:10:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 146b4bb5-9da7-4875-bb9b-de16a583bbc8. Oct 6 10:10:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:10:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zrzq5erzmount_test with fs ext3 Oct 6 10:10:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 10:10:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4f076523-b1ae-4de8-a801-3056da8dd76a r/w with ordered data mode. Quota mode: none. Oct 6 10:10:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zrzq5erzmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:10:25 storageqe-109 systemd[1]: tmp-libblockdev.zrzq5erzmount_test.mount: Deactivated successfully. Oct 6 10:10:25 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4f076523-b1ae-4de8-a801-3056da8dd76a. Oct 6 10:10:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:10:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vyv5lxb5mount_test with fs ext2 Oct 6 10:10:35 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 10:10:35 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ad2d6dd0-23a4-4845-8771-f8d08e180609 r/w without journal. Quota mode: none. Oct 6 10:10:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vyv5lxb5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum cryptsetup --header '/tmp/testheaderuRc' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 6 10:10:40 storageqe-109 systemd[1]: tmp-libblockdev.vyv5lxb5mount_test.mount: Deactivated successfully. Oct 6 10:10:40 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ad2d6dd0-23a4-4845-8771-f8d08e180609. Oct 6 10:10:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:10:40 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 10:10:40 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum Oct 6 10:10:41 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderuRc' --sector-size '4096' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:11:01 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderuRc' --sector-size '4096' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:11:11 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' luksOpen /dev/mapper/npo2linear fPawOAYWum -q cryptsetup --header '/tmp/testheaderuRc' status fPawOAYWum -q Oct 6 10:11:21 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' status fPawOAYWum -q cryptsetup --header '/tmp/testheaderuRc' --resilience 'checksum' --active-name 'fPawOAYWum' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 6 10:11:31 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuRc' --resilience 'checksum' --active-name 'fPawOAYWum' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:11:51 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:11:51 storageqe-109 stratisd[4947]: [2025-10-06T14:11:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:11:51 storageqe-109 stratisd[4947]: [2025-10-06T14:11:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup reencrypt /dev/mapper/npo2linear -q --decrypt Oct 6 10:12:01 storageqe-109 journal: cryptsetup reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --sector-size '512' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:12:11 storageqe-109 journal: cryptsetup --type 'luks2' --sector-size '512' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 6 10:12:11 storageqe-109 stratisd[4947]: [2025-10-06T14:12:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:12:11 storageqe-109 stratisd[4947]: [2025-10-06T14:12:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:12:21 storageqe-109 journal: cryptsetup luksOpen /dev/mapper/npo2linear fPawOAYWum -q Oct 6 10:12:21 storageqe-109 stratisd[4947]: [2025-10-06T14:12:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:12:21 storageqe-109 stratisd[4947]: [2025-10-06T14:12:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:12:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.3z8afgkxmount_test with fs xfs Oct 6 10:12:41 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 013b19f5-3ade-4bec-a02b-5855d2fdcd2b Oct 6 10:12:41 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 6 10:12:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3z8afgkxmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:12:46 storageqe-109 systemd[1]: tmp-libblockdev.3z8afgkxmount_test.mount: Deactivated successfully. Oct 6 10:12:46 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 013b19f5-3ade-4bec-a02b-5855d2fdcd2b Oct 6 10:12:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs xfs in remove_crypt Oct 6 10:12:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x89pqrmxmount_test with fs ext4 Oct 6 10:12:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a2054936-310b-4646-91c5-b74ec2519821 r/w with ordered data mode. Quota mode: none. Oct 6 10:12:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x89pqrmxmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:13:01 storageqe-109 systemd[1]: tmp-libblockdev.x89pqrmxmount_test.mount: Deactivated successfully. Oct 6 10:13:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a2054936-310b-4646-91c5-b74ec2519821. Oct 6 10:13:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext4 in remove_crypt Oct 6 10:13:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9id89ug3mount_test with fs ext3 Oct 6 10:13:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 6 10:13:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 85708518-27a9-423d-80d8-a72ca375cf1d r/w with ordered data mode. Quota mode: none. Oct 6 10:13:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9id89ug3mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:13:16 storageqe-109 systemd[1]: tmp-libblockdev.9id89ug3mount_test.mount: Deactivated successfully. Oct 6 10:13:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 85708518-27a9-423d-80d8-a72ca375cf1d. Oct 6 10:13:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext3 in remove_crypt Oct 6 10:13:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xmgl5apvmount_test with fs ext2 Oct 6 10:13:26 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 6 10:13:26 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 29342a11-d329-4a68-97f5-c45ac4aa7424 r/w without journal. Quota mode: none. Oct 6 10:13:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xmgl5apvmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt INFO: remove crypt device fPawOAYWum INFO: finishe the remove crypt device fPawOAYWum Oct 6 10:13:31 storageqe-109 systemd[1]: tmp-libblockdev.xmgl5apvmount_test.mount: Deactivated successfully. Oct 6 10:13:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 29342a11-d329-4a68-97f5-c45ac4aa7424. Oct 6 10:13:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/fPawOAYWum and fs ext2 in remove_crypt Oct 6 10:13:31 storageqe-109 INFO: remove crypt device fPawOAYWum Oct 6 10:13:31 storageqe-109 INFO: finishe the remove crypt device fPawOAYWum INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_with_header[npo2_linear] #### Oct 6 10:13:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 10:13:36 storageqe-109 INFO: #### END test_reencrypt_with_header[npo2_linear] #### Oct 6 10:13:36 storageqe-109 stratisd[4947]: [2025-10-06T14:13:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:13:36 storageqe-109 stratisd[4947]: [2025-10-06T14:13:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:13:36 storageqe-109 stratisd[4947]: [2025-10-06T14:13:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:13:36 storageqe-109 stratisd[4947]: [2025-10-06T14:13:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:13:37 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 10:13:38 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 10:13:39 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 10:13:39 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 10:13:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 10:13:49 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_luks_intergrity[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 10:13:55 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 10:13:55 storageqe-109 INFO: #### will start test_luks_intergrity[npo2_linear] ##### Oct 6 10:13:55 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 512, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:14:00 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 512, 1, None Oct 6 10:14:00 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:14:00 storageqe-109 stratisd[4947]: [2025-10-06T14:14:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:14:00 storageqe-109 stratisd[4947]: [2025-10-06T14:14:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:14:04 storageqe-109 stratisd[4947]: [2025-10-06T14:14:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:14:04 storageqe-109 stratisd[4947]: [2025-10-06T14:14:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:14:09 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:14:14 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:14:14 storageqe-109 stratisd[4947]: [2025-10-06T14:14:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:14:14 storageqe-109 stratisd[4947]: [2025-10-06T14:14:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:14:24 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:14:34 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:14:44 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:14:54 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q Oct 6 10:15:04 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:15:14 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:15:24 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:15:34 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:15:45 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:15:55 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:16:05 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:16:05 storageqe-109 stratisd[4947]: [2025-10-06T14:16:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:16:05 storageqe-109 stratisd[4947]: [2025-10-06T14:16:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-plain64, hmac-sha256, 256, 512, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:16:15 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 512, 1, None Oct 6 10:16:15 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:16:15 storageqe-109 stratisd[4947]: [2025-10-06T14:16:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:16:15 storageqe-109 stratisd[4947]: [2025-10-06T14:16:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:16:15 storageqe-109 kernel: alg: No test for authenc(hmac(sha256),xts(aes)) (authenc(hmac(sha256-ni),xts-aes-vaes-avx2)) Oct 6 10:16:19 storageqe-109 stratisd[4947]: [2025-10-06T14:16:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:16:19 storageqe-109 stratisd[4947]: [2025-10-06T14:16:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:16:29 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:16:29 storageqe-109 stratisd[4947]: [2025-10-06T14:16:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:16:29 storageqe-109 stratisd[4947]: [2025-10-06T14:16:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:16:39 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:16:49 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:16:59 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:17:09 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q Oct 6 10:17:20 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:17:30 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:17:40 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:17:50 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:18:00 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:18:10 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:18:20 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:18:20 storageqe-109 stratisd[4947]: [2025-10-06T14:18:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:18:20 storageqe-109 stratisd[4947]: [2025-10-06T14:18:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 256, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:18:30 storageqe-109 INFO: aes-xts-random, hmac-sha256, 256, 512, None, None Oct 6 10:18:30 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:18:30 storageqe-109 stratisd[4947]: [2025-10-06T14:18:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:18:30 storageqe-109 stratisd[4947]: [2025-10-06T14:18:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:18:35 storageqe-109 stratisd[4947]: [2025-10-06T14:18:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:18:35 storageqe-109 stratisd[4947]: [2025-10-06T14:18:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:18:45 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:18:45 storageqe-109 stratisd[4947]: [2025-10-06T14:18:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:18:45 storageqe-109 stratisd[4947]: [2025-10-06T14:18:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:18:55 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:19:05 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:19:15 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:19:25 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:19:35 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 512, None, None Oct 6 10:19:36 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:19:36 storageqe-109 stratisd[4947]: [2025-10-06T14:19:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:19:36 storageqe-109 stratisd[4947]: [2025-10-06T14:19:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:19:41 storageqe-109 stratisd[4947]: [2025-10-06T14:19:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:19:41 storageqe-109 stratisd[4947]: [2025-10-06T14:19:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:19:51 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:19:51 storageqe-109 stratisd[4947]: [2025-10-06T14:19:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:19:51 storageqe-109 stratisd[4947]: [2025-10-06T14:19:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:20:01 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:20:11 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:20:21 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:20:31 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 512, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:20:41 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 512, None, None Oct 6 10:20:41 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:20:42 storageqe-109 stratisd[4947]: [2025-10-06T14:20:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:20:42 storageqe-109 stratisd[4947]: [2025-10-06T14:20:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:20:46 storageqe-109 stratisd[4947]: [2025-10-06T14:20:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:20:46 storageqe-109 stratisd[4947]: [2025-10-06T14:20:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:20:56 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:20:56 storageqe-109 stratisd[4947]: [2025-10-06T14:20:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:20:56 storageqe-109 stratisd[4947]: [2025-10-06T14:20:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:21:06 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:21:16 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:21:26 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:21:36 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-random, hmac-sha256, 512, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:21:46 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 512, None, None Oct 6 10:21:46 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:21:46 storageqe-109 stratisd[4947]: [2025-10-06T14:21:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:21:46 storageqe-109 stratisd[4947]: [2025-10-06T14:21:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:21:52 storageqe-109 stratisd[4947]: [2025-10-06T14:21:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:21:52 storageqe-109 stratisd[4947]: [2025-10-06T14:21:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:22:02 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:22:02 storageqe-109 stratisd[4947]: [2025-10-06T14:22:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:22:02 storageqe-109 stratisd[4947]: [2025-10-06T14:22:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:22:12 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:22:22 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:22:32 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:22:42 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:22:52 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, None Oct 6 10:22:52 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:22:52 storageqe-109 stratisd[4947]: [2025-10-06T14:22:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:22:52 storageqe-109 stratisd[4947]: [2025-10-06T14:22:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:22:55 storageqe-109 stratisd[4947]: [2025-10-06T14:22:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:22:55 storageqe-109 stratisd[4947]: [2025-10-06T14:22:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:23:05 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:23:05 storageqe-109 stratisd[4947]: [2025-10-06T14:23:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:23:05 storageqe-109 stratisd[4947]: [2025-10-06T14:23:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:23:15 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:23:25 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:23:35 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:23:45 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:23:56 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, None Oct 6 10:23:56 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:23:56 storageqe-109 stratisd[4947]: [2025-10-06T14:23:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:23:56 storageqe-109 stratisd[4947]: [2025-10-06T14:23:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:23:58 storageqe-109 stratisd[4947]: [2025-10-06T14:23:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:23:58 storageqe-109 stratisd[4947]: [2025-10-06T14:23:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:24:08 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:24:09 storageqe-109 stratisd[4947]: [2025-10-06T14:24:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:24:09 storageqe-109 stratisd[4947]: [2025-10-06T14:24:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:24:19 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:24:29 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:24:39 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:24:49 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:24:59 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None Oct 6 10:24:59 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:24:59 storageqe-109 stratisd[4947]: [2025-10-06T14:24:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:24:59 storageqe-109 stratisd[4947]: [2025-10-06T14:24:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:25:02 storageqe-109 stratisd[4947]: [2025-10-06T14:25:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:25:02 storageqe-109 stratisd[4947]: [2025-10-06T14:25:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:25:12 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:25:12 storageqe-109 stratisd[4947]: [2025-10-06T14:25:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:25:12 storageqe-109 stratisd[4947]: [2025-10-06T14:25:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:25:22 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:25:32 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:25:42 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:25:52 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:26:02 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, None Oct 6 10:26:02 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:26:02 storageqe-109 stratisd[4947]: [2025-10-06T14:26:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:26:02 storageqe-109 stratisd[4947]: [2025-10-06T14:26:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:26:05 storageqe-109 stratisd[4947]: [2025-10-06T14:26:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:26:05 storageqe-109 stratisd[4947]: [2025-10-06T14:26:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:26:15 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:26:15 storageqe-109 stratisd[4947]: [2025-10-06T14:26:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:26:15 storageqe-109 stratisd[4947]: [2025-10-06T14:26:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:26:25 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:26:35 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:26:45 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:26:55 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q Oct 6 10:27:05 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:27:15 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:27:25 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:27:35 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:27:45 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:27:55 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:28:05 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:28:06 storageqe-109 stratisd[4947]: [2025-10-06T14:28:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:28:06 storageqe-109 stratisd[4947]: [2025-10-06T14:28:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:28:16 storageqe-109 INFO: aes-xts-random, hmac-sha256, 256, 4096, None, None Oct 6 10:28:16 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:28:16 storageqe-109 stratisd[4947]: [2025-10-06T14:28:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:28:16 storageqe-109 stratisd[4947]: [2025-10-06T14:28:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:28:19 storageqe-109 stratisd[4947]: [2025-10-06T14:28:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:28:19 storageqe-109 stratisd[4947]: [2025-10-06T14:28:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:28:29 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:28:29 storageqe-109 stratisd[4947]: [2025-10-06T14:28:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:28:29 storageqe-109 stratisd[4947]: [2025-10-06T14:28:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:28:39 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:28:49 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:28:59 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:29:09 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:29:19 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None Oct 6 10:29:19 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:29:19 storageqe-109 stratisd[4947]: [2025-10-06T14:29:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:29:19 storageqe-109 stratisd[4947]: [2025-10-06T14:29:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:29:23 storageqe-109 stratisd[4947]: [2025-10-06T14:29:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:29:23 storageqe-109 stratisd[4947]: [2025-10-06T14:29:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:29:33 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:29:33 storageqe-109 stratisd[4947]: [2025-10-06T14:29:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:29:33 storageqe-109 stratisd[4947]: [2025-10-06T14:29:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:29:43 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:29:53 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:30:03 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:30:13 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:30:23 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None Oct 6 10:30:23 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:30:23 storageqe-109 stratisd[4947]: [2025-10-06T14:30:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:30:23 storageqe-109 stratisd[4947]: [2025-10-06T14:30:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:30:26 storageqe-109 stratisd[4947]: [2025-10-06T14:30:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:30:26 storageqe-109 stratisd[4947]: [2025-10-06T14:30:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:30:36 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:30:36 storageqe-109 stratisd[4947]: [2025-10-06T14:30:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:30:36 storageqe-109 stratisd[4947]: [2025-10-06T14:30:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:30:46 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:30:56 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:31:06 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:31:16 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:31:26 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None Oct 6 10:31:26 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:31:26 storageqe-109 stratisd[4947]: [2025-10-06T14:31:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:31:26 storageqe-109 stratisd[4947]: [2025-10-06T14:31:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:31:29 storageqe-109 stratisd[4947]: [2025-10-06T14:31:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:31:29 storageqe-109 stratisd[4947]: [2025-10-06T14:31:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:31:39 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:31:39 storageqe-109 stratisd[4947]: [2025-10-06T14:31:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:31:39 storageqe-109 stratisd[4947]: [2025-10-06T14:31:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:31:49 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:31:59 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:32:09 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:32:19 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 512, 4096, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:32:29 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 4096, 1, None Oct 6 10:32:29 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:32:30 storageqe-109 stratisd[4947]: [2025-10-06T14:32:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:32:30 storageqe-109 stratisd[4947]: [2025-10-06T14:32:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:32:32 storageqe-109 stratisd[4947]: [2025-10-06T14:32:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:32:32 storageqe-109 stratisd[4947]: [2025-10-06T14:32:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:32:42 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:32:42 storageqe-109 stratisd[4947]: [2025-10-06T14:32:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:32:42 storageqe-109 stratisd[4947]: [2025-10-06T14:32:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:32:52 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:33:02 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:33:12 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:33:22 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q Oct 6 10:33:33 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:33:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:33:53 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:34:03 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:34:13 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:34:23 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:34:33 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:34:33 storageqe-109 stratisd[4947]: [2025-10-06T14:34:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:34:33 storageqe-109 stratisd[4947]: [2025-10-06T14:34:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:34:43 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None Oct 6 10:34:43 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:34:43 storageqe-109 stratisd[4947]: [2025-10-06T14:34:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:34:43 storageqe-109 stratisd[4947]: [2025-10-06T14:34:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:34:46 storageqe-109 stratisd[4947]: [2025-10-06T14:34:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:34:46 storageqe-109 stratisd[4947]: [2025-10-06T14:34:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:34:56 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:34:56 storageqe-109 stratisd[4947]: [2025-10-06T14:34:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:34:56 storageqe-109 stratisd[4947]: [2025-10-06T14:34:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:35:06 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:35:16 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:35:26 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:35:36 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:35:46 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None Oct 6 10:35:46 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:35:46 storageqe-109 stratisd[4947]: [2025-10-06T14:35:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:35:46 storageqe-109 stratisd[4947]: [2025-10-06T14:35:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:35:50 storageqe-109 stratisd[4947]: [2025-10-06T14:35:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:35:50 storageqe-109 stratisd[4947]: [2025-10-06T14:35:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:36:00 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:36:00 storageqe-109 stratisd[4947]: [2025-10-06T14:36:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:36:00 storageqe-109 stratisd[4947]: [2025-10-06T14:36:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:36:10 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:36:20 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:36:30 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:36:40 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:36:50 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None Oct 6 10:36:50 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:36:50 storageqe-109 stratisd[4947]: [2025-10-06T14:36:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:36:50 storageqe-109 stratisd[4947]: [2025-10-06T14:36:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:36:53 storageqe-109 stratisd[4947]: [2025-10-06T14:36:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:36:53 storageqe-109 stratisd[4947]: [2025-10-06T14:36:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:37:03 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:37:03 storageqe-109 stratisd[4947]: [2025-10-06T14:37:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:37:03 storageqe-109 stratisd[4947]: [2025-10-06T14:37:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:37:13 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:37:23 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:37:33 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:37:43 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-gcm-random, aead, 128, 512, None, None cryptsetup --integrity 'aead' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:37:54 storageqe-109 INFO: aes-gcm-random, aead, 128, 512, None, None Oct 6 10:37:54 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:37:54 storageqe-109 stratisd[4947]: [2025-10-06T14:37:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:37:54 storageqe-109 stratisd[4947]: [2025-10-06T14:37:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:37:58 storageqe-109 stratisd[4947]: [2025-10-06T14:37:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:37:58 storageqe-109 stratisd[4947]: [2025-10-06T14:37:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:38:08 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:38:08 storageqe-109 stratisd[4947]: [2025-10-06T14:38:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:38:08 storageqe-109 stratisd[4947]: [2025-10-06T14:38:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:38:18 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:38:28 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:38:38 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:38:48 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-gcm-random, aead, 128, 4096, None, None cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:38:58 storageqe-109 INFO: aes-gcm-random, aead, 128, 4096, None, None Oct 6 10:38:58 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:38:58 storageqe-109 stratisd[4947]: [2025-10-06T14:38:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:38:58 storageqe-109 stratisd[4947]: [2025-10-06T14:38:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:39:01 storageqe-109 stratisd[4947]: [2025-10-06T14:39:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:39:01 storageqe-109 stratisd[4947]: [2025-10-06T14:39:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:39:11 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:39:11 storageqe-109 stratisd[4947]: [2025-10-06T14:39:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:39:11 storageqe-109 stratisd[4947]: [2025-10-06T14:39:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:39:21 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:39:31 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:39:41 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:39:51 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-gcm-random, aead, 256, 4096, None, None cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:40:01 storageqe-109 INFO: aes-gcm-random, aead, 256, 4096, None, None Oct 6 10:40:01 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:40:01 storageqe-109 stratisd[4947]: [2025-10-06T14:40:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:40:01 storageqe-109 stratisd[4947]: [2025-10-06T14:40:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:40:04 storageqe-109 stratisd[4947]: [2025-10-06T14:40:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:40:04 storageqe-109 stratisd[4947]: [2025-10-06T14:40:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:40:14 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:40:14 storageqe-109 stratisd[4947]: [2025-10-06T14:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:40:14 storageqe-109 stratisd[4947]: [2025-10-06T14:40:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:40:24 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:40:34 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:40:44 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:40:54 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: chacha20-plain64, poly1305, 256, 512, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:41:04 storageqe-109 INFO: chacha20-plain64, poly1305, 256, 512, None, None Oct 6 10:41:04 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:41:04 storageqe-109 stratisd[4947]: [2025-10-06T14:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:41:04 storageqe-109 stratisd[4947]: [2025-10-06T14:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:41:08 storageqe-109 stratisd[4947]: [2025-10-06T14:41:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:41:08 storageqe-109 stratisd[4947]: [2025-10-06T14:41:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:41:18 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:41:18 storageqe-109 stratisd[4947]: [2025-10-06T14:41:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:41:18 storageqe-109 stratisd[4947]: [2025-10-06T14:41:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:41:28 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:41:38 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:41:48 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:41:58 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: chacha20-random, poly1305, 256, 512, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:42:09 storageqe-109 INFO: chacha20-random, poly1305, 256, 512, None, None Oct 6 10:42:09 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:42:09 storageqe-109 stratisd[4947]: [2025-10-06T14:42:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:42:09 storageqe-109 stratisd[4947]: [2025-10-06T14:42:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:42:13 storageqe-109 stratisd[4947]: [2025-10-06T14:42:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:42:13 storageqe-109 stratisd[4947]: [2025-10-06T14:42:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:42:23 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:42:23 storageqe-109 stratisd[4947]: [2025-10-06T14:42:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:42:23 storageqe-109 stratisd[4947]: [2025-10-06T14:42:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:42:34 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:42:44 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:42:54 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:43:04 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: chacha20-plain64, poly1305, 256, 4096, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:43:14 storageqe-109 INFO: chacha20-plain64, poly1305, 256, 4096, None, None Oct 6 10:43:14 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:43:14 storageqe-109 stratisd[4947]: [2025-10-06T14:43:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:43:14 storageqe-109 stratisd[4947]: [2025-10-06T14:43:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:43:17 storageqe-109 stratisd[4947]: [2025-10-06T14:43:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:43:17 storageqe-109 stratisd[4947]: [2025-10-06T14:43:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:43:27 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:43:27 storageqe-109 stratisd[4947]: [2025-10-06T14:43:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:43:27 storageqe-109 stratisd[4947]: [2025-10-06T14:43:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:43:37 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:43:47 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:43:57 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:44:07 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: chacha20-random, poly1305, 256, 4096, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:44:17 storageqe-109 INFO: chacha20-random, poly1305, 256, 4096, None, None Oct 6 10:44:17 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:44:17 storageqe-109 stratisd[4947]: [2025-10-06T14:44:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:44:17 storageqe-109 stratisd[4947]: [2025-10-06T14:44:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:44:20 storageqe-109 stratisd[4947]: [2025-10-06T14:44:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:44:20 storageqe-109 stratisd[4947]: [2025-10-06T14:44:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:44:30 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:44:30 storageqe-109 stratisd[4947]: [2025-10-06T14:44:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:44:30 storageqe-109 stratisd[4947]: [2025-10-06T14:44:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:44:40 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:44:50 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:45:00 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:45:10 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: the add_device_inline device dm-3 support npo2 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:45:20 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 6 10:45:20 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True Oct 6 10:45:20 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:45:20 storageqe-109 stratisd[4947]: [2025-10-06T14:45:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:45:20 storageqe-109 stratisd[4947]: [2025-10-06T14:45:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:45:23 storageqe-109 stratisd[4947]: [2025-10-06T14:45:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:45:23 storageqe-109 stratisd[4947]: [2025-10-06T14:45:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:45:33 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:45:33 storageqe-109 stratisd[4947]: [2025-10-06T14:45:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:45:33 storageqe-109 stratisd[4947]: [2025-10-06T14:45:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:45:43 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:45:53 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:46:03 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:46:13 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:46:23 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, True Oct 6 10:46:23 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:46:23 storageqe-109 stratisd[4947]: [2025-10-06T14:46:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:46:23 storageqe-109 stratisd[4947]: [2025-10-06T14:46:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:46:26 storageqe-109 stratisd[4947]: [2025-10-06T14:46:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:46:26 storageqe-109 stratisd[4947]: [2025-10-06T14:46:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:46:36 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:46:36 storageqe-109 stratisd[4947]: [2025-10-06T14:46:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:46:36 storageqe-109 stratisd[4947]: [2025-10-06T14:46:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:46:46 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:46:56 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:47:06 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:47:16 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:47:26 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, True Oct 6 10:47:26 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:47:26 storageqe-109 stratisd[4947]: [2025-10-06T14:47:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:47:26 storageqe-109 stratisd[4947]: [2025-10-06T14:47:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:47:29 storageqe-109 stratisd[4947]: [2025-10-06T14:47:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:47:29 storageqe-109 stratisd[4947]: [2025-10-06T14:47:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:47:39 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:47:39 storageqe-109 stratisd[4947]: [2025-10-06T14:47:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:47:39 storageqe-109 stratisd[4947]: [2025-10-06T14:47:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:47:49 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:47:59 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:48:09 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:48:19 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q Oct 6 10:48:29 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:48:39 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' --header '/home/backfileOGCZhmoIdE' open /dev/mapper/npo2linear OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:48:49 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:48:59 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q Oct 6 10:49:09 storageqe-109 journal: cryptsetup --header '/home/backfileOGCZhmoIdE' status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:49:19 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:49:29 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfileOGCZhmoIdE' --key-file '/tmp/testfileFoU' luksHeaderRestore /dev/mapper/npo2linear -q Oct 6 10:49:29 storageqe-109 stratisd[4947]: [2025-10-06T14:49:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:49:29 storageqe-109 stratisd[4947]: [2025-10-06T14:49:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 256, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:49:39 storageqe-109 INFO: aes-xts-random, hmac-sha256, 256, 4096, None, True Oct 6 10:49:39 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:49:39 storageqe-109 stratisd[4947]: [2025-10-06T14:49:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:49:39 storageqe-109 stratisd[4947]: [2025-10-06T14:49:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:49:42 storageqe-109 stratisd[4947]: [2025-10-06T14:49:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:49:42 storageqe-109 stratisd[4947]: [2025-10-06T14:49:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:49:52 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:49:52 storageqe-109 stratisd[4947]: [2025-10-06T14:49:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:49:52 storageqe-109 stratisd[4947]: [2025-10-06T14:49:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:50:02 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:50:12 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:50:22 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:50:32 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:50:42 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True Oct 6 10:50:42 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:50:42 storageqe-109 stratisd[4947]: [2025-10-06T14:50:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:50:42 storageqe-109 stratisd[4947]: [2025-10-06T14:50:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:50:45 storageqe-109 stratisd[4947]: [2025-10-06T14:50:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:50:45 storageqe-109 stratisd[4947]: [2025-10-06T14:50:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:50:55 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:50:55 storageqe-109 stratisd[4947]: [2025-10-06T14:50:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:50:55 storageqe-109 stratisd[4947]: [2025-10-06T14:50:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:51:06 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:51:16 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:51:26 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:51:36 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: aes-gcm-random, aead, 256, 4096, None, True cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:51:46 storageqe-109 INFO: aes-gcm-random, aead, 256, 4096, None, True Oct 6 10:51:46 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:51:46 storageqe-109 stratisd[4947]: [2025-10-06T14:51:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:51:46 storageqe-109 stratisd[4947]: [2025-10-06T14:51:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:51:48 storageqe-109 stratisd[4947]: [2025-10-06T14:51:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:51:48 storageqe-109 stratisd[4947]: [2025-10-06T14:51:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:51:58 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:51:58 storageqe-109 stratisd[4947]: [2025-10-06T14:51:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:51:58 storageqe-109 stratisd[4947]: [2025-10-06T14:51:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:52:08 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:52:18 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:52:28 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:52:38 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: chacha20-plain64, poly1305, 256, 4096, None, True cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:52:49 storageqe-109 INFO: chacha20-plain64, poly1305, 256, 4096, None, True Oct 6 10:52:49 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfileFoU' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 10:52:49 storageqe-109 stratisd[4947]: [2025-10-06T14:52:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:52:49 storageqe-109 stratisd[4947]: [2025-10-06T14:52:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:52:51 storageqe-109 stratisd[4947]: [2025-10-06T14:52:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:52:51 storageqe-109 stratisd[4947]: [2025-10-06T14:52:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:53:01 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileFoU' open /dev/mapper/npo2linear OGCZhmoIdE -q Oct 6 10:53:01 storageqe-109 stratisd[4947]: [2025-10-06T14:53:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 10:53:01 storageqe-109 stratisd[4947]: [2025-10-06T14:53:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OGCZhmoIdE -q Oct 6 10:53:11 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:53:21 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup status OGCZhmoIdE -q Oct 6 10:53:31 storageqe-109 journal: cryptsetup status OGCZhmoIdE -q cryptsetup close OGCZhmoIdE -q Oct 6 10:53:41 storageqe-109 journal: cryptsetup close OGCZhmoIdE -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_intergrity[npo2_linear] #### INFO: #### will start test_dm_integrity_format[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 10:53:56 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 10:53:56 storageqe-109 INFO: #### END test_luks_intergrity[npo2_linear] #### Oct 6 10:53:56 storageqe-109 INFO: #### will start test_dm_integrity_format[npo2_linear] ##### Oct 6 10:53:56 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:54:02 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:54:19 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:54:29 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:54:39 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 10:54:49 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 10:55:14 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 10:55:24 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 10:55:34 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 10:55:44 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 10:56:01 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 10:56:21 storageqe-109 journal: integritysetup close poFdIvrOzN -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:56:31 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:56:45 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:56:55 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:57:05 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 10:57:15 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 10:57:38 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 10:57:48 storageqe-109 journal: integritysetup status poFdIvrOzN -q Oct 6 10:57:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 10:57:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 10:57:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. integritysetup status poFdIvrOzN -q Oct 6 10:57:58 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 10:58:08 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 10:58:24 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 10:58:42 storageqe-109 journal: integritysetup close poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 10:58:52 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:59:06 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:59:16 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 10:59:26 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 10:59:36 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:00:00 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:00:10 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:00:20 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:00:30 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:00:45 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 11:01:04 storageqe-109 journal: integritysetup close poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 6 11:01:14 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:01:28 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:01:38 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:01:48 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:01:58 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:02:22 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:02:32 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:02:42 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:02:52 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:03:07 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 11:03:26 storageqe-109 journal: integritysetup close poFdIvrOzN -q INFO: the add_device_inline device dm-3 support npo2 integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 11:03:36 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 6 11:03:36 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:03:50 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:04:00 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:04:10 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:04:20 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:04:44 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:04:54 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:05:04 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:05:14 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:05:30 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 11:05:48 storageqe-109 journal: integritysetup close poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 11:05:58 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:06:13 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:06:23 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:06:33 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:06:43 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:06:43 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 11:06:44 storageqe-109 dnf[1073554]: Updating Subscription Management repositories. Oct 6 11:06:44 storageqe-109 dnf[1073554]: Unable to read consumer identity Oct 6 11:06:44 storageqe-109 dnf[1073554]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 11:06:44 storageqe-109 dnf[1073554]: Metadata cache refreshed recently. Oct 6 11:06:44 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 11:06:44 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. integritysetup status poFdIvrOzN -q Oct 6 11:07:07 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:07:17 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:07:27 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:07:37 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:07:53 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '32' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 11:08:11 storageqe-109 journal: integritysetup close poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 11:08:22 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:08:37 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:08:47 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:08:57 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:09:07 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:09:30 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:09:40 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:09:50 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:10:00 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:10:16 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilelnF' --integrity-key-size '4096' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 11:10:35 storageqe-109 journal: integritysetup close poFdIvrOzN -q integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 6 11:10:45 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:10:59 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:11:09 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 6 11:11:19 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:11:29 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:11:53 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:12:03 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:12:13 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup status poFdIvrOzN -q Oct 6 11:12:23 storageqe-109 journal: integritysetup status poFdIvrOzN -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear poFdIvrOzN -q Oct 6 11:12:38 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear poFdIvrOzN -q integritysetup close poFdIvrOzN -q Oct 6 11:12:56 storageqe-109 journal: integritysetup close poFdIvrOzN -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_integrity_format[npo2_linear] #### INFO: #### will start test_integrity_error_detection[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:13:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:13:11 storageqe-109 INFO: #### END test_dm_integrity_format[npo2_linear] #### Oct 6 11:13:11 storageqe-109 INFO: #### will start test_integrity_error_detection[npo2_linear] ##### Oct 6 11:13:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:13:16 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:13:29 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:13:39 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:14:02 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:14:02 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:14:02 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:14:02 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 6 11:14:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:14:12 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:14:12 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:14:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:14:12 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 11:14:22 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:14:35 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:14:45 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:15:03 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:15:03 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:15:03 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:15:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:15:13 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:15:13 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:15:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:15:13 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:15:23 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:15:36 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:15:46 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:16:08 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:16:08 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:16:08 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:16:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:16:18 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:16:18 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:16:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:16:18 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 11:16:29 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:16:41 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:16:51 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:17:10 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:17:10 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:17:10 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:17:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:17:20 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:17:20 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:17:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:17:20 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:17:30 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:17:45 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:17:55 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:18:34 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:18:34 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:18:34 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:18:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:18:45 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:18:45 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:18:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:18:45 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' format /dev/mapper/npo2linear -q Oct 6 11:18:55 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:19:10 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:19:20 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:19:59 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:19:59 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:19:59 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:19:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:20:09 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:20:09 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:20:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:20:09 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 11:20:19 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 11:20:19 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 11:20:20 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 11:20:20 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:20:33 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:20:43 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:21:04 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:21:04 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:21:04 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:21:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:21:14 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:21:14 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:21:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:21:14 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:21:24 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:21:41 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:21:51 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:22:43 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:22:43 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:22:43 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:22:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:22:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:22:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:22:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:22:53 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 6 11:23:03 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:23:17 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:23:27 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:23:49 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:23:49 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:23:49 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:23:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:23:59 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:23:59 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:23:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:23:59 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:24:09 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:24:27 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:24:37 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:25:29 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:25:29 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:25:29 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:25:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:25:40 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:25:40 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:25:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:25:40 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:25:50 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:26:04 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:26:14 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:26:36 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:26:36 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:26:36 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:26:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:26:46 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:26:46 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:26:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:26:46 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -B -q Oct 6 11:26:56 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:27:09 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B integritysetup close NroatDMlQU -q Oct 6 11:27:19 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:27:41 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:27:41 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:27:41 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:27:51 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:27:51 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:27:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:27:51 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -B -q Oct 6 11:28:01 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:28:14 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B integritysetup close NroatDMlQU -q Oct 6 11:28:24 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:28:42 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:28:43 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:28:43 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:28:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:28:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:28:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:28:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:28:53 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -B -q Oct 6 11:29:03 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:29:20 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B integritysetup close NroatDMlQU -q Oct 6 11:29:30 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:30:21 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:30:22 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:30:22 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:30:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:30:32 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:30:32 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:30:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:30:32 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -B -q Oct 6 11:30:42 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:30:55 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B integritysetup close NroatDMlQU -q Oct 6 11:31:06 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:31:28 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:31:28 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:31:28 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:31:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:31:38 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:31:38 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:31:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:31:38 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q Oct 6 11:31:48 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:32:06 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B integritysetup close NroatDMlQU -q Oct 6 11:32:16 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:33:08 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:33:08 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:33:08 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:33:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:33:18 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:33:18 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:33:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:33:18 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q Oct 6 11:33:28 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:33:42 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B integritysetup close NroatDMlQU -q Oct 6 11:33:52 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:34:14 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q -B Oct 6 11:34:14 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:34:14 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:34:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:34:24 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:34:24 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 6 11:34:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:34:24 storageqe-109 journal: integritysetup close NroatDMlQU -q INFO: the add_device_inline device dm-3 support npo2 integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 6 11:34:34 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 6 11:34:34 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:34:47 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:34:57 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:35:14 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:35:14 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:35:14 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:35:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:35:24 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:35:24 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:35:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:35:24 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 6 11:35:34 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:35:47 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:35:57 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:36:14 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:36:14 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:36:14 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:36:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:36:24 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:36:24 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:36:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:36:24 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 6 11:36:35 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:36:49 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:36:59 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:37:16 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:37:16 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:37:16 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:37:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:37:26 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:37:26 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:37:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:37:26 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 6 11:37:36 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:37:51 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:38:01 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:38:19 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:38:19 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:38:19 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:38:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:38:29 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:38:29 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:38:29 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-inline Oct 6 11:38:39 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:38:54 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q integritysetup close NroatDMlQU -q Oct 6 11:39:04 storageqe-109 journal: integritysetup close NroatDMlQU -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:39:21 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilevKa' --integrity-key-size '32' open /dev/mapper/npo2linear NroatDMlQU --integrity-no-journal -q Oct 6 11:39:21 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:39:21 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:39:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close NroatDMlQU -q Oct 6 11:39:31 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:39:31 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 6 11:39:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 11:39:31 storageqe-109 journal: integritysetup close NroatDMlQU -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_error_detection[npo2_linear] #### INFO: #### will start test_integrity_int_journal[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:39:46 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:39:46 storageqe-109 INFO: #### END test_integrity_error_detection[npo2_linear] #### Oct 6 11:39:46 storageqe-109 INFO: #### will start test_integrity_int_journal[npo2_linear] ##### Oct 6 11:39:46 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32' --sector-size '512' --tag-size '4' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:39:51 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '512' --tag-size '4' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' open /dev/mapper/npo2linear CFsBMkTbKI -q Oct 6 11:40:04 storageqe-109 journal: integritysetup --integrity 'crc32' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' open /dev/mapper/npo2linear CFsBMkTbKI -q integritysetup close CFsBMkTbKI -q Oct 6 11:40:14 storageqe-109 journal: integritysetup close CFsBMkTbKI -q integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '20' format /dev/mapper/npo2linear -q Oct 6 11:40:24 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '20' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '20' open /dev/mapper/npo2linear CFsBMkTbKI -q Oct 6 11:40:38 storageqe-109 journal: integritysetup --integrity 'sha256' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '20' open /dev/mapper/npo2linear CFsBMkTbKI -q integritysetup close CFsBMkTbKI -q Oct 6 11:40:48 storageqe-109 journal: integritysetup close CFsBMkTbKI -q integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:40:58 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' open /dev/mapper/npo2linear CFsBMkTbKI -q Oct 6 11:41:14 storageqe-109 journal: integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '32' open /dev/mapper/npo2linear CFsBMkTbKI -q integritysetup close CFsBMkTbKI -q Oct 6 11:41:24 storageqe-109 journal: integritysetup close CFsBMkTbKI -q integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '4096' format /dev/mapper/npo2linear -q Oct 6 11:41:34 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '4096' open /dev/mapper/npo2linear CFsBMkTbKI -q Oct 6 11:41:49 storageqe-109 journal: integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilewQH' --journal-integrity-key-size '4096' open /dev/mapper/npo2linear CFsBMkTbKI -q integritysetup close CFsBMkTbKI -q Oct 6 11:41:59 storageqe-109 journal: integritysetup close CFsBMkTbKI -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_int_journal[npo2_linear] #### INFO: #### will start test_integrity_int_journal_crypt[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:42:14 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:42:14 storageqe-109 INFO: #### END test_integrity_int_journal[npo2_linear] #### Oct 6 11:42:14 storageqe-109 INFO: #### will start test_integrity_int_journal_crypt[npo2_linear] ##### Oct 6 11:42:14 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:42:19 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' open /dev/mapper/npo2linear lGSeDjLuxN -q Oct 6 11:42:32 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' open /dev/mapper/npo2linear lGSeDjLuxN -q integritysetup close lGSeDjLuxN -q Oct 6 11:42:42 storageqe-109 journal: integritysetup close lGSeDjLuxN -q integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q Oct 6 11:42:52 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' open /dev/mapper/npo2linear lGSeDjLuxN -q Oct 6 11:43:05 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' open /dev/mapper/npo2linear lGSeDjLuxN -q integritysetup close lGSeDjLuxN -q Oct 6 11:43:15 storageqe-109 journal: integritysetup close lGSeDjLuxN -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:43:25 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' open /dev/mapper/npo2linear lGSeDjLuxN -q Oct 6 11:43:38 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '32' open /dev/mapper/npo2linear lGSeDjLuxN -q integritysetup close lGSeDjLuxN -q Oct 6 11:43:48 storageqe-109 journal: integritysetup close lGSeDjLuxN -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q Oct 6 11:43:58 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' open /dev/mapper/npo2linear lGSeDjLuxN -q Oct 6 11:44:11 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilexNG' --journal-crypt-key-size '16' open /dev/mapper/npo2linear lGSeDjLuxN -q integritysetup close lGSeDjLuxN -q Oct 6 11:44:21 storageqe-109 journal: integritysetup close lGSeDjLuxN -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_int_journal_crypt[npo2_linear] #### INFO: #### will start test_integrity_int_mode[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:44:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:44:36 storageqe-109 INFO: #### END test_integrity_int_journal_crypt[npo2_linear] #### Oct 6 11:44:36 storageqe-109 INFO: #### will start test_integrity_int_mode[npo2_linear] ##### Oct 6 11:44:36 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:44:41 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qMtjWDhQoL -q Oct 6 11:44:54 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:45:04 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:45:14 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:45:24 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal Oct 6 11:45:34 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal integritysetup status qMtjWDhQoL -q Oct 6 11:45:44 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:45:54 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:46:04 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:46:14 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode Oct 6 11:46:24 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode integritysetup status qMtjWDhQoL -q Oct 6 11:46:34 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:46:44 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:46:54 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'crc32' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:47:04 storageqe-109 journal: integritysetup --integrity 'crc32' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qMtjWDhQoL -q Oct 6 11:47:17 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:47:27 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:47:37 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:47:47 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal Oct 6 11:47:57 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal integritysetup status qMtjWDhQoL -q Oct 6 11:48:07 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:48:17 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:48:27 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:48:37 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode Oct 6 11:48:47 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode integritysetup status qMtjWDhQoL -q Oct 6 11:48:58 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:49:08 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:49:18 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'sha1' --tag-size '20' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:49:28 storageqe-109 journal: integritysetup --integrity 'sha1' --tag-size '20' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qMtjWDhQoL -q Oct 6 11:49:43 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:49:53 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:50:03 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:50:13 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal Oct 6 11:50:23 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal integritysetup status qMtjWDhQoL -q Oct 6 11:50:33 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:50:43 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:50:53 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:51:03 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode Oct 6 11:51:13 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode integritysetup status qMtjWDhQoL -q Oct 6 11:51:23 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:51:33 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:51:43 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '512' format /dev/mapper/npo2linear -q Oct 6 11:51:53 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qMtjWDhQoL -q Oct 6 11:52:11 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:52:21 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:52:31 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:52:41 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal Oct 6 11:52:51 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal integritysetup status qMtjWDhQoL -q Oct 6 11:53:01 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:53:11 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:53:21 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:53:31 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode Oct 6 11:53:41 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode integritysetup status qMtjWDhQoL -q Oct 6 11:53:51 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:54:01 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:54:11 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '512' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:54:21 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '512' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q Oct 6 11:54:39 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:54:49 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:54:59 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:55:09 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal Oct 6 11:55:19 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal integritysetup status qMtjWDhQoL -q Oct 6 11:55:29 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:55:39 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:55:49 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:55:59 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode Oct 6 11:56:09 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode integritysetup status qMtjWDhQoL -q Oct 6 11:56:19 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:56:29 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:56:39 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 6 11:56:50 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q Oct 6 11:57:03 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:57:13 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:57:23 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:57:34 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal Oct 6 11:57:44 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-no-journal integritysetup status qMtjWDhQoL -q Oct 6 11:57:54 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:58:04 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:58:14 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:58:24 storageqe-109 journal: integritysetup close qMtjWDhQoL -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode Oct 6 11:58:34 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileylV' --integrity-key-size '32' open /dev/mapper/npo2linear qMtjWDhQoL -q --integrity-recovery-mode integritysetup status qMtjWDhQoL -q Oct 6 11:58:44 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup status qMtjWDhQoL -q Oct 6 11:58:54 storageqe-109 journal: integritysetup status qMtjWDhQoL -q integritysetup close qMtjWDhQoL -q Oct 6 11:59:04 storageqe-109 journal: integritysetup close qMtjWDhQoL -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_int_mode[npo2_linear] #### INFO: #### will start test_feature_test[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:59:19 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 11:59:19 storageqe-109 INFO: #### END test_integrity_int_mode[npo2_linear] #### Oct 6 11:59:19 storageqe-109 INFO: #### will start test_feature_test[npo2_linear] ##### Oct 6 11:59:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup format /dev/mapper/npo2linear -q --no-wipe Oct 6 11:59:24 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 6 11:59:24 storageqe-109 journal: integritysetup format /dev/mapper/npo2linear -q --no-wipe integritysetup open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 11:59:34 storageqe-109 journal: integritysetup open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate integritysetup close KFQngCWqBj -q Oct 6 12:00:10 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate-reset Oct 6 12:00:20 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate-reset Oct 6 12:00:20 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 12:00:20 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 12:00:20 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. integritysetup close KFQngCWqBj -q Oct 6 12:00:57 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --data-device '/dev/loop0' format /dev/mapper/npo2linear -q Oct 6 12:01:07 storageqe-109 journal: integritysetup --data-device '/dev/loop0' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop0' open /dev/mapper/npo2linear KFQngCWqBj -q Oct 6 12:01:18 storageqe-109 journal: integritysetup --data-device '/dev/loop0' open /dev/mapper/npo2linear KFQngCWqBj -q integritysetup status KFQngCWqBj -q Oct 6 12:01:28 storageqe-109 journal: integritysetup status KFQngCWqBj -q integritysetup close KFQngCWqBj -q Oct 6 12:01:38 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/loop0 Oct 6 12:01:48 storageqe-109 journal: integritysetup format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/loop0 integritysetup --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-bitmap-mode Oct 6 12:02:01 storageqe-109 journal: integritysetup --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-bitmap-mode integritysetup status KFQngCWqBj -q Oct 6 12:02:11 storageqe-109 journal: integritysetup status KFQngCWqBj -q integritysetup status KFQngCWqBj -q Oct 6 12:02:21 storageqe-109 journal: integritysetup status KFQngCWqBj -q integritysetup close KFQngCWqBj -q Oct 6 12:02:31 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-legacy-hmac --no-wipe Oct 6 12:02:41 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-legacy-hmac --no-wipe integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 12:02:51 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 12:02:51 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Recalculating with HMAC is disabled for security reasons - if you really need it, use the argument "legacy_recalculate" (-EOPNOTSUPP) Oct 6 12:02:51 storageqe-109 kernel: device-mapper: ioctl: error adding target to table integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-legacy-recalculate Oct 6 12:03:01 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-legacy-recalculate integritysetup close KFQngCWqBj -q Oct 6 12:03:11 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe Oct 6 12:03:22 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 12:03:32 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 12:03:32 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Recalculating with HMAC is disabled for security reasons - if you really need it, use the argument "legacy_recalculate" (-EOPNOTSUPP) Oct 6 12:03:32 storageqe-109 kernel: device-mapper: ioctl: error adding target to table integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-legacy-recalculate Oct 6 12:03:42 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-legacy-recalculate integritysetup close KFQngCWqBj -q Oct 6 12:03:52 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe --integrity-legacy-hmac Oct 6 12:04:02 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe --integrity-legacy-hmac integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 12:04:12 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 12:04:12 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Recalculating with HMAC is disabled for security reasons - if you really need it, use the argument "legacy_recalculate" (-EOPNOTSUPP) Oct 6 12:04:12 storageqe-109 kernel: device-mapper: ioctl: error adding target to table integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-legacy-recalculate Oct 6 12:04:22 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-legacy-recalculate integritysetup close KFQngCWqBj -q Oct 6 12:04:32 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe Oct 6 12:04:42 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe integritysetup dump /dev/mapper/npo2linear -q Oct 6 12:04:52 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate Oct 6 12:05:02 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilecOW' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileCSx' --journal-integrity-key-size '32' open /dev/mapper/npo2linear KFQngCWqBj -q --integrity-recalculate integritysetup close KFQngCWqBj -q Oct 6 12:05:12 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 6 12:05:23 storageqe-109 journal: integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear KFQngCWqBj -q Oct 6 12:05:35 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear KFQngCWqBj -q integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/KFQngCWqBj -q Oct 6 12:05:45 storageqe-109 journal: integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/KFQngCWqBj -q integritysetup close KFQngCWqBj -q Oct 6 12:05:55 storageqe-109 journal: integritysetup close KFQngCWqBj -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfilecOW' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilecOW' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfilecOW' format /dev/mapper/npo2linear -q Oct 6 12:06:06 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfilecOW' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilecOW' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfilecOW' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfilecOW' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilecOW' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfilecOW' open /dev/mapper/npo2linear KFQngCWqBj -q Oct 6 12:06:23 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfilecOW' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilecOW' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfilecOW' open /dev/mapper/npo2linear KFQngCWqBj -q integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/KFQngCWqBj -q Oct 6 12:06:33 storageqe-109 journal: integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/KFQngCWqBj -q integritysetup close KFQngCWqBj -q Oct 6 12:06:44 storageqe-109 journal: integritysetup close KFQngCWqBj -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_feature_test[npo2_linear] #### INFO: #### will start test_integrity_resize[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 12:06:59 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 12:06:59 storageqe-109 INFO: #### END test_feature_test[npo2_linear] #### Oct 6 12:06:59 storageqe-109 INFO: #### will start test_integrity_resize[npo2_linear] ##### Oct 6 12:06:59 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 6 12:07:04 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 6 12:07:04 storageqe-109 journal: integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:07:16 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:07:27 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:07:37 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q integritysetup close YylniOxQcG -q Oct 6 12:07:47 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 6 12:07:57 storageqe-109 journal: integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:08:09 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:08:20 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:08:30 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup close YylniOxQcG -q Oct 6 12:08:40 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 6 12:08:50 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:09:01 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:09:11 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:09:21 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q integritysetup close YylniOxQcG -q Oct 6 12:09:31 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 6 12:09:41 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:09:53 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:10:03 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:10:13 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup close YylniOxQcG -q Oct 6 12:10:23 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q Oct 6 12:10:33 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:10:51 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:11:01 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:11:11 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q integritysetup close YylniOxQcG -q Oct 6 12:11:21 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q Oct 6 12:11:32 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:11:49 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:11:59 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:12:10 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup close YylniOxQcG -q Oct 6 12:12:20 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q Oct 6 12:12:30 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:12:46 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:12:56 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:13:06 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q integritysetup close YylniOxQcG -q Oct 6 12:13:16 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q Oct 6 12:13:27 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:13:43 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileZxN' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:13:53 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:14:03 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup close YylniOxQcG -q Oct 6 12:14:13 storageqe-109 journal: integritysetup close YylniOxQcG -q INFO: the add_device_inline device dm-3 support npo2 integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q Oct 6 12:14:23 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 6 12:14:23 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:14:36 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:14:46 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q Oct 6 12:14:56 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q integritysetup close YylniOxQcG -q Oct 6 12:15:06 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q Oct 6 12:15:16 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:15:29 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:15:39 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:15:49 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup close YylniOxQcG -q Oct 6 12:15:59 storageqe-109 journal: integritysetup close YylniOxQcG -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q Oct 6 12:16:09 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q Oct 6 12:16:24 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileZxN' open /dev/mapper/npo2linear YylniOxQcG -q integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:16:34 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe Oct 6 12:16:44 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/YylniOxQcG -q --wipe integritysetup close YylniOxQcG -q Oct 6 12:16:54 storageqe-109 journal: integritysetup close YylniOxQcG -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_resize[npo2_linear] #### Oct 6 12:17:09 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 12:17:09 storageqe-109 INFO: #### END test_integrity_resize[npo2_linear] #### Oct 6 12:17:10 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 12:17:11 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 12:17:12 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 12:17:12 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 12:17:12 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 12:17:22 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_check_fec[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 12:17:28 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 12:17:28 storageqe-109 INFO: #### will start test_check_fec[npo2_linear] ##### Oct 6 12:17:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 12:17:33 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 6 12:17:33 storageqe-109 kernel: sde: Oct 6 12:17:33 storageqe-109 kernel: sde: sde1 Oct 6 12:17:33 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:17:33 storageqe-109 kernel: sdd: Oct 6 12:17:34 storageqe-109 kernel: sdd: sdd1 Oct 6 12:17:34 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:17:42 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear 4794d61a43456e528ed4d46268a2dcdf01e8e76d47180cfffe72f6e14e7735dc Oct 6 12:17:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear 4794d61a43456e528ed4d46268a2dcdf01e8e76d47180cfffe72f6e14e7735dc Oct 6 12:17:44 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:17:54 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 4794d61a43456e528ed4d46268a2dcdf01e8e76d47180cfffe72f6e14e7735dc Oct 6 12:18:04 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 4794d61a43456e528ed4d46268a2dcdf01e8e76d47180cfffe72f6e14e7735dc veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:18:14 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:18:24 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:18:24 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:18:34 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:18:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:18:55 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:19:05 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:19:05 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:19:15 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:19:25 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:19:35 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:19:45 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:19:45 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:19:55 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:20:05 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:20:15 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:20:26 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:20:26 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:20:36 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:20:46 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 6 12:21:00 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 37a2d78909f475d0842dfd0c1e5957dfc9cabe5bd27a2df5392000471cb4d225 Oct 6 12:22:06 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 37a2d78909f475d0842dfd0c1e5957dfc9cabe5bd27a2df5392000471cb4d225 Oct 6 12:22:06 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:22:32 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 37a2d78909f475d0842dfd0c1e5957dfc9cabe5bd27a2df5392000471cb4d225 Oct 6 12:22:43 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 37a2d78909f475d0842dfd0c1e5957dfc9cabe5bd27a2df5392000471cb4d225 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:23:02 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 d1453d0f46c22c588f5a669631a4a7457e46951b5fbf03aa3b28b252a5142e74 Oct 6 12:24:08 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 d1453d0f46c22c588f5a669631a4a7457e46951b5fbf03aa3b28b252a5142e74 Oct 6 12:24:08 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:24:34 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 d1453d0f46c22c588f5a669631a4a7457e46951b5fbf03aa3b28b252a5142e74 Oct 6 12:24:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 d1453d0f46c22c588f5a669631a4a7457e46951b5fbf03aa3b28b252a5142e74 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:25:04 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 77a17e9e0ec8c898ad3fd5c354fd8f5eb3c477230bd41883c14e6e0b97c4d2cc Oct 6 12:26:10 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 77a17e9e0ec8c898ad3fd5c354fd8f5eb3c477230bd41883c14e6e0b97c4d2cc Oct 6 12:26:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:26:36 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 77a17e9e0ec8c898ad3fd5c354fd8f5eb3c477230bd41883c14e6e0b97c4d2cc Oct 6 12:26:46 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 77a17e9e0ec8c898ad3fd5c354fd8f5eb3c477230bd41883c14e6e0b97c4d2cc veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:27:06 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 0a8d9963ac76df68fa8bb36d7c02ab340315f1cd15fecbf1de71980c033fa1ed Oct 6 12:28:11 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 0a8d9963ac76df68fa8bb36d7c02ab340315f1cd15fecbf1de71980c033fa1ed Oct 6 12:28:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yAWdUtKIPp Oct 6 12:28:38 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 0a8d9963ac76df68fa8bb36d7c02ab340315f1cd15fecbf1de71980c033fa1ed Oct 6 12:28:48 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 0a8d9963ac76df68fa8bb36d7c02ab340315f1cd15fecbf1de71980c033fa1ed veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:29:03 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear 67ed0e4cd1cc897139d118a5a33b690fe6e55e59610fc0c294a74dae4c4c8389 Oct 6 12:29:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear 67ed0e4cd1cc897139d118a5a33b690fe6e55e59610fc0c294a74dae4c4c8389 Oct 6 12:29:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:29:13 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:29:24 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:29:24 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 67ed0e4cd1cc897139d118a5a33b690fe6e55e59610fc0c294a74dae4c4c8389 Oct 6 12:29:34 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 67ed0e4cd1cc897139d118a5a33b690fe6e55e59610fc0c294a74dae4c4c8389 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:29:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:29:54 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:29:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:29:54 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:30:04 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:30:04 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:30:14 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:30:25 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:30:35 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:30:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:30:35 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:30:45 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:30:45 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:30:55 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:31:05 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:31:15 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:31:15 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:31:15 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:31:25 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:31:25 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:31:35 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:31:46 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:31:56 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:31:56 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:31:56 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:32:06 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:32:06 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:32:16 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 6 12:32:30 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 e4ba1abeaa5b23ff8adf0d636aae49d3f8c935fa0e6057e146dfd7eab2422dfb Oct 6 12:33:36 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 e4ba1abeaa5b23ff8adf0d636aae49d3f8c935fa0e6057e146dfd7eab2422dfb Oct 6 12:33:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:33:36 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:33:46 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:34:03 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 e4ba1abeaa5b23ff8adf0d636aae49d3f8c935fa0e6057e146dfd7eab2422dfb Oct 6 12:34:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 e4ba1abeaa5b23ff8adf0d636aae49d3f8c935fa0e6057e146dfd7eab2422dfb veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:35:01 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 fa9340372abb4f68d2b6233313d62bc05a21094baf38f666de0aec17c2037905 Oct 6 12:36:07 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 fa9340372abb4f68d2b6233313d62bc05a21094baf38f666de0aec17c2037905 Oct 6 12:36:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:36:07 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:36:17 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:36:34 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 fa9340372abb4f68d2b6233313d62bc05a21094baf38f666de0aec17c2037905 Oct 6 12:36:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 fa9340372abb4f68d2b6233313d62bc05a21094baf38f666de0aec17c2037905 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:37:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 79745743959312d80c047e47c699c4079e9b21b7bb58fd32e7dd64fd6ab504e9 Oct 6 12:38:39 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 79745743959312d80c047e47c699c4079e9b21b7bb58fd32e7dd64fd6ab504e9 Oct 6 12:38:39 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:38:39 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:38:49 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:39:05 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 79745743959312d80c047e47c699c4079e9b21b7bb58fd32e7dd64fd6ab504e9 Oct 6 12:39:15 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 79745743959312d80c047e47c699c4079e9b21b7bb58fd32e7dd64fd6ab504e9 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:40:04 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 7920c89fb3937510a29784ffdedf1580005c03e0e2d8a0a29002d2cc0468aaee Oct 6 12:41:10 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 7920c89fb3937510a29784ffdedf1580005c03e0e2d8a0a29002d2cc0468aaee Oct 6 12:41:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:41:10 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:41:20 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:41:36 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 7920c89fb3937510a29784ffdedf1580005c03e0e2d8a0a29002d2cc0468aaee Oct 6 12:41:46 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 7920c89fb3937510a29784ffdedf1580005c03e0e2d8a0a29002d2cc0468aaee veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:42:31 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear b542faaedb648438edc96c0d58076ba33dda3a1c2844310d72527edcea1baef7 Oct 6 12:42:41 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear b542faaedb648438edc96c0d58076ba33dda3a1c2844310d72527edcea1baef7 Oct 6 12:42:41 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:42:41 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:42:51 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:42:51 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear b542faaedb648438edc96c0d58076ba33dda3a1c2844310d72527edcea1baef7 Oct 6 12:43:01 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear b542faaedb648438edc96c0d58076ba33dda3a1c2844310d72527edcea1baef7 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:43:12 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:43:22 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:43:22 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:43:22 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:43:32 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:43:32 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:43:42 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:43:52 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:44:02 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:44:02 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:44:02 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:44:12 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:44:12 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:44:23 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:44:33 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:44:43 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:44:43 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:44:43 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:44:53 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:44:53 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:45:03 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:45:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:45:23 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:45:23 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:45:23 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:45:33 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:45:33 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:45:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 6 12:45:58 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 1ff3b9e593d6610761e58c902acc708db906fa4de1bc6e1effc9479142767efb Oct 6 12:47:04 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 1ff3b9e593d6610761e58c902acc708db906fa4de1bc6e1effc9479142767efb Oct 6 12:47:04 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:47:04 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:47:14 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:47:30 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 1ff3b9e593d6610761e58c902acc708db906fa4de1bc6e1effc9479142767efb Oct 6 12:47:40 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 1ff3b9e593d6610761e58c902acc708db906fa4de1bc6e1effc9479142767efb veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:48:29 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 d93f91c11f8714cd665d8b4611d8c96b8885ebaa72fbd2a040f1da48f18e5b32 Oct 6 12:49:35 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 d93f91c11f8714cd665d8b4611d8c96b8885ebaa72fbd2a040f1da48f18e5b32 Oct 6 12:49:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:49:35 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:49:45 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:50:01 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 d93f91c11f8714cd665d8b4611d8c96b8885ebaa72fbd2a040f1da48f18e5b32 Oct 6 12:50:12 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 d93f91c11f8714cd665d8b4611d8c96b8885ebaa72fbd2a040f1da48f18e5b32 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:51:00 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 a531c027bbbebbcd10a487fa6c0ad8d3255c6cf8e5672de95a35b43b42e5f500 Oct 6 12:52:06 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 a531c027bbbebbcd10a487fa6c0ad8d3255c6cf8e5672de95a35b43b42e5f500 Oct 6 12:52:06 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:52:06 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:52:16 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:52:33 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 a531c027bbbebbcd10a487fa6c0ad8d3255c6cf8e5672de95a35b43b42e5f500 Oct 6 12:52:43 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 a531c027bbbebbcd10a487fa6c0ad8d3255c6cf8e5672de95a35b43b42e5f500 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 12:53:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 6c84924d1143d27a1cfd7f6ed9e2f7e6d7794825286b7b29f10ed00b7235d788 Oct 6 12:54:37 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 6c84924d1143d27a1cfd7f6ed9e2f7e6d7794825286b7b29f10ed00b7235d788 Oct 6 12:54:37 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:54:38 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:54:48 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:55:04 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 6c84924d1143d27a1cfd7f6ed9e2f7e6d7794825286b7b29f10ed00b7235d788 Oct 6 12:55:14 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 6c84924d1143d27a1cfd7f6ed9e2f7e6d7794825286b7b29f10ed00b7235d788 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:55:59 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear a36b8cee0581f0e721bd0d5d0f4eb868b82ba85c218d1735aae506166cebbc10 Oct 6 12:56:09 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear a36b8cee0581f0e721bd0d5d0f4eb868b82ba85c218d1735aae506166cebbc10 Oct 6 12:56:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:56:09 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:56:19 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:56:19 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear a36b8cee0581f0e721bd0d5d0f4eb868b82ba85c218d1735aae506166cebbc10 Oct 6 12:56:29 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear a36b8cee0581f0e721bd0d5d0f4eb868b82ba85c218d1735aae506166cebbc10 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:56:39 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:56:50 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:56:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:56:50 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:57:00 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:57:00 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:57:10 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:57:20 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:57:30 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:57:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:57:30 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:57:40 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:57:40 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 6 12:57:50 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 6 12:58:01 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:58:11 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:58:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:58:11 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:58:21 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:58:21 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:58:31 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 12:58:41 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:58:51 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:58:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 12:58:51 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 12:59:01 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 12:59:01 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 6 12:59:11 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 6 12:59:26 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 3001108fc3a1276e4d0ab8ad21ebc1b94e1553106af939a7b541dcd0c51506d2 Oct 6 13:00:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create yAWdUtKIPp /dev/mapper/npo2linear --no-superblock /dev/sde1 3001108fc3a1276e4d0ab8ad21ebc1b94e1553106af939a7b541dcd0c51506d2 Oct 6 13:00:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:00:32 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 13:00:42 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 13:00:58 storageqe-109 journal: veritysetup close yAWdUtKIPp Oct 6 13:00:58 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 13:00:58 storageqe-109 dnf[1089239]: Updating Subscription Management repositories. Oct 6 13:00:58 storageqe-109 dnf[1089239]: Unable to read consumer identity Oct 6 13:00:58 storageqe-109 dnf[1089239]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-AppStream 654 kB/s | 2.8 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-AppStream-debuginfo 544 kB/s | 1.5 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-BaseOS 732 kB/s | 2.7 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-BaseOS-debuginfo 558 kB/s | 1.5 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-CRB 799 kB/s | 2.7 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-CRB-debuginfo 570 kB/s | 1.5 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-HighAvailability 895 kB/s | 2.8 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-HighAvailability-debuginfo 654 kB/s | 1.5 kB 00:00 Oct 6 13:00:58 storageqe-109 dnf[1089239]: beaker-NFV 942 kB/s | 2.7 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: beaker-NFV-debuginfo 513 kB/s | 1.5 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: beaker-RT 872 kB/s | 2.7 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: beaker-RT-debuginfo 540 kB/s | 1.5 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: beaker-SAP 807 kB/s | 2.7 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: beaker-SAP-debuginfo 499 kB/s | 1.5 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: beaker-SAPHANA 791 kB/s | 2.7 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: beaker-SAPHANA-debuginfo 526 kB/s | 1.5 kB 00:00 Oct 6 13:00:59 storageqe-109 dnf[1089239]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 6 13:01:01 storageqe-109 dnf[1089239]: beaker-harness 756 B/s | 1.3 kB 00:01 Oct 6 13:01:01 storageqe-109 dnf[1089239]: Google Cloud CLI 3.9 kB/s | 1.4 kB 00:00 Oct 6 13:01:02 storageqe-109 dnf[1089239]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 6 13:01:03 storageqe-109 dnf[1089239]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 6 13:01:03 storageqe-109 dnf[1089239]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 6 13:01:03 storageqe-109 dnf[1089239]: Metadata cache created. Oct 6 13:01:04 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 13:01:04 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 13:01:04 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 329ms CPU time, 85.7M memory peak. veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 3001108fc3a1276e4d0ab8ad21ebc1b94e1553106af939a7b541dcd0c51506d2 Oct 6 13:01:08 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 3001108fc3a1276e4d0ab8ad21ebc1b94e1553106af939a7b541dcd0c51506d2 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:01:57 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 ff851821f2067e8e595836499eccb98347e666972017cb36f7cb7830bde03075 Oct 6 13:03:03 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 ff851821f2067e8e595836499eccb98347e666972017cb36f7cb7830bde03075 Oct 6 13:03:03 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:03:03 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 13:03:13 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 13:03:29 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 ff851821f2067e8e595836499eccb98347e666972017cb36f7cb7830bde03075 Oct 6 13:03:39 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 ff851821f2067e8e595836499eccb98347e666972017cb36f7cb7830bde03075 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:04:28 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 ea78a645f0786171ded66dccd66024d2a9924ede9e94d575b0f6584b30f9d352 Oct 6 13:05:34 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 ea78a645f0786171ded66dccd66024d2a9924ede9e94d575b0f6584b30f9d352 Oct 6 13:05:34 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:05:34 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 13:05:44 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 13:06:01 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 ea78a645f0786171ded66dccd66024d2a9924ede9e94d575b0f6584b30f9d352 Oct 6 13:06:11 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 ea78a645f0786171ded66dccd66024d2a9924ede9e94d575b0f6584b30f9d352 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:07:00 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 daf2386e259bdf6706787c9ea1e4588f5b7b3296e86df12d10d3cc26cac7828b Oct 6 13:08:05 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create yAWdUtKIPp /dev/mapper/npo2linear /dev/sde1 daf2386e259bdf6706787c9ea1e4588f5b7b3296e86df12d10d3cc26cac7828b Oct 6 13:08:05 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:08:06 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 6 13:08:16 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close yAWdUtKIPp Oct 6 13:08:32 storageqe-109 journal: veritysetup close yAWdUtKIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 daf2386e259bdf6706787c9ea1e4588f5b7b3296e86df12d10d3cc26cac7828b Oct 6 13:08:42 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 daf2386e259bdf6706787c9ea1e4588f5b7b3296e86df12d10d3cc26cac7828b Oct 6 13:09:27 storageqe-109 kernel: sde: Oct 6 13:09:27 storageqe-109 kernel: sdd: sdd1 Oct 6 13:09:27 storageqe-109 kernel: sdd: INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_check_fec[npo2_linear] #### INFO: #### will start test_offset[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 13:09:32 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 13:09:32 storageqe-109 INFO: #### END test_check_fec[npo2_linear] #### Oct 6 13:09:32 storageqe-109 INFO: #### will start test_offset[npo2_linear] ##### Oct 6 13:09:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --data-blocks '256' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 13:09:37 storageqe-109 journal: veritysetup --data-blocks '256' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '128' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 13:09:47 storageqe-109 journal: veritysetup --data-blocks '128' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '512' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 13:09:57 storageqe-109 journal: veritysetup --data-blocks '512' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '4096' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 13:10:07 storageqe-109 journal: veritysetup --data-blocks '4096' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '8152' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 13:10:17 storageqe-109 journal: veritysetup --data-blocks '8152' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_offset[npo2_linear] #### INFO: #### will start test_dm_verity_options[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 13:10:32 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 13:10:32 storageqe-109 INFO: #### END test_offset[npo2_linear] #### Oct 6 13:10:32 storageqe-109 INFO: #### will start test_dm_verity_options[npo2_linear] ##### Oct 6 13:10:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:10:37 storageqe-109 kernel: loop2: detected capacity change from 0 to 12582912 Oct 6 13:10:37 storageqe-109 kernel: sde: Oct 6 13:10:37 storageqe-109 kernel: sde: sde1 Oct 6 13:10:37 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --ignore-corruption Oct 6 13:10:52 storageqe-109 journal: veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --ignore-corruption Oct 6 13:10:52 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vGXgFaslun Oct 6 13:11:06 storageqe-109 journal: veritysetup close vGXgFaslun veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:11:16 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --restart-on-corruption Oct 6 13:11:31 storageqe-109 journal: veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --restart-on-corruption Oct 6 13:11:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vGXgFaslun Oct 6 13:11:44 storageqe-109 journal: veritysetup close vGXgFaslun veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:11:54 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --ignore-zero-blocks Oct 6 13:12:09 storageqe-109 journal: veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --ignore-zero-blocks Oct 6 13:12:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vGXgFaslun Oct 6 13:12:22 storageqe-109 journal: veritysetup close vGXgFaslun veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:12:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --ignore-corruption --ignore-zero-blocks Oct 6 13:12:47 storageqe-109 journal: veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --ignore-corruption --ignore-zero-blocks Oct 6 13:12:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vGXgFaslun Oct 6 13:13:00 storageqe-109 journal: veritysetup close vGXgFaslun veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:13:10 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --check-at-most-once Oct 6 13:13:25 storageqe-109 journal: veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --check-at-most-once Oct 6 13:13:25 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vGXgFaslun Oct 6 13:13:38 storageqe-109 journal: veritysetup close vGXgFaslun veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:13:49 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --panic-on-corruption Oct 6 13:14:04 storageqe-109 journal: veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --panic-on-corruption Oct 6 13:14:04 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vGXgFaslun Oct 6 13:14:17 storageqe-109 journal: veritysetup close vGXgFaslun veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:14:27 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --use-tasklets Oct 6 13:14:42 storageqe-109 journal: veritysetup create vGXgFaslun /dev/mapper/npo2linear /dev/sde1 14dcd825554037b312ce5175d102c3b6f998083f5b188279774987814dd8fc9c --use-tasklets Oct 6 13:14:42 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vGXgFaslun Oct 6 13:14:55 storageqe-109 journal: veritysetup close vGXgFaslun Oct 6 13:15:05 storageqe-109 kernel: sde: INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_options[npo2_linear] #### INFO: #### will start test_dm_verity_check[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 13:15:10 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 13:15:10 storageqe-109 INFO: #### END test_dm_verity_options[npo2_linear] #### Oct 6 13:15:10 storageqe-109 INFO: #### will start test_dm_verity_check[npo2_linear] ##### Oct 6 13:15:10 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 13:15:15 storageqe-109 kernel: sde: Oct 6 13:15:15 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:15:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:15:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZBlUgwzXRJ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:15:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZBlUgwzXRJ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:15:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ZBlUgwzXRJ Oct 6 13:16:10 storageqe-109 journal: veritysetup close ZBlUgwzXRJ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:16:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DhbrTHdtPB /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:16:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DhbrTHdtPB /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:16:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:16:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:31 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close DhbrTHdtPB Oct 6 13:16:40 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:16:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:16:41 storageqe-109 journal: veritysetup close DhbrTHdtPB veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:16:55 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:17:12 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BscSlpMixo /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:17:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BscSlpMixo /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:17:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BscSlpMixo Oct 6 13:17:46 storageqe-109 journal: veritysetup close BscSlpMixo veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:17:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ivjQkJwyNH /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:18:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ivjQkJwyNH /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:18:13 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:13 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ivjQkJwyNH Oct 6 13:18:23 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:18:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:18:23 storageqe-109 journal: veritysetup close ivjQkJwyNH veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 13:18:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:18:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WIgnrTxJPz /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:19:11 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WIgnrTxJPz /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:19:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close WIgnrTxJPz Oct 6 13:19:29 storageqe-109 journal: veritysetup close WIgnrTxJPz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:19:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GwYxhbKACo /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:19:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GwYxhbKACo /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:19:50 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:19:50 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close GwYxhbKACo Oct 6 13:20:00 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:20:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:20:00 storageqe-109 journal: veritysetup close GwYxhbKACo veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:20:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:20:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UpOJkbVAHY /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:20:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UpOJkbVAHY /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:20:48 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close UpOJkbVAHY Oct 6 13:21:05 storageqe-109 journal: veritysetup close UpOJkbVAHY veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:21:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qRxGBgwjOd /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:21:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qRxGBgwjOd /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:21:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:32 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close qRxGBgwjOd Oct 6 13:21:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:21:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:21:42 storageqe-109 journal: veritysetup close qRxGBgwjOd veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:21:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:22:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create gQDxUhWejf /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:22:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create gQDxUhWejf /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:22:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close gQDxUhWejf Oct 6 13:22:49 storageqe-109 journal: veritysetup close gQDxUhWejf veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:22:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xzDOCVXHvh /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:23:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xzDOCVXHvh /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:23:09 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:09 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close xzDOCVXHvh Oct 6 13:23:19 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:23:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:23:19 storageqe-109 journal: veritysetup close xzDOCVXHvh veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:23:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:23:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MWlDhXqFTG /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:24:07 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MWlDhXqFTG /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:24:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close MWlDhXqFTG Oct 6 13:24:26 storageqe-109 journal: veritysetup close MWlDhXqFTG veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:24:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OzefolTdLF /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:24:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OzefolTdLF /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:24:53 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:24:53 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close OzefolTdLF Oct 6 13:25:03 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:25:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:25:03 storageqe-109 journal: veritysetup close OzefolTdLF veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 13:25:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:25:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VbBfUPczDx /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:25:51 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VbBfUPczDx /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:25:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close VbBfUPczDx Oct 6 13:26:10 storageqe-109 journal: veritysetup close VbBfUPczDx veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:26:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YkupeShXKq /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:26:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YkupeShXKq /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:26:30 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 13:26:30 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 13:26:30 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:30 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close YkupeShXKq Oct 6 13:26:40 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:26:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:26:40 storageqe-109 journal: veritysetup close YkupeShXKq veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:26:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:27:11 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BrHMYkCGPW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:27:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BrHMYkCGPW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:27:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BrHMYkCGPW Oct 6 13:27:46 storageqe-109 journal: veritysetup close BrHMYkCGPW veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:27:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zNEMJorKSW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:28:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zNEMJorKSW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:28:13 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:13 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zNEMJorKSW Oct 6 13:28:23 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:28:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:28:23 storageqe-109 journal: veritysetup close zNEMJorKSW Oct 6 13:28:33 storageqe-109 kernel: sde: Oct 6 13:28:33 storageqe-109 kernel: sde: Oct 6 13:28:33 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:28:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:28:55 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VMDxAiwXhK /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:29:12 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VMDxAiwXhK /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:29:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close VMDxAiwXhK Oct 6 13:29:30 storageqe-109 journal: veritysetup close VMDxAiwXhK veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:29:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create eCQthfsJwr /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:29:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create eCQthfsJwr /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:29:50 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close eCQthfsJwr Oct 6 13:30:00 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:30:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:30:00 storageqe-109 journal: veritysetup close eCQthfsJwr veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:30:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:30:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create uawtfIQqAn /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:30:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create uawtfIQqAn /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:30:48 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close uawtfIQqAn Oct 6 13:31:06 storageqe-109 journal: veritysetup close uawtfIQqAn veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:31:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DqluYtcFNi /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:31:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DqluYtcFNi /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:31:33 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:34 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close DqluYtcFNi Oct 6 13:31:43 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:31:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:31:43 storageqe-109 journal: veritysetup close DqluYtcFNi veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 13:31:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:32:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WhdriqwuHL /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:32:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WhdriqwuHL /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:32:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close WhdriqwuHL Oct 6 13:32:49 storageqe-109 journal: veritysetup close WhdriqwuHL veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:32:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hQpGZsJyXT /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:33:10 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hQpGZsJyXT /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:33:10 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:10 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close hQpGZsJyXT Oct 6 13:33:20 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:33:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:33:20 storageqe-109 journal: veritysetup close hQpGZsJyXT veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:33:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:33:51 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JLbmePwIWD /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:34:08 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JLbmePwIWD /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:34:08 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close JLbmePwIWD Oct 6 13:34:26 storageqe-109 journal: veritysetup close JLbmePwIWD veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:34:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ybjFVqeZPr /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:34:52 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ybjFVqeZPr /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:34:52 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:34:52 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:34:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:34:53 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ybjFVqeZPr Oct 6 13:35:02 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:35:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:35:03 storageqe-109 journal: veritysetup close ybjFVqeZPr veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:35:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:35:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fcZdDJepBS /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:35:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fcZdDJepBS /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:35:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close fcZdDJepBS Oct 6 13:36:08 storageqe-109 journal: veritysetup close fcZdDJepBS veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:36:18 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sNtKZmluMj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:36:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sNtKZmluMj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:36:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:36:28 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:36:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:29 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close sNtKZmluMj Oct 6 13:36:39 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:36:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:36:39 storageqe-109 journal: veritysetup close sNtKZmluMj veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:36:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:37:10 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create shJBaOHQcW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:37:27 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create shJBaOHQcW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:37:27 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close shJBaOHQcW Oct 6 13:37:45 storageqe-109 journal: veritysetup close shJBaOHQcW veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:37:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RahzESGPuC /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:38:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RahzESGPuC /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:38:13 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:13 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close RahzESGPuC Oct 6 13:38:23 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:38:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:38:23 storageqe-109 journal: veritysetup close RahzESGPuC veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 13:38:37 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:38:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lGQzmVXPUv /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:39:10 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lGQzmVXPUv /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:39:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close lGQzmVXPUv Oct 6 13:39:28 storageqe-109 journal: veritysetup close lGQzmVXPUv veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:39:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dTkoxtVrDS /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:39:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dTkoxtVrDS /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:39:48 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:49 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close dTkoxtVrDS Oct 6 13:39:58 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:39:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:39:58 storageqe-109 journal: veritysetup close dTkoxtVrDS veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:40:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:40:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UioLElJRMg /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:40:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UioLElJRMg /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:40:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close UioLElJRMg Oct 6 13:41:05 storageqe-109 journal: veritysetup close UioLElJRMg veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:41:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create EhPRuyfbWH /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:41:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create EhPRuyfbWH /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:41:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:32 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close EhPRuyfbWH Oct 6 13:41:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:41:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:41:42 storageqe-109 journal: veritysetup close EhPRuyfbWH Oct 6 13:41:52 storageqe-109 kernel: sde: Oct 6 13:41:52 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:41:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:42:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RaTrHOnUeB /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:42:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RaTrHOnUeB /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:42:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close RaTrHOnUeB Oct 6 13:42:48 storageqe-109 journal: veritysetup close RaTrHOnUeB veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:42:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lvriHnMbVG /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:43:08 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lvriHnMbVG /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:43:08 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:43:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:09 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close lvriHnMbVG Oct 6 13:43:18 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:43:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:43:18 storageqe-109 journal: veritysetup close lvriHnMbVG veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:43:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:43:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DgIrhHAzOt /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:44:07 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DgIrhHAzOt /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:44:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close DgIrhHAzOt Oct 6 13:44:25 storageqe-109 journal: veritysetup close DgIrhHAzOt veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:44:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HoupQsFfEj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:44:51 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HoupQsFfEj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:44:51 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:44:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:44:52 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close HoupQsFfEj Oct 6 13:45:01 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:45:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:45:01 storageqe-109 journal: veritysetup close HoupQsFfEj veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 13:45:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:45:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZyJoEGQlYB /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:45:49 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZyJoEGQlYB /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:45:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ZyJoEGQlYB Oct 6 13:46:07 storageqe-109 journal: veritysetup close ZyJoEGQlYB veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:46:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hdWJoknCAK /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:46:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hdWJoknCAK /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:46:28 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:28 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close hdWJoknCAK Oct 6 13:46:38 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:46:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:46:38 storageqe-109 journal: veritysetup close hdWJoknCAK veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:46:52 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:47:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UuItdlixPj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:47:26 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UuItdlixPj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:47:26 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close UuItdlixPj Oct 6 13:47:44 storageqe-109 journal: veritysetup close UuItdlixPj veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:47:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UYZcAaQLvP /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:48:11 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UYZcAaQLvP /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:48:11 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:11 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close UYZcAaQLvP Oct 6 13:48:21 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:48:21 storageqe-109 journal: veritysetup close UYZcAaQLvP veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:48:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:48:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fgRTmLxqcV /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:49:10 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fgRTmLxqcV /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:49:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close fgRTmLxqcV Oct 6 13:49:28 storageqe-109 journal: veritysetup close fgRTmLxqcV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:49:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RJWhPnokQg /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:49:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RJWhPnokQg /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:49:48 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:48 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close RJWhPnokQg Oct 6 13:49:58 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:49:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:49:58 storageqe-109 journal: veritysetup close RJWhPnokQg veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:50:12 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:50:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ltiZbkQgaD /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:50:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ltiZbkQgaD /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:50:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ltiZbkQgaD Oct 6 13:51:05 storageqe-109 journal: veritysetup close ltiZbkQgaD veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:51:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YCQWGRfbtX /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:51:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YCQWGRfbtX /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:51:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:32 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close YCQWGRfbtX Oct 6 13:51:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:51:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:51:42 storageqe-109 journal: veritysetup close YCQWGRfbtX veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 13:51:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:52:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ioQgYeykSK /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:52:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ioQgYeykSK /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:52:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ioQgYeykSK Oct 6 13:52:49 storageqe-109 journal: veritysetup close ioQgYeykSK veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:52:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XBxZTiJHKQ /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:53:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XBxZTiJHKQ /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:53:09 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:09 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close XBxZTiJHKQ Oct 6 13:53:19 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:53:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:53:19 storageqe-109 journal: veritysetup close XBxZTiJHKQ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:53:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:53:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PQclGKNUhp /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:54:07 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PQclGKNUhp /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:54:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close PQclGKNUhp Oct 6 13:54:25 storageqe-109 journal: veritysetup close PQclGKNUhp veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:54:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HUkleCWOvT /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:54:52 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HUkleCWOvT /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 13:54:52 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:54:52 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close HUkleCWOvT Oct 6 13:55:02 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:55:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:55:02 storageqe-109 journal: veritysetup close HUkleCWOvT Oct 6 13:55:12 storageqe-109 kernel: sde: Oct 6 13:55:12 storageqe-109 kernel: sde: Oct 6 13:55:12 storageqe-109 kernel: sde: sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:55:17 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:55:34 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DvKSJFHApY /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:55:50 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DvKSJFHApY /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:55:50 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close DvKSJFHApY Oct 6 13:56:08 storageqe-109 journal: veritysetup close DvKSJFHApY veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:56:18 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WxHfJCGwnM /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:56:28 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WxHfJCGwnM /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 13:56:28 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:56:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:29 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close WxHfJCGwnM Oct 6 13:56:38 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:56:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:56:38 storageqe-109 journal: veritysetup close WxHfJCGwnM veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 13:56:53 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:57:10 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mZBlpxDMgd /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:57:27 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mZBlpxDMgd /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:57:27 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close mZBlpxDMgd Oct 6 13:57:45 storageqe-109 journal: veritysetup close mZBlpxDMgd veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:57:55 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create guFYdrHLlt /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:58:12 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create guFYdrHLlt /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 13:58:12 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:12 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close guFYdrHLlt Oct 6 13:58:22 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:58:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:58:22 storageqe-109 journal: veritysetup close guFYdrHLlt veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 13:58:36 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:58:53 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MfAqGPboKz /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:59:10 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MfAqGPboKz /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:59:10 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close MfAqGPboKz Oct 6 13:59:29 storageqe-109 journal: veritysetup close MfAqGPboKz veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:59:39 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jPIiZdavNl /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:59:49 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jPIiZdavNl /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 13:59:49 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:49 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close jPIiZdavNl Oct 6 13:59:59 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 13:59:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 13:59:59 storageqe-109 journal: veritysetup close jPIiZdavNl veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:00:13 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:00:30 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WlRXmutcGB /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:00:47 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WlRXmutcGB /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:00:47 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close WlRXmutcGB Oct 6 14:01:05 storageqe-109 journal: veritysetup close WlRXmutcGB veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:01:15 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZXtHsIpdhl /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:01:32 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZXtHsIpdhl /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 14:01:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:32 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ZXtHsIpdhl Oct 6 14:01:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:01:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:01:42 storageqe-109 journal: veritysetup close ZXtHsIpdhl veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:01:56 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:02:13 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GvRYoeBSWX /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:02:30 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GvRYoeBSWX /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:02:30 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close GvRYoeBSWX Oct 6 14:02:48 storageqe-109 journal: veritysetup close GvRYoeBSWX veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:02:58 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OfIcVJLjNp /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:03:08 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OfIcVJLjNp /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 14:03:08 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:08 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close OfIcVJLjNp Oct 6 14:03:18 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:03:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:03:18 storageqe-109 journal: veritysetup close OfIcVJLjNp veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:03:33 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:03:50 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GDnTExypwo /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:04:07 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GDnTExypwo /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:04:07 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close GDnTExypwo Oct 6 14:04:25 storageqe-109 journal: veritysetup close GDnTExypwo veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:04:35 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YDGXPRvQiS /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:04:52 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YDGXPRvQiS /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 14:04:52 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:04:52 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close YDGXPRvQiS Oct 6 14:05:02 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:05:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:05:02 storageqe-109 journal: veritysetup close YDGXPRvQiS veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 14:05:16 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:05:33 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CUidhzaqoN /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:05:50 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CUidhzaqoN /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:05:50 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close CUidhzaqoN Oct 6 14:06:09 storageqe-109 journal: veritysetup close CUidhzaqoN veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:06:19 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GrFLZmUfYD /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:06:29 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GrFLZmUfYD /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 14:06:29 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:29 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close GrFLZmUfYD Oct 6 14:06:39 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:06:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:06:39 storageqe-109 journal: veritysetup close GrFLZmUfYD veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:06:53 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:07:10 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VDEjnpewaJ /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:07:27 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VDEjnpewaJ /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:07:27 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close VDEjnpewaJ Oct 6 14:07:46 storageqe-109 journal: veritysetup close VDEjnpewaJ veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:07:56 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PwvtsRzmrp /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:08:13 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PwvtsRzmrp /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 14:08:13 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:13 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close PwvtsRzmrp Oct 6 14:08:23 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:08:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:08:23 storageqe-109 journal: veritysetup close PwvtsRzmrp Oct 6 14:08:33 storageqe-109 kernel: sde: Oct 6 14:08:33 storageqe-109 kernel: sde: Oct 6 14:08:33 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:08:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:08:55 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create mywHtjlCBQ /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:09:11 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create mywHtjlCBQ /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:09:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close mywHtjlCBQ Oct 6 14:09:29 storageqe-109 journal: veritysetup close mywHtjlCBQ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:09:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create DimRdVfpoq /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:09:49 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create DimRdVfpoq /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:09:49 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:50 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close DimRdVfpoq Oct 6 14:09:59 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:09:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:09:59 storageqe-109 journal: veritysetup close DimRdVfpoq veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:10:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:10:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create zqubNVWBKA /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:10:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create zqubNVWBKA /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:10:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close zqubNVWBKA Oct 6 14:11:05 storageqe-109 journal: veritysetup close zqubNVWBKA veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:11:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create EAFcqQhbCW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:11:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create EAFcqQhbCW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:11:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:32 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close EAFcqQhbCW Oct 6 14:11:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:11:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:11:42 storageqe-109 journal: veritysetup close EAFcqQhbCW veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 14:11:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:12:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create qvmKsHBTen /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:12:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create qvmKsHBTen /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:12:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:12:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 14:12:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 14:12:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. veritysetup close qvmKsHBTen Oct 6 14:12:49 storageqe-109 journal: veritysetup close qvmKsHBTen veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:12:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create qVaCWyAwjk /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:13:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create qVaCWyAwjk /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:13:09 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:09 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close qVaCWyAwjk Oct 6 14:13:19 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:13:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:13:19 storageqe-109 journal: veritysetup close qVaCWyAwjk veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:13:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:13:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create KispljWAkh /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:14:07 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create KispljWAkh /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:14:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close KispljWAkh Oct 6 14:14:25 storageqe-109 journal: veritysetup close KispljWAkh veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:14:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create XeYWhGCgos /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:14:51 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create XeYWhGCgos /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:14:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:14:51 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:14:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:51 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:52 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:14:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:14:52 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close XeYWhGCgos Oct 6 14:15:01 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:15:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:15:01 storageqe-109 journal: veritysetup close XeYWhGCgos veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:15:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:15:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create rjDIELctbh /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:15:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create rjDIELctbh /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:15:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close rjDIELctbh Oct 6 14:16:08 storageqe-109 journal: veritysetup close rjDIELctbh veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:16:18 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create EcTArGolek /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:16:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create EcTArGolek /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:16:28 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:28 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close EcTArGolek Oct 6 14:16:38 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:16:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:16:38 storageqe-109 journal: veritysetup close EcTArGolek veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:16:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:17:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create rhMFOtPRZV /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:17:26 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create rhMFOtPRZV /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:17:26 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close rhMFOtPRZV Oct 6 14:17:44 storageqe-109 journal: veritysetup close rhMFOtPRZV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:17:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create nKCGdIYlbe /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:18:10 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create nKCGdIYlbe /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:18:10 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:10 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close nKCGdIYlbe Oct 6 14:18:20 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:18:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:18:20 storageqe-109 journal: veritysetup close nKCGdIYlbe veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 14:18:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:18:52 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create lcmiHJrvxI /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:19:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create lcmiHJrvxI /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:19:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close lcmiHJrvxI Oct 6 14:19:27 storageqe-109 journal: veritysetup close lcmiHJrvxI veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:19:37 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create HTFUvhnXDL /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:19:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create HTFUvhnXDL /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:19:47 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:47 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close HTFUvhnXDL Oct 6 14:19:57 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:19:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:19:57 storageqe-109 journal: veritysetup close HTFUvhnXDL veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:20:12 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:20:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create eOWvKMNhoJ /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:20:45 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create eOWvKMNhoJ /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:20:45 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close eOWvKMNhoJ Oct 6 14:21:03 storageqe-109 journal: veritysetup close eOWvKMNhoJ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:21:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create mcUuOlzrWM /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:21:29 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create mcUuOlzrWM /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 6 14:21:29 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:21:29 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:21:29 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:29 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close mcUuOlzrWM Oct 6 14:21:40 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:21:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:21:40 storageqe-109 journal: veritysetup close mcUuOlzrWM Oct 6 14:21:50 storageqe-109 kernel: sde: Oct 6 14:21:50 storageqe-109 kernel: sde: Oct 6 14:21:50 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:21:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:22:11 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wRgGBPfTyA /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:22:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wRgGBPfTyA /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:22:28 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close wRgGBPfTyA Oct 6 14:22:45 storageqe-109 journal: veritysetup close wRgGBPfTyA veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:22:55 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DoaTwUNEvr /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:23:05 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DoaTwUNEvr /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:23:05 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:23:05 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:23:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:06 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close DoaTwUNEvr Oct 6 14:23:16 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:23:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:23:16 storageqe-109 journal: veritysetup close DoaTwUNEvr veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:23:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:23:46 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SCfiGPeTud /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:24:03 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SCfiGPeTud /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:24:03 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close SCfiGPeTud Oct 6 14:24:20 storageqe-109 journal: veritysetup close SCfiGPeTud veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:24:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AixSsUVFmp /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:24:46 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AixSsUVFmp /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:24:46 storageqe-109 auditd[957]: Audit daemon rotating log files Oct 6 14:24:46 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:47 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close AixSsUVFmp Oct 6 14:24:56 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:24:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:24:56 storageqe-109 journal: veritysetup close AixSsUVFmp veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 14:25:11 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:25:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JSIwLEpfGd /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:25:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JSIwLEpfGd /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:25:44 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close JSIwLEpfGd Oct 6 14:26:02 storageqe-109 journal: veritysetup close JSIwLEpfGd veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:26:12 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RnkKCmATuz /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:26:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RnkKCmATuz /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:26:22 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:22 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close RnkKCmATuz Oct 6 14:26:32 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:26:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:26:32 storageqe-109 journal: veritysetup close RnkKCmATuz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:26:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:27:04 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ckzHGMEVKg /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:27:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ckzHGMEVKg /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:27:20 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close ckzHGMEVKg Oct 6 14:27:38 storageqe-109 journal: veritysetup close ckzHGMEVKg veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:27:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mZcBAxztyV /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:28:05 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mZcBAxztyV /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:28:05 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:05 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close mZcBAxztyV Oct 6 14:28:15 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:28:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:28:15 storageqe-109 journal: veritysetup close mZcBAxztyV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:28:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:28:46 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lpngBwbcfe /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:29:03 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lpngBwbcfe /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:29:03 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close lpngBwbcfe Oct 6 14:29:20 storageqe-109 journal: veritysetup close lpngBwbcfe veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:29:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create uTgoUjILpM /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:29:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create uTgoUjILpM /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:29:40 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:29:40 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:29:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:41 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close uTgoUjILpM Oct 6 14:29:51 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:29:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:29:51 storageqe-109 journal: veritysetup close uTgoUjILpM veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:30:05 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:30:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VnvGtBRfdo /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:30:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VnvGtBRfdo /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:30:38 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close VnvGtBRfdo Oct 6 14:30:56 storageqe-109 journal: veritysetup close VnvGtBRfdo veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:31:06 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hVqEJSkjxB /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:31:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hVqEJSkjxB /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:31:22 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:31:22 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:31:22 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:22 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:22 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:22 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close hVqEJSkjxB Oct 6 14:31:32 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:31:33 storageqe-109 journal: veritysetup close hVqEJSkjxB veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 14:31:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:32:04 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zHnaPutZio /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:32:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zHnaPutZio /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:32:20 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close zHnaPutZio Oct 6 14:32:38 storageqe-109 journal: veritysetup close zHnaPutZio veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:32:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create crAoSKftWk /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:32:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create crAoSKftWk /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:32:58 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:32:58 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close crAoSKftWk Oct 6 14:33:08 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:33:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:33:08 storageqe-109 journal: veritysetup close crAoSKftWk veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:33:23 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:33:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create beDajGYsBL /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:33:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create beDajGYsBL /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:33:56 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close beDajGYsBL Oct 6 14:34:14 storageqe-109 journal: veritysetup close beDajGYsBL veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:34:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UwWphCAQds /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:34:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UwWphCAQds /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 6 14:34:40 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:34:40 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:34:40 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:40 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:40 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:40 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:40 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:40 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:34:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:41 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close UwWphCAQds Oct 6 14:34:50 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:34:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:34:50 storageqe-109 journal: veritysetup close UwWphCAQds Oct 6 14:35:01 storageqe-109 kernel: sde: sde1 Oct 6 14:35:01 storageqe-109 kernel: sde: Oct 6 14:35:01 storageqe-109 kernel: sde: Oct 6 14:35:01 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:35:05 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:35:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create HrliwdAGpv /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:35:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create HrliwdAGpv /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:35:39 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close HrliwdAGpv Oct 6 14:35:56 storageqe-109 journal: veritysetup close HrliwdAGpv veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:36:06 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create GeETyDchiz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:36:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create GeETyDchiz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:36:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:17 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close GeETyDchiz Oct 6 14:36:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:36:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:36:27 storageqe-109 journal: veritysetup close GeETyDchiz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:36:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:36:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create bHcEvBafjl /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:37:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create bHcEvBafjl /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:37:14 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close bHcEvBafjl Oct 6 14:37:32 storageqe-109 journal: veritysetup close bHcEvBafjl veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:37:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create izAUVPZobE /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:37:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create izAUVPZobE /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:37:59 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:37:59 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close izAUVPZobE Oct 6 14:38:09 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:38:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:38:09 storageqe-109 journal: veritysetup close izAUVPZobE veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 14:38:23 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:38:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create ORtgqWomNp /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:38:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create ORtgqWomNp /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:38:57 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close ORtgqWomNp Oct 6 14:39:15 storageqe-109 journal: veritysetup close ORtgqWomNp veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:39:25 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create iAOwItzrhH /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:39:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create iAOwItzrhH /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:39:35 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:35 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close iAOwItzrhH Oct 6 14:39:45 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:39:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:39:45 storageqe-109 journal: veritysetup close iAOwItzrhH veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:39:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:40:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WSIXJhPlMY /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:40:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WSIXJhPlMY /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:40:33 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close WSIXJhPlMY Oct 6 14:40:50 storageqe-109 journal: veritysetup close WSIXJhPlMY veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:41:00 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WActznRiwF /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:41:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WActznRiwF /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:41:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:17 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close WActznRiwF Oct 6 14:41:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:41:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:41:27 storageqe-109 journal: veritysetup close WActznRiwF veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:41:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:41:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create iqWUZPduhw /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:42:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create iqWUZPduhw /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:42:15 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close iqWUZPduhw Oct 6 14:42:32 storageqe-109 journal: veritysetup close iqWUZPduhw veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:42:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create zcQAepFNVf /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:42:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create zcQAepFNVf /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:42:53 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:42:53 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zcQAepFNVf Oct 6 14:43:03 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:43:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:43:03 storageqe-109 journal: veritysetup close zcQAepFNVf veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:43:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:43:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create IWdvQEhtSc /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:43:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create IWdvQEhtSc /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:43:50 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close IWdvQEhtSc Oct 6 14:44:08 storageqe-109 journal: veritysetup close IWdvQEhtSc veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:44:18 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create VKCHDoBAzx /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:44:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create VKCHDoBAzx /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:44:35 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:35 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close VKCHDoBAzx Oct 6 14:44:45 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:44:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:44:45 storageqe-109 journal: veritysetup close VKCHDoBAzx veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 6 14:44:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:45:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create fPNCJniTaw /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:45:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create fPNCJniTaw /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:45:32 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close fPNCJniTaw Oct 6 14:45:50 storageqe-109 journal: veritysetup close fPNCJniTaw Oct 6 14:45:50 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 14:45:50 storageqe-109 dnf[1102151]: Updating Subscription Management repositories. Oct 6 14:45:50 storageqe-109 dnf[1102151]: Unable to read consumer identity Oct 6 14:45:50 storageqe-109 dnf[1102151]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 14:45:50 storageqe-109 dnf[1102151]: Metadata cache refreshed recently. Oct 6 14:45:50 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 14:45:50 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:46:00 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WpNCxiuTEn /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:46:10 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WpNCxiuTEn /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:46:10 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:10 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close WpNCxiuTEn Oct 6 14:46:20 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:46:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:46:20 storageqe-109 journal: veritysetup close WpNCxiuTEn veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 6 14:46:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:46:51 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create NsgmReVEPf /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:47:08 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create NsgmReVEPf /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:47:08 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close NsgmReVEPf Oct 6 14:47:26 storageqe-109 journal: veritysetup close NsgmReVEPf veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:47:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create GnLbQAEzvM /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:47:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create GnLbQAEzvM /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 14:47:53 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:47:53 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close GnLbQAEzvM Oct 6 14:48:03 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:48:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:48:03 storageqe-109 journal: veritysetup close GnLbQAEzvM Oct 6 14:48:13 storageqe-109 kernel: sde: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:48:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:48:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XSaybIsgQp /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:48:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XSaybIsgQp /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:48:37 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close XSaybIsgQp Oct 6 14:48:47 storageqe-109 journal: veritysetup close XSaybIsgQp veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:48:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FItsUaXTWR /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:49:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FItsUaXTWR /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:49:07 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:07 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close FItsUaXTWR Oct 6 14:49:17 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:49:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:49:17 storageqe-109 journal: veritysetup close FItsUaXTWR veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:49:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:49:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jtXLWCurgV /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:49:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jtXLWCurgV /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:49:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close jtXLWCurgV Oct 6 14:50:01 storageqe-109 journal: veritysetup close jtXLWCurgV veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:50:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HgdyPvjNzF /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:50:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HgdyPvjNzF /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:50:21 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:21 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close HgdyPvjNzF Oct 6 14:50:31 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:50:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:50:31 storageqe-109 journal: veritysetup close HgdyPvjNzF veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 14:50:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:50:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hFwWmSclro /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:51:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hFwWmSclro /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:51:05 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close hFwWmSclro Oct 6 14:51:15 storageqe-109 journal: veritysetup close hFwWmSclro veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:51:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create IoOiDFJcvd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:51:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create IoOiDFJcvd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:51:35 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:35 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close IoOiDFJcvd Oct 6 14:51:45 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:51:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:51:45 storageqe-109 journal: veritysetup close IoOiDFJcvd veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:51:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:52:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ebzXHqIAKc /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:52:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ebzXHqIAKc /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:52:19 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ebzXHqIAKc Oct 6 14:52:29 storageqe-109 journal: veritysetup close ebzXHqIAKc veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:52:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jdupBYzRkQ /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:52:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jdupBYzRkQ /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:52:49 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:49 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close jdupBYzRkQ Oct 6 14:52:59 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:52:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:52:59 storageqe-109 journal: veritysetup close jdupBYzRkQ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:53:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:53:23 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WvbNOHrXFm /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:53:33 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WvbNOHrXFm /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:53:33 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close WvbNOHrXFm Oct 6 14:53:43 storageqe-109 journal: veritysetup close WvbNOHrXFm veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:53:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xCZyMsEUWT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:54:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xCZyMsEUWT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:54:03 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:03 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close xCZyMsEUWT Oct 6 14:54:13 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:54:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:54:13 storageqe-109 journal: veritysetup close xCZyMsEUWT veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:54:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:54:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sEwFqBLfJX /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:54:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sEwFqBLfJX /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:54:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close sEwFqBLfJX Oct 6 14:54:57 storageqe-109 journal: veritysetup close sEwFqBLfJX veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:55:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TNJZPrCFoy /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:55:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TNJZPrCFoy /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:55:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:17 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close TNJZPrCFoy Oct 6 14:55:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:55:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:55:27 storageqe-109 journal: veritysetup close TNJZPrCFoy veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 14:55:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:55:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create IVPiuqCTpw /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:56:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create IVPiuqCTpw /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:56:01 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close IVPiuqCTpw Oct 6 14:56:11 storageqe-109 journal: veritysetup close IVPiuqCTpw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:56:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DsmNTORIph /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:56:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DsmNTORIph /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:56:31 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:31 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close DsmNTORIph Oct 6 14:56:41 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:56:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:56:41 storageqe-109 journal: veritysetup close DsmNTORIph veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:56:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:57:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create voqwjLOIFg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:57:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create voqwjLOIFg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:57:15 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close voqwjLOIFg Oct 6 14:57:25 storageqe-109 journal: veritysetup close voqwjLOIFg veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:57:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jWQtfAdMmD /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:57:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jWQtfAdMmD /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:57:45 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:46 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close jWQtfAdMmD Oct 6 14:57:55 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:57:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 14:57:55 storageqe-109 journal: veritysetup close jWQtfAdMmD veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:58:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:58:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OdYyjqsHrW /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:58:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OdYyjqsHrW /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:58:29 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close OdYyjqsHrW Oct 6 14:58:39 storageqe-109 journal: veritysetup close OdYyjqsHrW veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:58:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create klzibqfsIS /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:58:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create klzibqfsIS /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 14:58:59 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:58:59 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close klzibqfsIS Oct 6 14:59:09 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 14:59:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 14:59:09 storageqe-109 journal: veritysetup close klzibqfsIS veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 14:59:23 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:59:33 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DTsGlkCcVg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:59:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DTsGlkCcVg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 14:59:43 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close DTsGlkCcVg Oct 6 14:59:53 storageqe-109 journal: veritysetup close DTsGlkCcVg veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:00:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ajwxKYGNSI /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:00:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ajwxKYGNSI /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:00:13 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:14 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ajwxKYGNSI Oct 6 15:00:23 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:00:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:00:23 storageqe-109 journal: veritysetup close ajwxKYGNSI veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:00:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:00:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PRCydQNbkn /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:00:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PRCydQNbkn /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:00:57 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close PRCydQNbkn Oct 6 15:01:07 storageqe-109 journal: veritysetup close PRCydQNbkn veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:01:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PxmdgblSHo /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:01:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PxmdgblSHo /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:01:27 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:28 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close PxmdgblSHo Oct 6 15:01:37 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:01:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:01:37 storageqe-109 journal: veritysetup close PxmdgblSHo veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:01:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:02:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UOJmsloVPL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:02:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UOJmsloVPL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:02:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close UOJmsloVPL Oct 6 15:02:21 storageqe-109 journal: veritysetup close UOJmsloVPL veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:02:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NxIswQhTEO /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:02:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NxIswQhTEO /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:02:41 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:02:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:42 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close NxIswQhTEO Oct 6 15:02:51 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:02:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:02:51 storageqe-109 journal: veritysetup close NxIswQhTEO veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:03:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:03:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dSgEmtNOrK /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:03:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dSgEmtNOrK /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:03:25 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close dSgEmtNOrK Oct 6 15:03:35 storageqe-109 journal: veritysetup close dSgEmtNOrK veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:03:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OSPrqEsFRy /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:03:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OSPrqEsFRy /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:03:55 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:03:55 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:03:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:03:56 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close OSPrqEsFRy Oct 6 15:04:05 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:04:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:04:05 storageqe-109 journal: veritysetup close OSPrqEsFRy veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:04:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:04:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SiEuAlbepk /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:04:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SiEuAlbepk /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:04:39 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close SiEuAlbepk Oct 6 15:04:49 storageqe-109 journal: veritysetup close SiEuAlbepk veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:04:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zTrDkisbIf /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:05:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zTrDkisbIf /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:05:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:05:09 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:05:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:10 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zTrDkisbIf Oct 6 15:05:20 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:05:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:05:20 storageqe-109 journal: veritysetup close zTrDkisbIf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:05:33 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:05:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pyDdtwhLCJ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:05:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pyDdtwhLCJ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:05:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close pyDdtwhLCJ Oct 6 15:06:03 storageqe-109 journal: veritysetup close pyDdtwhLCJ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:06:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JhYZzUvtKP /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:06:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JhYZzUvtKP /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:06:24 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:24 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close JhYZzUvtKP Oct 6 15:06:34 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:06:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:06:34 storageqe-109 journal: veritysetup close JhYZzUvtKP veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:06:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:06:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YzAEroVZFb /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:07:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YzAEroVZFb /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:07:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close YzAEroVZFb Oct 6 15:07:17 storageqe-109 journal: veritysetup close YzAEroVZFb veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:07:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BCvbeKjaZy /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:07:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BCvbeKjaZy /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:07:38 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:38 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close BCvbeKjaZy Oct 6 15:07:48 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:07:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:07:48 storageqe-109 journal: veritysetup close BCvbeKjaZy veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:08:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:08:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YCGNFPiXpE /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:08:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YCGNFPiXpE /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:08:21 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close YCGNFPiXpE Oct 6 15:08:31 storageqe-109 journal: veritysetup close YCGNFPiXpE veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:08:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create yocXARNbGp /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:08:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create yocXARNbGp /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:08:52 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:08:52 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close yocXARNbGp Oct 6 15:09:02 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:09:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:09:02 storageqe-109 journal: veritysetup close yocXARNbGp veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:09:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:09:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create boiCTYfyhm /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:09:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create boiCTYfyhm /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:09:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close boiCTYfyhm Oct 6 15:09:45 storageqe-109 journal: veritysetup close boiCTYfyhm veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:09:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create cIOhUHieqg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:10:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create cIOhUHieqg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:10:06 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:06 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close cIOhUHieqg Oct 6 15:10:16 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:10:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:10:16 storageqe-109 journal: veritysetup close cIOhUHieqg veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:10:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:10:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DlLFpNTrQE /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:10:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DlLFpNTrQE /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:10:49 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close DlLFpNTrQE Oct 6 15:11:00 storageqe-109 journal: veritysetup close DlLFpNTrQE veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:11:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HiMOjAWEFa /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:11:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HiMOjAWEFa /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:11:20 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:20 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close HiMOjAWEFa Oct 6 15:11:30 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:11:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:11:30 storageqe-109 journal: veritysetup close HiMOjAWEFa veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:11:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:11:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CIZoAUXtbY /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:12:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CIZoAUXtbY /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:12:04 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close CIZoAUXtbY Oct 6 15:12:14 storageqe-109 journal: veritysetup close CIZoAUXtbY veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:12:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zvYMkXHlqW /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:12:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zvYMkXHlqW /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:12:34 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:34 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zvYMkXHlqW Oct 6 15:12:44 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:12:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:12:44 storageqe-109 journal: veritysetup close zvYMkXHlqW veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:12:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:13:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QEexWoFsDK /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:13:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QEexWoFsDK /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:13:18 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close QEexWoFsDK Oct 6 15:13:28 storageqe-109 journal: veritysetup close QEexWoFsDK veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:13:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OHRQfcMpDL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:13:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OHRQfcMpDL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:13:48 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:48 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close OHRQfcMpDL Oct 6 15:13:58 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:13:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:13:58 storageqe-109 journal: veritysetup close OHRQfcMpDL veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:14:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:14:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OWTYbDgUoz /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:14:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OWTYbDgUoz /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:14:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close OWTYbDgUoz Oct 6 15:14:42 storageqe-109 journal: veritysetup close OWTYbDgUoz veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:14:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VyUFTvJjhk /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:15:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VyUFTvJjhk /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:15:02 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:02 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close VyUFTvJjhk Oct 6 15:15:12 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:15:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:15:12 storageqe-109 journal: veritysetup close VyUFTvJjhk veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:15:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:15:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nZKraOUBLD /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:15:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nZKraOUBLD /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:15:46 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close nZKraOUBLD Oct 6 15:15:56 storageqe-109 journal: veritysetup close nZKraOUBLD veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:16:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create matoqwLMFD /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:16:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create matoqwLMFD /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:16:16 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:16 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close matoqwLMFD Oct 6 15:16:26 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:16:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:16:26 storageqe-109 journal: veritysetup close matoqwLMFD veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:16:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:16:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create asuEdhZWvH /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:17:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create asuEdhZWvH /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:17:00 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close asuEdhZWvH Oct 6 15:17:10 storageqe-109 journal: veritysetup close asuEdhZWvH veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:17:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create yONbVSTgas /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:17:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create yONbVSTgas /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:17:30 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:30 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close yONbVSTgas Oct 6 15:17:40 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:17:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:17:40 storageqe-109 journal: veritysetup close yONbVSTgas veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:17:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:18:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xOcVIUgCPe /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:18:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xOcVIUgCPe /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:18:14 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close xOcVIUgCPe Oct 6 15:18:24 storageqe-109 journal: veritysetup close xOcVIUgCPe veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:18:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lAnodMENYi /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:18:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lAnodMENYi /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:18:44 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:44 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close lAnodMENYi Oct 6 15:18:54 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:18:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:18:54 storageqe-109 journal: veritysetup close lAnodMENYi veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:19:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:19:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NiXIsSPlMd /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:19:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NiXIsSPlMd /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:19:28 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close NiXIsSPlMd Oct 6 15:19:38 storageqe-109 journal: veritysetup close NiXIsSPlMd veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:19:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zoIRXGxiWF /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:19:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zoIRXGxiWF /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:19:58 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:19:58 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zoIRXGxiWF Oct 6 15:20:08 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:20:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:20:08 storageqe-109 journal: veritysetup close zoIRXGxiWF veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:20:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:20:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vJUqLMGljS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:20:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vJUqLMGljS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:20:42 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close vJUqLMGljS Oct 6 15:20:52 storageqe-109 journal: veritysetup close vJUqLMGljS veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:21:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iEsjIcJmof /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:21:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iEsjIcJmof /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:21:12 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:12 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close iEsjIcJmof Oct 6 15:21:22 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:21:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:21:22 storageqe-109 journal: veritysetup close iEsjIcJmof veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:21:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:21:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XzUIOAsrwR /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:21:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XzUIOAsrwR /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:21:56 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close XzUIOAsrwR Oct 6 15:22:06 storageqe-109 journal: veritysetup close XzUIOAsrwR veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:22:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pIgmBYanNM /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:22:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pIgmBYanNM /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:22:26 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:26 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close pIgmBYanNM Oct 6 15:22:36 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:22:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:22:36 storageqe-109 journal: veritysetup close pIgmBYanNM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:22:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:23:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pedUYClLan /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:23:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pedUYClLan /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:23:10 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close pedUYClLan Oct 6 15:23:20 storageqe-109 journal: veritysetup close pedUYClLan veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:23:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create egTdGLZmIF /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:23:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create egTdGLZmIF /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:23:40 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:40 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close egTdGLZmIF Oct 6 15:23:50 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:23:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:23:50 storageqe-109 journal: veritysetup close egTdGLZmIF veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:24:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:24:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZAcRGCIhJM /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:24:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZAcRGCIhJM /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:24:24 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close ZAcRGCIhJM Oct 6 15:24:34 storageqe-109 journal: veritysetup close ZAcRGCIhJM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:24:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jeyZAvEWur /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:24:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jeyZAvEWur /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:24:54 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:24:55 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close jeyZAvEWur Oct 6 15:25:04 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:25:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:25:04 storageqe-109 journal: veritysetup close jeyZAvEWur veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:25:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:25:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create KPGeFAwcVd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:25:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create KPGeFAwcVd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:25:38 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close KPGeFAwcVd Oct 6 15:25:48 storageqe-109 journal: veritysetup close KPGeFAwcVd veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:25:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NibXdfWlOS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:26:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NibXdfWlOS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:26:08 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 rsyslogd[1103]: imjournal: journal files changed, reloading... [v8.2506.0-2.el10 try https://www.rsyslog.com/e/0 ] Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:08 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close NibXdfWlOS Oct 6 15:26:18 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:26:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:26:18 storageqe-109 journal: veritysetup close NibXdfWlOS veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:26:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:26:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iGnfxXOAvR /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:26:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iGnfxXOAvR /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:26:52 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close iGnfxXOAvR Oct 6 15:27:02 storageqe-109 journal: veritysetup close iGnfxXOAvR veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:27:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HNnMwOCSDB /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:27:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HNnMwOCSDB /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 6 15:27:22 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:23 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close HNnMwOCSDB Oct 6 15:27:32 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:27:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:27:32 storageqe-109 journal: veritysetup close HNnMwOCSDB veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:27:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:27:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create bAzouYsPUZ /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:28:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create bAzouYsPUZ /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:28:06 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close bAzouYsPUZ Oct 6 15:28:16 storageqe-109 journal: veritysetup close bAzouYsPUZ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:28:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create UTbqGnsFyh /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:28:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create UTbqGnsFyh /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:28:36 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:37 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close UTbqGnsFyh Oct 6 15:28:46 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:28:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:28:46 storageqe-109 journal: veritysetup close UTbqGnsFyh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:29:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:29:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create qVMLbuoKDZ /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:29:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create qVMLbuoKDZ /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:29:20 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close qVMLbuoKDZ Oct 6 15:29:30 storageqe-109 journal: veritysetup close qVMLbuoKDZ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:29:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create zRywKMSgnI /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:29:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create zRywKMSgnI /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:29:50 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:29:51 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zRywKMSgnI Oct 6 15:30:00 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:30:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:30:00 storageqe-109 journal: veritysetup close zRywKMSgnI veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:30:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:30:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create pUkKejVhXb /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:30:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create pUkKejVhXb /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:30:34 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close pUkKejVhXb Oct 6 15:30:44 storageqe-109 journal: veritysetup close pUkKejVhXb veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:30:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create oskDUVnAXd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:31:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create oskDUVnAXd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:31:04 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:05 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close oskDUVnAXd Oct 6 15:31:14 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:31:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:31:14 storageqe-109 journal: veritysetup close oskDUVnAXd veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:31:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:31:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create zGnvLpDAgh /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:31:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create zGnvLpDAgh /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:31:48 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close zGnvLpDAgh Oct 6 15:31:58 storageqe-109 journal: veritysetup close zGnvLpDAgh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:32:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dqzTGwHLBC /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:32:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dqzTGwHLBC /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:32:18 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:32:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:19 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close dqzTGwHLBC Oct 6 15:32:28 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:32:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:32:28 storageqe-109 journal: veritysetup close dqzTGwHLBC veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:32:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:32:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create PSrCQknuAL /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:33:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create PSrCQknuAL /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:33:02 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close PSrCQknuAL Oct 6 15:33:12 storageqe-109 journal: veritysetup close PSrCQknuAL veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:33:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create THuYADxNXn /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:33:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create THuYADxNXn /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:33:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:33:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:33 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close THuYADxNXn Oct 6 15:33:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:33:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:33:42 storageqe-109 journal: veritysetup close THuYADxNXn veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:33:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:34:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create SDIMhYgCuA /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:34:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create SDIMhYgCuA /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:34:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close SDIMhYgCuA Oct 6 15:34:26 storageqe-109 journal: veritysetup close SDIMhYgCuA veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:34:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create bPMYRFshqw /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:34:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create bPMYRFshqw /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:34:46 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:34:46 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:34:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:34:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:47 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close bPMYRFshqw Oct 6 15:34:56 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:34:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:34:56 storageqe-109 journal: veritysetup close bPMYRFshqw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:35:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:35:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create yHFIvdNOpM /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:35:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create yHFIvdNOpM /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:35:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close yHFIvdNOpM Oct 6 15:35:40 storageqe-109 journal: veritysetup close yHFIvdNOpM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:35:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create GKRzpLUrXh /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:36:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create GKRzpLUrXh /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:36:00 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:36:00 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 15:36:00 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 15:36:01 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 15:36:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:01 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close GKRzpLUrXh Oct 6 15:36:10 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:36:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:36:11 storageqe-109 journal: veritysetup close GKRzpLUrXh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:36:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:36:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create uVRgkKjdMv /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:36:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create uVRgkKjdMv /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:36:44 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close uVRgkKjdMv Oct 6 15:36:54 storageqe-109 journal: veritysetup close uVRgkKjdMv veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:37:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create oZSJwFNryc /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:37:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create oZSJwFNryc /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 6 15:37:14 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 15:37:14 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:37:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:15 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close oZSJwFNryc Oct 6 15:37:25 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:37:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:37:25 storageqe-109 journal: veritysetup close oZSJwFNryc veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:37:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:37:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SjdoRznbQM /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:37:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SjdoRznbQM /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:37:58 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close SjdoRznbQM Oct 6 15:38:08 storageqe-109 journal: veritysetup close SjdoRznbQM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:38:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jeFktcRydD /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:38:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jeFktcRydD /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:38:28 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:38:28 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:38:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:29 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close jeFktcRydD Oct 6 15:38:39 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:38:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:38:39 storageqe-109 journal: veritysetup close jeFktcRydD veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:38:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:39:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create tZbmIeYuTn /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:39:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create tZbmIeYuTn /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:39:12 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close tZbmIeYuTn Oct 6 15:39:22 storageqe-109 journal: veritysetup close tZbmIeYuTn veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:39:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ODGfWgiSYw /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:39:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ODGfWgiSYw /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:39:42 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:39:43 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:43 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ODGfWgiSYw Oct 6 15:39:53 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:39:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:39:53 storageqe-109 journal: veritysetup close ODGfWgiSYw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:40:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:40:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nSxWBzYRpo /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:40:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nSxWBzYRpo /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:40:26 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close nSxWBzYRpo Oct 6 15:40:36 storageqe-109 journal: veritysetup close nSxWBzYRpo veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:40:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QbwkLjSZih /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:40:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QbwkLjSZih /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:40:57 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:40:57 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close QbwkLjSZih Oct 6 15:41:07 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:41:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:41:07 storageqe-109 journal: veritysetup close QbwkLjSZih veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:41:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:41:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sAxgHqnXCO /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:41:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sAxgHqnXCO /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:41:40 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close sAxgHqnXCO Oct 6 15:41:50 storageqe-109 journal: veritysetup close sAxgHqnXCO veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:42:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JdnpRoXEYO /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:42:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JdnpRoXEYO /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:42:11 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:11 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close JdnpRoXEYO Oct 6 15:42:21 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:42:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:42:21 storageqe-109 journal: veritysetup close JdnpRoXEYO veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:42:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:42:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AoEHZbejNg /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:42:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AoEHZbejNg /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:42:54 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close AoEHZbejNg Oct 6 15:43:04 storageqe-109 journal: veritysetup close AoEHZbejNg veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:43:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zveVGnCdRu /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:43:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zveVGnCdRu /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:43:25 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:25 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zveVGnCdRu Oct 6 15:43:35 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:43:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:43:35 storageqe-109 journal: veritysetup close zveVGnCdRu veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:43:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:43:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jSLnDhEltr /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:44:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jSLnDhEltr /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:44:08 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close jSLnDhEltr Oct 6 15:44:18 storageqe-109 journal: veritysetup close jSLnDhEltr veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:44:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PFcyjMserw /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:44:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PFcyjMserw /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:44:39 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:39 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close PFcyjMserw Oct 6 15:44:49 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:44:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:44:49 storageqe-109 journal: veritysetup close PFcyjMserw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:45:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:45:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DsYcjZbdLI /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:45:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create DsYcjZbdLI /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:45:22 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close DsYcjZbdLI Oct 6 15:45:32 storageqe-109 journal: veritysetup close DsYcjZbdLI veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:45:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pRyGZwCvjF /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:45:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pRyGZwCvjF /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:45:53 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:45:53 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close pRyGZwCvjF Oct 6 15:46:03 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:46:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:46:03 storageqe-109 journal: veritysetup close pRyGZwCvjF veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:46:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:46:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PHQDUltxap /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:46:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PHQDUltxap /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:46:36 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close PHQDUltxap Oct 6 15:46:47 storageqe-109 journal: veritysetup close PHQDUltxap veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:46:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wcKmlRAZQh /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:47:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wcKmlRAZQh /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:47:07 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:07 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close wcKmlRAZQh Oct 6 15:47:17 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:47:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:47:17 storageqe-109 journal: veritysetup close wcKmlRAZQh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:47:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:47:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create JmUzLglqjh /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:47:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create JmUzLglqjh /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:47:50 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close JmUzLglqjh Oct 6 15:48:01 storageqe-109 journal: veritysetup close JmUzLglqjh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:48:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create LRIxlhtVmY /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:48:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create LRIxlhtVmY /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:48:21 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:21 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close LRIxlhtVmY Oct 6 15:48:31 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:48:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:48:31 storageqe-109 journal: veritysetup close LRIxlhtVmY veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:48:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:48:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create EtTabysAHD /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:49:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create EtTabysAHD /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:49:04 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close EtTabysAHD Oct 6 15:49:15 storageqe-109 journal: veritysetup close EtTabysAHD veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:49:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create gTzCfGZAhM /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:49:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create gTzCfGZAhM /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:49:35 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:35 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close gTzCfGZAhM Oct 6 15:49:45 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:49:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:49:45 storageqe-109 journal: veritysetup close gTzCfGZAhM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:49:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:50:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create nwjBcuIstr /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:50:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create nwjBcuIstr /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:50:18 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close nwjBcuIstr Oct 6 15:50:29 storageqe-109 journal: veritysetup close nwjBcuIstr veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:50:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create wUhVAHcZGq /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:50:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create wUhVAHcZGq /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:50:49 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:49 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close wUhVAHcZGq Oct 6 15:50:59 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:50:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:50:59 storageqe-109 journal: veritysetup close wUhVAHcZGq veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:51:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:51:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create wQvhCnWcAf /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:51:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create wQvhCnWcAf /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:51:32 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close wQvhCnWcAf Oct 6 15:51:43 storageqe-109 journal: veritysetup close wQvhCnWcAf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:51:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create LHrdiFtAOc /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:52:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create LHrdiFtAOc /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:52:03 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:03 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close LHrdiFtAOc Oct 6 15:52:13 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:52:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:52:13 storageqe-109 journal: veritysetup close LHrdiFtAOc veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:52:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:52:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create OAcTWILixM /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:52:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create OAcTWILixM /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:52:47 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close OAcTWILixM Oct 6 15:52:57 storageqe-109 journal: veritysetup close OAcTWILixM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:53:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create kYzhdNKajq /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:53:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create kYzhdNKajq /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:53:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:17 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close kYzhdNKajq Oct 6 15:53:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:53:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:53:27 storageqe-109 journal: veritysetup close kYzhdNKajq veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:53:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:53:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create GoZdBMEHmu /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:54:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create GoZdBMEHmu /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:54:01 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close GoZdBMEHmu Oct 6 15:54:11 storageqe-109 journal: veritysetup close GoZdBMEHmu veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:54:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create EODopnqlRc /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:54:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create EODopnqlRc /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:54:31 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:31 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close EODopnqlRc Oct 6 15:54:41 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:54:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:54:41 storageqe-109 journal: veritysetup close EODopnqlRc veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 6 15:54:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:55:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create FfnkUSOswC /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:55:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create FfnkUSOswC /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:55:15 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close FfnkUSOswC Oct 6 15:55:25 storageqe-109 journal: veritysetup close FfnkUSOswC veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:55:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create IXvehDmJWp /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:55:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create IXvehDmJWp /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:55:45 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:45 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close IXvehDmJWp Oct 6 15:55:55 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:55:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 15:55:55 storageqe-109 journal: veritysetup close IXvehDmJWp veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 6 15:56:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:56:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create JYohBMnUWX /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:56:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create JYohBMnUWX /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:56:29 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close JYohBMnUWX Oct 6 15:56:39 storageqe-109 journal: veritysetup close JYohBMnUWX veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:56:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create dnSEPptOrI /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:56:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create dnSEPptOrI /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 6 15:56:59 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:56:59 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close dnSEPptOrI Oct 6 15:57:09 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 15:57:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 6 15:57:09 storageqe-109 journal: veritysetup close dnSEPptOrI INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_check[npo2_linear] #### INFO: #### will start test_dm_verity_format[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 15:57:24 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 15:57:24 storageqe-109 INFO: #### END test_dm_verity_check[npo2_linear] #### Oct 6 15:57:24 storageqe-109 INFO: #### will start test_dm_verity_format[npo2_linear] ##### Oct 6 15:57:24 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 15:57:29 storageqe-109 kernel: loop3: detected capacity change from 0 to 12582912 Oct 6 15:57:29 storageqe-109 kernel: sde: Oct 6 15:57:29 storageqe-109 kernel: sde: sde1 Oct 6 15:57:29 storageqe-109 kernel: loop4: detected capacity change from 0 to 12582912 veritysetup --fec-device '/dev/sdd1' --fec-roots '2' --hash 'sha256' format /dev/mapper/npo2linear /dev/sde1 Oct 6 15:57:29 storageqe-109 kernel: sdd: Oct 6 15:57:30 storageqe-109 kernel: sdd: sdd1 Oct 6 15:57:30 storageqe-109 journal: veritysetup --fec-device '/dev/sdd1' --fec-roots '2' --hash 'sha256' format /dev/mapper/npo2linear /dev/sde1 Oct 6 15:58:26 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 15:58:26 storageqe-109 dnf[1115382]: Updating Subscription Management repositories. Oct 6 15:58:26 storageqe-109 dnf[1115382]: Unable to read consumer identity Oct 6 15:58:26 storageqe-109 dnf[1115382]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 15:58:26 storageqe-109 dnf[1115382]: Metadata cache refreshed recently. Oct 6 15:58:26 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 15:58:26 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. veritysetup verify /dev/mapper/npo2linear /dev/sde1 9c6655a1630516002cc05aaef3b993e21ee1b385da692563e9cd05697da20d22 Oct 6 15:58:36 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/sde1 9c6655a1630516002cc05aaef3b993e21ee1b385da692563e9cd05697da20d22 veritysetup verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 6 15:58:53 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 veritysetup --fec-device '/dev/sdd1' --fec-roots '2' verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 6 15:59:10 storageqe-109 journal: veritysetup --fec-device '/dev/sdd1' --fec-roots '2' verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 veritysetup open /dev/mapper/npo2linear mLkzIKoNdt /dev/sde1 9c6655a1630516002cc05aaef3b993e21ee1b385da692563e9cd05697da20d22 Oct 6 16:00:01 storageqe-109 journal: veritysetup open /dev/mapper/npo2linear mLkzIKoNdt /dev/sde1 9c6655a1630516002cc05aaef3b993e21ee1b385da692563e9cd05697da20d22 Oct 6 16:00:01 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close mLkzIKoNdt Oct 6 16:00:11 storageqe-109 journal: veritysetup close mLkzIKoNdt veritysetup open /dev/mapper/npo2linear mLkzIKoNdt /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 6 16:00:21 storageqe-109 journal: veritysetup open /dev/mapper/npo2linear mLkzIKoNdt /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 6 16:00:21 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 6 16:00:21 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close mLkzIKoNdt Oct 6 16:00:31 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 6 16:00:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 6 16:00:31 storageqe-109 journal: veritysetup close mLkzIKoNdt Oct 6 16:00:41 storageqe-109 kernel: sde: sde1 Oct 6 16:00:41 storageqe-109 kernel: sde: Oct 6 16:00:41 storageqe-109 kernel: sdd: sdd1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_format[npo2_linear] #### Oct 6 16:00:46 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:00:46 storageqe-109 INFO: #### END test_dm_verity_format[npo2_linear] #### Oct 6 16:00:48 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:00:48 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:00:49 storageqe-109 kernel: sdd: Oct 6 16:00:49 storageqe-109 kernel: sde: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 16:00:49 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 16:00:49 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 16:00:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 16:01:00 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_udisks_info[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:06 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:06 storageqe-109 INFO: #### will start test_udisks_info[npo2_linear] ##### Oct 6 16:01:06 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisks_info[npo2_linear] #### INFO: #### will start test_udisks_info_detailed[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:16 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:16 storageqe-109 INFO: #### END test_udisks_info[npo2_linear] #### Oct 6 16:01:16 storageqe-109 INFO: #### will start test_udisks_info_detailed[npo2_linear] ##### Oct 6 16:01:16 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:19 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisks_info_detailed[npo2_linear] #### INFO: #### will start test_udisksctl_smart_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:26 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:26 storageqe-109 INFO: #### END test_udisks_info_detailed[npo2_linear] #### Oct 6 16:01:26 storageqe-109 INFO: #### will start test_udisksctl_smart_operations[npo2_linear] ##### Oct 6 16:01:26 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_smart_operations[npo2_linear] #### INFO: #### will start test_udisksctl_filesystem_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:36 storageqe-109 INFO: #### END test_udisksctl_smart_operations[npo2_linear] #### Oct 6 16:01:36 storageqe-109 INFO: #### will start test_udisksctl_filesystem_operations[npo2_linear] ##### Oct 6 16:01:36 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8e9f09ac-60ce-4c03-b37a-a34fc987e132 r/w with ordered data mode. Quota mode: none. Oct 6 16:01:44 storageqe-109 udisksd[5174]: Mounted /dev/dm-3 at /run/media/root/8e9f09ac-60ce-4c03-b37a-a34fc987e132 on behalf of uid 0 Oct 6 16:01:44 storageqe-109 systemd[1]: run-media-root-8e9f09ac\x2d60ce\x2d4c03\x2db37a\x2da34fc987e132.mount: Deactivated successfully. Oct 6 16:01:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8e9f09ac-60ce-4c03-b37a-a34fc987e132. Oct 6 16:01:44 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/8e9f09ac-60ce-4c03-b37a-a34fc987e132 (device 253:3 is not mounted) Oct 6 16:01:44 storageqe-109 udisksd[5174]: Unmounted /dev/dm-3 on behalf of uid 0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_filesystem_operations[npo2_linear] #### INFO: #### will start test_udisksctl_power_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:49 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:49 storageqe-109 INFO: #### END test_udisksctl_filesystem_operations[npo2_linear] #### Oct 6 16:01:49 storageqe-109 INFO: #### will start test_udisksctl_power_operations[npo2_linear] ##### Oct 6 16:01:49 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_power_operations[npo2_linear] #### INFO: #### will start test_udisksctl_unlock_lock_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:59 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:01:59 storageqe-109 INFO: #### END test_udisksctl_power_operations[npo2_linear] #### Oct 6 16:01:59 storageqe-109 INFO: #### will start test_udisksctl_unlock_lock_operations[npo2_linear] ##### Oct 6 16:01:59 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:12 storageqe-109 stratisd[4947]: [2025-10-06T20:02:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:02:12 storageqe-109 stratisd[4947]: [2025-10-06T20:02:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:02:14 storageqe-109 stratisd[4947]: [2025-10-06T20:02:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:02:14 storageqe-109 stratisd[4947]: [2025-10-06T20:02:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:02:14 storageqe-109 udisksd[5174]: Unlocked device /dev/dm-3 as /dev/dm-4 Oct 6 16:02:14 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64772, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-4 now has another dm-uuid (NULL) Oct 6 16:02:14 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64772, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-4 now has another dm-uuid (NULL) Oct 6 16:02:14 storageqe-109 udisksd[5174]: Locked device /dev/dm-3 (was unlocked as /dev/dm-4) INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_unlock_lock_operations[npo2_linear] #### INFO: #### will start test_udisksctl_status ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:19 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:19 storageqe-109 INFO: #### END test_udisksctl_unlock_lock_operations[npo2_linear] #### Oct 6 16:02:19 storageqe-109 INFO: #### will start test_udisksctl_status ##### Oct 6 16:02:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_status #### INFO: #### will start test_udisksctl_dump ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:29 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:29 storageqe-109 INFO: #### END test_udisksctl_status #### Oct 6 16:02:30 storageqe-109 INFO: #### will start test_udisksctl_dump ##### Oct 6 16:02:30 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_dump #### INFO: #### will start test_udisksctl_monitor ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:40 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:40 storageqe-109 INFO: #### END test_udisksctl_dump #### Oct 6 16:02:40 storageqe-109 INFO: #### will start test_udisksctl_monitor ##### Oct 6 16:02:40 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_monitor #### INFO: #### will start test_udisksctl_loop_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:50 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:50 storageqe-109 INFO: #### END test_udisksctl_monitor #### Oct 6 16:02:50 storageqe-109 INFO: #### will start test_udisksctl_loop_operations ##### Oct 6 16:02:50 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:02:55 storageqe-109 kernel: loop0: detected capacity change from 0 to 20480 Oct 6 16:02:55 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /tmp/udisks_test_loop.img) Oct 6 16:02:55 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_test_loop.img) Oct 6 16:02:55 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_loop_operations #### INFO: #### will start test_udisksctl_help_commands ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:00 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:00 storageqe-109 INFO: #### END test_udisksctl_loop_operations #### Oct 6 16:03:00 storageqe-109 INFO: #### will start test_udisksctl_help_commands ##### Oct 6 16:03:00 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_help_commands #### INFO: #### will start test_udisksctl_error_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:10 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:10 storageqe-109 INFO: #### END test_udisksctl_help_commands #### Oct 6 16:03:10 storageqe-109 INFO: #### will start test_udisksctl_error_handling ##### Oct 6 16:03:10 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_error_handling #### INFO: #### will start test_udisksctl_special_characters ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:20 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:20 storageqe-109 INFO: #### END test_udisksctl_error_handling #### Oct 6 16:03:20 storageqe-109 INFO: #### will start test_udisksctl_special_characters ##### Oct 6 16:03:20 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_special_characters #### INFO: #### will start test_udisksctl_concurrent_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:31 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:31 storageqe-109 INFO: #### END test_udisksctl_special_characters #### Oct 6 16:03:31 storageqe-109 INFO: #### will start test_udisksctl_concurrent_operations ##### Oct 6 16:03:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_concurrent_operations #### INFO: #### will start test_udisksctl_large_output_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:41 storageqe-109 INFO: #### END test_udisksctl_concurrent_operations #### Oct 6 16:03:41 storageqe-109 INFO: #### will start test_udisksctl_large_output_handling ##### Oct 6 16:03:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_large_output_handling #### INFO: #### will start test_udisksctl_timeout_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:51 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:03:51 storageqe-109 INFO: #### END test_udisksctl_large_output_handling #### Oct 6 16:03:51 storageqe-109 INFO: #### will start test_udisksctl_timeout_handling ##### Oct 6 16:03:51 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_timeout_handling #### INFO: #### will start test_udisksctl_mount_point_special_characters ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:01 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:01 storageqe-109 INFO: #### END test_udisksctl_timeout_handling #### Oct 6 16:04:01 storageqe-109 INFO: #### will start test_udisksctl_mount_point_special_characters ##### Oct 6 16:04:01 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:06 storageqe-109 kernel: loop0: detected capacity change from 0 to 102400 Oct 6 16:04:06 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /tmp/udisks_mount_test.img) Oct 6 16:04:06 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:06 storageqe-109 systemd[1]: run-media-root-047e9f4e\x2d43ff\x2d45ae\x2dbdfa\x2d1e975922d340.mount: Deactivated successfully. Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 (device 7:0 is not mounted) Oct 6 16:04:06 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 (device 7:0 is not mounted) Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 (device 7:0 is not mounted) Oct 6 16:04:06 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 (device 7:0 is not mounted) Oct 6 16:04:06 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 on behalf of uid 0 Oct 6 16:04:06 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 (device 7:0 is not mounted) Oct 6 16:04:06 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340. Oct 6 16:04:06 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:07 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 on behalf of uid 0 Oct 6 16:04:07 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:07 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 (device 7:0 is not mounted) Oct 6 16:04:07 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340. Oct 6 16:04:07 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:07 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 on behalf of uid 0 Oct 6 16:04:07 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:07 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 047e9f4e-43ff-45ae-bdfa-1e975922d340. Oct 6 16:04:07 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/047e9f4e-43ff-45ae-bdfa-1e975922d340 (device 7:0 is not mounted) Oct 6 16:04:07 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:07 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_mount_test.img) Oct 6 16:04:07 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:04:07 storageqe-109 systemd[1]: run-media-root-047e9f4e\x2d43ff\x2d45ae\x2dbdfa\x2d1e975922d340.mount: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_mount_point_special_characters #### INFO: #### will start test_udisksctl_special_filesystems ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:12 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:12 storageqe-109 INFO: #### END test_udisksctl_mount_point_special_characters #### Oct 6 16:04:12 storageqe-109 INFO: #### will start test_udisksctl_special_filesystems ##### Oct 6 16:04:12 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:17 storageqe-109 kernel: loop0: detected capacity change from 0 to 102400 Oct 6 16:04:17 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /tmp/udisks_fs_test1.img) Oct 6 16:04:17 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/test label with on behalf of uid 0 Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 4bb43765-17d7-4cf3-a121-7042d3997ad3 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:17 storageqe-109 systemd[1]: run-media-root-test\x20label\x20with.mount: Deactivated successfully. Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 4bb43765-17d7-4cf3-a121-7042d3997ad3. Oct 6 16:04:17 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/test label with (device 7:0 is not mounted) Oct 6 16:04:17 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:17 storageqe-109 kernel: loop1: detected capacity change from 0 to 102400 Oct 6 16:04:17 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /tmp/udisks_fs_test2.img) Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop1): mounting ext3 file system using the ext4 subsystem Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop1): mounted filesystem e7eb053f-d328-4e85-9162-92ba0eb2f6ed r/w with ordered data mode. Quota mode: none. Oct 6 16:04:17 storageqe-109 udisksd[5174]: Mounted /dev/loop1 at /run/media/root/test label with on behalf of uid 0 Oct 6 16:04:17 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/test label with (device 7:1 is not mounted) Oct 6 16:04:17 storageqe-109 udisksd[5174]: Unmounted /dev/loop1 on behalf of uid 0 Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop1): unmounting filesystem e7eb053f-d328-4e85-9162-92ba0eb2f6ed. Oct 6 16:04:17 storageqe-109 kernel: loop2: detected capacity change from 0 to 102400 Oct 6 16:04:17 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /tmp/udisks_fs_test3.img) Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop2): mounting ext2 file system using the ext4 subsystem Oct 6 16:04:17 storageqe-109 udisksd[5174]: Mounted /dev/loop2 at /run/media/root/test label with on behalf of uid 0 Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop2): mounted filesystem 316d70ec-8786-42e5-b925-e6517113c47a r/w without journal. Quota mode: none. Oct 6 16:04:17 storageqe-109 kernel: EXT4-fs (loop2): unmounting filesystem 316d70ec-8786-42e5-b925-e6517113c47a. Oct 6 16:04:17 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/test label with (device 7:2 is not mounted) Oct 6 16:04:17 storageqe-109 udisksd[5174]: Unmounted /dev/loop2 on behalf of uid 0 Oct 6 16:04:17 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_fs_test1.img) Oct 6 16:04:17 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:04:17 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /tmp/udisks_fs_test2.img) Oct 6 16:04:17 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:04:18 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /tmp/udisks_fs_test3.img) Oct 6 16:04:18 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 16:04:18 storageqe-109 systemd[1]: run-media-root-test\x20label\x20with.mount: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_special_filesystems #### INFO: #### will start test_udisksctl_unicode_and_encoding ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:23 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:23 storageqe-109 INFO: #### END test_udisksctl_special_filesystems #### Oct 6 16:04:23 storageqe-109 INFO: #### will start test_udisksctl_unicode_and_encoding ##### Oct 6 16:04:23 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_unicode_and_encoding #### INFO: #### will start test_udisksctl_path_traversal_security ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:33 storageqe-109 INFO: #### END test_udisksctl_unicode_and_encoding #### Oct 6 16:04:33 storageqe-109 INFO: #### will start test_udisksctl_path_traversal_security ##### Oct 6 16:04:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_path_traversal_security #### INFO: #### will start test_udisksctl_special_filesystem_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:43 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:43 storageqe-109 INFO: #### END test_udisksctl_path_traversal_security #### Oct 6 16:04:43 storageqe-109 INFO: #### will start test_udisksctl_special_filesystem_operations ##### Oct 6 16:04:44 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:49 storageqe-109 kernel: loop0: detected capacity change from 0 to 204800 Oct 6 16:04:49 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /tmp/udisks_special_fs_test.img) Oct 6 16:04:49 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/b84b351b-4c4a-424a-a914-9ced9d2bd627 on behalf of uid 0 Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem b84b351b-4c4a-424a-a914-9ced9d2bd627 r/w with ordered data mode. Quota mode: none. Oct 6 16:04:49 storageqe-109 systemd[1]: run-media-root-b84b351b\x2d4c4a\x2d424a\x2da914\x2d9ced9d2bd627.mount: Deactivated successfully. Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem b84b351b-4c4a-424a-a914-9ced9d2bd627. Oct 6 16:04:49 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/b84b351b-4c4a-424a-a914-9ced9d2bd627 (device 7:0 is not mounted) Oct 6 16:04:49 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem Oct 6 16:04:49 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/de0a4a71-96ec-4890-8357-485c838fee1d on behalf of uid 0 Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem de0a4a71-96ec-4890-8357-485c838fee1d r/w with ordered data mode. Quota mode: none. Oct 6 16:04:49 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/de0a4a71-96ec-4890-8357-485c838fee1d (device 7:0 is not mounted) Oct 6 16:04:49 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem de0a4a71-96ec-4890-8357-485c838fee1d. Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 6f96f806-2ab4-4405-9675-35062ebcd7f3 r/w without journal. Quota mode: none. Oct 6 16:04:49 storageqe-109 udisksd[5174]: Mounted /dev/loop0 at /run/media/root/6f96f806-2ab4-4405-9675-35062ebcd7f3 on behalf of uid 0 Oct 6 16:04:49 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/6f96f806-2ab4-4405-9675-35062ebcd7f3 (device 7:0 is not mounted) Oct 6 16:04:49 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 6f96f806-2ab4-4405-9675-35062ebcd7f3. Oct 6 16:04:49 storageqe-109 udisksd[5174]: Unmounted /dev/loop0 on behalf of uid 0 Oct 6 16:04:49 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_special_fs_test.img) Oct 6 16:04:49 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:04:50 storageqe-109 systemd[1]: run-media-root-de0a4a71\x2d96ec\x2d4890\x2d8357\x2d485c838fee1d.mount: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_special_filesystem_operations #### INFO: #### will start test_udisksctl_comprehensive_command_coverage ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:04:54 storageqe-109 INFO: #### END test_udisksctl_special_filesystem_operations #### Oct 6 16:04:54 storageqe-109 INFO: #### will start test_udisksctl_comprehensive_command_coverage ##### Oct 6 16:04:54 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_comprehensive_command_coverage #### Oct 6 16:05:05 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:05 storageqe-109 INFO: #### END test_udisksctl_comprehensive_command_coverage #### Oct 6 16:05:06 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:06 storageqe-109 INFO: #### test_device after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 16:05:08 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 16:05:08 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 16:05:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 16:05:18 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_init_nvme ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:19 storageqe-109 INFO: #### will start test_init_nvme ##### Oct 6 16:05:19 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: Namespace object for /dev/nvme0n1: :1.29 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7fbfb46fe030> Oct 6 16:05:25 storageqe-109 INFO: Namespace object for /dev/nvme0n1: :1.29 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7fbfb46fe030> INFO: Drive path for /dev/nvme0n1: / Oct 6 16:05:26 storageqe-109 INFO: Drive path for /dev/nvme0n1: / INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_init_nvme #### INFO: #### will start test_ata_driver ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:32 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:32 storageqe-109 INFO: #### END test_init_nvme #### Oct 6 16:05:32 storageqe-109 INFO: #### will start test_ata_driver ##### Oct 6 16:05:32 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:38 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_ata_driver #### INFO: #### will start test_vdo ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:44 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:05:44 storageqe-109 INFO: #### END test_ata_driver #### Oct 6 16:05:44 storageqe-109 INFO: #### will start test_vdo ##### Oct 6 16:05:44 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:06:00 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 6 16:06:00 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 6 16:06:00 storageqe-109 kernel: loop0: Oct 6 16:06:02 storageqe-109 UDS/vdoformat[1119954]: INFO (vdoformat/1119954) Using 2 indexing zones for concurrency. Oct 6 16:06:02 storageqe-109 kernel: device-mapper: vdo18:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:06:02 storageqe-109 kernel: device-mapper: vdo18:lvm: loading device '253:4' Oct 6 16:06:02 storageqe-109 kernel: device-mapper: vdo18:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo18:lvm: starting device '253:4' Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:physQ0: VDO commencing normal operation Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:journa: Setting UDS index target state to online Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:dedupe: creating index: 253:3 Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' started Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:dedupe: Using 2 indexing zones for concurrency. Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:03 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:03 storageqe-109 systemd[1]: Started dm-event.service - Device-mapper event daemon. Oct 6 16:06:03 storageqe-109 dmeventd[1119988]: dmeventd ready for processing. Oct 6 16:06:03 storageqe-109 dmeventd[1119988]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: VDOPool /org/freedesktop/UDisks2/lvm/vg03/udisks_test_vdopool Oct 6 16:06:04 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/vg03/udisks_test_vdopool INFO: OperatingMode normal Oct 6 16:06:05 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 6 16:06:06 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 6 16:06:07 storageqe-109 INFO: IndexState online INFO: UsedSize 4988477440 Oct 6 16:06:08 storageqe-109 INFO: UsedSize 4988477440 INFO: Compression 1 Oct 6 16:06:09 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 6 16:06:10 storageqe-109 INFO: Deduplication 1 Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo18:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo18:lvm: preparing to modify device '253:4' Oct 6 16:06:10 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:dedupe: beginning save (vcn 18446744073709551615) Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:packer: compression is enabled Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:dedupe: finished save (vcn 18446744073709551615) Oct 6 16:06:10 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:10 storageqe-109 dmeventd[1119988]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:11 storageqe-109 kernel: device-mapper: vdo18:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:06:11 storageqe-109 kernel: device-mapper: vdo18:lvm: preparing to modify device '253:4' Oct 6 16:06:11 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:11 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:11 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:12 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:12 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:packer: compression is disabled Oct 6 16:06:12 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:12 storageqe-109 dmeventd[1119988]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo18:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo18:lvm: preparing to modify device '253:4' Oct 6 16:06:13 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:dedupe: loading or rebuilding index: 253:3 Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:packer: compression is disabled Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:dedupe: Using 2 indexing zones for concurrency. Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:13 storageqe-109 dmeventd[1119988]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:13 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:dedupe: loaded index from chapter 0 through chapter 0 Oct 6 16:06:14 storageqe-109 kernel: device-mapper: vdo18:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:06:14 storageqe-109 kernel: device-mapper: vdo18:lvm: preparing to modify device '253:4' Oct 6 16:06:14 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:14 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:14 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:14 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:14 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:packer: compression is enabled Oct 6 16:06:14 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:14 storageqe-109 dmeventd[1119988]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: table line: V4 /dev/dm-3 2266112 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: preparing to modify device '253:4' Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: Preparing to resize physical to 2266112 Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: Done preparing to resize physical Oct 6 16:06:17 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: Physical block count was 1741824, now 2266112 Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:packer: compression is enabled Oct 6 16:06:17 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:17 storageqe-109 dmeventd[1119988]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: the 9281994752 8589934592 Oct 6 16:06:20 storageqe-109 INFO: the 9281994752 8589934592 INFO:before lv vdo 78622228480 Oct 6 16:06:21 storageqe-109 journal: INFO:before lv vdo 78622228480 Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: table line: V4 /dev/dm-3 2266112 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: preparing to modify device '253:4' Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: Preparing to resize logical to 95974656 Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: Done preparing to resize logical Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: Resizing logical to 95974656 Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: Logical blocks now 95974656 Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:packer: compression is enabled Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:21 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: resuming device '253:4' Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo: dm_vdo18:packer: compression is enabled Oct 6 16:06:21 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' resumed Oct 6 16:06:21 storageqe-109 dmeventd[1119988]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: after lv vdo 393111142400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 7 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 91 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 4872976 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 4191472 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 18 Oct 6 16:06:24 storageqe-109 INFO: after lv vdo 393111142400 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 7 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics maxVIOs 91 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 4872976 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 4191472 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics instance 18 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 95974656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9064448 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 95974656 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9064448 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410015090 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410015090 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 7 INFO: vdo.GetStatistics overheadBlocksUsed 1218244 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 54 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2266112 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 7 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 1218244 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 6 16:06:24 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics usedPercent 54 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2266112 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 2 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 2 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 6 16:06:25 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 6 16:06:25 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 6 16:06:25 storageqe-109 kernel: device-mapper: vdo18:lvm: suspending device '253:4' Oct 6 16:06:25 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' suspended Oct 6 16:06:25 storageqe-109 kernel: device-mapper: vdo18:lvm: stopping device '253:4' Oct 6 16:06:25 storageqe-109 kernel: device-mapper: vdo18:lvm: device '253:4' stopped Oct 6 16:06:32 storageqe-109 kernel: loop0: Oct 6 16:06:32 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 6 16:06:32 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_vdo #### INFO: #### will start test_bz1567992_luks_resize ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:06:38 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:06:38 storageqe-109 INFO: #### END test_vdo #### Oct 6 16:06:38 storageqe-109 INFO: #### will start test_bz1567992_luks_resize ##### Oct 6 16:06:38 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:06:44 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:06:44 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 6 16:06:44 storageqe-109 kernel: loop0: INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks1'}, signature=dbus.Signature('sv')) Oct 6 16:06:45 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks1'}, signature=dbus.Signature('sv')) INFO: HintEncryptionType Oct 6 16:06:53 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 2097152 Oct 6 16:06:54 storageqe-109 INFO: MetadataSize 2097152 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 6 16:06:55 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: changed passwd to redhatredhat Oct 6 16:07:01 storageqe-109 INFO: changed passwd to redhatredhat Oct 6 16:07:01 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:07:01 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:07:01 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:03 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:06 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 INFO: changed passwd to test123456 Oct 6 16:07:11 storageqe-109 INFO: changed passwd to test123456 Oct 6 16:07:11 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:07:11 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:07:11 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:13 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:16 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:07:21 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:07:21 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:23 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:25 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:07:31 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:07:31 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:33 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:35 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:07:41 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:07:41 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 6 16:07:41 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:07:41 storageqe-109 stratisd[4947]: [2025-10-06T20:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:07:41 storageqe-109 stratisd[4947]: [2025-10-06T20:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:07:41 storageqe-109 stratisd[4947]: [2025-10-06T20:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:07:41 storageqe-109 stratisd[4947]: [2025-10-06T20:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 6 16:07:43 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 6 16:07:44 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 6 16:07:45 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 6 16:07:46 storageqe-109 INFO: foramt to luks2 Oct 6 16:07:46 storageqe-109 INFO: foramt to pbkdf2 INFO: changed passwd to redhatredhat Oct 6 16:07:52 storageqe-109 stratisd[4947]: [2025-10-06T20:07:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:07:52 storageqe-109 stratisd[4947]: [2025-10-06T20:07:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:07:52 storageqe-109 INFO: changed passwd to redhatredhat Oct 6 16:07:52 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:07:52 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:07:52 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:54 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:07:56 storageqe-109 stratisd[4947]: [2025-10-06T20:07:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:07:56 storageqe-109 stratisd[4947]: [2025-10-06T20:07:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:07:56 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 INFO: changed passwd to test123456 Oct 6 16:08:04 storageqe-109 stratisd[4947]: [2025-10-06T20:08:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:04 storageqe-109 stratisd[4947]: [2025-10-06T20:08:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:04 storageqe-109 INFO: changed passwd to test123456 Oct 6 16:08:04 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:08:04 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:08:04 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:08:06 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:08:08 storageqe-109 stratisd[4947]: [2025-10-06T20:08:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:08 storageqe-109 stratisd[4947]: [2025-10-06T20:08:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:08 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:08:17 storageqe-109 stratisd[4947]: [2025-10-06T20:08:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:17 storageqe-109 stratisd[4947]: [2025-10-06T20:08:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:17 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:08:17 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:08:19 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:08:21 storageqe-109 stratisd[4947]: [2025-10-06T20:08:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:21 storageqe-109 stratisd[4947]: [2025-10-06T20:08:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:21 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:08:29 storageqe-109 stratisd[4947]: [2025-10-06T20:08:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:29 storageqe-109 stratisd[4947]: [2025-10-06T20:08:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:29 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:08:29 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:08:31 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:08:33 storageqe-109 stratisd[4947]: [2025-10-06T20:08:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:33 storageqe-109 stratisd[4947]: [2025-10-06T20:08:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:34 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:08:42 storageqe-109 stratisd[4947]: [2025-10-06T20:08:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:42 storageqe-109 stratisd[4947]: [2025-10-06T20:08:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:42 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:08:42 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 6 16:08:42 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:08:42 storageqe-109 stratisd[4947]: [2025-10-06T20:08:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:42 storageqe-109 stratisd[4947]: [2025-10-06T20:08:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:42 storageqe-109 stratisd[4947]: [2025-10-06T20:08:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:08:42 storageqe-109 stratisd[4947]: [2025-10-06T20:08:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 6 16:08:44 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 6 16:08:45 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 6 16:08:46 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 6 16:08:47 storageqe-109 INFO: foramt to luks2 Oct 6 16:08:47 storageqe-109 INFO: foramt to pbkdf2 INFO: before convert luks dump info {'keyslots': {'0': {'type': 'luks2', 'key_size': 64, 'af': {'type': 'luks1', 'stripes': 4000, 'hash': 'sha256'}, 'area': {'type': 'raw', 'offset': '32768', 'size': '258048', 'encryption': 'aes-xts-plain64', 'key_size': 64}, 'kdf': {'type': 'pbkdf2', 'hash': 'sha256', 'iterations': 1000, 'salt': 'iZR/NfO/Tyuflc2CmH0VazViabEqkTgxo6Ws8olvxWU='}}}, 'tokens': {}, 'segments': {'0': {'type': 'crypt', 'offset': '16777216', 'size': 'dynamic', 'iv_tweak': '0', 'encryption': 'aes-xts-plain64', 'sector_size': 512}}, 'digests': {'0': {'type': 'pbkdf2', 'keyslots': ['0'], 'segments': ['0'], 'hash': 'sha256', 'iterations': 1000, 'salt': 'PTmQNJDNy4IhxmyT248JNNYfnKioZ64YqKnh90yn8zU=', 'digest': 'QKoCp1D0Y+QmH3k3MB7vGQtNgcG0j+i8L/0jrvixTto='}}, 'config': {'json_size': '12288', 'keyslots_size': '16744448'}} Oct 6 16:08:48 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:08:48 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:08:48 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 6 16:08:48 storageqe-109 INFO: before convert luks dump info {'keyslots': {'0': {'type': 'luks2', 'key_size': 64, 'af': {'type': 'luks1', 'stripes': 4000, 'hash': 'sha256'}, 'area': {'type': 'raw', 'offset': '32768', 'size': '258048', 'encryption': 'aes-xts-plain64', 'key_size': 64}, 'kdf': {'type': 'pbkdf2', 'hash': 'sha256', 'iterations': 1000, 'salt': 'iZR/NfO/Tyuflc2CmH0VazViabEqkTgxo6Ws8olvxWU='}}}, 'tokens': {}, 'segments': {'0': {'type': 'crypt', 'offset': '16777216', 'size': 'dynamic', 'iv_tweak': '0', 'encryption': 'aes-xts-plain64', 'sector_size': 512}}, 'digests': {'0': {'type': 'pbkdf2', 'keyslots': ['0'], 'segments': ['0'], 'hash': 'sha256', 'iterations': 1000, 'salt': 'PTmQNJDNy4IhxmyT248JNNYfnKioZ64YqKnh90yn8zU=', 'digest': 'QKoCp1D0Y+QmH3k3MB7vGQtNgcG0j+i8L/0jrvixTto='}}, 'config': {'json_size': '12288', 'keyslots_size': '16744448'}} INFO: will convert to luks1 INFO: will convert to luks2 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:09:18 storageqe-109 INFO: will convert to luks1 Oct 6 16:09:18 storageqe-109 INFO: will convert to luks2 Oct 6 16:09:18 storageqe-109 stratisd[4947]: [2025-10-06T20:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:18 storageqe-109 stratisd[4947]: [2025-10-06T20:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:18 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:09:18 storageqe-109 stratisd[4947]: [2025-10-06T20:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:18 storageqe-109 stratisd[4947]: [2025-10-06T20:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:18 storageqe-109 stratisd[4947]: [2025-10-06T20:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:18 storageqe-109 stratisd[4947]: [2025-10-06T20:09:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 6 16:09:20 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 6 16:09:21 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 6 16:09:22 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 6 16:09:23 storageqe-109 INFO: foramt to luks2 Oct 6 16:09:23 storageqe-109 INFO: foramt to pbkdf2 Oct 6 16:09:25 storageqe-109 stratisd[4947]: [2025-10-06T20:09:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:25 storageqe-109 stratisd[4947]: [2025-10-06T20:09:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:25 storageqe-109 stratisd[4947]: [2025-10-06T20:09:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:25 storageqe-109 stratisd[4947]: [2025-10-06T20:09:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:09:28 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:09:28 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:09:28 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 6 16:09:33 storageqe-109 kernel: loop0: Oct 6 16:09:33 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 6 16:09:33 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz1567992_luks_resize #### INFO: #### will start test_part_mount ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:09:39 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:09:39 storageqe-109 INFO: #### END test_bz1567992_luks_resize #### Oct 6 16:09:39 storageqe-109 INFO: #### will start test_part_mount ##### Oct 6 16:09:39 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:09:45 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:09:45 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 6 16:09:45 storageqe-109 kernel: loop0: Oct 6 16:09:53 storageqe-109 kernel: loop0: p1 Oct 6 16:09:53 storageqe-109 kernel: EXT4-fs (loop0p1): mounting ext3 file system using the ext4 subsystem Oct 6 16:09:53 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem 2cf20686-df2b-4ce7-9993-f11e2418fbb8 r/w with ordered data mode. Quota mode: none. Oct 6 16:09:53 storageqe-109 udisksd[5174]: Mounted /dev/loop0p1 at /run/media/root/2cf20686-df2b-4ce7-9993-f11e2418fbb8 on behalf of uid 0 Oct 6 16:09:54 storageqe-109 systemd[1]: run-media-root-2cf20686\x2ddf2b\x2d4ce7\x2d9993\x2df11e2418fbb8.mount: Deactivated successfully. Oct 6 16:09:54 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem 2cf20686-df2b-4ce7-9993-f11e2418fbb8. Oct 6 16:09:54 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/2cf20686-df2b-4ce7-9993-f11e2418fbb8 (device 259:3 is not mounted) Oct 6 16:09:54 storageqe-109 udisksd[5174]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 6 16:09:54 storageqe-109 kernel: XFS (loop0p1): Mounting V5 Filesystem 50f6d467-0206-4c95-a3ce-98f0c18fad62 Oct 6 16:09:54 storageqe-109 kernel: XFS (loop0p1): Ending clean mount Oct 6 16:09:54 storageqe-109 udisksd[5174]: Mounted /dev/loop0p1 at /run/media/root/50f6d467-0206-4c95-a3ce-98f0c18fad62 on behalf of uid 0 Oct 6 16:09:54 storageqe-109 kernel: XFS (loop0p1): Unmounting Filesystem 50f6d467-0206-4c95-a3ce-98f0c18fad62 Oct 6 16:09:54 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/50f6d467-0206-4c95-a3ce-98f0c18fad62 (device 259:3 is not mounted) Oct 6 16:09:54 storageqe-109 udisksd[5174]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 6 16:09:54 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem 7cc19bb7-5ac8-4a64-a848-12809726511c r/w with ordered data mode. Quota mode: none. Oct 6 16:09:54 storageqe-109 udisksd[5174]: Mounted /dev/loop0p1 at /run/media/root/7cc19bb7-5ac8-4a64-a848-12809726511c on behalf of uid 0 Oct 6 16:09:54 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem 7cc19bb7-5ac8-4a64-a848-12809726511c. Oct 6 16:09:54 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/7cc19bb7-5ac8-4a64-a848-12809726511c (device 259:3 is not mounted) Oct 6 16:09:54 storageqe-109 udisksd[5174]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 6 16:09:54 storageqe-109 systemd[1]: run-media-root-50f6d467\x2d0206\x2d4c95\x2da3ce\x2d98f0c18fad62.mount: Deactivated successfully. Oct 6 16:09:59 storageqe-109 kernel: loop0: Oct 6 16:09:59 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 6 16:09:59 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_part_mount #### INFO: #### will start test_bz1400056_md ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:10:05 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:10:05 storageqe-109 INFO: #### END test_part_mount #### Oct 6 16:10:05 storageqe-109 INFO: #### will start test_bz1400056_md ##### Oct 6 16:10:05 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:10:11 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:10:11 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop10.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:10:12 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:10:12 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 6 16:10:12 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:10:12 storageqe-109 INFO: raid level raid0 Oct 6 16:10:12 storageqe-109 INFO: raid name test_md Oct 6 16:10:12 storageqe-109 INFO: raid chunk 1048576 Oct 6 16:10:12 storageqe-109 INFO: raid bitmap None Oct 6 16:10:12 storageqe-109 INFO: raid version 1.2 Oct 6 16:10:12 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 INFO: Name test_md Oct 6 16:10:16 storageqe-109 INFO: Name test_md INFO: UUID 908ef136:f8467d15:df52ea8c:06fd0b1a Oct 6 16:10:17 storageqe-109 INFO: UUID 908ef136:f8467d15:df52ea8c:06fd0b1a INFO: Level raid0 Oct 6 16:10:18 storageqe-109 INFO: Level raid0 INFO: NumDevices 2 Oct 6 16:10:19 storageqe-109 INFO: NumDevices 2 INFO: Size 2141192192 Oct 6 16:10:20 storageqe-109 INFO: Size 2141192192 INFO: SyncAction Oct 6 16:10:21 storageqe-109 INFO: SyncAction INFO: SyncCompleted 0.0 Oct 6 16:10:22 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 6 16:10:23 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 6 16:10:24 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 6 16:10:25 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy Oct 6 16:10:26 storageqe-109 INFO: ConsistencyPolicy INFO: BitmapLocation dbus.Array([dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 6 16:10:27 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 6 16:10:28 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 6 16:10:29 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 6 16:10:30 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 6 16:10:31 storageqe-109 INFO: Running 1 INFO: bitma is , Oct 6 16:10:32 storageqe-109 INFO: bitma is , INFO: BitmapLocation Oct 6 16:10:33 storageqe-109 INFO: BitmapLocation Oct 6 16:10:39 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 6 16:10:39 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 054157dd-197d-4473-bd59-1ca6f4740096 r/w with ordered data mode. Quota mode: none. Oct 6 16:10:39 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/054157dd-197d-4473-bd59-1ca6f4740096 on behalf of uid 0 Oct 6 16:10:42 storageqe-109 systemd[1]: run-media-root-054157dd\x2d197d\x2d4473\x2dbd59\x2d1ca6f4740096.mount: Deactivated successfully. Oct 6 16:10:42 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 054157dd-197d-4473-bd59-1ca6f4740096. Oct 6 16:10:42 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/054157dd-197d-4473-bd59-1ca6f4740096 (device 9:127 is not mounted) Oct 6 16:10:42 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:10:51 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 6f59385c-33cf-43d9-ad05-df5f50890fb8 Oct 6 16:10:51 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/6f59385c-33cf-43d9-ad05-df5f50890fb8 on behalf of uid 0 Oct 6 16:10:51 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 6 16:10:54 storageqe-109 systemd[1]: run-media-root-6f59385c\x2d33cf\x2d43d9\x2dad05\x2ddf5f50890fb8.mount: Deactivated successfully. Oct 6 16:10:54 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 6f59385c-33cf-43d9-ad05-df5f50890fb8 Oct 6 16:10:54 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/6f59385c-33cf-43d9-ad05-df5f50890fb8 (device 9:127 is not mounted) Oct 6 16:10:54 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:11:02 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/2cc7d42c-b6f3-44b2-8f38-8a5233afe036 on behalf of uid 0 Oct 6 16:11:02 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 2cc7d42c-b6f3-44b2-8f38-8a5233afe036 r/w with ordered data mode. Quota mode: none. Oct 6 16:11:05 storageqe-109 systemd[1]: run-media-root-2cc7d42c\x2db6f3\x2d44b2\x2d8f38\x2d8a5233afe036.mount: Deactivated successfully. Oct 6 16:11:05 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 2cc7d42c-b6f3-44b2-8f38-8a5233afe036. Oct 6 16:11:05 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/2cc7d42c-b6f3-44b2-8f38-8a5233afe036 (device 9:127 is not mounted) Oct 6 16:11:05 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:11:09 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 6 16:11:09 storageqe-109 kernel: md: md127 stopped. Oct 6 16:11:09 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:11:12 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 6 16:11:12 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:11:12 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 6 16:11:12 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:11:12 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:11:12 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop10.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.0 Oct 6 16:11:13 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:11:13 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 6 16:11:13 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:11:13 storageqe-109 INFO: raid level raid1 Oct 6 16:11:13 storageqe-109 INFO: raid name test_md Oct 6 16:11:13 storageqe-109 INFO: raid chunk 0 Oct 6 16:11:13 storageqe-109 INFO: raid bitmap None Oct 6 16:11:13 storageqe-109 INFO: raid version 1.0 Oct 6 16:11:13 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:11:13 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:11:13 storageqe-109 kernel: md127: detected capacity change from 0 to 2097024 Oct 6 16:11:13 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:11:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:18 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 6 16:11:21 storageqe-109 INFO: Name test_md INFO: UUID 25d0ac53:11a4621b:1847e68c:1a32683e Oct 6 16:11:22 storageqe-109 INFO: UUID 25d0ac53:11a4621b:1847e68c:1a32683e INFO: Level raid1 Oct 6 16:11:23 storageqe-109 INFO: Level raid1 INFO: NumDevices 2 Oct 6 16:11:24 storageqe-109 INFO: NumDevices 2 INFO: Size 1073676288 Oct 6 16:11:25 storageqe-109 INFO: Size 1073676288 INFO: SyncAction idle Oct 6 16:11:26 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 6 16:11:27 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 6 16:11:28 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 6 16:11:29 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 6 16:11:30 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy resync Oct 6 16:11:31 storageqe-109 INFO: ConsistencyPolicy resync INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 6 16:11:32 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 0 Oct 6 16:11:33 storageqe-109 INFO: ChunkSize 0 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 6 16:11:34 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 6 16:11:35 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 6 16:11:36 storageqe-109 INFO: Running 1 INFO: bitma is none, INFO: looks don't set bitmap Oct 6 16:11:37 storageqe-109 INFO: bitma is none, Oct 6 16:11:37 storageqe-109 INFO: looks don't set bitmap Oct 6 16:11:37 storageqe-109 kernel: md127: bitmap file is out of date (0 < 17) -- forcing full recovery Oct 6 16:11:37 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery INFO: BitmapLocation -16 Oct 6 16:11:39 storageqe-109 INFO: BitmapLocation -16 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop2 at 0x7fbfb458eff0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop2 /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 16:11:40 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 16:11:40 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop0.img) Oct 6 16:11:40 storageqe-109 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop2 at 0x7fbfb458eff0> Oct 6 16:11:40 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop2 /org/freedesktop/UDisks2/block_devices/loop2 INFO: Oct 6 16:11:42 storageqe-109 INFO: INFO: Oct 6 16:11:45 storageqe-109 INFO: Oct 6 16:11:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:52 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 6 16:11:52 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/54dd6b94-e614-4e17-a418-1e76b51d9b63 on behalf of uid 0 Oct 6 16:11:52 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 54dd6b94-e614-4e17-a418-1e76b51d9b63 r/w with ordered data mode. Quota mode: none. Oct 6 16:11:52 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:55 storageqe-109 systemd[1]: run-media-root-54dd6b94\x2de614\x2d4e17\x2da418\x2d1e76b51d9b63.mount: Deactivated successfully. Oct 6 16:11:55 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 54dd6b94-e614-4e17-a418-1e76b51d9b63. Oct 6 16:11:55 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/54dd6b94-e614-4e17-a418-1e76b51d9b63 (device 9:127 is not mounted) Oct 6 16:11:55 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:11:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:11:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:03 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem c89aea7d-5de0-4852-a2f9-0fee38cb6f97 Oct 6 16:12:03 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/c89aea7d-5de0-4852-a2f9-0fee38cb6f97 on behalf of uid 0 Oct 6 16:12:03 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 6 16:12:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:06 storageqe-109 systemd[1]: run-media-root-c89aea7d\x2d5de0\x2d4852\x2da2f9\x2d0fee38cb6f97.mount: Deactivated successfully. Oct 6 16:12:06 storageqe-109 kernel: XFS (md127): Unmounting Filesystem c89aea7d-5de0-4852-a2f9-0fee38cb6f97 Oct 6 16:12:06 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/c89aea7d-5de0-4852-a2f9-0fee38cb6f97 (device 9:127 is not mounted) Oct 6 16:12:06 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:12:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:14 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem d65f2992-fb38-4730-a0ab-4029d95d18c5 r/w with ordered data mode. Quota mode: none. Oct 6 16:12:14 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/d65f2992-fb38-4730-a0ab-4029d95d18c5 on behalf of uid 0 Oct 6 16:12:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:17 storageqe-109 systemd[1]: run-media-root-d65f2992\x2dfb38\x2d4730\x2da0ab\x2d4029d95d18c5.mount: Deactivated successfully. Oct 6 16:12:17 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem d65f2992-fb38-4730-a0ab-4029d95d18c5. Oct 6 16:12:17 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/d65f2992-fb38-4730-a0ab-4029d95d18c5 (device 9:127 is not mounted) Oct 6 16:12:17 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:12:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:21 storageqe-109 kernel: md127: detected capacity change from 2097024 to 0 Oct 6 16:12:21 storageqe-109 kernel: md: md127 stopped. Oct 6 16:12:21 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:12:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 6 16:12:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:12:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 6 16:12:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:12:25 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:12:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 6 16:12:25 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:12:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 6 16:12:25 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid4 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.2 Oct 6 16:12:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/loop12.img) Oct 6 16:12:25 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 6 16:12:25 storageqe-109 INFO: raid level raid4 Oct 6 16:12:25 storageqe-109 INFO: raid name test_md Oct 6 16:12:25 storageqe-109 INFO: raid chunk 1048576 Oct 6 16:12:25 storageqe-109 INFO: raid bitmap internal Oct 6 16:12:25 storageqe-109 INFO: raid version 1.2 Oct 6 16:12:26 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 16:12:26 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 16:12:26 storageqe-109 kernel: md/raid:md127: raid level 4 active with 2 out of 3 devices, algorithm 0 Oct 6 16:12:26 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 Oct 6 16:12:26 storageqe-109 kernel: md: recover of RAID array md127 Oct 6 16:12:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: Name test_md Oct 6 16:12:30 storageqe-109 INFO: Name test_md INFO: UUID 9778f168:871604c6:8f98c160:f4da238c Oct 6 16:12:31 storageqe-109 INFO: UUID 9778f168:871604c6:8f98c160:f4da238c Oct 6 16:12:31 storageqe-109 kernel: md: md127: recover done. INFO: Level raid4 Oct 6 16:12:32 storageqe-109 INFO: Level raid4 INFO: NumDevices 3 Oct 6 16:12:33 storageqe-109 INFO: NumDevices 3 INFO: Size 2141192192 Oct 6 16:12:34 storageqe-109 INFO: Size 2141192192 INFO: SyncAction idle Oct 6 16:12:35 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 6 16:12:36 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 6 16:12:37 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 6 16:12:38 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 6 16:12:39 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 6 16:12:40 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 6 16:12:41 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 6 16:12:42 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 6 16:12:43 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 6 16:12:44 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 6 16:12:45 storageqe-109 INFO: Running 1 INFO: bitma is +8, Oct 6 16:12:46 storageqe-109 INFO: bitma is +8, INFO: BitmapLocation +8 Oct 6 16:12:47 storageqe-109 INFO: BitmapLocation +8 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop4 at 0x7fbfb458f050> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop4 /org/freedesktop/UDisks2/block_devices/loop4 Oct 6 16:12:48 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 6 16:12:48 storageqe-109 udisksd[5174]: Set up loop device /dev/loop4 (backed by /home/loop0.img) Oct 6 16:12:48 storageqe-109 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop4 at 0x7fbfb458f050> Oct 6 16:12:48 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop4 /org/freedesktop/UDisks2/block_devices/loop4 INFO: Oct 6 16:12:50 storageqe-109 INFO: INFO: Oct 6 16:12:53 storageqe-109 INFO: Oct 6 16:12:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:12:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:00 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 6 16:13:00 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/cc5aec03-ec6d-44e4-b6fa-26b36c78b332 on behalf of uid 0 Oct 6 16:13:00 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem cc5aec03-ec6d-44e4-b6fa-26b36c78b332 r/w with ordered data mode. Quota mode: none. Oct 6 16:13:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:03 storageqe-109 systemd[1]: run-media-root-cc5aec03\x2dec6d\x2d44e4\x2db6fa\x2d26b36c78b332.mount: Deactivated successfully. Oct 6 16:13:03 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem cc5aec03-ec6d-44e4-b6fa-26b36c78b332. Oct 6 16:13:03 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/cc5aec03-ec6d-44e4-b6fa-26b36c78b332 (device 9:127 is not mounted) Oct 6 16:13:03 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:13:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:11 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem b38d2fe1-62b7-4d00-b2d1-53e7d334afef Oct 6 16:13:11 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 6 16:13:11 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/b38d2fe1-62b7-4d00-b2d1-53e7d334afef on behalf of uid 0 Oct 6 16:13:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:14 storageqe-109 systemd[1]: run-media-root-b38d2fe1\x2d62b7\x2d4d00\x2db2d1\x2d53e7d334afef.mount: Deactivated successfully. Oct 6 16:13:14 storageqe-109 kernel: XFS (md127): Unmounting Filesystem b38d2fe1-62b7-4d00-b2d1-53e7d334afef Oct 6 16:13:14 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/b38d2fe1-62b7-4d00-b2d1-53e7d334afef (device 9:127 is not mounted) Oct 6 16:13:14 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:13:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:22 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/b41a3244-d833-49de-9cfa-2d0e61f15687 on behalf of uid 0 Oct 6 16:13:22 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem b41a3244-d833-49de-9cfa-2d0e61f15687 r/w with ordered data mode. Quota mode: none. Oct 6 16:13:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:25 storageqe-109 systemd[1]: run-media-root-b41a3244\x2dd833\x2d49de\x2d9cfa\x2d2d0e61f15687.mount: Deactivated successfully. Oct 6 16:13:25 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem b41a3244-d833-49de-9cfa-2d0e61f15687. Oct 6 16:13:25 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/b41a3244-d833-49de-9cfa-2d0e61f15687 (device 9:127 is not mounted) Oct 6 16:13:25 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:13:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:29 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 6 16:13:29 storageqe-109 kernel: md: md127 stopped. Oct 6 16:13:29 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:13:32 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 6 16:13:32 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:13:32 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 6 16:13:32 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:13:32 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 6 16:13:32 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 16:13:33 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:13:33 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 6 16:13:33 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:13:33 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop11.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid5 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.0 Oct 6 16:13:34 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 16:13:34 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/loop12.img) Oct 6 16:13:34 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 6 16:13:34 storageqe-109 INFO: raid level raid5 Oct 6 16:13:34 storageqe-109 INFO: raid name test_md Oct 6 16:13:34 storageqe-109 INFO: raid chunk 1048576 Oct 6 16:13:34 storageqe-109 INFO: raid bitmap internal Oct 6 16:13:34 storageqe-109 INFO: raid version 1.0 Oct 6 16:13:34 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 16:13:34 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 16:13:34 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 6 16:13:34 storageqe-109 kernel: md127: detected capacity change from 0 to 4190208 Oct 6 16:13:34 storageqe-109 kernel: md: recover of RAID array md127 Oct 6 16:13:34 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:34 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:13:34 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: Name test_md Oct 6 16:13:38 storageqe-109 INFO: Name test_md INFO: UUID 86a49a83:e83ce803:91aa0eb3:831ac1dc Oct 6 16:13:39 storageqe-109 INFO: UUID 86a49a83:e83ce803:91aa0eb3:831ac1dc Oct 6 16:13:39 storageqe-109 kernel: md: md127: recover done. INFO: Level raid5 Oct 6 16:13:40 storageqe-109 INFO: Level raid5 INFO: NumDevices 3 Oct 6 16:13:41 storageqe-109 INFO: NumDevices 3 INFO: Size 2145386496 Oct 6 16:13:42 storageqe-109 INFO: Size 2145386496 INFO: SyncAction idle Oct 6 16:13:43 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 6 16:13:44 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 6 16:13:45 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 6 16:13:46 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 6 16:13:47 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 6 16:13:48 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 6 16:13:49 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 6 16:13:50 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 6 16:13:51 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 6 16:13:52 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 6 16:13:53 storageqe-109 INFO: Running 1 INFO: bitma is -16, Oct 6 16:13:54 storageqe-109 INFO: bitma is -16, INFO: BitmapLocation -16 Oct 6 16:13:55 storageqe-109 INFO: BitmapLocation -16 Oct 6 16:13:56 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop5 at 0x7fbfb458ecc0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop5 /org/freedesktop/UDisks2/block_devices/loop5 Oct 6 16:13:56 storageqe-109 udisksd[5174]: Set up loop device /dev/loop5 (backed by /home/loop0.img) Oct 6 16:13:56 storageqe-109 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop5 at 0x7fbfb458ecc0> Oct 6 16:13:56 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop5 /org/freedesktop/UDisks2/block_devices/loop5 INFO: Oct 6 16:13:58 storageqe-109 INFO: INFO: Oct 6 16:14:01 storageqe-109 INFO: Oct 6 16:14:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:08 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 6 16:14:08 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 589429e3-c867-45d0-b617-8bc838193e45 r/w with ordered data mode. Quota mode: none. Oct 6 16:14:08 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/589429e3-c867-45d0-b617-8bc838193e45 on behalf of uid 0 Oct 6 16:14:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:11 storageqe-109 systemd[1]: run-media-root-589429e3\x2dc867\x2d45d0\x2db617\x2d8bc838193e45.mount: Deactivated successfully. Oct 6 16:14:11 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 589429e3-c867-45d0-b617-8bc838193e45. Oct 6 16:14:11 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/589429e3-c867-45d0-b617-8bc838193e45 (device 9:127 is not mounted) Oct 6 16:14:11 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:14:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:19 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem b15902ec-853d-4b23-a952-8c35f0107ed8 Oct 6 16:14:19 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/b15902ec-853d-4b23-a952-8c35f0107ed8 on behalf of uid 0 Oct 6 16:14:19 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 6 16:14:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:22 storageqe-109 systemd[1]: run-media-root-b15902ec\x2d853d\x2d4b23\x2da952\x2d8c35f0107ed8.mount: Deactivated successfully. Oct 6 16:14:22 storageqe-109 kernel: XFS (md127): Unmounting Filesystem b15902ec-853d-4b23-a952-8c35f0107ed8 Oct 6 16:14:22 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/b15902ec-853d-4b23-a952-8c35f0107ed8 (device 9:127 is not mounted) Oct 6 16:14:22 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:14:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:30 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/d237c805-c182-4e62-848d-6d2d354222d0 on behalf of uid 0 Oct 6 16:14:30 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem d237c805-c182-4e62-848d-6d2d354222d0 r/w with ordered data mode. Quota mode: none. Oct 6 16:14:30 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:33 storageqe-109 systemd[1]: run-media-root-d237c805\x2dc182\x2d4e62\x2d848d\x2d6d2d354222d0.mount: Deactivated successfully. Oct 6 16:14:33 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem d237c805-c182-4e62-848d-6d2d354222d0. Oct 6 16:14:33 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/d237c805-c182-4e62-848d-6d2d354222d0 (device 9:127 is not mounted) Oct 6 16:14:33 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:14:33 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:37 storageqe-109 kernel: md127: detected capacity change from 4190208 to 0 Oct 6 16:14:37 storageqe-109 kernel: md: md127 stopped. Oct 6 16:14:38 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:14:40 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 6 16:14:40 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:14:40 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 6 16:14:40 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:14:40 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 6 16:14:40 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 16:14:41 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:14:41 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 6 16:14:41 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:14:41 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 6 16:14:42 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 16:14:42 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/loop12.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] INFO: raid level raid6 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.2 Oct 6 16:14:42 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 6 16:14:42 storageqe-109 udisksd[5174]: Set up loop device /dev/loop6 (backed by /home/loop13.img) Oct 6 16:14:42 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] Oct 6 16:14:42 storageqe-109 INFO: raid level raid6 Oct 6 16:14:42 storageqe-109 INFO: raid name test_md Oct 6 16:14:42 storageqe-109 INFO: raid chunk 1048576 Oct 6 16:14:42 storageqe-109 INFO: raid bitmap internal Oct 6 16:14:42 storageqe-109 INFO: raid version 1.2 Oct 6 16:14:42 storageqe-109 kernel: md/raid:md127: not clean -- starting background reconstruction Oct 6 16:14:42 storageqe-109 kernel: md/raid:md127: device loop6 operational as raid disk 3 Oct 6 16:14:42 storageqe-109 kernel: md/raid:md127: device loop3 operational as raid disk 2 Oct 6 16:14:42 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 16:14:42 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 16:14:42 storageqe-109 kernel: md/raid:md127: raid level 6 active with 4 out of 4 devices, algorithm 2 Oct 6 16:14:42 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 Oct 6 16:14:42 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:14:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:14:47 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 6 16:14:50 storageqe-109 INFO: Name test_md INFO: UUID 1d76691b:12f5a359:8c72d935:826cf948 Oct 6 16:14:51 storageqe-109 INFO: UUID 1d76691b:12f5a359:8c72d935:826cf948 INFO: Level raid6 Oct 6 16:14:52 storageqe-109 INFO: Level raid6 INFO: NumDevices 4 Oct 6 16:14:54 storageqe-109 INFO: NumDevices 4 INFO: Size 2141192192 Oct 6 16:14:55 storageqe-109 INFO: Size 2141192192 INFO: SyncAction idle Oct 6 16:14:56 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 6 16:14:57 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 6 16:14:58 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 6 16:14:59 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 6 16:15:00 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 6 16:15:01 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 6 16:15:02 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 6 16:15:03 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6'), dbus.Int32(3), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 6 16:15:05 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 6 16:15:06 storageqe-109 INFO: Running 1 INFO: bitma is +8, Oct 6 16:15:07 storageqe-109 INFO: bitma is +8, INFO: BitmapLocation +8 Oct 6 16:15:08 storageqe-109 INFO: BitmapLocation +8 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop7 at 0x7fbfb458f4d0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop7 /org/freedesktop/UDisks2/block_devices/loop7 Oct 6 16:15:08 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 6 16:15:08 storageqe-109 udisksd[5174]: Set up loop device /dev/loop7 (backed by /home/loop0.img) Oct 6 16:15:08 storageqe-109 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop7 at 0x7fbfb458f4d0> Oct 6 16:15:08 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop7 /org/freedesktop/UDisks2/block_devices/loop7 INFO: Oct 6 16:15:10 storageqe-109 INFO: INFO: Oct 6 16:15:13 storageqe-109 INFO: Oct 6 16:15:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:20 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 6 16:15:20 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/a67cf7d3-3aa2-4126-ad69-32a9ce957e65 on behalf of uid 0 Oct 6 16:15:20 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem a67cf7d3-3aa2-4126-ad69-32a9ce957e65 r/w with ordered data mode. Quota mode: none. Oct 6 16:15:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:23 storageqe-109 systemd[1]: run-media-root-a67cf7d3\x2d3aa2\x2d4126\x2dad69\x2d32a9ce957e65.mount: Deactivated successfully. Oct 6 16:15:23 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem a67cf7d3-3aa2-4126-ad69-32a9ce957e65. Oct 6 16:15:23 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/a67cf7d3-3aa2-4126-ad69-32a9ce957e65 (device 9:127 is not mounted) Oct 6 16:15:23 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:15:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:31 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 8ae088d2-4234-4c5a-b146-92a00f1bf86f Oct 6 16:15:31 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 6 16:15:31 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/8ae088d2-4234-4c5a-b146-92a00f1bf86f on behalf of uid 0 Oct 6 16:15:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:35 storageqe-109 systemd[1]: run-media-root-8ae088d2\x2d4234\x2d4c5a\x2db146\x2d92a00f1bf86f.mount: Deactivated successfully. Oct 6 16:15:35 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 8ae088d2-4234-4c5a-b146-92a00f1bf86f Oct 6 16:15:35 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/8ae088d2-4234-4c5a-b146-92a00f1bf86f (device 9:127 is not mounted) Oct 6 16:15:35 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:15:35 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:43 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/5dec6fb9-8226-411e-8f38-abfcedefc51d on behalf of uid 0 Oct 6 16:15:43 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 5dec6fb9-8226-411e-8f38-abfcedefc51d r/w with ordered data mode. Quota mode: none. Oct 6 16:15:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:46 storageqe-109 systemd[1]: run-media-root-5dec6fb9\x2d8226\x2d411e\x2d8f38\x2dabfcedefc51d.mount: Deactivated successfully. Oct 6 16:15:46 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 5dec6fb9-8226-411e-8f38-abfcedefc51d. Oct 6 16:15:46 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/5dec6fb9-8226-411e-8f38-abfcedefc51d (device 9:127 is not mounted) Oct 6 16:15:46 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:15:46 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:50 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 6 16:15:50 storageqe-109 kernel: md: md127 stopped. Oct 6 16:15:50 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:15:53 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 6 16:15:53 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:15:53 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 6 16:15:53 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:15:53 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 6 16:15:53 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 16:15:53 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop6 (was backed by /home/loop13.img) Oct 6 16:15:53 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop6 Oct 6 16:15:53 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:15:53 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 6 16:15:54 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:15:54 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 6 16:15:54 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 16:15:54 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/loop12.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] INFO: raid level raid10 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.0 Oct 6 16:15:55 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 6 16:15:55 storageqe-109 udisksd[5174]: Set up loop device /dev/loop6 (backed by /home/loop13.img) Oct 6 16:15:55 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] Oct 6 16:15:55 storageqe-109 INFO: raid level raid10 Oct 6 16:15:55 storageqe-109 INFO: raid name test_md Oct 6 16:15:55 storageqe-109 INFO: raid chunk 1048576 Oct 6 16:15:55 storageqe-109 INFO: raid bitmap internal Oct 6 16:15:55 storageqe-109 INFO: raid version 1.0 Oct 6 16:15:55 storageqe-109 kernel: md/raid10:md127: not clean -- starting background reconstruction Oct 6 16:15:55 storageqe-109 kernel: md/raid10:md127: active with 4 out of 4 devices Oct 6 16:15:55 storageqe-109 kernel: md127: detected capacity change from 0 to 4190208 Oct 6 16:15:55 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:15:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:15:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:05 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 6 16:16:07 storageqe-109 INFO: Name test_md INFO: UUID cab4185a:86b1f247:733b6818:929730c1 Oct 6 16:16:08 storageqe-109 INFO: UUID cab4185a:86b1f247:733b6818:929730c1 INFO: Level raid10 Oct 6 16:16:09 storageqe-109 INFO: Level raid10 INFO: NumDevices 4 Oct 6 16:16:10 storageqe-109 INFO: NumDevices 4 INFO: Size 2145386496 Oct 6 16:16:11 storageqe-109 INFO: Size 2145386496 INFO: SyncAction idle Oct 6 16:16:12 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 6 16:16:13 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 6 16:16:14 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 6 16:16:15 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 6 16:16:16 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 6 16:16:17 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 6 16:16:18 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 6 16:16:19 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6'), dbus.Int32(3), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 6 16:16:21 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 6 16:16:22 storageqe-109 INFO: Running 1 INFO: bitma is -16, Oct 6 16:16:23 storageqe-109 INFO: bitma is -16, INFO: BitmapLocation -16 Oct 6 16:16:24 storageqe-109 INFO: BitmapLocation -16 Oct 6 16:16:25 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop8 at 0x7fbfb458f590> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop8 /org/freedesktop/UDisks2/block_devices/loop8 Oct 6 16:16:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop8 (backed by /home/loop0.img) Oct 6 16:16:25 storageqe-109 INFO: new_disk_obj :1.29 /org/freedesktop/UDisks2/block_devices/loop8 at 0x7fbfb458f590> Oct 6 16:16:25 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop8 /org/freedesktop/UDisks2/block_devices/loop8 INFO: Oct 6 16:16:27 storageqe-109 INFO: INFO: Oct 6 16:16:30 storageqe-109 INFO: Oct 6 16:16:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:37 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 6 16:16:37 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/54f607ee-2f09-4bc9-9c8a-c7aec817d3b4 on behalf of uid 0 Oct 6 16:16:37 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 54f607ee-2f09-4bc9-9c8a-c7aec817d3b4 r/w with ordered data mode. Quota mode: none. Oct 6 16:16:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:40 storageqe-109 systemd[1]: run-media-root-54f607ee\x2d2f09\x2d4bc9\x2d9c8a\x2dc7aec817d3b4.mount: Deactivated successfully. Oct 6 16:16:40 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 54f607ee-2f09-4bc9-9c8a-c7aec817d3b4. Oct 6 16:16:40 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/54f607ee-2f09-4bc9-9c8a-c7aec817d3b4 (device 9:127 is not mounted) Oct 6 16:16:40 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:16:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:48 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 3e1d2c89-6cdf-4e3a-9e2c-359768589cd1 Oct 6 16:16:48 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 6 16:16:48 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/3e1d2c89-6cdf-4e3a-9e2c-359768589cd1 on behalf of uid 0 Oct 6 16:16:48 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:51 storageqe-109 systemd[1]: run-media-root-3e1d2c89\x2d6cdf\x2d4e3a\x2d9e2c\x2d359768589cd1.mount: Deactivated successfully. Oct 6 16:16:51 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 3e1d2c89-6cdf-4e3a-9e2c-359768589cd1 Oct 6 16:16:51 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/3e1d2c89-6cdf-4e3a-9e2c-359768589cd1 (device 9:127 is not mounted) Oct 6 16:16:51 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:16:51 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:16:59 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 36068cdc-831c-412a-b9c5-3c2a6a95a9ac r/w with ordered data mode. Quota mode: none. Oct 6 16:16:59 storageqe-109 udisksd[5174]: Mounted /dev/md127 at /run/media/root/36068cdc-831c-412a-b9c5-3c2a6a95a9ac on behalf of uid 0 Oct 6 16:16:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:17:02 storageqe-109 systemd[1]: run-media-root-36068cdc\x2d831c\x2d412a\x2db9c5\x2d3c2a6a95a9ac.mount: Deactivated successfully. Oct 6 16:17:02 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 36068cdc-831c-412a-b9c5-3c2a6a95a9ac. Oct 6 16:17:02 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/36068cdc-831c-412a-b9c5-3c2a6a95a9ac (device 9:127 is not mounted) Oct 6 16:17:02 storageqe-109 udisksd[5174]: Unmounted /dev/md127 on behalf of uid 0 Oct 6 16:17:02 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:17:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:17:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:17:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:17:06 storageqe-109 kernel: md127: detected capacity change from 4190208 to 0 Oct 6 16:17:06 storageqe-109 kernel: md: md127 stopped. Oct 6 16:17:06 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:17:09 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 6 16:17:09 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:17:09 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 6 16:17:09 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:17:09 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 6 16:17:09 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 16:17:09 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop6 (was backed by /home/loop13.img) Oct 6 16:17:10 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop6 Oct 6 16:17:11 storageqe-109 udisksd[5174]: udisks_state_check_loop_entry: unexpected name for /dev/loop4 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 6 16:17:11 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop4 Oct 6 16:17:11 storageqe-109 udisksd[5174]: udisks_state_check_loop_entry: unexpected name for /dev/loop5 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 6 16:17:11 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop5 Oct 6 16:17:11 storageqe-109 udisksd[5174]: udisks_state_check_loop_entry: unexpected name for /dev/loop7 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 6 16:17:11 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop7 Oct 6 16:17:11 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop8 Oct 6 16:17:11 storageqe-109 udisksd[5174]: udisks_state_check_loop_entry: unexpected name for /dev/loop2 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 6 16:17:11 storageqe-109 udisksd[5174]: udisks_state_check_loop_entry: unexpected name for /dev/loop2 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 6 16:17:11 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz1400056_md #### INFO: #### will start test_bz1710257_iSCSI_initiator_byte ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:17:16 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:17:16 storageqe-109 INFO: #### END test_bz1400056_md #### Oct 6 16:17:16 storageqe-109 INFO: #### will start test_bz1710257_iSCSI_initiator_byte ##### Oct 6 16:17:16 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz1710257_iSCSI_initiator_byte #### INFO: #### will start test_bz1668291_snapshot ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:17:28 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:17:28 storageqe-109 INFO: #### END test_bz1710257_iSCSI_initiator_byte #### Oct 6 16:17:28 storageqe-109 INFO: #### will start test_bz1668291_snapshot ##### Oct 6 16:17:28 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:17:35 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:17:35 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 6 16:17:35 storageqe-109 kernel: loop0: Oct 6 16:17:39 storageqe-109 dmeventd[1119988]: Monitoring snapshot vg03-snap01. Oct 6 16:17:40 storageqe-109 dmeventd[1119988]: No longer monitoring snapshot vg03-snap01. Oct 6 16:17:47 storageqe-109 kernel: loop0: Oct 6 16:17:47 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 6 16:17:47 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz1668291_snapshot #### INFO: #### will start test_bz1534904_get_thin_size ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:17:53 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:17:53 storageqe-109 INFO: #### END test_bz1668291_snapshot #### Oct 6 16:17:53 storageqe-109 INFO: #### will start test_bz1534904_get_thin_size ##### Oct 6 16:17:53 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:00 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:18:00 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 6 16:18:00 storageqe-109 kernel: loop0: Oct 6 16:18:02 storageqe-109 dmeventd[1119988]: Monitoring thin pool vg03-tp3. Oct 6 16:18:04 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool vg03-tp3. Oct 6 16:18:05 storageqe-109 dmeventd[1119988]: Monitoring thin pool vg03-tp3-tpool. Oct 6 16:18:08 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool vg03-tp3-tpool. Oct 6 16:18:15 storageqe-109 kernel: loop0: Oct 6 16:18:15 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 6 16:18:15 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz1534904_get_thin_size #### INFO: #### will start test_bz2120697_ata_secure_erase ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:21 storageqe-109 INFO: #### END test_bz1534904_get_thin_size #### Oct 6 16:18:21 storageqe-109 INFO: #### will start test_bz2120697_ata_secure_erase ##### Oct 6 16:18:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:28 storageqe-109 systemd[1]: Reload requested from client PID 1131447 ('systemctl') (unit session-4.scope)... Oct 6 16:18:28 storageqe-109 systemd[1]: Reloading... Oct 6 16:18:28 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 6 16:18:28 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 16:18:28 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 6 16:18:28 storageqe-109 systemd[1]: Reloading finished in 143 ms. Oct 6 16:18:28 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:18:28 storageqe-109 iscsid[5612]: iscsid shutting down. Oct 6 16:18:28 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:18:28 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:18:28 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:18:28 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:18:28 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 16:18:29 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 16:18:29 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 16:18:29 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz2120697_ata_secure_erase #### INFO: #### will start test_journalctl_log_check ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:45 storageqe-109 INFO: #### END test_bz2120697_ata_secure_erase #### Oct 6 16:18:45 storageqe-109 INFO: #### will start test_journalctl_log_check ##### Oct 6 16:18:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_journalctl_log_check #### INFO: #### will start test_bz1983602_iscsi_login_failed ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:57 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:57 storageqe-109 INFO: #### END test_journalctl_log_check #### Oct 6 16:18:57 storageqe-109 INFO: #### will start test_bz1983602_iscsi_login_failed ##### Oct 6 16:18:57 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:18:59 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 Oct 6 16:19:04 storageqe-109 INFO: Setting up local iSCSI target... Oct 6 16:19:04 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 6 16:19:04 storageqe-109 INFO: Creating test disk files... Oct 6 16:19:04 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 6 16:19:04 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 16:19:04 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 16:19:04 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 6 16:19:04 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 16:19:04 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 6 16:19:04 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 16:19:05 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Clearing existing targetcli configuration... Oct 6 16:19:05 storageqe-109 kernel: Rounding down aligned max_sectors from 4294967295 to 4294967288 INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 16:19:07 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 16:19:07 storageqe-109 kernel: dev[00000000f2722835]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:07 storageqe-109 kernel: dev[000000008460b8a8]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:07 storageqe-109 kernel: dev[00000000bdc6d537]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:07 storageqe-109 kernel: dev[00000000a565df83]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:07 storageqe-109 kernel: dev[000000009d671c9d]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:07 storageqe-109 kernel: dev[00000000c56b68ab]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:07 storageqe-109 kernel: dev[0000000071e52b60]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:07 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 6 16:19:07 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:07 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:07 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 6 16:19:07 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 6 16:19:07 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:07 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 6 16:19:07 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 6 16:19:07 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 6 16:19:07 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:07 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 6 16:19:07 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:07 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 6 16:19:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 6 16:19:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 6 16:19:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 6 16:19:07 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 6 16:19:07 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:07 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 6 16:19:07 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 INFO: Waiting for targetcli configuration to take effect... Oct 6 16:19:07 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 6 16:19:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:07 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 6 16:19:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 6 16:19:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 6 16:19:07 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 6 16:19:07 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:07 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 6 16:19:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:07 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 6 16:19:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 6 16:19:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 6 16:19:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 6 16:19:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk Oct 6 16:19:07 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 6 16:19:17 storageqe-109 INFO: Verifying iSCSI target setup... Oct 6 16:19:17 storageqe-109 INFO: Found 4 LIO target(s) Oct 6 16:19:17 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 6 16:19:17 storageqe-109 kernel: iscsi: registered transport (tcp) Oct 6 16:19:18 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:19:18 storageqe-109 iscsid[1131498]: iscsid shutting down. Oct 6 16:19:18 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:19:18 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:19:18 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:19:18 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:19:18 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 16:19:18 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:19:18 storageqe-109 iscsid[1132530]: iscsid shutting down. Oct 6 16:19:18 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:19:18 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:19:18 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:19:18 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:19:18 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 16:19:18 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 16:19:18 storageqe-109 iscsid[1132536]: iscsid: Login authentication failed with target iqn.2003-01.udisks.test:iscsi-test-noauth, T bit set on response, but authenticaton not complete Oct 6 16:19:18 storageqe-109 iscsid[1132536]: iscsid: connection1:0 Login error (Login status 5) Oct 6 16:19:18 storageqe-109 kernel: iSCSI Login negotiation failed. Oct 6 16:19:18 storageqe-109 iscsid[1132536]: iscsid: Connection1:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 6 16:19:19 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:19:19 storageqe-109 iscsid[1132536]: iscsid shutting down. Oct 6 16:19:19 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:19:19 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:19:19 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:19:19 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:19:19 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 16:19:19 storageqe-109 iscsid[1132548]: iscsid shutting down. Oct 6 16:19:19 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:19:19 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:19:19 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:19:19 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:19:19 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:19:19 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 16:19:19 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 16:19:19 storageqe-109 iscsid[1132551]: iscsid: Connection2:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 6 16:19:19 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:19 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 6 16:19:19 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 6 16:19:19 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:20 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 6 16:19:20 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 6 16:19:20 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:20 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:20 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 6 16:19:20 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 6 16:19:20 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:20 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk Oct 6 16:19:20 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 6 16:19:20 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 6 16:19:20 storageqe-109 iscsid[1132551]: iscsid: Connection2:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 6 16:19:21 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 6 16:19:21 storageqe-109 INFO: Clearing targetcli configuration... Oct 6 16:19:21 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 6 16:19:21 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 6 16:19:21 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 6 16:19:21 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 6 16:19:21 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 6 16:19:21 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 6 16:19:21 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 6 16:19:21 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 6 16:19:22 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 6 16:19:22 storageqe-109 INFO: Removing test disk files... Oct 6 16:19:22 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 6 16:19:22 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 6 16:19:22 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 6 16:19:22 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 6 16:19:22 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 6 16:19:22 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 6 16:19:22 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 6 16:19:22 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz1983602_iscsi_login_failed #### INFO: #### will start test_bz2136557_iscsi_chap ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:19:28 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:19:28 storageqe-109 INFO: #### END test_bz1983602_iscsi_login_failed #### Oct 6 16:19:28 storageqe-109 INFO: #### will start test_bz2136557_iscsi_chap ##### Oct 6 16:19:28 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 16:19:34 storageqe-109 INFO: Setting up local iSCSI target... Oct 6 16:19:34 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 6 16:19:34 storageqe-109 INFO: Creating test disk files... Oct 6 16:19:34 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 6 16:19:34 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 16:19:34 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 16:19:34 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 6 16:19:34 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 16:19:35 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 6 16:19:35 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 16:19:35 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 16:19:37 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 16:19:37 storageqe-109 kernel: dev[000000009cdbba7b]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:37 storageqe-109 kernel: dev[000000003dbe9af2]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:37 storageqe-109 kernel: dev[0000000011d70dcf]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:37 storageqe-109 kernel: dev[00000000b21374dd]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:37 storageqe-109 kernel: dev[0000000099b056cf]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:37 storageqe-109 kernel: dev[000000002fc11c7c]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:37 storageqe-109 kernel: dev[00000000c31320a7]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:19:37 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 6 16:19:37 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:37 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:37 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 6 16:19:37 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 6 16:19:37 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:37 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 6 16:19:37 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 6 16:19:37 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:37 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 6 16:19:37 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:37 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 6 16:19:37 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:37 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 6 16:19:37 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 6 16:19:37 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:37 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 6 16:19:37 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 6 16:19:37 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 6 16:19:37 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:37 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 6 16:19:37 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 6 16:19:37 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:37 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:37 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 6 16:19:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:37 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 6 16:19:37 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:37 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 6 16:19:37 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:37 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 6 16:19:37 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 6 16:19:37 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 6 16:19:37 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 6 16:19:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:37 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:37 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:19:37 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 6 16:19:37 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 INFO: Waiting for targetcli configuration to take effect... Oct 6 16:19:37 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 6 16:19:38 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:38 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 6 16:19:38 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:38 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:38 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 6 16:19:38 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 6 16:19:38 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:38 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk Oct 6 16:19:38 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 6 16:19:48 storageqe-109 INFO: Verifying iSCSI target setup... Oct 6 16:19:48 storageqe-109 INFO: Found 4 LIO target(s) Oct 6 16:19:48 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 6 16:19:48 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:19:48 storageqe-109 iscsid[1132551]: iscsid shutting down. Oct 6 16:19:48 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:19:48 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:19:48 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:19:48 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:19:48 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 16:19:48 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 16:19:48 storageqe-109 iscsid[1133030]: iscsid: Connection3:0 to [target: iqn.2003-01.udisks.test:iscsi-test-chap, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 6 16:19:48 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:48 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 6 16:19:48 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 2 INFO: initfw_name None Oct 6 16:19:48 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 6 16:19:48 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:48 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 6 16:19:48 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:48 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:48 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 6 16:19:48 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 6 16:19:48 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:48 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk Oct 6 16:19:48 storageqe-109 INFO: initfw_name None INFO: init_name iqn.1994-05.com.redhat:iscsi-test INFO: init_name_raw iqn.1994-05.com.redhat:iscsi-test Oct 6 16:19:48 storageqe-109 INFO: init_name iqn.1994-05.com.redhat:iscsi-test Oct 6 16:19:48 storageqe-109 INFO: init_name_raw iqn.1994-05.com.redhat:iscsi-test INFO: target_name iqn.2003-01.udisks.test:iscsi-test-chap Oct 6 16:19:50 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-chap INFO: tpgt 1 Oct 6 16:19:51 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 6 16:19:52 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 6 16:19:53 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 6 16:19:54 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 6 16:19:55 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 6 16:19:56 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 6 16:19:57 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 6 16:19:58 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 Oct 6 16:19:59 storageqe-109 INFO: tgt_reset_timeout 30 Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 6 16:19:59 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 6 16:19:59 storageqe-109 iscsid[1133030]: iscsid: Connection3:0 to [target: iqn.2003-01.udisks.test:iscsi-test-chap, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 6 16:19:59 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:19:59 storageqe-109 iscsid[1133030]: iscsid shutting down. Oct 6 16:19:59 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:19:59 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:19:59 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:19:59 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:19:59 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 16:19:59 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 16:19:59 storageqe-109 iscsid[1133121]: iscsid: Connection4:0 to [target: iqn.2003-01.udisks.test:iscsi-test-mutual, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 6 16:19:59 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 6 16:19:59 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 6 16:19:59 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 3 Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:19:59 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 6 16:19:59 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:19:59 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: target_name iqn.2003-01.udisks.test:iscsi-test-mutual Oct 6 16:20:01 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-mutual INFO: tpgt 1 Oct 6 16:20:02 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 6 16:20:03 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 6 16:20:04 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 6 16:20:05 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 6 16:20:06 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 6 16:20:07 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 6 16:20:08 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 6 16:20:09 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 6 16:20:10 storageqe-109 INFO: tgt_reset_timeout 30 Oct 6 16:20:11 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 6 16:20:11 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 6 16:20:11 storageqe-109 iscsid[1133121]: iscsid: Connection4:0 to [target: iqn.2003-01.udisks.test:iscsi-test-mutual, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 6 16:20:11 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 6 16:20:11 storageqe-109 INFO: Clearing targetcli configuration... Oct 6 16:20:11 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 6 16:20:11 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 6 16:20:11 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 6 16:20:11 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 6 16:20:11 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 6 16:20:11 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 6 16:20:11 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 6 16:20:11 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 6 16:20:11 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 6 16:20:11 storageqe-109 INFO: Removing test disk files... Oct 6 16:20:11 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 6 16:20:11 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 6 16:20:11 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 6 16:20:11 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 6 16:20:11 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 6 16:20:11 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 6 16:20:11 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 6 16:20:11 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz2136557_iscsi_chap #### INFO: #### will start test_md_stop ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:20:18 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:20:18 storageqe-109 INFO: #### END test_bz2136557_iscsi_chap #### Oct 6 16:20:18 storageqe-109 INFO: #### will start test_md_stop ##### Oct 6 16:20:18 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:20:24 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:20:24 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_stop_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_stop INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:20:25 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:20:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_stop_1.img) Oct 6 16:20:25 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:20:25 storageqe-109 INFO: raid level raid1 Oct 6 16:20:25 storageqe-109 INFO: raid name test_md_stop Oct 6 16:20:25 storageqe-109 INFO: raid chunk 0 Oct 6 16:20:25 storageqe-109 INFO: raid bitmap None Oct 6 16:20:25 storageqe-109 INFO: raid version 1.2 Oct 6 16:20:25 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:20:25 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:20:25 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:20:25 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:20:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:20:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:20:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:20:30 storageqe-109 kernel: md: md127: resync done. Oct 6 16:20:34 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:20:34 storageqe-109 kernel: md: md127 stopped. Oct 6 16:20:34 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:20:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_stop_0.img) Oct 6 16:20:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:20:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_stop_1.img) Oct 6 16:20:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_md_stop #### INFO: #### will start test_fs_label_and_resize ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:20:44 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:20:44 storageqe-109 INFO: #### END test_md_stop #### Oct 6 16:20:44 storageqe-109 INFO: #### will start test_fs_label_and_resize ##### Oct 6 16:20:44 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:20:51 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:20:51 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_fs.img) Oct 6 16:20:51 storageqe-109 kernel: loop0: Oct 6 16:21:04 storageqe-109 kernel: loop0: Oct 6 16:21:04 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_fs.img) Oct 6 16:21:04 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fs_label_and_resize #### INFO: #### will start test_fstab_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:11 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:11 storageqe-109 INFO: #### END test_fs_label_and_resize #### Oct 6 16:21:11 storageqe-109 INFO: #### will start test_fstab_handling ##### Oct 6 16:21:11 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:17 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:21:17 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_fstab.img) Oct 6 16:21:29 storageqe-109 kernel: loop0: Oct 6 16:21:29 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_fstab.img) Oct 6 16:21:29 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_fstab_handling #### INFO: #### will start test_manager_device_listing_and_resolving ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:35 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:35 storageqe-109 INFO: #### END test_fstab_handling #### Oct 6 16:21:35 storageqe-109 INFO: #### will start test_manager_device_listing_and_resolving ##### Oct 6 16:21:35 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:42 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:21:42 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_manager.img) Oct 6 16:21:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_manager.img) Oct 6 16:21:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_manager_device_listing_and_resolving #### INFO: #### will start test_luks_change_password ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:48 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:48 storageqe-109 INFO: #### END test_manager_device_listing_and_resolving #### Oct 6 16:21:48 storageqe-109 INFO: #### will start test_luks_change_password ##### Oct 6 16:21:48 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:21:54 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:21:55 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_luks_passwd.img) Oct 6 16:21:55 storageqe-109 kernel: loop0: INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'initial_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:21:55 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'initial_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:21:55 storageqe-109 stratisd[4947]: [2025-10-06T20:21:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:21:55 storageqe-109 stratisd[4947]: [2025-10-06T20:21:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:21:56 storageqe-109 stratisd[4947]: [2025-10-06T20:21:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:21:56 storageqe-109 stratisd[4947]: [2025-10-06T20:21:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 6 16:21:57 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 6 16:21:58 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 6 16:21:59 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 6 16:22:00 storageqe-109 INFO: foramt to luks2 Oct 6 16:22:00 storageqe-109 INFO: foramt to pbkdf2 INFO: changed passwd to redhatredhat Oct 6 16:22:06 storageqe-109 stratisd[4947]: [2025-10-06T20:22:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:06 storageqe-109 stratisd[4947]: [2025-10-06T20:22:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:06 storageqe-109 INFO: changed passwd to redhatredhat Oct 6 16:22:06 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:22:06 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:22:06 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:08 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:10 storageqe-109 stratisd[4947]: [2025-10-06T20:22:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:10 storageqe-109 stratisd[4947]: [2025-10-06T20:22:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:10 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 INFO: changed passwd to initial_password Oct 6 16:22:19 storageqe-109 stratisd[4947]: [2025-10-06T20:22:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:19 storageqe-109 stratisd[4947]: [2025-10-06T20:22:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:19 storageqe-109 INFO: changed passwd to initial_password Oct 6 16:22:19 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:22:19 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:22:19 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:21 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:22 storageqe-109 stratisd[4947]: [2025-10-06T20:22:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:22 storageqe-109 stratisd[4947]: [2025-10-06T20:22:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:23 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:22:31 storageqe-109 stratisd[4947]: [2025-10-06T20:22:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:31 storageqe-109 stratisd[4947]: [2025-10-06T20:22:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:31 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:22:31 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:33 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:35 storageqe-109 stratisd[4947]: [2025-10-06T20:22:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:35 storageqe-109 stratisd[4947]: [2025-10-06T20:22:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:35 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:22:44 storageqe-109 stratisd[4947]: [2025-10-06T20:22:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:44 storageqe-109 stratisd[4947]: [2025-10-06T20:22:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:44 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:22:44 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:46 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 6 16:22:48 storageqe-109 stratisd[4947]: [2025-10-06T20:22:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:48 storageqe-109 stratisd[4947]: [2025-10-06T20:22:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:48 storageqe-109 udisksd[5174]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 6 16:22:56 storageqe-109 stratisd[4947]: [2025-10-06T20:22:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:56 storageqe-109 stratisd[4947]: [2025-10-06T20:22:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:22:56 storageqe-109 udisksd[5174]: LUKS device 253:3 was manually removed Oct 6 16:22:56 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 6 16:23:01 storageqe-109 kernel: loop0: Oct 6 16:23:01 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_luks_passwd.img) Oct 6 16:23:01 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_change_password #### INFO: #### will start test_manager_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:08 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:08 storageqe-109 INFO: #### END test_luks_change_password #### Oct 6 16:23:08 storageqe-109 INFO: #### will start test_manager_properties ##### Oct 6 16:23:08 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_manager_properties #### INFO: #### will start test_nvme_manager_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:23 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:23 storageqe-109 INFO: #### END test_manager_properties #### Oct 6 16:23:23 storageqe-109 INFO: #### will start test_nvme_manager_properties ##### Oct 6 16:23:23 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_manager_properties #### INFO: #### will start test_nvme_smart_update ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:42 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:42 storageqe-109 INFO: #### END test_nvme_manager_properties #### Oct 6 16:23:42 storageqe-109 INFO: #### will start test_nvme_smart_update ##### Oct 6 16:23:42 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_smart_update #### INFO: #### will start test_nvme_smart_get_attributes ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:23:56 storageqe-109 INFO: #### END test_nvme_smart_update #### Oct 6 16:23:56 storageqe-109 INFO: #### will start test_nvme_smart_get_attributes ##### Oct 6 16:23:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_smart_get_attributes #### INFO: #### will start test_nvme_smart_self_test ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:24:09 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:24:09 storageqe-109 INFO: #### END test_nvme_smart_get_attributes #### Oct 6 16:24:09 storageqe-109 INFO: #### will start test_nvme_smart_self_test ##### Oct 6 16:24:09 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_smart_self_test #### INFO: #### will start test_nvme_properties_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:24:22 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:24:22 storageqe-109 INFO: #### END test_nvme_smart_self_test #### Oct 6 16:24:22 storageqe-109 INFO: #### will start test_nvme_properties_validation ##### Oct 6 16:24:22 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_properties_validation #### INFO: #### will start test_iscsi_session_logout_no_interface ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:24:36 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:24:36 storageqe-109 INFO: #### END test_nvme_properties_validation #### Oct 6 16:24:36 storageqe-109 INFO: #### will start test_iscsi_session_logout_no_interface ##### Oct 6 16:24:36 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 Oct 6 16:24:42 storageqe-109 INFO: Setting up local iSCSI target... Oct 6 16:24:42 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 6 16:24:42 storageqe-109 INFO: Creating test disk files... Oct 6 16:24:42 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 6 16:24:42 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 16:24:42 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 16:24:42 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 6 16:24:42 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 16:24:43 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 6 16:24:43 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 16:24:43 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 16:24:45 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 16:24:45 storageqe-109 kernel: dev[000000005422450a]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:24:45 storageqe-109 kernel: dev[000000009cdbba7b]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:24:45 storageqe-109 kernel: dev[000000003dbe9af2]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:24:45 storageqe-109 kernel: dev[0000000011d70dcf]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:24:45 storageqe-109 kernel: dev[00000000b21374dd]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:24:45 storageqe-109 kernel: dev[0000000099b056cf]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:24:45 storageqe-109 kernel: dev[000000002fc11c7c]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 16:24:45 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 6 16:24:45 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:24:45 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:24:45 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 6 16:24:45 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 6 16:24:45 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:24:45 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 6 16:24:45 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 6 16:24:45 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 6 16:24:45 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 6 16:24:45 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:24:45 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 6 16:24:45 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 6 16:24:45 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:24:45 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 6 16:24:45 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 6 16:24:45 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:24:45 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:24:45 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 6 16:24:45 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:24:45 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 6 16:24:45 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 6 16:24:45 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:24:45 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 6 16:24:45 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 6 16:24:45 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 6 16:24:45 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 6 16:24:45 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 6 16:24:45 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 16:24:45 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 6 16:24:45 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 6 16:24:45 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:24:45 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 6 16:24:45 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 6 16:24:45 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 6 16:24:45 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:45 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 6 16:24:45 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 6 16:24:46 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 6 16:24:56 storageqe-109 INFO: Verifying iSCSI target setup... Oct 6 16:24:56 storageqe-109 INFO: Found 4 LIO target(s) Oct 6 16:24:56 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 6 16:24:56 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 16:24:56 storageqe-109 iscsid[1133121]: iscsid shutting down. Oct 6 16:24:56 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 16:24:56 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 16:24:56 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 16:24:56 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 16:24:56 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 16:24:56 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 16:24:56 storageqe-109 iscsid[1142526]: iscsid: Connection5:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 6 16:24:56 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 6 16:24:56 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 6 16:24:56 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 6 16:24:56 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 6 16:24:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 16:24:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 6 16:24:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 16:24:56 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 6 16:24:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 6 16:24:56 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 16:24:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: target_name iqn.2003-01.udisks.test:iscsi-test-noauth Oct 6 16:24:58 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-noauth INFO: tpgt 1 Oct 6 16:24:59 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 6 16:25:00 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 6 16:25:01 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 6 16:25:02 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 6 16:25:03 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 6 16:25:04 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 6 16:25:05 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 6 16:25:06 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 6 16:25:07 storageqe-109 INFO: tgt_reset_timeout 30 Oct 6 16:25:07 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 6 16:25:07 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 6 16:25:07 storageqe-109 iscsid[1142526]: iscsid: Connection5:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 6 16:25:07 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 6 16:25:07 storageqe-109 INFO: Clearing targetcli configuration... Oct 6 16:25:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 6 16:25:07 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 6 16:25:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 6 16:25:07 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 6 16:25:08 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 6 16:25:08 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 6 16:25:08 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 6 16:25:08 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 6 16:25:08 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 6 16:25:08 storageqe-109 INFO: Removing test disk files... Oct 6 16:25:08 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 6 16:25:08 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 6 16:25:08 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 6 16:25:08 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 6 16:25:08 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 6 16:25:08 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 6 16:25:08 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 6 16:25:08 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_iscsi_session_logout_no_interface #### INFO: #### will start test_iscsi_discover_invalid_target ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:25:14 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:25:14 storageqe-109 INFO: #### END test_iscsi_session_logout_no_interface #### Oct 6 16:25:14 storageqe-109 INFO: #### will start test_iscsi_discover_invalid_target ##### Oct 6 16:25:14 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_iscsi_discover_invalid_target #### INFO: #### will start test_vdo_deduplication_and_compression ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:25:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:25:27 storageqe-109 INFO: #### END test_iscsi_discover_invalid_target #### Oct 6 16:25:27 storageqe-109 INFO: #### will start test_vdo_deduplication_and_compression ##### Oct 6 16:25:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:25:43 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 6 16:25:43 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_vdo_dedup.img) Oct 6 16:25:43 storageqe-109 lvm[1143158]: PV /dev/loop0 not used. Oct 6 16:25:43 storageqe-109 lvm[1143161]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:25:43 storageqe-109 systemd[1]: Started lvm-activate-test_vdo_vg.service - [systemd-run] /usr/sbin/lvm vgchange -aay --autoactivation event test_vdo_vg. Oct 6 16:25:43 storageqe-109 lvm[1143163]: 0 logical volume(s) in volume group "test_vdo_vg" now active Oct 6 16:25:43 storageqe-109 systemd[1]: lvm-activate-test_vdo_vg.service: Deactivated successfully. Oct 6 16:25:44 storageqe-109 UDS/vdoformat[1143179]: INFO (vdoformat/1143179) Using 2 indexing zones for concurrency. Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo19:lvm: loading device '253:4' Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo19:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo19:lvm: starting device '253:4' Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:physQ0: VDO commencing normal operation Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:journa: Setting UDS index target state to online Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: creating index: 253:3 Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' started Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: Using 2 indexing zones for concurrency. Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:25:44 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:25:44 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:44 storageqe-109 lvm[1143221]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:25:44 storageqe-109 lvm[1143221]: VG test_vdo_vg finished INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_vg/udisks_test_vdopool Oct 6 16:25:46 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_vg/udisks_test_vdopool INFO: OperatingMode normal Oct 6 16:25:47 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 6 16:25:48 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 6 16:25:49 storageqe-109 INFO: IndexState online INFO: UsedSize 3219931136 Oct 6 16:25:50 storageqe-109 INFO: UsedSize 3219931136 INFO: Compression 1 Oct 6 16:25:51 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 6 16:25:52 storageqe-109 INFO: Deduplication 1 Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:25:52 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: beginning save (vcn 18446744073709551615) Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is enabled Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:25:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: finished save (vcn 18446744073709551615) Oct 6 16:25:52 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:52 storageqe-109 lvm[1143283]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:25:52 storageqe-109 lvm[1143283]: VG test_vdo_vg finished Oct 6 16:25:53 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:25:53 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:25:53 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:53 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:25:53 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:25:53 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:25:53 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is disabled Oct 6 16:25:53 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:25:53 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:53 storageqe-109 lvm[1143303]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:25:53 storageqe-109 lvm[1143303]: VG test_vdo_vg finished Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:25:54 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: loading or rebuilding index: 253:3 Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is disabled Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: Using 2 indexing zones for concurrency. Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:25:54 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:54 storageqe-109 lvm[1143328]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:25:54 storageqe-109 lvm[1143328]: VG test_vdo_vg finished Oct 6 16:25:54 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: loaded index from chapter 0 through chapter 0 Oct 6 16:25:55 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:25:55 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:25:55 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:55 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:25:55 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:25:55 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:25:55 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is enabled Oct 6 16:25:55 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:25:56 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:56 storageqe-109 lvm[1143348]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:25:56 storageqe-109 lvm[1143348]: VG test_vdo_vg finished Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: Preparing to resize physical to 2358272 Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: Done preparing to resize physical Oct 6 16:25:59 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: Physical block count was 1833984, now 2358272 Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is enabled Oct 6 16:25:59 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:25:59 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:25:59 storageqe-109 lvm[1143375]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:25:59 storageqe-109 lvm[1143375]: VG test_vdo_vg finished INFO: the 9659482112 8589934592 Oct 6 16:26:02 storageqe-109 INFO: the 9659482112 8589934592 INFO:before lv vdo 80509665280 Oct 6 16:26:03 storageqe-109 journal: INFO:before lv vdo 80509665280 Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: Preparing to resize logical to 98278656 Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: Done preparing to resize logical Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: Resizing logical to 98278656 Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: Logical blocks now 98278656 Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is enabled Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:26:03 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is enabled Oct 6 16:26:03 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:26:03 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:03 storageqe-109 lvm[1143409]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:26:03 storageqe-109 lvm[1143409]: VG test_vdo_vg finished INFO: after lv vdo 402548326400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 5 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 80 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 6 16:26:05 storageqe-109 INFO: after lv vdo 402548326400 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 5 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics maxVIOs 80 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 19 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 98278656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9433088 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics instance 19 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 6 16:26:05 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 98278656 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9433088 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics blocksWritten 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573248 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 5 INFO: vdo.GetStatistics overheadBlocksUsed 786470 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 34 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2358272 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573248 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 5 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 786470 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics usedPercent 34 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2358272 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 3 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 3 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 6 16:26:06 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:26:09 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is enabled Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:26:09 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:09 storageqe-109 lvm[1144091]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:26:09 storageqe-109 lvm[1144091]: VG test_vdo_vg finished Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:26:09 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is disabled Oct 6 16:26:09 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:26:09 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:09 storageqe-109 lvm[1144106]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:26:09 storageqe-109 lvm[1144106]: VG test_vdo_vg finished Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:26:11 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: loading or rebuilding index: 253:3 Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is disabled Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: Using 2 indexing zones for concurrency. Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:26:11 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:dedupe: loaded index from chapter 0 through chapter 0 Oct 6 16:26:11 storageqe-109 lvm[1144133]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:26:11 storageqe-109 lvm[1144133]: VG test_vdo_vg finished Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: preparing to modify device '253:4' Oct 6 16:26:11 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: resuming device '253:4' Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo19:packer: compression is enabled Oct 6 16:26:11 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' resumed Oct 6 16:26:11 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:11 storageqe-109 lvm[1144148]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 6 16:26:11 storageqe-109 lvm[1144148]: VG test_vdo_vg finished Oct 6 16:26:14 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 16:26:14 storageqe-109 kernel: device-mapper: vdo19:lvm: suspending device '253:4' Oct 6 16:26:14 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' suspended Oct 6 16:26:14 storageqe-109 kernel: device-mapper: vdo19:lvm: stopping device '253:4' Oct 6 16:26:14 storageqe-109 kernel: device-mapper: vdo19:lvm: device '253:4' stopped Oct 6 16:26:15 storageqe-109 lvm[1144170]: PV /dev/loop0 not used. Oct 6 16:26:15 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_vdo_dedup.img) Oct 6 16:26:15 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_vdo_deduplication_and_compression #### INFO: #### will start test_partition_resize ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:26:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:26:21 storageqe-109 INFO: #### END test_vdo_deduplication_and_compression #### Oct 6 16:26:21 storageqe-109 INFO: #### will start test_partition_resize ##### Oct 6 16:26:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:26:27 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:26:27 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_resize.img) Oct 6 16:26:27 storageqe-109 kernel: loop0: Oct 6 16:26:28 storageqe-109 kernel: loop0: p1 Oct 6 16:26:33 storageqe-109 udisksd[5174]: Could not open /dev/loop0p1 to query new partition size Oct 6 16:26:33 storageqe-109 kernel: loop0: p1 Oct 6 16:27:01 storageqe-109 kernel: loop0: Oct 6 16:27:01 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_resize.img) Oct 6 16:27:01 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_partition_resize #### INFO: #### will start test_nvme_size_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:27:08 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:27:08 storageqe-109 INFO: #### END test_partition_resize #### Oct 6 16:27:08 storageqe-109 INFO: #### will start test_nvme_size_properties ##### Oct 6 16:27:08 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_size_properties #### INFO: #### will start test_iscsi_get_firmware_initiator_name_failure ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:27:24 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:27:24 storageqe-109 INFO: #### END test_nvme_size_properties #### Oct 6 16:27:24 storageqe-109 INFO: #### will start test_iscsi_get_firmware_initiator_name_failure ##### Oct 6 16:27:24 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_iscsi_get_firmware_initiator_name_failure #### INFO: #### will start test_mdraid_basic_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:27:36 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:27:36 storageqe-109 INFO: #### END test_iscsi_get_firmware_initiator_name_failure #### Oct 6 16:27:36 storageqe-109 INFO: #### will start test_mdraid_basic_properties ##### Oct 6 16:27:36 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:27:43 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:27:43 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_props1.img) Oct 6 16:27:43 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:27:43 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_props2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_props INFO: raid chunk 524288 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:27:44 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 16:27:44 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop_md_props3.img) Oct 6 16:27:44 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 6 16:27:44 storageqe-109 INFO: raid level raid5 Oct 6 16:27:44 storageqe-109 INFO: raid name test_md_props Oct 6 16:27:44 storageqe-109 INFO: raid chunk 524288 Oct 6 16:27:44 storageqe-109 INFO: raid bitmap None Oct 6 16:27:44 storageqe-109 INFO: raid version 1.2 Oct 6 16:27:44 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 16:27:44 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 16:27:44 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 6 16:27:44 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 16:27:44 storageqe-109 kernel: md: recover of RAID array md127 Oct 6 16:27:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:27:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:27:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:27:49 storageqe-109 kernel: md: md127: recover done. Oct 6 16:27:52 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 16:27:52 storageqe-109 kernel: md: md127 stopped. Oct 6 16:27:52 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:27:55 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_props1.img) Oct 6 16:27:55 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:27:55 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_props2.img) Oct 6 16:27:55 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:27:55 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/loop_md_props3.img) Oct 6 16:27:55 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_basic_properties #### INFO: #### will start test_mdraid_set_bitmap_location ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:01 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:01 storageqe-109 INFO: #### END test_mdraid_basic_properties #### Oct 6 16:28:01 storageqe-109 INFO: #### will start test_mdraid_set_bitmap_location ##### Oct 6 16:28:01 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:08 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:28:08 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_set_bitmap1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_set_bitmap INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:28:08 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:28:08 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_set_bitmap2.img) Oct 6 16:28:08 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:28:08 storageqe-109 INFO: raid level raid1 Oct 6 16:28:08 storageqe-109 INFO: raid name test_md_set_bitmap Oct 6 16:28:08 storageqe-109 INFO: raid chunk 0 Oct 6 16:28:08 storageqe-109 INFO: raid bitmap None Oct 6 16:28:08 storageqe-109 INFO: raid version 1.2 Oct 6 16:28:08 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:28:08 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:28:08 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:28:08 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:28:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:28:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:28:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:28:14 storageqe-109 kernel: md: md127: resync done. Oct 6 16:28:17 storageqe-109 kernel: md127: bitmap file is out of date (0 < 17) -- forcing full recovery Oct 6 16:28:17 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery Oct 6 16:28:22 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:28:22 storageqe-109 kernel: md: md127 stopped. Oct 6 16:28:22 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:28:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_set_bitmap1.img) Oct 6 16:28:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:28:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_set_bitmap2.img) Oct 6 16:28:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_set_bitmap_location #### INFO: #### will start test_mdraid_with_internal_bitmap ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:31 storageqe-109 INFO: #### END test_mdraid_set_bitmap_location #### Oct 6 16:28:31 storageqe-109 INFO: #### will start test_mdraid_with_internal_bitmap ##### Oct 6 16:28:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:37 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:28:37 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_bitmap1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_bitmap INFO: raid chunk 0 INFO: raid bitmap internal INFO: raid version 1.2 Oct 6 16:28:38 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:28:38 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_bitmap2.img) Oct 6 16:28:38 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:28:38 storageqe-109 INFO: raid level raid1 Oct 6 16:28:38 storageqe-109 INFO: raid name test_md_bitmap Oct 6 16:28:38 storageqe-109 INFO: raid chunk 0 Oct 6 16:28:38 storageqe-109 INFO: raid bitmap internal Oct 6 16:28:38 storageqe-109 INFO: raid version 1.2 Oct 6 16:28:38 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:28:38 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:28:38 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:28:38 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:28:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:28:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:28:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:28:43 storageqe-109 kernel: md: md127: resync done. Oct 6 16:28:47 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:28:47 storageqe-109 kernel: md: md127 stopped. Oct 6 16:28:47 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:28:50 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_bitmap1.img) Oct 6 16:28:50 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:28:50 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_bitmap2.img) Oct 6 16:28:50 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_with_internal_bitmap #### INFO: #### will start test_mdraid_sync_progress_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:28:56 storageqe-109 INFO: #### END test_mdraid_with_internal_bitmap #### Oct 6 16:28:56 storageqe-109 INFO: #### will start test_mdraid_sync_progress_properties ##### Oct 6 16:28:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:29:03 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:29:03 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_progress1.img) Oct 6 16:29:03 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_progress INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:29:03 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_progress2.img) Oct 6 16:29:03 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:29:04 storageqe-109 INFO: raid level raid1 Oct 6 16:29:04 storageqe-109 INFO: raid name test_md_progress Oct 6 16:29:04 storageqe-109 INFO: raid chunk 0 Oct 6 16:29:04 storageqe-109 INFO: raid bitmap None Oct 6 16:29:04 storageqe-109 INFO: raid version 1.2 Oct 6 16:29:04 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:29:04 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:29:04 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:29:04 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:29:04 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:29:04 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:29:04 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:29:09 storageqe-109 kernel: md: md127: resync done. Oct 6 16:29:21 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:29:21 storageqe-109 kernel: md: md127 stopped. Oct 6 16:29:21 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:29:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_progress1.img) Oct 6 16:29:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:29:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_progress2.img) Oct 6 16:29:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_sync_progress_properties #### INFO: #### will start test_mdraid_consistency_policy ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:29:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:29:30 storageqe-109 INFO: #### END test_mdraid_sync_progress_properties #### Oct 6 16:29:30 storageqe-109 INFO: #### will start test_mdraid_consistency_policy ##### Oct 6 16:29:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:29:37 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:29:37 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_policy1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_policy INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:29:37 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:29:37 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_policy2.img) Oct 6 16:29:37 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:29:37 storageqe-109 INFO: raid level raid1 Oct 6 16:29:37 storageqe-109 INFO: raid name test_md_policy Oct 6 16:29:37 storageqe-109 INFO: raid chunk 0 Oct 6 16:29:37 storageqe-109 INFO: raid bitmap None Oct 6 16:29:37 storageqe-109 INFO: raid version 1.2 Oct 6 16:29:37 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:29:37 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:29:37 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:29:37 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:29:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:29:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:29:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:29:43 storageqe-109 kernel: md: md127: resync done. Oct 6 16:29:46 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:29:46 storageqe-109 kernel: md: md127 stopped. Oct 6 16:29:47 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:29:49 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_policy1.img) Oct 6 16:29:49 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:29:49 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_policy2.img) Oct 6 16:29:49 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_consistency_policy #### INFO: #### will start test_mdraid_sync_actions ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:29:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:29:56 storageqe-109 INFO: #### END test_mdraid_consistency_policy #### Oct 6 16:29:56 storageqe-109 INFO: #### will start test_mdraid_sync_actions ##### Oct 6 16:29:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:30:02 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:30:02 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_sync1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_sync INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:30:03 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:30:03 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_sync2.img) Oct 6 16:30:03 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:30:03 storageqe-109 INFO: raid level raid1 Oct 6 16:30:03 storageqe-109 INFO: raid name test_md_sync Oct 6 16:30:03 storageqe-109 INFO: raid chunk 0 Oct 6 16:30:03 storageqe-109 INFO: raid bitmap None Oct 6 16:30:03 storageqe-109 INFO: raid version 1.2 Oct 6 16:30:03 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:30:03 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:30:03 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:30:03 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:30:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:30:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:30:03 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:30:08 storageqe-109 kernel: md: md127: resync done. Oct 6 16:30:10 storageqe-109 kernel: md: check of RAID array md127 Oct 6 16:30:15 storageqe-109 kernel: md: md127: check done. Oct 6 16:30:18 storageqe-109 kernel: md: repair of RAID array md127 Oct 6 16:30:20 storageqe-109 kernel: md: md127: repair interrupted. Oct 6 16:30:20 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:30:20 storageqe-109 kernel: md: md127 stopped. Oct 6 16:30:20 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:30:23 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_sync1.img) Oct 6 16:30:23 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:30:23 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_sync2.img) Oct 6 16:30:23 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_sync_actions #### INFO: #### will start test_luks_remove_with_teardown ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:30:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:30:29 storageqe-109 INFO: #### END test_mdraid_sync_actions #### Oct 6 16:30:29 storageqe-109 INFO: #### will start test_luks_remove_with_teardown ##### Oct 6 16:30:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:30:36 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:30:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_luks_teardown.img) INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'teardown_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:30:37 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'teardown_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 6 16:30:37 storageqe-109 stratisd[4947]: [2025-10-06T20:30:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:30:37 storageqe-109 stratisd[4947]: [2025-10-06T20:30:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:30:37 storageqe-109 stratisd[4947]: [2025-10-06T20:30:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:30:37 storageqe-109 stratisd[4947]: [2025-10-06T20:30:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: HintEncryptionType Oct 6 16:30:38 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 6 16:30:39 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 6 16:30:40 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 6 16:30:41 storageqe-109 INFO: foramt to luks2 Oct 6 16:30:41 storageqe-109 INFO: foramt to pbkdf2 Oct 6 16:30:43 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:30:43 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:30:43 storageqe-109 udisksd[5174]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 6 16:30:52 storageqe-109 kernel: loop0: Oct 6 16:30:52 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_luks_teardown.img) Oct 6 16:30:52 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_remove_with_teardown #### INFO: #### will start test_vdo_resize ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:30:59 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:30:59 storageqe-109 INFO: #### END test_luks_remove_with_teardown #### Oct 6 16:30:59 storageqe-109 INFO: #### will start test_vdo_resize ##### Oct 6 16:30:59 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:31:14 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 6 16:31:14 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_vdo_resize1.img) Oct 6 16:31:29 storageqe-109 kernel: loop1: detected capacity change from 0 to 31457280 Oct 6 16:31:29 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 16:31:29 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_vdo_resize2.img) Oct 6 16:31:29 storageqe-109 lvm[1147744]: PV /dev/loop0 not used. Oct 6 16:31:29 storageqe-109 lvm[1147748]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:29 storageqe-109 systemd[1]: Started lvm-activate-test_vdo_resize_vg.service - [systemd-run] /usr/sbin/lvm vgchange -aay --autoactivation event test_vdo_resize_vg. Oct 6 16:31:29 storageqe-109 lvm[1147751]: 0 logical volume(s) in volume group "test_vdo_resize_vg" now active Oct 6 16:31:29 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 16:31:29 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 16:31:29 storageqe-109 systemd[1]: lvm-activate-test_vdo_resize_vg.service: Deactivated successfully. Oct 6 16:31:30 storageqe-109 UDS/vdoformat[1147768]: INFO (vdoformat/1147768) Using 2 indexing zones for concurrency. Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo20:lvm: loading device '253:4' Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo20:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo20:lvm: starting device '253:4' Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:physQ0: VDO commencing normal operation Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:journa: Setting UDS index target state to online Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:dedupe: creating index: 253:3 Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:dedupe: Using 2 indexing zones for concurrency. Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' started Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:30 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:30 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:30 storageqe-109 lvm[1147811]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:30 storageqe-109 lvm[1147811]: VG test_vdo_resize_vg finished INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_resize_vg/udisks_test_vdopool Oct 6 16:31:32 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_resize_vg/udisks_test_vdopool INFO: OperatingMode normal Oct 6 16:31:33 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 6 16:31:34 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 6 16:31:35 storageqe-109 INFO: IndexState online INFO: UsedSize 3219931136 Oct 6 16:31:36 storageqe-109 INFO: UsedSize 3219931136 INFO: Compression 1 Oct 6 16:31:37 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 6 16:31:38 storageqe-109 INFO: Deduplication 1 Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:38 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:dedupe: beginning save (vcn 18446744073709551615) Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:dedupe: finished save (vcn 18446744073709551615) Oct 6 16:31:38 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:38 storageqe-109 lvm[1147873]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:38 storageqe-109 lvm[1147873]: VG test_vdo_resize_vg finished Oct 6 16:31:39 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:39 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:39 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:39 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:39 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:39 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:39 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is disabled Oct 6 16:31:39 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:39 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:39 storageqe-109 lvm[1147893]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:39 storageqe-109 lvm[1147893]: VG test_vdo_resize_vg finished Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:40 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:dedupe: loading or rebuilding index: 253:3 Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is disabled Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:dedupe: Using 2 indexing zones for concurrency. Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:40 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:40 storageqe-109 lvm[1147918]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:40 storageqe-109 lvm[1147918]: VG test_vdo_resize_vg finished Oct 6 16:31:40 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:dedupe: loaded index from chapter 0 through chapter 0 Oct 6 16:31:41 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:41 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:41 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:41 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:41 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:41 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:41 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:41 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:41 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:41 storageqe-109 lvm[1147938]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:41 storageqe-109 lvm[1147938]: VG test_vdo_resize_vg finished Oct 6 16:31:44 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:44 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:44 storageqe-109 kernel: device-mapper: vdo20:lvm: Preparing to resize physical to 2358272 Oct 6 16:31:44 storageqe-109 kernel: device-mapper: vdo20:lvm: Done preparing to resize physical Oct 6 16:31:44 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:44 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:44 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:44 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:45 storageqe-109 kernel: device-mapper: vdo20:lvm: Physical block count was 1833984, now 2358272 Oct 6 16:31:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:45 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:45 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:45 storageqe-109 lvm[1147965]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:45 storageqe-109 lvm[1147965]: VG test_vdo_resize_vg finished INFO: the 9659482112 8589934592 Oct 6 16:31:48 storageqe-109 INFO: the 9659482112 8589934592 INFO:before lv vdo 80509665280 Oct 6 16:31:49 storageqe-109 journal: INFO:before lv vdo 80509665280 Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: Preparing to resize logical to 98278656 Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: Done preparing to resize logical Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: Resizing logical to 98278656 Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: Logical blocks now 98278656 Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:49 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:49 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:49 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:49 storageqe-109 lvm[1147999]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:49 storageqe-109 lvm[1147999]: VG test_vdo_resize_vg finished INFO: after lv vdo 402548326400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 5 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 68 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 6 16:31:51 storageqe-109 INFO: after lv vdo 402548326400 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 5 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics maxVIOs 68 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 20 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics instance 20 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 98278656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9433088 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 98278656 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9433088 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 6 16:31:51 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 5 INFO: vdo.GetStatistics overheadBlocksUsed 786470 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 34 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2358272 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 5 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 786470 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics usedPercent 34 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2358272 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 3 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 3 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 6 16:31:52 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: Preparing to resize logical to 196557056 Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: Done preparing to resize logical Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: Resizing logical to 196557056 Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: Logical blocks now 196557056 Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:53 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:53 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:54 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:54 storageqe-109 lvm[1148685]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:54 storageqe-109 lvm[1148685]: VG test_vdo_resize_vg finished Oct 6 16:31:57 storageqe-109 lvm[1148696]: PV /dev/loop1 not used. Oct 6 16:31:57 storageqe-109 lvm[1148698]: PV /dev/loop1 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:57 storageqe-109 lvm[1148698]: VG test_vdo_resize_vg finished Oct 6 16:31:57 storageqe-109 lvm[1148700]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:57 storageqe-109 lvm[1148700]: VG test_vdo_resize_vg finished Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: table line: V4 /dev/dm-3 3668992 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: preparing to modify device '253:4' Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: Preparing to resize physical to 3668992 Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: Done preparing to resize physical Oct 6 16:31:57 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: resuming device '253:4' Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: Physical block count was 2358272, now 3668992 Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo: dm_vdo20:packer: compression is enabled Oct 6 16:31:57 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' resumed Oct 6 16:31:57 storageqe-109 dmeventd[1119988]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:57 storageqe-109 lvm[1148721]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:57 storageqe-109 lvm[1148722]: PV /dev/loop1 online, VG test_vdo_resize_vg is complete. Oct 6 16:31:57 storageqe-109 lvm[1148721]: VG test_vdo_resize_vg finished Oct 6 16:31:57 storageqe-109 lvm[1148722]: VG test_vdo_resize_vg finished Oct 6 16:31:59 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 6 16:31:59 storageqe-109 kernel: device-mapper: vdo20:lvm: suspending device '253:4' Oct 6 16:31:59 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' suspended Oct 6 16:31:59 storageqe-109 kernel: device-mapper: vdo20:lvm: stopping device '253:4' Oct 6 16:31:59 storageqe-109 kernel: device-mapper: vdo20:lvm: device '253:4' stopped Oct 6 16:31:59 storageqe-109 lvm[1148744]: PV /dev/loop0 not used. Oct 6 16:31:59 storageqe-109 lvm[1148745]: PV /dev/loop1 not used. Oct 6 16:31:59 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_vdo_resize1.img) Oct 6 16:31:59 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:31:59 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_vdo_resize2.img) Oct 6 16:31:59 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_vdo_resize #### INFO: #### will start test_mdraid_chunk_size_property ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:06 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:06 storageqe-109 INFO: #### END test_vdo_resize #### Oct 6 16:32:06 storageqe-109 INFO: #### will start test_mdraid_chunk_size_property ##### Oct 6 16:32:06 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:12 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:32:12 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_chunk1.img) Oct 6 16:32:13 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:32:13 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_chunk2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_chunk INFO: raid chunk 262144 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:32:13 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 16:32:13 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop_md_chunk3.img) Oct 6 16:32:13 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 6 16:32:13 storageqe-109 INFO: raid level raid5 Oct 6 16:32:13 storageqe-109 INFO: raid name test_md_chunk Oct 6 16:32:13 storageqe-109 INFO: raid chunk 262144 Oct 6 16:32:13 storageqe-109 INFO: raid bitmap None Oct 6 16:32:13 storageqe-109 INFO: raid version 1.2 Oct 6 16:32:13 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 16:32:13 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 16:32:13 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 6 16:32:13 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 16:32:13 storageqe-109 kernel: md: recover of RAID array md127 Oct 6 16:32:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:32:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:32:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:32:19 storageqe-109 kernel: md: md127: recover interrupted. Oct 6 16:32:19 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 16:32:19 storageqe-109 kernel: md: md127 stopped. Oct 6 16:32:19 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:32:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_chunk1.img) Oct 6 16:32:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:32:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_chunk2.img) Oct 6 16:32:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:32:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/loop_md_chunk3.img) Oct 6 16:32:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_chunk_size_property #### INFO: #### will start test_mdraid_add_and_remove_spare ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:28 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:28 storageqe-109 INFO: #### END test_mdraid_chunk_size_property #### Oct 6 16:32:28 storageqe-109 INFO: #### will start test_mdraid_add_and_remove_spare ##### Oct 6 16:32:28 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:35 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:32:35 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_add_spare1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_add_spare INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:32:35 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:32:35 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_add_spare2.img) Oct 6 16:32:35 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:32:35 storageqe-109 INFO: raid level raid1 Oct 6 16:32:35 storageqe-109 INFO: raid name test_md_add_spare Oct 6 16:32:35 storageqe-109 INFO: raid chunk 0 Oct 6 16:32:35 storageqe-109 INFO: raid bitmap None Oct 6 16:32:35 storageqe-109 INFO: raid version 1.2 Oct 6 16:32:35 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:32:35 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:32:35 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:32:35 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:32:35 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:32:35 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:32:35 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:32:41 storageqe-109 kernel: md: md127: resync done. Oct 6 16:32:43 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 16:32:43 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop_md_spare.img) Oct 6 16:32:50 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:32:50 storageqe-109 kernel: md: md127 stopped. Oct 6 16:32:50 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:32:54 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:32:54 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:32:54 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_add_and_remove_spare #### INFO: #### will start test_mdraid_degraded_state ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:59 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:32:59 storageqe-109 INFO: #### END test_mdraid_add_and_remove_spare #### Oct 6 16:32:59 storageqe-109 INFO: #### will start test_mdraid_degraded_state ##### Oct 6 16:32:59 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:33:06 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:33:06 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_degraded1.img) Oct 6 16:33:06 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:33:06 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_degraded2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_degraded INFO: raid chunk 524288 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:33:07 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 16:33:07 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop_md_degraded3.img) Oct 6 16:33:07 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 6 16:33:07 storageqe-109 INFO: raid level raid5 Oct 6 16:33:07 storageqe-109 INFO: raid name test_md_degraded Oct 6 16:33:07 storageqe-109 INFO: raid chunk 524288 Oct 6 16:33:07 storageqe-109 INFO: raid bitmap None Oct 6 16:33:07 storageqe-109 INFO: raid version 1.2 Oct 6 16:33:07 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 16:33:07 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 16:33:07 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 6 16:33:07 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 16:33:07 storageqe-109 kernel: md: recover of RAID array md127 Oct 6 16:33:07 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:33:07 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:33:07 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:33:12 storageqe-109 kernel: md: md127: recover done. Oct 6 16:33:15 storageqe-109 kernel: md/raid:md127: Disk failure on loop1, disabling device. Oct 6 16:33:15 storageqe-109 kernel: md/raid:md127: Operation continuing on 2 devices. Oct 6 16:33:20 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 16:33:20 storageqe-109 kernel: md: md127 stopped. Oct 6 16:33:20 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:33:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:33:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:33:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_degraded_state #### INFO: #### will start test_mdraid_delete_method ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:33:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:33:29 storageqe-109 INFO: #### END test_mdraid_degraded_state #### Oct 6 16:33:29 storageqe-109 INFO: #### will start test_mdraid_delete_method ##### Oct 6 16:33:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:33:36 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:33:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_delete1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_delete INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:33:36 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:33:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_delete2.img) Oct 6 16:33:36 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:33:36 storageqe-109 INFO: raid level raid1 Oct 6 16:33:36 storageqe-109 INFO: raid name test_md_delete Oct 6 16:33:36 storageqe-109 INFO: raid chunk 0 Oct 6 16:33:36 storageqe-109 INFO: raid bitmap None Oct 6 16:33:36 storageqe-109 INFO: raid version 1.2 Oct 6 16:33:37 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:33:37 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:33:37 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:33:37 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:33:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:33:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:33:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:33:42 storageqe-109 kernel: md: md127: resync done. Oct 6 16:33:45 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:33:45 storageqe-109 kernel: md: md127 stopped. Oct 6 16:33:45 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:33:49 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 16:33:49 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_delete_method #### INFO: #### will start test_mdraid_activedevices_property_structure ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:33:54 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:33:54 storageqe-109 INFO: #### END test_mdraid_delete_method #### Oct 6 16:33:54 storageqe-109 INFO: #### will start test_mdraid_activedevices_property_structure ##### Oct 6 16:33:54 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:34:01 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:34:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_active1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_active INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:34:01 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 16:34:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_active2.img) Oct 6 16:34:01 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:34:01 storageqe-109 INFO: raid level raid1 Oct 6 16:34:01 storageqe-109 INFO: raid name test_md_active Oct 6 16:34:01 storageqe-109 INFO: raid chunk 0 Oct 6 16:34:01 storageqe-109 INFO: raid bitmap None Oct 6 16:34:01 storageqe-109 INFO: raid version 1.2 Oct 6 16:34:01 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:34:01 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:34:01 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:34:01 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:34:01 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:34:01 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:34:01 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:34:07 storageqe-109 kernel: md: md127: resync done. Oct 6 16:34:11 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:34:11 storageqe-109 kernel: md: md127 stopped. Oct 6 16:34:12 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:34:14 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_active1.img) Oct 6 16:34:14 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:34:14 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_active2.img) Oct 6 16:34:14 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_activedevices_property_structure #### INFO: #### will start test_mdraid_size_property_verification ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:34:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:34:21 storageqe-109 INFO: #### END test_mdraid_activedevices_property_structure #### Oct 6 16:34:21 storageqe-109 INFO: #### will start test_mdraid_size_property_verification ##### Oct 6 16:34:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:34:27 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 16:34:27 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_size1.img) Oct 6 16:34:28 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_size1 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:34:28 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_size2.img) Oct 6 16:34:28 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:34:28 storageqe-109 INFO: raid level raid1 Oct 6 16:34:28 storageqe-109 INFO: raid name test_md_size1 Oct 6 16:34:28 storageqe-109 INFO: raid chunk 0 Oct 6 16:34:28 storageqe-109 INFO: raid bitmap None Oct 6 16:34:28 storageqe-109 INFO: raid version 1.2 Oct 6 16:34:28 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 16:34:28 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 16:34:28 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 16:34:28 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 16:34:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:34:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:34:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 16:34:33 storageqe-109 kernel: md: md127: resync done. Oct 6 16:34:37 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 16:34:37 storageqe-109 kernel: md: md127 stopped. Oct 6 16:34:37 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_md_size0 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 6 16:34:42 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 16:34:42 storageqe-109 INFO: raid level raid0 Oct 6 16:34:42 storageqe-109 INFO: raid name test_md_size0 Oct 6 16:34:42 storageqe-109 INFO: raid chunk 0 Oct 6 16:34:42 storageqe-109 INFO: raid bitmap None Oct 6 16:34:42 storageqe-109 INFO: raid version 1.2 Oct 6 16:34:42 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 16:34:47 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 16:34:47 storageqe-109 kernel: md: md127 stopped. Oct 6 16:34:47 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 16:34:50 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_size1.img) Oct 6 16:34:50 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 16:34:50 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_size2.img) Oct 6 16:34:50 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_mdraid_size_property_verification #### INFO: #### will start test_nvme_smart_properties_validation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:34:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:34:56 storageqe-109 INFO: #### END test_mdraid_size_property_verification #### Oct 6 16:34:56 storageqe-109 INFO: #### will start test_nvme_smart_properties_validation ##### Oct 6 16:34:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_smart_properties_validation #### INFO: #### will start test_nvme_drive_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:10 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:10 storageqe-109 INFO: #### END test_nvme_smart_properties_validation #### Oct 6 16:35:10 storageqe-109 INFO: #### will start test_nvme_drive_properties ##### Oct 6 16:35:10 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_drive_properties #### INFO: #### will start test_nvme_controller_static_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:23 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:23 storageqe-109 INFO: #### END test_nvme_drive_properties #### Oct 6 16:35:23 storageqe-109 INFO: #### will start test_nvme_controller_static_properties ##### Oct 6 16:35:23 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_controller_static_properties #### INFO: #### will start test_nvme_namespace_size_property ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:36 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:36 storageqe-109 INFO: #### END test_nvme_controller_static_properties #### Oct 6 16:35:36 storageqe-109 INFO: #### will start test_nvme_namespace_size_property ##### Oct 6 16:35:36 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_size_property #### INFO: #### will start test_nvme_namespace_properties_detailed ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:50 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:35:50 storageqe-109 INFO: #### END test_nvme_namespace_size_property #### Oct 6 16:35:50 storageqe-109 INFO: #### will start test_nvme_namespace_properties_detailed ##### Oct 6 16:35:50 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_properties_detailed #### INFO: #### will start test_nvme_namespace_format ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:36:12 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:36:12 storageqe-109 INFO: #### END test_nvme_namespace_properties_detailed #### Oct 6 16:36:12 storageqe-109 INFO: #### will start test_nvme_namespace_format ##### Oct 6 16:36:12 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:36:20 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 6 16:38:22 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_format #### INFO: #### will start test_nvme_namespace_format_invalid_lba ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:40:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:40:30 storageqe-109 INFO: #### END test_nvme_namespace_format #### Oct 6 16:40:30 storageqe-109 INFO: #### will start test_nvme_namespace_format_invalid_lba ##### Oct 6 16:40:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:40:36 storageqe-109 udisksd[5174]: Error formatting namespace /org/freedesktop/UDisks2/block_devices/nvme0n1: Couldn't match desired LBA data block size in a device supported LBA format data sizes (g-bd-nvme-error-quark, 3) INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_format_invalid_lba #### INFO: #### will start test_nvme_namespace_format_invalid_secure_erase ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:40:42 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:40:42 storageqe-109 INFO: #### END test_nvme_namespace_format_invalid_lba #### Oct 6 16:40:42 storageqe-109 INFO: #### will start test_nvme_namespace_format_invalid_secure_erase ##### Oct 6 16:40:42 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_format_invalid_secure_erase #### INFO: #### will start test_nvme_block_size_consistency_after_format ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:40:56 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:40:56 storageqe-109 INFO: #### END test_nvme_namespace_format_invalid_secure_erase #### Oct 6 16:40:56 storageqe-109 INFO: #### will start test_nvme_block_size_consistency_after_format ##### Oct 6 16:40:56 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:41:06 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 6 16:43:08 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_block_size_consistency_after_format #### INFO: #### will start test_nvme_namespace_wwn_property ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:45:15 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:45:15 storageqe-109 INFO: #### END test_nvme_block_size_consistency_after_format #### Oct 6 16:45:15 storageqe-109 INFO: #### will start test_nvme_namespace_wwn_property ##### Oct 6 16:45:15 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_wwn_property #### INFO: #### will start test_nvme_namespace_utilization ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:45:29 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:45:29 storageqe-109 INFO: #### END test_nvme_namespace_wwn_property #### Oct 6 16:45:29 storageqe-109 INFO: #### will start test_nvme_namespace_utilization ##### Oct 6 16:45:29 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:45:47 storageqe-109 kernel: XFS (nvme0n1): Mounting V5 Filesystem f83ceb3b-c7d1-42cd-8ef5-31c0723b94be Oct 6 16:45:47 storageqe-109 kernel: XFS (nvme0n1): Ending clean mount Oct 6 16:45:47 storageqe-109 udisksd[5174]: Mounted /dev/nvme0n1 at /run/media/root/f83ceb3b-c7d1-42cd-8ef5-31c0723b94be on behalf of uid 0 Oct 6 16:45:47 storageqe-109 systemd[1]: run-media-root-f83ceb3b\x2dc7d1\x2d42cd\x2d8ef5\x2d31c0723b94be.mount: Deactivated successfully. Oct 6 16:45:47 storageqe-109 kernel: XFS (nvme0n1): Unmounting Filesystem f83ceb3b-c7d1-42cd-8ef5-31c0723b94be Oct 6 16:45:47 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/f83ceb3b-c7d1-42cd-8ef5-31c0723b94be (device 259:1 is not mounted) Oct 6 16:45:47 storageqe-109 udisksd[5174]: Unmounted /dev/nvme0n1 on behalf of uid 0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_utilization #### INFO: #### will start test_luks_on_4k_nvme_namespace ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:45:54 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:45:54 storageqe-109 INFO: #### END test_nvme_namespace_utilization #### Oct 6 16:45:54 storageqe-109 INFO: #### will start test_luks_on_4k_nvme_namespace ##### Oct 6 16:45:54 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:46:02 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 6 16:48:11 storageqe-109 stratisd[4947]: [2025-10-06T20:48:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:48:11 storageqe-109 stratisd[4947]: [2025-10-06T20:48:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:48:13 storageqe-109 stratisd[4947]: [2025-10-06T20:48:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:48:13 storageqe-109 stratisd[4947]: [2025-10-06T20:48:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 16:48:17 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:48:17 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 16:48:17 storageqe-109 udisksd[5174]: Locked device /dev/nvme0n1 (was unlocked as /dev/dm-3) Oct 6 16:48:18 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_on_4k_nvme_namespace #### INFO: #### will start test_nvme_namespace_format_on_mounted_device ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:50:24 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:50:24 storageqe-109 INFO: #### END test_luks_on_4k_nvme_namespace #### Oct 6 16:50:24 storageqe-109 INFO: #### will start test_nvme_namespace_format_on_mounted_device ##### Oct 6 16:50:24 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:50:37 storageqe-109 kernel: XFS (nvme0n1): Mounting V5 Filesystem 9bb5a545-7934-4874-a2ae-ae48a68d952a Oct 6 16:50:37 storageqe-109 kernel: XFS (nvme0n1): Ending clean mount Oct 6 16:50:37 storageqe-109 udisksd[5174]: Mounted /dev/nvme0n1 at /run/media/root/9bb5a545-7934-4874-a2ae-ae48a68d952a on behalf of uid 0 Oct 6 16:50:37 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 6 16:50:38 storageqe-109 udisksd[5174]: Error re-reading partition table (BLKRRPART ioctl) on /dev/nvme0n1: Device or resource busy Oct 6 16:50:39 storageqe-109 systemd[1]: run-media-root-9bb5a545\x2d7934\x2d4874\x2da2ae\x2dae48a68d952a.mount: Deactivated successfully. Oct 6 16:50:40 storageqe-109 kernel: XFS (nvme0n1): Unmounting Filesystem 9bb5a545-7934-4874-a2ae-ae48a68d952a Oct 6 16:50:40 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/9bb5a545-7934-4874-a2ae-ae48a68d952a (device 259:1 is not mounted) Oct 6 16:50:40 storageqe-109 udisksd[5174]: Unmounted /dev/nvme0n1 on behalf of uid 0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_format_on_mounted_device #### INFO: #### will start test_nvme_namespace_format_with_metadata ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:50:46 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:50:46 storageqe-109 INFO: #### END test_nvme_namespace_format_on_mounted_device #### Oct 6 16:50:46 storageqe-109 INFO: #### will start test_nvme_namespace_format_with_metadata ##### Oct 6 16:50:46 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:50:54 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 6 16:52:56 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_format_with_metadata #### INFO: #### will start test_nvme_namespace_format_with_extra_options ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:55:02 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:55:02 storageqe-109 INFO: #### END test_nvme_namespace_format_with_metadata #### Oct 6 16:55:02 storageqe-109 INFO: #### will start test_nvme_namespace_format_with_extra_options ##### Oct 6 16:55:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:55:09 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 6 16:57:11 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_nvme_namespace_format_with_extra_options #### INFO: #### will start test_lvm_on_nvme_namespace ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:59:18 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:59:18 storageqe-109 INFO: #### END test_nvme_namespace_format_with_extra_options #### Oct 6 16:59:18 storageqe-109 INFO: #### will start test_lvm_on_nvme_namespace ##### Oct 6 16:59:18 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lvm_on_nvme_namespace #### INFO: #### will start test_concurrent_error_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:59:45 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:59:45 storageqe-109 INFO: #### END test_lvm_on_nvme_namespace #### Oct 6 16:59:45 storageqe-109 INFO: #### will start test_concurrent_error_handling ##### Oct 6 16:59:45 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_error_handling #### INFO: #### will start test_resource_exhaustion_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:59:55 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 16:59:55 storageqe-109 INFO: #### END test_concurrent_error_handling #### Oct 6 16:59:55 storageqe-109 INFO: #### will start test_resource_exhaustion_recovery ##### Oct 6 16:59:55 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:00:01 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:00:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/resource_0.img) Oct 6 17:00:01 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:00:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/resource_1.img) Oct 6 17:00:01 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:00:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/resource_2.img) Oct 6 17:00:02 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 17:00:02 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/resource_3.img) Oct 6 17:00:02 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 6 17:00:02 storageqe-109 udisksd[5174]: Set up loop device /dev/loop4 (backed by /home/resource_4.img) Oct 6 17:00:03 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 6 17:00:03 storageqe-109 udisksd[5174]: Set up loop device /dev/loop5 (backed by /home/resource_5.img) Oct 6 17:00:03 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 6 17:00:03 storageqe-109 udisksd[5174]: Set up loop device /dev/loop6 (backed by /home/resource_6.img) Oct 6 17:00:03 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 6 17:00:04 storageqe-109 udisksd[5174]: Set up loop device /dev/loop7 (backed by /home/resource_7.img) Oct 6 17:00:04 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 6 17:00:04 storageqe-109 udisksd[5174]: Set up loop device /dev/loop8 (backed by /home/resource_8.img) Oct 6 17:00:05 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 6 17:00:05 storageqe-109 udisksd[5174]: Set up loop device /dev/loop9 (backed by /home/resource_9.img) Oct 6 17:00:06 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 6 17:00:06 storageqe-109 udisksd[5174]: Set up loop device /dev/loop10 (backed by /home/resource_10.img) Oct 6 17:00:07 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 6 17:00:07 storageqe-109 udisksd[5174]: Set up loop device /dev/loop11 (backed by /home/resource_11.img) Oct 6 17:00:08 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 6 17:00:08 storageqe-109 udisksd[5174]: Set up loop device /dev/loop12 (backed by /home/resource_12.img) Oct 6 17:00:09 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 6 17:00:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop13 (backed by /home/resource_13.img) Oct 6 17:00:10 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 6 17:00:10 storageqe-109 udisksd[5174]: Set up loop device /dev/loop14 (backed by /home/resource_14.img) Oct 6 17:00:11 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 6 17:00:11 storageqe-109 udisksd[5174]: Set up loop device /dev/loop15 (backed by /home/resource_15.img) Oct 6 17:00:12 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 6 17:00:12 storageqe-109 udisksd[5174]: Set up loop device /dev/loop16 (backed by /home/resource_16.img) Oct 6 17:00:13 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 6 17:00:13 storageqe-109 udisksd[5174]: Set up loop device /dev/loop17 (backed by /home/resource_17.img) Oct 6 17:00:14 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 6 17:00:14 storageqe-109 udisksd[5174]: Set up loop device /dev/loop18 (backed by /home/resource_18.img) Oct 6 17:00:15 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 6 17:00:15 storageqe-109 udisksd[5174]: Set up loop device /dev/loop19 (backed by /home/resource_19.img) Oct 6 17:00:16 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 6 17:00:16 storageqe-109 udisksd[5174]: Set up loop device /dev/loop20 (backed by /home/resource_20.img) Oct 6 17:00:17 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 6 17:00:17 storageqe-109 udisksd[5174]: Set up loop device /dev/loop21 (backed by /home/resource_21.img) Oct 6 17:00:18 storageqe-109 kernel: loop22: detected capacity change from 0 to 2097152 Oct 6 17:00:18 storageqe-109 udisksd[5174]: Set up loop device /dev/loop22 (backed by /home/resource_22.img) Oct 6 17:00:19 storageqe-109 kernel: loop23: detected capacity change from 0 to 2097152 Oct 6 17:00:19 storageqe-109 udisksd[5174]: Set up loop device /dev/loop23 (backed by /home/resource_23.img) Oct 6 17:00:19 storageqe-109 kernel: loop24: detected capacity change from 0 to 2097152 Oct 6 17:00:19 storageqe-109 udisksd[5174]: Set up loop device /dev/loop24 (backed by /home/resource_24.img) Oct 6 17:00:20 storageqe-109 kernel: loop25: detected capacity change from 0 to 2097152 Oct 6 17:00:20 storageqe-109 udisksd[5174]: Set up loop device /dev/loop25 (backed by /home/resource_25.img) Oct 6 17:00:21 storageqe-109 kernel: loop26: detected capacity change from 0 to 2097152 Oct 6 17:00:21 storageqe-109 udisksd[5174]: Set up loop device /dev/loop26 (backed by /home/resource_26.img) Oct 6 17:00:22 storageqe-109 kernel: loop27: detected capacity change from 0 to 2097152 Oct 6 17:00:22 storageqe-109 udisksd[5174]: Set up loop device /dev/loop27 (backed by /home/resource_27.img) Oct 6 17:00:23 storageqe-109 kernel: loop28: detected capacity change from 0 to 2097152 Oct 6 17:00:23 storageqe-109 udisksd[5174]: Set up loop device /dev/loop28 (backed by /home/resource_28.img) Oct 6 17:00:24 storageqe-109 kernel: loop29: detected capacity change from 0 to 2097152 Oct 6 17:00:24 storageqe-109 udisksd[5174]: Set up loop device /dev/loop29 (backed by /home/resource_29.img) Oct 6 17:00:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/resource_0.img) Oct 6 17:00:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:00:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/resource_1.img) Oct 6 17:00:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:00:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/resource_2.img) Oct 6 17:00:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:00:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/resource_3.img) Oct 6 17:00:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 17:00:24 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop4 (was backed by /home/resource_4.img) Oct 6 17:00:24 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop4 Oct 6 17:00:25 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/recovery.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop5 (was backed by /home/resource_5.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop5 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop6 (was backed by /home/resource_6.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop6 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop7 (was backed by /home/resource_7.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop7 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop8 (was backed by /home/resource_8.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop8 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop9 (was backed by /home/resource_9.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop9 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop10 (was backed by /home/resource_10.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop10 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop11 (was backed by /home/resource_11.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop11 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop12 (was backed by /home/resource_12.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop12 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop13 (was backed by /home/resource_13.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop13 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop14 (was backed by /home/resource_14.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop14 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop15 (was backed by /home/resource_15.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop15 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop16 (was backed by /home/resource_16.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop16 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop17 (was backed by /home/resource_17.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop17 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop18 (was backed by /home/resource_18.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop18 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop19 (was backed by /home/resource_19.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop19 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop20 (was backed by /home/resource_20.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop20 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop21 (was backed by /home/resource_21.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop21 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop22 (was backed by /home/resource_22.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop22 Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop23 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop23 (was backed by /home/resource_23.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop24 (was backed by /home/resource_24.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop24 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop25 (was backed by /home/resource_25.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop25 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop26 (was backed by /home/resource_26.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop26 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop27 (was backed by /home/resource_27.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop27 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop28 (was backed by /home/resource_28.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop28 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop29 (was backed by /home/resource_29.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop29 Oct 6 17:00:25 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/recovery.img) Oct 6 17:00:25 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_resource_exhaustion_recovery #### INFO: #### will start test_interrupted_operation_recovery ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:00:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:00:30 storageqe-109 INFO: #### END test_resource_exhaustion_recovery #### Oct 6 17:00:30 storageqe-109 INFO: #### will start test_interrupted_operation_recovery ##### Oct 6 17:00:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:00:36 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:00:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/interrupt_test.img) Oct 6 17:00:36 storageqe-109 kernel: loop0: Oct 6 17:00:44 storageqe-109 kernel: loop0: Oct 6 17:00:44 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/interrupt_test.img) Oct 6 17:00:44 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_interrupted_operation_recovery #### INFO: #### will start test_cascading_error_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:00:49 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:00:49 storageqe-109 INFO: #### END test_interrupted_operation_recovery #### Oct 6 17:00:49 storageqe-109 INFO: #### will start test_cascading_error_handling ##### Oct 6 17:00:49 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:00:54 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:00:54 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/cascade_test.img) Oct 6 17:00:54 storageqe-109 kernel: loop0: Oct 6 17:01:00 storageqe-109 kernel: loop0: Oct 6 17:01:00 storageqe-109 kernel: loop0: Oct 6 17:01:06 storageqe-109 kernel: loop0: Oct 6 17:01:06 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/cascade_test.img) Oct 6 17:01:06 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_cascading_error_handling #### INFO: #### will start test_malformed_parameter_handling ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:11 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:11 storageqe-109 INFO: #### END test_cascading_error_handling #### Oct 6 17:01:11 storageqe-109 INFO: #### will start test_malformed_parameter_handling ##### Oct 6 17:01:11 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_malformed_parameter_handling #### INFO: #### will start test_dbus_error_propagation ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:21 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:21 storageqe-109 INFO: #### END test_malformed_parameter_handling #### Oct 6 17:01:21 storageqe-109 INFO: #### will start test_dbus_error_propagation ##### Oct 6 17:01:21 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dbus_error_propagation #### INFO: #### will start test_state_consistency_after_errors ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:31 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:31 storageqe-109 INFO: #### END test_dbus_error_propagation #### Oct 6 17:01:31 storageqe-109 INFO: #### will start test_state_consistency_after_errors ##### Oct 6 17:01:31 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:36 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 6 17:01:36 storageqe-109 kernel: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:01:36 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop0': Invalid argument Oct 6 17:01:36 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:01:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/consistency_test.img) Oct 6 17:01:36 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/consistency_test.img) Oct 6 17:01:36 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_state_consistency_after_errors #### INFO: #### will start test_error_handling_under_load ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:41 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:41 storageqe-109 INFO: #### END test_state_consistency_after_errors #### Oct 6 17:01:41 storageqe-109 INFO: #### will start test_error_handling_under_load ##### Oct 6 17:01:41 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_error_handling_under_load #### INFO: #### will start test_basic_and_id_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:52 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:01:52 storageqe-109 INFO: #### END test_error_handling_under_load #### Oct 6 17:01:52 storageqe-109 INFO: #### will start test_basic_and_id_properties ##### Oct 6 17:01:52 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: Testing on real device(s): ['/dev/nvme0n1'] Oct 6 17:01:57 storageqe-109 INFO: Testing on real device(s): ['/dev/nvme0n1'] INFO: Wiping device /dev/nvme0n1 after test. Oct 6 17:02:01 storageqe-109 INFO: Wiping device /dev/nvme0n1 after test. INFO: Released device(s) ['/dev/nvme0n1'] back to the pool. Oct 6 17:02:03 storageqe-109 INFO: Released device(s) ['/dev/nvme0n1'] back to the pool. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_basic_and_id_properties #### INFO: #### will start test_hint_and_misc_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 6 17:02:08 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 6 17:02:08 storageqe-109 INFO: #### END test_basic_and_id_properties #### Oct 6 17:02:08 storageqe-109 INFO: #### will start test_hint_and_misc_properties ##### Oct 6 17:02:09 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Testing on real device(s): ['/dev/sdb'] Oct 6 17:02:14 storageqe-109 INFO: Testing on real device(s): ['/dev/sdb'] INFO: Wiping device /dev/sdb after test. Oct 6 17:02:19 storageqe-109 INFO: Wiping device /dev/sdb after test. INFO: Released device(s) ['/dev/sdb'] back to the pool. Oct 6 17:02:21 storageqe-109 INFO: Released device(s) ['/dev/sdb'] back to the pool. INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_hint_and_misc_properties #### INFO: #### will start test_crypto_backing_device_property ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 6 17:02:26 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 6 17:02:26 storageqe-109 INFO: #### END test_hint_and_misc_properties #### Oct 6 17:02:26 storageqe-109 INFO: #### will start test_crypto_backing_device_property ##### Oct 6 17:02:26 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: Testing on real device(s): ['/dev/sdc'] Oct 6 17:02:31 storageqe-109 INFO: Testing on real device(s): ['/dev/sdc'] Oct 6 17:02:38 storageqe-109 stratisd[4947]: [2025-10-06T21:02:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 17:02:38 storageqe-109 stratisd[4947]: [2025-10-06T21:02:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 17:02:41 storageqe-109 stratisd[4947]: [2025-10-06T21:02:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 6 17:02:41 storageqe-109 stratisd[4947]: [2025-10-06T21:02:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: Wiping device /dev/sdc after test. Oct 6 17:02:45 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 17:02:45 storageqe-109 udisksd[5174]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 6 17:02:45 storageqe-109 udisksd[5174]: Locked device /dev/sdc (was unlocked as /dev/dm-3) Oct 6 17:02:45 storageqe-109 INFO: Wiping device /dev/sdc after test. INFO: Released device(s) ['/dev/sdc'] back to the pool. Oct 6 17:02:47 storageqe-109 INFO: Released device(s) ['/dev/sdc'] back to the pool. INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_crypto_backing_device_property #### INFO: #### will start test_mdraid_related_properties ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:02:52 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:02:52 storageqe-109 INFO: #### END test_crypto_backing_device_property #### Oct 6 17:02:52 storageqe-109 INFO: #### will start test_mdraid_related_properties ##### Oct 6 17:02:52 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:02:58 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:02:58 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_md_member_0.img) Oct 6 17:02:58 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_raid_props INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version None Oct 6 17:02:58 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_md_member_1.img) Oct 6 17:02:58 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 17:02:58 storageqe-109 INFO: raid level raid1 Oct 6 17:02:58 storageqe-109 INFO: raid name test_raid_props Oct 6 17:02:58 storageqe-109 INFO: raid chunk 0 Oct 6 17:02:58 storageqe-109 INFO: raid bitmap None Oct 6 17:02:58 storageqe-109 INFO: raid version None Oct 6 17:02:58 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 17:02:58 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 17:02:58 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 17:02:58 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 17:02:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:02:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:02:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:03:04 storageqe-109 kernel: md: md127: resync done. Oct 6 17:03:11 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 17:03:11 storageqe-109 kernel: md: md127 stopped. Oct 6 17:03:11 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 17:03:14 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_member_0.img) Oct 6 17:03:14 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:03:14 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_member_1.img) Oct 6 17:03:14 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_mdraid_related_properties #### INFO: #### will start test_drive_properties_and_methods ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:19 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:19 storageqe-109 INFO: #### END test_mdraid_related_properties #### Oct 6 17:03:19 storageqe-109 INFO: #### will start test_drive_properties_and_methods ##### Oct 6 17:03:19 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_drive_properties_and_methods #### INFO: #### will start test_drive_ata_properties_and_methods ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:30 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:30 storageqe-109 INFO: #### END test_drive_properties_and_methods #### Oct 6 17:03:30 storageqe-109 INFO: #### will start test_drive_ata_properties_and_methods ##### Oct 6 17:03:30 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_drive_ata_properties_and_methods #### INFO: #### will start test_invalid_device_path_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:40 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:40 storageqe-109 INFO: #### END test_drive_ata_properties_and_methods #### Oct 6 17:03:40 storageqe-109 INFO: #### will start test_invalid_device_path_handling ##### Oct 6 17:03:40 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:45 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:03:45 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/nonexistent_file.img) Oct 6 17:03:45 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/nonexistent_file.img) Oct 6 17:03:45 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: start Cleaning up error handling test: test_invalid_device_path_handling INFO: start Cleaning _cleanup_automounts Oct 6 17:03:46 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:03:46 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/file_that_does_not_exist) Oct 6 17:03:46 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/file_that_does_not_exist) Oct 6 17:03:46 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:03:46 storageqe-109 journal: Oct 6 17:03:46 storageqe-109 INFO: start Cleaning up error handling test: test_invalid_device_path_handling Oct 6 17:03:46 storageqe-109 journal: Oct 6 17:03:46 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_invalid_device_path_handling #### INFO: #### will start test_permission_denied_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:51 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:03:51 storageqe-109 INFO: #### END test_invalid_device_path_handling #### Oct 6 17:03:51 storageqe-109 INFO: #### will start test_permission_denied_handling ##### Oct 6 17:03:51 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: start Cleaning up error handling test: test_permission_denied_handling INFO: start Cleaning _cleanup_automounts Oct 6 17:03:56 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:03:56 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /tmp/udisks2_error_test_y4h47xtk/error_test_permission_test.img) Oct 6 17:03:56 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks2_error_test_y4h47xtk/error_test_permission_test.img) Oct 6 17:03:56 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:03:56 storageqe-109 journal: Oct 6 17:03:56 storageqe-109 INFO: start Cleaning up error handling test: test_permission_denied_handling Oct 6 17:03:56 storageqe-109 journal: Oct 6 17:03:56 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_permission_denied_handling #### INFO: #### will start test_insufficient_space_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:04:01 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:04:01 storageqe-109 INFO: #### END test_permission_denied_handling #### Oct 6 17:04:01 storageqe-109 INFO: #### will start test_insufficient_space_handling ##### Oct 6 17:04:01 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: start Cleaning up error handling test: test_insufficient_space_handling INFO: start Cleaning _cleanup_automounts Oct 6 17:04:59 storageqe-109 journal: Oct 6 17:04:59 storageqe-109 INFO: start Cleaning up error handling test: test_insufficient_space_handling Oct 6 17:04:59 storageqe-109 journal: Oct 6 17:04:59 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_insufficient_space_handling #### INFO: #### will start test_corrupted_filesystem_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:04 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:05 storageqe-109 INFO: #### END test_insufficient_space_handling #### Oct 6 17:05:05 storageqe-109 INFO: #### will start test_corrupted_filesystem_handling ##### Oct 6 17:05:05 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:10 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:05:10 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/error_test_corrupted_fs.img) Oct 6 17:05:10 storageqe-109 kernel: loop0: INFO: start Cleaning up error handling test: test_corrupted_filesystem_handling INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 6 17:05:11 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem 77190f0c-d85d-40bd-95cd-3c313960d770 r/w with ordered data mode. Quota mode: none. Oct 6 17:05:11 storageqe-109 udisksd[5174]: Mounted /dev/loop0p1 at /run/media/root/77190f0c-d85d-40bd-95cd-3c313960d770 on behalf of uid 0 Oct 6 17:05:11 storageqe-109 journal: Oct 6 17:05:11 storageqe-109 INFO: start Cleaning up error handling test: test_corrupted_filesystem_handling Oct 6 17:05:11 storageqe-109 journal: Oct 6 17:05:11 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 6 17:05:11 storageqe-109 journal: Oct 6 17:05:11 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 6 17:05:11 storageqe-109 systemd[1]: run-media-root-77190f0c\x2dd85d\x2d40bd\x2d95cd\x2d3c313960d770.mount: Deactivated successfully. Oct 6 17:05:11 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/77190f0c-d85d-40bd-95cd-3c313960d770 (device 259:2 is not mounted) Oct 6 17:05:11 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem 77190f0c-d85d-40bd-95cd-3c313960d770. Oct 6 17:05:11 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/error_test_corrupted_fs.img) Oct 6 17:05:11 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_corrupted_filesystem_handling #### INFO: #### will start test_device_busy_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:16 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:16 storageqe-109 INFO: #### END test_corrupted_filesystem_handling #### Oct 6 17:05:16 storageqe-109 INFO: #### will start test_device_busy_handling ##### Oct 6 17:05:16 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:21 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:05:21 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/error_test_device_busy.img) Oct 6 17:05:21 storageqe-109 kernel: loop0: Oct 6 17:05:22 storageqe-109 udisksd[5174]: Mounted /dev/loop0p1 at /run/media/root/93cc861d-ada4-43b3-9516-c2eb440b4995 on behalf of uid 0 Oct 6 17:05:22 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem 93cc861d-ada4-43b3-9516-c2eb440b4995 r/w with ordered data mode. Quota mode: none. INFO: start Cleaning up error handling test: test_device_busy_handling INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 6 17:05:27 storageqe-109 udisksd[5174]: [fdisk] Failed to remove partition 1 from system Oct 6 17:05:27 storageqe-109 journal: Oct 6 17:05:27 storageqe-109 INFO: start Cleaning up error handling test: test_device_busy_handling Oct 6 17:05:27 storageqe-109 journal: Oct 6 17:05:27 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 6 17:05:27 storageqe-109 journal: Oct 6 17:05:27 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 6 17:05:27 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/93cc861d-ada4-43b3-9516-c2eb440b4995 (device 259:2 is not mounted) Oct 6 17:05:27 storageqe-109 systemd[1]: run-media-root-93cc861d\x2dada4\x2d43b3\x2d9516\x2dc2eb440b4995.mount: Deactivated successfully. Oct 6 17:05:27 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem 93cc861d-ada4-43b3-9516-c2eb440b4995. Oct 6 17:05:27 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/error_test_device_busy.img) Oct 6 17:05:27 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_device_busy_handling #### INFO: #### will start test_invalid_parameters_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:32 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:32 storageqe-109 INFO: #### END test_device_busy_handling #### Oct 6 17:05:32 storageqe-109 INFO: #### will start test_invalid_parameters_handling ##### Oct 6 17:05:32 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: start Cleaning up error handling test: test_invalid_parameters_handling INFO: start Cleaning _cleanup_automounts Oct 6 17:05:37 storageqe-109 journal: Oct 6 17:05:37 storageqe-109 INFO: start Cleaning up error handling test: test_invalid_parameters_handling Oct 6 17:05:37 storageqe-109 journal: Oct 6 17:05:37 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_invalid_parameters_handling #### INFO: #### will start test_concurrent_operation_conflicts ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:42 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:42 storageqe-109 INFO: #### END test_invalid_parameters_handling #### Oct 6 17:05:42 storageqe-109 INFO: #### will start test_concurrent_operation_conflicts ##### Oct 6 17:05:42 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:48 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:05:48 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/error_test_concurrent_test.img) Oct 6 17:05:48 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:05:48 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/error_test_concurrent_test.img) Oct 6 17:05:48 storageqe-109 kernel: loop0: Oct 6 17:05:48 storageqe-109 kernel: loop1: INFO: start Cleaning up error handling test: test_concurrent_operation_conflicts INFO: start Cleaning _cleanup_automounts Oct 6 17:05:49 storageqe-109 journal: Oct 6 17:05:49 storageqe-109 INFO: start Cleaning up error handling test: test_concurrent_operation_conflicts Oct 6 17:05:49 storageqe-109 journal: Oct 6 17:05:49 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_concurrent_operation_conflicts #### INFO: #### will start test_system_resource_exhaustion ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:54 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:54 storageqe-109 INFO: #### END test_concurrent_operation_conflicts #### Oct 6 17:05:54 storageqe-109 INFO: #### will start test_system_resource_exhaustion ##### Oct 6 17:05:54 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:05:59 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:05:59 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_resource_test_0.img) Oct 6 17:06:00 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 17:06:00 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/error_test_resource_test_1.img) Oct 6 17:06:00 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 6 17:06:00 storageqe-109 udisksd[5174]: Set up loop device /dev/loop4 (backed by /home/error_test_resource_test_2.img) Oct 6 17:06:01 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 6 17:06:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop5 (backed by /home/error_test_resource_test_3.img) Oct 6 17:06:01 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 6 17:06:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop6 (backed by /home/error_test_resource_test_4.img) Oct 6 17:06:01 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 6 17:06:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop7 (backed by /home/error_test_resource_test_5.img) Oct 6 17:06:02 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 6 17:06:02 storageqe-109 udisksd[5174]: Set up loop device /dev/loop8 (backed by /home/error_test_resource_test_6.img) Oct 6 17:06:02 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 6 17:06:02 storageqe-109 udisksd[5174]: Set up loop device /dev/loop9 (backed by /home/error_test_resource_test_7.img) Oct 6 17:06:03 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 6 17:06:03 storageqe-109 udisksd[5174]: Set up loop device /dev/loop10 (backed by /home/error_test_resource_test_8.img) Oct 6 17:06:04 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 6 17:06:04 storageqe-109 udisksd[5174]: Set up loop device /dev/loop11 (backed by /home/error_test_resource_test_9.img) Oct 6 17:06:05 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 6 17:06:05 storageqe-109 udisksd[5174]: Set up loop device /dev/loop12 (backed by /home/error_test_resource_test_10.img) Oct 6 17:06:06 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 6 17:06:06 storageqe-109 udisksd[5174]: Set up loop device /dev/loop13 (backed by /home/error_test_resource_test_11.img) Oct 6 17:06:07 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 6 17:06:07 storageqe-109 udisksd[5174]: Set up loop device /dev/loop14 (backed by /home/error_test_resource_test_12.img) Oct 6 17:06:08 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 6 17:06:08 storageqe-109 udisksd[5174]: Set up loop device /dev/loop15 (backed by /home/error_test_resource_test_13.img) Oct 6 17:06:09 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 6 17:06:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop16 (backed by /home/error_test_resource_test_14.img) Oct 6 17:06:10 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 6 17:06:10 storageqe-109 udisksd[5174]: Set up loop device /dev/loop17 (backed by /home/error_test_resource_test_15.img) Oct 6 17:06:11 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 6 17:06:11 storageqe-109 udisksd[5174]: Set up loop device /dev/loop18 (backed by /home/error_test_resource_test_16.img) Oct 6 17:06:12 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 6 17:06:12 storageqe-109 udisksd[5174]: Set up loop device /dev/loop19 (backed by /home/error_test_resource_test_17.img) Oct 6 17:06:13 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 6 17:06:13 storageqe-109 udisksd[5174]: Set up loop device /dev/loop20 (backed by /home/error_test_resource_test_18.img) Oct 6 17:06:13 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 6 17:06:14 storageqe-109 udisksd[5174]: Set up loop device /dev/loop21 (backed by /home/error_test_resource_test_19.img) Oct 6 17:06:14 storageqe-109 kernel: loop22: detected capacity change from 0 to 2097152 Oct 6 17:06:14 storageqe-109 udisksd[5174]: Set up loop device /dev/loop22 (backed by /home/error_test_resource_test_20.img) Oct 6 17:06:15 storageqe-109 kernel: loop23: detected capacity change from 0 to 2097152 Oct 6 17:06:15 storageqe-109 udisksd[5174]: Set up loop device /dev/loop23 (backed by /home/error_test_resource_test_21.img) Oct 6 17:06:16 storageqe-109 kernel: loop24: detected capacity change from 0 to 2097152 Oct 6 17:06:16 storageqe-109 udisksd[5174]: Set up loop device /dev/loop24 (backed by /home/error_test_resource_test_22.img) Oct 6 17:06:17 storageqe-109 kernel: loop25: detected capacity change from 0 to 2097152 Oct 6 17:06:17 storageqe-109 udisksd[5174]: Set up loop device /dev/loop25 (backed by /home/error_test_resource_test_23.img) Oct 6 17:06:18 storageqe-109 kernel: loop26: detected capacity change from 0 to 2097152 Oct 6 17:06:18 storageqe-109 udisksd[5174]: Set up loop device /dev/loop26 (backed by /home/error_test_resource_test_24.img) Oct 6 17:06:19 storageqe-109 kernel: loop27: detected capacity change from 0 to 2097152 Oct 6 17:06:19 storageqe-109 udisksd[5174]: Set up loop device /dev/loop27 (backed by /home/error_test_resource_test_25.img) Oct 6 17:06:20 storageqe-109 kernel: loop28: detected capacity change from 0 to 2097152 Oct 6 17:06:20 storageqe-109 udisksd[5174]: Set up loop device /dev/loop28 (backed by /home/error_test_resource_test_26.img) Oct 6 17:06:21 storageqe-109 kernel: loop29: detected capacity change from 0 to 2097152 Oct 6 17:06:21 storageqe-109 udisksd[5174]: Set up loop device /dev/loop29 (backed by /home/error_test_resource_test_27.img) Oct 6 17:06:22 storageqe-109 kernel: loop30: detected capacity change from 0 to 2097152 Oct 6 17:06:22 storageqe-109 udisksd[5174]: Set up loop device /dev/loop30 (backed by /home/error_test_resource_test_28.img) Oct 6 17:06:23 storageqe-109 kernel: loop31: detected capacity change from 0 to 2097152 Oct 6 17:06:23 storageqe-109 udisksd[5174]: Set up loop device /dev/loop31 (backed by /home/error_test_resource_test_29.img) Oct 6 17:06:24 storageqe-109 kernel: loop32: detected capacity change from 0 to 2097152 Oct 6 17:06:24 storageqe-109 udisksd[5174]: Set up loop device /dev/loop32 (backed by /home/error_test_resource_test_30.img) Oct 6 17:06:25 storageqe-109 kernel: loop33: detected capacity change from 0 to 2097152 Oct 6 17:06:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop33 (backed by /home/error_test_resource_test_31.img) Oct 6 17:06:26 storageqe-109 kernel: loop34: detected capacity change from 0 to 2097152 Oct 6 17:06:26 storageqe-109 udisksd[5174]: Set up loop device /dev/loop34 (backed by /home/error_test_resource_test_32.img) Oct 6 17:06:27 storageqe-109 kernel: loop35: detected capacity change from 0 to 2097152 Oct 6 17:06:27 storageqe-109 udisksd[5174]: Set up loop device /dev/loop35 (backed by /home/error_test_resource_test_33.img) Oct 6 17:06:28 storageqe-109 kernel: loop36: detected capacity change from 0 to 2097152 Oct 6 17:06:28 storageqe-109 udisksd[5174]: Set up loop device /dev/loop36 (backed by /home/error_test_resource_test_34.img) Oct 6 17:06:29 storageqe-109 kernel: loop37: detected capacity change from 0 to 2097152 Oct 6 17:06:29 storageqe-109 udisksd[5174]: Set up loop device /dev/loop37 (backed by /home/error_test_resource_test_35.img) Oct 6 17:06:30 storageqe-109 kernel: loop38: detected capacity change from 0 to 2097152 Oct 6 17:06:30 storageqe-109 udisksd[5174]: Set up loop device /dev/loop38 (backed by /home/error_test_resource_test_36.img) Oct 6 17:06:31 storageqe-109 kernel: loop39: detected capacity change from 0 to 2097152 Oct 6 17:06:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop39 (backed by /home/error_test_resource_test_37.img) Oct 6 17:06:32 storageqe-109 kernel: loop40: detected capacity change from 0 to 2097152 Oct 6 17:06:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop40 (backed by /home/error_test_resource_test_38.img) Oct 6 17:06:32 storageqe-109 kernel: loop41: detected capacity change from 0 to 2097152 Oct 6 17:06:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop41 (backed by /home/error_test_resource_test_39.img) Oct 6 17:06:33 storageqe-109 kernel: loop42: detected capacity change from 0 to 2097152 Oct 6 17:06:33 storageqe-109 udisksd[5174]: Set up loop device /dev/loop42 (backed by /home/error_test_resource_test_40.img) Oct 6 17:06:34 storageqe-109 kernel: loop43: detected capacity change from 0 to 2097152 Oct 6 17:06:34 storageqe-109 udisksd[5174]: Set up loop device /dev/loop43 (backed by /home/error_test_resource_test_41.img) Oct 6 17:06:35 storageqe-109 kernel: loop44: detected capacity change from 0 to 2097152 Oct 6 17:06:35 storageqe-109 udisksd[5174]: Set up loop device /dev/loop44 (backed by /home/error_test_resource_test_42.img) Oct 6 17:06:36 storageqe-109 kernel: loop45: detected capacity change from 0 to 2097152 Oct 6 17:06:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop45 (backed by /home/error_test_resource_test_43.img) Oct 6 17:06:37 storageqe-109 kernel: loop46: detected capacity change from 0 to 2097152 Oct 6 17:06:37 storageqe-109 udisksd[5174]: Set up loop device /dev/loop46 (backed by /home/error_test_resource_test_44.img) Oct 6 17:06:38 storageqe-109 kernel: loop47: detected capacity change from 0 to 2097152 Oct 6 17:06:38 storageqe-109 udisksd[5174]: Set up loop device /dev/loop47 (backed by /home/error_test_resource_test_45.img) Oct 6 17:06:39 storageqe-109 kernel: loop48: detected capacity change from 0 to 2097152 Oct 6 17:06:39 storageqe-109 udisksd[5174]: Set up loop device /dev/loop48 (backed by /home/error_test_resource_test_46.img) Oct 6 17:06:40 storageqe-109 kernel: loop49: detected capacity change from 0 to 2097152 Oct 6 17:06:40 storageqe-109 udisksd[5174]: Set up loop device /dev/loop49 (backed by /home/error_test_resource_test_47.img) Oct 6 17:06:41 storageqe-109 kernel: loop50: detected capacity change from 0 to 2097152 Oct 6 17:06:41 storageqe-109 udisksd[5174]: Set up loop device /dev/loop50 (backed by /home/error_test_resource_test_48.img) Oct 6 17:06:42 storageqe-109 kernel: loop51: detected capacity change from 0 to 2097152 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Set up loop device /dev/loop51 (backed by /home/error_test_resource_test_49.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_resource_test_0.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/error_test_resource_test_1.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop4 (was backed by /home/error_test_resource_test_2.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop4 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop5 (was backed by /home/error_test_resource_test_3.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop5 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop6 (was backed by /home/error_test_resource_test_4.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop6 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop7 (was backed by /home/error_test_resource_test_5.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop7 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop8 (was backed by /home/error_test_resource_test_6.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop8 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop9 (was backed by /home/error_test_resource_test_7.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop9 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop10 (was backed by /home/error_test_resource_test_8.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop10 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop11 (was backed by /home/error_test_resource_test_9.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop11 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop12 (was backed by /home/error_test_resource_test_10.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop12 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop13 (was backed by /home/error_test_resource_test_11.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop13 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop14 (was backed by /home/error_test_resource_test_12.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop14 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop15 (was backed by /home/error_test_resource_test_13.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop15 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop16 (was backed by /home/error_test_resource_test_14.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop16 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop17 (was backed by /home/error_test_resource_test_15.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop17 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop18 (was backed by /home/error_test_resource_test_16.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop18 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop19 (was backed by /home/error_test_resource_test_17.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop19 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop20 (was backed by /home/error_test_resource_test_18.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop20 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop21 (was backed by /home/error_test_resource_test_19.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop21 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop22 (was backed by /home/error_test_resource_test_20.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop22 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop23 (was backed by /home/error_test_resource_test_21.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop23 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop24 (was backed by /home/error_test_resource_test_22.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop24 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop25 (was backed by /home/error_test_resource_test_23.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop25 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop26 (was backed by /home/error_test_resource_test_24.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop26 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop27 (was backed by /home/error_test_resource_test_25.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop27 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop28 (was backed by /home/error_test_resource_test_26.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop28 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop29 (was backed by /home/error_test_resource_test_27.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop29 INFO: start Cleaning up error handling test: test_system_resource_exhaustion INFO: start Cleaning _cleanup_automounts Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop30 (was backed by /home/error_test_resource_test_28.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop30 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop31 (was backed by /home/error_test_resource_test_29.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop31 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop32 (was backed by /home/error_test_resource_test_30.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop32 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop33 (was backed by /home/error_test_resource_test_31.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop33 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop34 (was backed by /home/error_test_resource_test_32.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop34 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop35 (was backed by /home/error_test_resource_test_33.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop35 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop36 (was backed by /home/error_test_resource_test_34.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop36 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop37 (was backed by /home/error_test_resource_test_35.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop37 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop38 (was backed by /home/error_test_resource_test_36.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop38 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop39 (was backed by /home/error_test_resource_test_37.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop39 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop40 (was backed by /home/error_test_resource_test_38.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop40 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop41 (was backed by /home/error_test_resource_test_39.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop41 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop42 (was backed by /home/error_test_resource_test_40.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop42 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop43 (was backed by /home/error_test_resource_test_41.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop43 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop44 (was backed by /home/error_test_resource_test_42.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop44 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop45 (was backed by /home/error_test_resource_test_43.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop45 Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop46 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop46 (was backed by /home/error_test_resource_test_44.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop47 (was backed by /home/error_test_resource_test_45.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop47 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop48 (was backed by /home/error_test_resource_test_46.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop48 Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop49 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop49 (was backed by /home/error_test_resource_test_47.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop50 (was backed by /home/error_test_resource_test_48.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop50 Oct 6 17:06:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop51 (was backed by /home/error_test_resource_test_49.img) Oct 6 17:06:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop51 Oct 6 17:06:42 storageqe-109 journal: Oct 6 17:06:42 storageqe-109 INFO: start Cleaning up error handling test: test_system_resource_exhaustion Oct 6 17:06:42 storageqe-109 journal: Oct 6 17:06:42 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_system_resource_exhaustion #### INFO: #### will start test_interrupted_operations_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:06:47 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:06:47 storageqe-109 INFO: #### END test_system_resource_exhaustion #### Oct 6 17:06:47 storageqe-109 INFO: #### will start test_interrupted_operations_handling ##### Oct 6 17:06:47 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:06:53 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:06:53 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_interrupt_test.img) Oct 6 17:06:53 storageqe-109 kernel: loop2: INFO: start Cleaning up error handling test: test_interrupted_operations_handling INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:06:55 storageqe-109 journal: Oct 6 17:06:55 storageqe-109 INFO: start Cleaning up error handling test: test_interrupted_operations_handling Oct 6 17:06:55 storageqe-109 journal: Oct 6 17:06:55 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 6 17:06:55 storageqe-109 journal: Oct 6 17:06:55 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:06:55 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_interrupt_test.img) Oct 6 17:06:55 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_interrupted_operations_handling #### INFO: #### will start test_malformed_dbus_messages_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:00 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:00 storageqe-109 INFO: #### END test_interrupted_operations_handling #### Oct 6 17:07:00 storageqe-109 INFO: #### will start test_malformed_dbus_messages_handling ##### Oct 6 17:07:00 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: start Cleaning up error handling test: test_malformed_dbus_messages_handling INFO: start Cleaning _cleanup_automounts Oct 6 17:07:05 storageqe-109 journal: Oct 6 17:07:05 storageqe-109 INFO: start Cleaning up error handling test: test_malformed_dbus_messages_handling Oct 6 17:07:05 storageqe-109 journal: Oct 6 17:07:05 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_malformed_dbus_messages_handling #### INFO: #### will start test_cleanup_after_errors ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:10 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:10 storageqe-109 INFO: #### END test_malformed_dbus_messages_handling #### Oct 6 17:07:10 storageqe-109 INFO: #### will start test_cleanup_after_errors ##### Oct 6 17:07:10 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:15 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:15 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_cleanup_test.img) Oct 6 17:07:15 storageqe-109 kernel: loop2: INFO: start Cleaning up error handling test: test_cleanup_after_errors INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:07:16 storageqe-109 udisksd[5174]: Mounted /dev/loop2p1 at /run/media/root/851afbd8-41a3-4206-894c-7e6143d95ce8 on behalf of uid 0 Oct 6 17:07:16 storageqe-109 kernel: EXT4-fs (loop2p1): mounted filesystem 851afbd8-41a3-4206-894c-7e6143d95ce8 r/w with ordered data mode. Quota mode: none. Oct 6 17:07:16 storageqe-109 journal: Oct 6 17:07:16 storageqe-109 INFO: start Cleaning up error handling test: test_cleanup_after_errors Oct 6 17:07:16 storageqe-109 journal: Oct 6 17:07:16 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 6 17:07:16 storageqe-109 journal: Oct 6 17:07:16 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:07:16 storageqe-109 systemd[1]: run-media-root-851afbd8\x2d41a3\x2d4206\x2d894c\x2d7e6143d95ce8.mount: Deactivated successfully. Oct 6 17:07:16 storageqe-109 udisksd[5174]: Cleaning up mount point /run/media/root/851afbd8-41a3-4206-894c-7e6143d95ce8 (device 259:3 is not mounted) Oct 6 17:07:16 storageqe-109 kernel: EXT4-fs (loop2p1): unmounting filesystem 851afbd8-41a3-4206-894c-7e6143d95ce8. Oct 6 17:07:16 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_cleanup_test.img) Oct 6 17:07:16 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_cleanup_after_errors #### INFO: #### will start test_memory_leak_detection ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:21 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:21 storageqe-109 INFO: #### END test_cleanup_after_errors #### Oct 6 17:07:21 storageqe-109 INFO: #### will start test_memory_leak_detection ##### Oct 6 17:07:21 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:26 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:26 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:26 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:26 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:27 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:27 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:27 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:27 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:27 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:27 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:27 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:27 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:28 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:28 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:28 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:28 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:28 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:28 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:28 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:28 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:29 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:29 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:29 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:29 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:29 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:29 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:29 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:29 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:29 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:29 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:29 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:29 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:30 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:30 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:30 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:30 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:30 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:30 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:30 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:30 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:31 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:31 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:31 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:31 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:31 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:31 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:31 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:31 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:31 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:32 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:32 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:32 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:32 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:32 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:32 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:33 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:33 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:33 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:33 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:33 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:33 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:33 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:33 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:34 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:34 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:34 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:34 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:34 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:34 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:34 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:34 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: start Cleaning up error handling test: test_memory_leak_detection INFO: start Cleaning _cleanup_automounts Oct 6 17:07:34 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:34 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 6 17:07:34 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 6 17:07:34 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:07:34 storageqe-109 journal: Oct 6 17:07:34 storageqe-109 INFO: start Cleaning up error handling test: test_memory_leak_detection Oct 6 17:07:34 storageqe-109 journal: Oct 6 17:07:34 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_memory_leak_detection #### INFO: #### will start test_udisks2_crash_conditions ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:39 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:39 storageqe-109 INFO: #### END test_memory_leak_detection #### Oct 6 17:07:39 storageqe-109 INFO: #### will start test_udisks2_crash_conditions ##### Oct 6 17:07:39 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:07:45 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:07:45 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_crash_test_0.img) Oct 6 17:07:46 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 17:07:46 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/error_test_crash_test_1.img) Oct 6 17:07:46 storageqe-109 kernel: loop3: Oct 6 17:07:47 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 6 17:07:47 storageqe-109 udisksd[5174]: Set up loop device /dev/loop4 (backed by /home/error_test_crash_test_2.img) Oct 6 17:07:47 storageqe-109 kernel: loop4: Oct 6 17:07:48 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 6 17:07:48 storageqe-109 udisksd[5174]: Set up loop device /dev/loop5 (backed by /home/error_test_crash_test_3.img) Oct 6 17:07:48 storageqe-109 kernel: loop5: Oct 6 17:07:49 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 6 17:07:49 storageqe-109 udisksd[5174]: Set up loop device /dev/loop6 (backed by /home/error_test_crash_test_4.img) Oct 6 17:07:49 storageqe-109 kernel: loop6: Oct 6 17:07:50 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 6 17:07:50 storageqe-109 udisksd[5174]: Set up loop device /dev/loop7 (backed by /home/error_test_crash_test_5.img) Oct 6 17:07:50 storageqe-109 kernel: loop7: Oct 6 17:07:51 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 6 17:07:51 storageqe-109 udisksd[5174]: Set up loop device /dev/loop8 (backed by /home/error_test_crash_test_6.img) Oct 6 17:07:51 storageqe-109 kernel: loop8: Oct 6 17:07:52 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 6 17:07:52 storageqe-109 udisksd[5174]: Set up loop device /dev/loop9 (backed by /home/error_test_crash_test_7.img) Oct 6 17:07:52 storageqe-109 kernel: loop9: Oct 6 17:07:53 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 6 17:07:53 storageqe-109 udisksd[5174]: Set up loop device /dev/loop10 (backed by /home/error_test_crash_test_8.img) Oct 6 17:07:53 storageqe-109 kernel: loop10: Oct 6 17:07:54 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 6 17:07:54 storageqe-109 udisksd[5174]: Set up loop device /dev/loop11 (backed by /home/error_test_crash_test_9.img) Oct 6 17:07:54 storageqe-109 kernel: loop11: Oct 6 17:07:55 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 6 17:07:55 storageqe-109 udisksd[5174]: Set up loop device /dev/loop12 (backed by /home/error_test_crash_test_10.img) Oct 6 17:07:55 storageqe-109 kernel: loop12: Oct 6 17:07:56 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 6 17:07:56 storageqe-109 udisksd[5174]: Set up loop device /dev/loop13 (backed by /home/error_test_crash_test_11.img) Oct 6 17:07:56 storageqe-109 kernel: loop13: Oct 6 17:07:58 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 6 17:07:58 storageqe-109 udisksd[5174]: Set up loop device /dev/loop14 (backed by /home/error_test_crash_test_12.img) Oct 6 17:07:58 storageqe-109 kernel: loop14: Oct 6 17:07:59 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 6 17:07:59 storageqe-109 udisksd[5174]: Set up loop device /dev/loop15 (backed by /home/error_test_crash_test_13.img) Oct 6 17:07:59 storageqe-109 kernel: loop15: Oct 6 17:08:00 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 6 17:08:00 storageqe-109 udisksd[5174]: Set up loop device /dev/loop16 (backed by /home/error_test_crash_test_14.img) Oct 6 17:08:01 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 6 17:08:01 storageqe-109 udisksd[5174]: Set up loop device /dev/loop17 (backed by /home/error_test_crash_test_15.img) Oct 6 17:08:01 storageqe-109 kernel: loop17: Oct 6 17:08:02 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 6 17:08:02 storageqe-109 udisksd[5174]: Set up loop device /dev/loop18 (backed by /home/error_test_crash_test_16.img) Oct 6 17:08:02 storageqe-109 kernel: loop18: Oct 6 17:08:03 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 6 17:08:03 storageqe-109 udisksd[5174]: Set up loop device /dev/loop19 (backed by /home/error_test_crash_test_17.img) Oct 6 17:08:03 storageqe-109 kernel: loop19: Oct 6 17:08:04 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 6 17:08:04 storageqe-109 udisksd[5174]: Set up loop device /dev/loop20 (backed by /home/error_test_crash_test_18.img) Oct 6 17:08:04 storageqe-109 kernel: loop20: Oct 6 17:08:06 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 6 17:08:06 storageqe-109 udisksd[5174]: Set up loop device /dev/loop21 (backed by /home/error_test_crash_test_19.img) Oct 6 17:08:06 storageqe-109 kernel: loop21: Oct 6 17:08:06 storageqe-109 kernel: loop22: detected capacity change from 0 to 2097152 Oct 6 17:08:06 storageqe-109 udisksd[5174]: Set up loop device /dev/loop22 (backed by /home/error_test_crash_test_20.img) Oct 6 17:08:07 storageqe-109 kernel: loop23: detected capacity change from 0 to 2097152 Oct 6 17:08:07 storageqe-109 udisksd[5174]: Set up loop device /dev/loop23 (backed by /home/error_test_crash_test_21.img) Oct 6 17:08:09 storageqe-109 kernel: loop24: detected capacity change from 0 to 2097152 Oct 6 17:08:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop24 (backed by /home/error_test_crash_test_22.img) Oct 6 17:08:09 storageqe-109 kernel: loop24: Oct 6 17:08:10 storageqe-109 kernel: loop25: detected capacity change from 0 to 2097152 Oct 6 17:08:10 storageqe-109 udisksd[5174]: Set up loop device /dev/loop25 (backed by /home/error_test_crash_test_23.img) Oct 6 17:08:10 storageqe-109 kernel: loop25: Oct 6 17:08:11 storageqe-109 kernel: loop26: detected capacity change from 0 to 2097152 Oct 6 17:08:11 storageqe-109 udisksd[5174]: Set up loop device /dev/loop26 (backed by /home/error_test_crash_test_24.img) Oct 6 17:08:11 storageqe-109 kernel: loop26: Oct 6 17:08:12 storageqe-109 kernel: loop27: detected capacity change from 0 to 2097152 Oct 6 17:08:12 storageqe-109 udisksd[5174]: Set up loop device /dev/loop27 (backed by /home/error_test_crash_test_25.img) Oct 6 17:08:12 storageqe-109 kernel: loop27: Oct 6 17:08:13 storageqe-109 kernel: loop28: detected capacity change from 0 to 2097152 Oct 6 17:08:13 storageqe-109 udisksd[5174]: Set up loop device /dev/loop28 (backed by /home/error_test_crash_test_26.img) Oct 6 17:08:13 storageqe-109 kernel: loop28: Oct 6 17:08:14 storageqe-109 kernel: loop29: detected capacity change from 0 to 2097152 Oct 6 17:08:14 storageqe-109 udisksd[5174]: Set up loop device /dev/loop29 (backed by /home/error_test_crash_test_27.img) Oct 6 17:08:14 storageqe-109 kernel: loop29: Oct 6 17:08:15 storageqe-109 kernel: loop30: detected capacity change from 0 to 2097152 Oct 6 17:08:15 storageqe-109 udisksd[5174]: Set up loop device /dev/loop30 (backed by /home/error_test_crash_test_28.img) Oct 6 17:08:15 storageqe-109 kernel: loop30: Oct 6 17:08:16 storageqe-109 kernel: loop31: detected capacity change from 0 to 2097152 Oct 6 17:08:16 storageqe-109 udisksd[5174]: Set up loop device /dev/loop31 (backed by /home/error_test_crash_test_29.img) Oct 6 17:08:16 storageqe-109 kernel: loop31: Oct 6 17:08:17 storageqe-109 kernel: loop32: detected capacity change from 0 to 2097152 Oct 6 17:08:17 storageqe-109 udisksd[5174]: Set up loop device /dev/loop32 (backed by /home/error_test_crash_test_30.img) Oct 6 17:08:17 storageqe-109 kernel: loop32: Oct 6 17:08:18 storageqe-109 kernel: loop33: detected capacity change from 0 to 2097152 Oct 6 17:08:19 storageqe-109 udisksd[5174]: Set up loop device /dev/loop33 (backed by /home/error_test_crash_test_31.img) Oct 6 17:08:19 storageqe-109 kernel: loop33: Oct 6 17:08:19 storageqe-109 kernel: loop34: detected capacity change from 0 to 2097152 Oct 6 17:08:19 storageqe-109 udisksd[5174]: Set up loop device /dev/loop34 (backed by /home/error_test_crash_test_32.img) Oct 6 17:08:19 storageqe-109 kernel: loop34: Oct 6 17:08:20 storageqe-109 kernel: loop35: detected capacity change from 0 to 2097152 Oct 6 17:08:20 storageqe-109 udisksd[5174]: Set up loop device /dev/loop35 (backed by /home/error_test_crash_test_33.img) Oct 6 17:08:20 storageqe-109 kernel: loop35: Oct 6 17:08:22 storageqe-109 kernel: loop36: detected capacity change from 0 to 2097152 Oct 6 17:08:22 storageqe-109 udisksd[5174]: Set up loop device /dev/loop36 (backed by /home/error_test_crash_test_34.img) Oct 6 17:08:22 storageqe-109 kernel: loop36: Oct 6 17:08:23 storageqe-109 kernel: loop37: detected capacity change from 0 to 2097152 Oct 6 17:08:23 storageqe-109 udisksd[5174]: Set up loop device /dev/loop37 (backed by /home/error_test_crash_test_35.img) Oct 6 17:08:23 storageqe-109 kernel: loop37: Oct 6 17:08:24 storageqe-109 kernel: loop38: detected capacity change from 0 to 2097152 Oct 6 17:08:24 storageqe-109 udisksd[5174]: Set up loop device /dev/loop38 (backed by /home/error_test_crash_test_36.img) Oct 6 17:08:24 storageqe-109 kernel: loop38: Oct 6 17:08:25 storageqe-109 kernel: loop39: detected capacity change from 0 to 2097152 Oct 6 17:08:25 storageqe-109 udisksd[5174]: Set up loop device /dev/loop39 (backed by /home/error_test_crash_test_37.img) Oct 6 17:08:25 storageqe-109 kernel: loop39: Oct 6 17:08:26 storageqe-109 kernel: loop40: detected capacity change from 0 to 2097152 Oct 6 17:08:26 storageqe-109 udisksd[5174]: Set up loop device /dev/loop40 (backed by /home/error_test_crash_test_38.img) Oct 6 17:08:26 storageqe-109 kernel: loop40: Oct 6 17:08:27 storageqe-109 kernel: loop41: detected capacity change from 0 to 2097152 Oct 6 17:08:27 storageqe-109 udisksd[5174]: Set up loop device /dev/loop41 (backed by /home/error_test_crash_test_39.img) Oct 6 17:08:27 storageqe-109 kernel: loop41: Oct 6 17:08:28 storageqe-109 kernel: loop42: detected capacity change from 0 to 2097152 Oct 6 17:08:28 storageqe-109 udisksd[5174]: Set up loop device /dev/loop42 (backed by /home/error_test_crash_test_40.img) Oct 6 17:08:28 storageqe-109 kernel: loop42: Oct 6 17:08:29 storageqe-109 kernel: loop43: detected capacity change from 0 to 2097152 Oct 6 17:08:29 storageqe-109 udisksd[5174]: Set up loop device /dev/loop43 (backed by /home/error_test_crash_test_41.img) Oct 6 17:08:29 storageqe-109 kernel: loop43: Oct 6 17:08:30 storageqe-109 kernel: loop44: detected capacity change from 0 to 2097152 Oct 6 17:08:30 storageqe-109 udisksd[5174]: Set up loop device /dev/loop44 (backed by /home/error_test_crash_test_42.img) Oct 6 17:08:30 storageqe-109 kernel: loop44: Oct 6 17:08:31 storageqe-109 kernel: loop45: detected capacity change from 0 to 2097152 Oct 6 17:08:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop45 (backed by /home/error_test_crash_test_43.img) Oct 6 17:08:31 storageqe-109 kernel: loop45: Oct 6 17:08:32 storageqe-109 kernel: loop46: detected capacity change from 0 to 2097152 Oct 6 17:08:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop46 (backed by /home/error_test_crash_test_44.img) Oct 6 17:08:32 storageqe-109 kernel: loop46: Oct 6 17:08:33 storageqe-109 kernel: loop47: detected capacity change from 0 to 2097152 Oct 6 17:08:33 storageqe-109 udisksd[5174]: Set up loop device /dev/loop47 (backed by /home/error_test_crash_test_45.img) Oct 6 17:08:33 storageqe-109 kernel: loop47: Oct 6 17:08:35 storageqe-109 kernel: loop48: detected capacity change from 0 to 2097152 Oct 6 17:08:35 storageqe-109 udisksd[5174]: Set up loop device /dev/loop48 (backed by /home/error_test_crash_test_46.img) Oct 6 17:08:35 storageqe-109 kernel: loop48: Oct 6 17:08:36 storageqe-109 kernel: loop49: detected capacity change from 0 to 2097152 Oct 6 17:08:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop49 (backed by /home/error_test_crash_test_47.img) Oct 6 17:08:36 storageqe-109 kernel: loop49: Oct 6 17:08:37 storageqe-109 kernel: loop50: detected capacity change from 0 to 2097152 Oct 6 17:08:37 storageqe-109 udisksd[5174]: Set up loop device /dev/loop50 (backed by /home/error_test_crash_test_48.img) Oct 6 17:08:37 storageqe-109 kernel: loop50: Oct 6 17:08:38 storageqe-109 kernel: loop51: detected capacity change from 0 to 2097152 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Set up loop device /dev/loop51 (backed by /home/error_test_crash_test_49.img) Oct 6 17:08:38 storageqe-109 kernel: loop51: Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_crash_test_0.img) Oct 6 17:08:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/error_test_crash_test_1.img) Oct 6 17:08:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop4 (was backed by /home/error_test_crash_test_2.img) Oct 6 17:08:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop4 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop5 (was backed by /home/error_test_crash_test_3.img) Oct 6 17:08:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop5 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop6 (was backed by /home/error_test_crash_test_4.img) Oct 6 17:08:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop6 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop7 (was backed by /home/error_test_crash_test_5.img) Oct 6 17:08:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop7 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop8 (was backed by /home/error_test_crash_test_6.img) Oct 6 17:08:38 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop8 Oct 6 17:08:38 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop9 (was backed by /home/error_test_crash_test_7.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop9 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop10 (was backed by /home/error_test_crash_test_8.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop10 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop11 (was backed by /home/error_test_crash_test_9.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop11 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop12 (was backed by /home/error_test_crash_test_10.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop12 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop13 (was backed by /home/error_test_crash_test_11.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop13 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop14 (was backed by /home/error_test_crash_test_12.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop14 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop15 (was backed by /home/error_test_crash_test_13.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop15 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop16 (was backed by /home/error_test_crash_test_14.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop16 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop17 (was backed by /home/error_test_crash_test_15.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop17 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop18 (was backed by /home/error_test_crash_test_16.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop18 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop19 (was backed by /home/error_test_crash_test_17.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop19 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop20 (was backed by /home/error_test_crash_test_18.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop20 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop21 (was backed by /home/error_test_crash_test_19.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop21 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop22 (was backed by /home/error_test_crash_test_20.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop22 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop23 (was backed by /home/error_test_crash_test_21.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop23 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop24 (was backed by /home/error_test_crash_test_22.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop24 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop25 (was backed by /home/error_test_crash_test_23.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop25 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop26 (was backed by /home/error_test_crash_test_24.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop26 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop27 (was backed by /home/error_test_crash_test_25.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop27 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop28 (was backed by /home/error_test_crash_test_26.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop28 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop29 (was backed by /home/error_test_crash_test_27.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop29 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop30 (was backed by /home/error_test_crash_test_28.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop30 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop31 (was backed by /home/error_test_crash_test_29.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop31 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop32 (was backed by /home/error_test_crash_test_30.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop32 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop33 (was backed by /home/error_test_crash_test_31.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop33 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop34 (was backed by /home/error_test_crash_test_32.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop34 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop35 (was backed by /home/error_test_crash_test_33.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop35 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop36 (was backed by /home/error_test_crash_test_34.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop36 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop37 (was backed by /home/error_test_crash_test_35.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop37 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop38 (was backed by /home/error_test_crash_test_36.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop38 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop39 (was backed by /home/error_test_crash_test_37.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop39 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop40 (was backed by /home/error_test_crash_test_38.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop40 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop41 (was backed by /home/error_test_crash_test_39.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop41 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop42 (was backed by /home/error_test_crash_test_40.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop42 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop43 (was backed by /home/error_test_crash_test_41.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop43 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop44 (was backed by /home/error_test_crash_test_42.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop44 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop45 (was backed by /home/error_test_crash_test_43.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop45 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop46 (was backed by /home/error_test_crash_test_44.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop46 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop47 (was backed by /home/error_test_crash_test_45.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop47 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop48 (was backed by /home/error_test_crash_test_46.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop48 Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop49 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop49 (was backed by /home/error_test_crash_test_47.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop50 (was backed by /home/error_test_crash_test_48.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop50 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop51 (was backed by /home/error_test_crash_test_49.img) Oct 6 17:08:39 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop51 Oct 6 17:08:39 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:08:39 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_concurrent_crash_test.img) Oct 6 17:08:39 storageqe-109 kernel: loop2: Oct 6 17:08:39 storageqe-109 kernel: loop2: Oct 6 17:08:39 storageqe-109 kernel: loop2: Oct 6 17:08:40 storageqe-109 udisksd[5174]: [fdisk] Failed to add partition 1 to system Oct 6 17:08:40 storageqe-109 kernel: loop2: Oct 6 17:08:40 storageqe-109 kernel: loop2: Oct 6 17:08:41 storageqe-109 kernel: loop2: Oct 6 17:08:45 storageqe-109 kernel: loop2: Oct 6 17:08:45 storageqe-109 kernel: loop2: Oct 6 17:08:46 storageqe-109 kernel: loop2: Oct 6 17:08:46 storageqe-109 kernel: loop2: Oct 6 17:08:47 storageqe-109 kernel: loop2: Oct 6 17:08:47 storageqe-109 kernel: loop2: Oct 6 17:08:51 storageqe-109 kernel: loop2: Oct 6 17:08:51 storageqe-109 kernel: loop2: Oct 6 17:08:52 storageqe-109 kernel: loop2: Oct 6 17:08:52 storageqe-109 kernel: loop2: Oct 6 17:08:53 storageqe-109 kernel: loop2: Oct 6 17:08:53 storageqe-109 kernel: loop2: Oct 6 17:08:57 storageqe-109 kernel: loop2: Oct 6 17:08:57 storageqe-109 kernel: loop2: Oct 6 17:08:58 storageqe-109 kernel: loop2: Oct 6 17:08:58 storageqe-109 kernel: loop2: Oct 6 17:08:58 storageqe-109 kernel: loop2: Oct 6 17:08:58 storageqe-109 kernel: loop2: Oct 6 17:09:03 storageqe-109 kernel: loop2: Oct 6 17:09:03 storageqe-109 kernel: loop2: Oct 6 17:09:03 storageqe-109 kernel: loop2: Oct 6 17:09:04 storageqe-109 kernel: loop2: Oct 6 17:09:04 storageqe-109 kernel: loop2: Oct 6 17:09:04 storageqe-109 kernel: loop2: Oct 6 17:09:08 storageqe-109 kernel: loop2: Oct 6 17:09:08 storageqe-109 kernel: loop2: Oct 6 17:09:09 storageqe-109 kernel: loop2: Oct 6 17:09:09 storageqe-109 kernel: loop2: Oct 6 17:09:10 storageqe-109 kernel: loop2: Oct 6 17:09:10 storageqe-109 kernel: loop2: Oct 6 17:09:14 storageqe-109 kernel: loop2: Oct 6 17:09:14 storageqe-109 kernel: loop2: Oct 6 17:09:15 storageqe-109 kernel: loop2: Oct 6 17:09:15 storageqe-109 kernel: loop2: Oct 6 17:09:15 storageqe-109 kernel: loop2: Oct 6 17:09:15 storageqe-109 kernel: loop2: Oct 6 17:09:20 storageqe-109 kernel: loop2: Oct 6 17:09:20 storageqe-109 kernel: loop2: Oct 6 17:09:20 storageqe-109 kernel: loop2: Oct 6 17:09:20 storageqe-109 kernel: loop2: Oct 6 17:09:21 storageqe-109 kernel: loop2: Oct 6 17:09:21 storageqe-109 kernel: loop2: Oct 6 17:09:25 storageqe-109 kernel: loop2: Oct 6 17:09:26 storageqe-109 kernel: loop2: Oct 6 17:09:26 storageqe-109 kernel: loop2: Oct 6 17:09:26 storageqe-109 kernel: loop2: Oct 6 17:09:27 storageqe-109 kernel: loop2: Oct 6 17:09:36 storageqe-109 kernel: loop2: Oct 6 17:09:37 storageqe-109 kernel: loop2: Oct 6 17:09:40 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 17:09:40 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/error_test_invalid_params_test.img) Oct 6 17:09:40 storageqe-109 kernel: loop2: INFO: start Cleaning up error handling test: test_udisks2_crash_conditions INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop3 Oct 6 17:09:40 storageqe-109 kernel: loop2: Oct 6 17:09:40 storageqe-109 journal: Oct 6 17:09:40 storageqe-109 INFO: start Cleaning up error handling test: test_udisks2_crash_conditions Oct 6 17:09:40 storageqe-109 journal: Oct 6 17:09:40 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 6 17:09:40 storageqe-109 journal: Oct 6 17:09:40 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:09:40 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_concurrent_crash_test.img) Oct 6 17:09:40 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:09:40 storageqe-109 journal: Oct 6 17:09:40 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop3 Oct 6 17:09:40 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/error_test_invalid_params_test.img) Oct 6 17:09:40 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_udisks2_crash_conditions #### INFO: #### will start test_force_udisks2_crash ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:09:45 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:09:45 storageqe-109 INFO: #### END test_udisks2_crash_conditions #### Oct 6 17:09:45 storageqe-109 INFO: #### will start test_force_udisks2_crash ##### Oct 6 17:09:45 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:09:50 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:09:50 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_force_crash.img) Oct 6 17:09:50 storageqe-109 kernel: loop2: Oct 6 17:09:50 storageqe-109 kernel: loop2: Oct 6 17:09:50 storageqe-109 kernel: loop2: Oct 6 17:09:50 storageqe-109 kernel: loop2: Oct 6 17:09:51 storageqe-109 udisksd[5174]: [fdisk] Failed to add partition 1 to system Oct 6 17:09:51 storageqe-109 kernel: loop2: p1 Oct 6 17:10:11 storageqe-109 udisksd[5174]: Error synchronizing after initial wipe: Timed out waiting for object Oct 6 17:10:11 storageqe-109 kernel: loop2: Oct 6 17:10:11 storageqe-109 kernel: loop2: Oct 6 17:10:12 storageqe-109 kernel: loop2: Oct 6 17:10:12 storageqe-109 kernel: loop2: Oct 6 17:10:12 storageqe-109 kernel: loop2: Oct 6 17:10:12 storageqe-109 kernel: loop2: Oct 6 17:10:12 storageqe-109 kernel: loop2: Oct 6 17:10:13 storageqe-109 kernel: loop2: Oct 6 17:10:13 storageqe-109 kernel: loop2: Oct 6 17:10:14 storageqe-109 kernel: loop2: Oct 6 17:10:16 storageqe-109 kernel: loop2: Oct 6 17:10:16 storageqe-109 kernel: loop2: Oct 6 17:10:17 storageqe-109 kernel: loop2: Oct 6 17:10:17 storageqe-109 kernel: loop2: Oct 6 17:10:18 storageqe-109 kernel: loop2: Oct 6 17:10:18 storageqe-109 kernel: loop2: Oct 6 17:10:19 storageqe-109 kernel: loop2: Oct 6 17:10:19 storageqe-109 kernel: loop2: Oct 6 17:10:20 storageqe-109 kernel: loop2: Oct 6 17:10:20 storageqe-109 kernel: loop2: Oct 6 17:10:22 storageqe-109 kernel: loop2: Oct 6 17:10:22 storageqe-109 kernel: loop2: Oct 6 17:10:23 storageqe-109 kernel: loop2: Oct 6 17:10:23 storageqe-109 kernel: loop2: Oct 6 17:10:24 storageqe-109 kernel: loop2: Oct 6 17:10:24 storageqe-109 kernel: loop2: Oct 6 17:10:25 storageqe-109 kernel: loop2: Oct 6 17:10:25 storageqe-109 kernel: loop2: Oct 6 17:10:26 storageqe-109 kernel: loop2: Oct 6 17:10:26 storageqe-109 kernel: loop2: Oct 6 17:10:28 storageqe-109 kernel: loop2: Oct 6 17:10:28 storageqe-109 kernel: loop2: Oct 6 17:10:29 storageqe-109 kernel: loop2: Oct 6 17:10:29 storageqe-109 kernel: loop2: Oct 6 17:10:29 storageqe-109 kernel: loop2: Oct 6 17:10:29 storageqe-109 kernel: loop2: Oct 6 17:10:31 storageqe-109 kernel: loop2: Oct 6 17:10:31 storageqe-109 kernel: loop2: Oct 6 17:10:31 storageqe-109 kernel: loop2: Oct 6 17:10:31 storageqe-109 kernel: loop2: Oct 6 17:10:34 storageqe-109 kernel: loop2: Oct 6 17:10:34 storageqe-109 kernel: loop2: Oct 6 17:10:34 storageqe-109 kernel: loop2: Oct 6 17:10:34 storageqe-109 kernel: loop2: Oct 6 17:10:35 storageqe-109 kernel: loop2: Oct 6 17:10:35 storageqe-109 kernel: loop2: Oct 6 17:10:36 storageqe-109 kernel: loop2: Oct 6 17:10:36 storageqe-109 kernel: loop2: Oct 6 17:10:37 storageqe-109 kernel: loop2: Oct 6 17:10:37 storageqe-109 kernel: loop2: Oct 6 17:10:39 storageqe-109 kernel: loop2: Oct 6 17:10:39 storageqe-109 kernel: loop2: Oct 6 17:10:40 storageqe-109 kernel: loop2: Oct 6 17:10:40 storageqe-109 kernel: loop2: Oct 6 17:10:41 storageqe-109 kernel: loop2: Oct 6 17:10:41 storageqe-109 kernel: loop2: Oct 6 17:10:42 storageqe-109 kernel: loop2: Oct 6 17:10:42 storageqe-109 kernel: loop2: Oct 6 17:10:42 storageqe-109 kernel: loop2: Oct 6 17:10:42 storageqe-109 kernel: loop2: Oct 6 17:10:45 storageqe-109 kernel: loop2: Oct 6 17:10:45 storageqe-109 kernel: loop2: Oct 6 17:10:46 storageqe-109 kernel: loop2: Oct 6 17:10:46 storageqe-109 kernel: loop2: Oct 6 17:10:46 storageqe-109 kernel: loop2: Oct 6 17:10:46 storageqe-109 kernel: loop2: Oct 6 17:10:47 storageqe-109 kernel: loop2: Oct 6 17:10:47 storageqe-109 kernel: loop2: Oct 6 17:10:48 storageqe-109 kernel: loop2: Oct 6 17:10:48 storageqe-109 kernel: loop2: Oct 6 17:10:51 storageqe-109 kernel: loop2: Oct 6 17:10:51 storageqe-109 kernel: loop2: Oct 6 17:10:51 storageqe-109 kernel: loop2: Oct 6 17:10:51 storageqe-109 kernel: loop2: Oct 6 17:10:52 storageqe-109 kernel: loop2: Oct 6 17:10:52 storageqe-109 kernel: loop2: Oct 6 17:10:53 storageqe-109 kernel: loop2: Oct 6 17:10:53 storageqe-109 kernel: loop2: Oct 6 17:10:54 storageqe-109 kernel: loop2: Oct 6 17:10:56 storageqe-109 kernel: loop2: Oct 6 17:10:57 storageqe-109 kernel: loop2: Oct 6 17:10:57 storageqe-109 kernel: loop2: Oct 6 17:10:57 storageqe-109 kernel: loop2: Oct 6 17:10:58 storageqe-109 kernel: loop2: Oct 6 17:10:58 storageqe-109 kernel: loop2: Oct 6 17:10:59 storageqe-109 kernel: loop2: Oct 6 17:10:59 storageqe-109 kernel: loop2: Oct 6 17:11:00 storageqe-109 kernel: loop2: Oct 6 17:11:00 storageqe-109 kernel: loop2: Oct 6 17:11:02 storageqe-109 kernel: loop2: Oct 6 17:11:02 storageqe-109 kernel: loop2: Oct 6 17:11:03 storageqe-109 kernel: loop2: Oct 6 17:11:03 storageqe-109 kernel: loop2: Oct 6 17:11:04 storageqe-109 kernel: loop2: Oct 6 17:11:04 storageqe-109 kernel: loop2: Oct 6 17:11:04 storageqe-109 kernel: loop2: Oct 6 17:11:04 storageqe-109 kernel: loop2: Oct 6 17:11:05 storageqe-109 kernel: loop2: Oct 6 17:11:05 storageqe-109 kernel: loop2: Oct 6 17:11:08 storageqe-109 kernel: loop2: Oct 6 17:11:08 storageqe-109 kernel: loop2: Oct 6 17:11:09 storageqe-109 kernel: loop2: Oct 6 17:11:09 storageqe-109 kernel: loop2: Oct 6 17:11:09 storageqe-109 kernel: loop2: Oct 6 17:11:09 storageqe-109 kernel: loop2: Oct 6 17:11:10 storageqe-109 kernel: loop2: Oct 6 17:11:10 storageqe-109 kernel: loop2: Oct 6 17:11:11 storageqe-109 kernel: loop2: Oct 6 17:11:11 storageqe-109 kernel: loop2: Oct 6 17:11:14 storageqe-109 kernel: loop2: Oct 6 17:11:14 storageqe-109 kernel: loop2: Oct 6 17:11:14 storageqe-109 kernel: loop2: Oct 6 17:11:14 storageqe-109 kernel: loop2: Oct 6 17:11:15 storageqe-109 kernel: loop2: Oct 6 17:11:15 storageqe-109 kernel: loop2: Oct 6 17:11:16 storageqe-109 kernel: loop2: Oct 6 17:11:16 storageqe-109 kernel: loop2: Oct 6 17:11:16 storageqe-109 kernel: loop2: Oct 6 17:11:16 storageqe-109 kernel: loop2: Oct 6 17:11:19 storageqe-109 kernel: loop2: Oct 6 17:11:19 storageqe-109 kernel: loop2: Oct 6 17:11:20 storageqe-109 kernel: loop2: Oct 6 17:11:20 storageqe-109 kernel: loop2: Oct 6 17:11:21 storageqe-109 kernel: loop2: Oct 6 17:11:21 storageqe-109 kernel: loop2: Oct 6 17:11:22 storageqe-109 kernel: loop2: Oct 6 17:11:22 storageqe-109 kernel: loop2: Oct 6 17:11:23 storageqe-109 kernel: loop2: Oct 6 17:11:23 storageqe-109 kernel: loop2: Oct 6 17:11:25 storageqe-109 kernel: loop2: Oct 6 17:11:25 storageqe-109 kernel: loop2: Oct 6 17:11:26 storageqe-109 kernel: loop2: Oct 6 17:11:26 storageqe-109 kernel: loop2: Oct 6 17:11:27 storageqe-109 kernel: loop2: Oct 6 17:11:27 storageqe-109 kernel: loop2: Oct 6 17:11:28 storageqe-109 kernel: loop2: Oct 6 17:11:28 storageqe-109 kernel: loop2: Oct 6 17:11:28 storageqe-109 kernel: loop2: Oct 6 17:11:28 storageqe-109 kernel: loop2: Oct 6 17:11:31 storageqe-109 kernel: loop2: Oct 6 17:11:31 storageqe-109 kernel: loop2: Oct 6 17:11:32 storageqe-109 kernel: loop2: Oct 6 17:11:32 storageqe-109 kernel: loop2: Oct 6 17:11:32 storageqe-109 kernel: loop2: Oct 6 17:11:32 storageqe-109 kernel: loop2: Oct 6 17:11:33 storageqe-109 kernel: loop2: Oct 6 17:11:33 storageqe-109 kernel: loop2: Oct 6 17:11:34 storageqe-109 kernel: loop2: Oct 6 17:11:34 storageqe-109 kernel: loop2: Oct 6 17:11:37 storageqe-109 kernel: loop2: Oct 6 17:11:37 storageqe-109 kernel: loop2: Oct 6 17:11:37 storageqe-109 kernel: loop2: Oct 6 17:11:37 storageqe-109 kernel: loop2: Oct 6 17:11:38 storageqe-109 kernel: loop2: Oct 6 17:11:38 storageqe-109 kernel: loop2: Oct 6 17:11:39 storageqe-109 kernel: loop2: Oct 6 17:11:39 storageqe-109 kernel: loop2: Oct 6 17:11:40 storageqe-109 kernel: loop2: Oct 6 17:11:40 storageqe-109 kernel: loop2: Oct 6 17:11:42 storageqe-109 kernel: loop2: Oct 6 17:11:42 storageqe-109 kernel: loop2: Oct 6 17:11:43 storageqe-109 kernel: loop2: Oct 6 17:11:43 storageqe-109 kernel: loop2: Oct 6 17:11:44 storageqe-109 kernel: loop2: Oct 6 17:11:45 storageqe-109 kernel: loop2: Oct 6 17:11:45 storageqe-109 kernel: loop2: Oct 6 17:11:46 storageqe-109 kernel: loop2: Oct 6 17:11:46 storageqe-109 kernel: loop2: Oct 6 17:11:48 storageqe-109 kernel: loop2: Oct 6 17:11:48 storageqe-109 kernel: loop2: Oct 6 17:11:49 storageqe-109 kernel: loop2: Oct 6 17:11:49 storageqe-109 kernel: loop2: Oct 6 17:11:50 storageqe-109 kernel: loop2: Oct 6 17:11:50 storageqe-109 kernel: loop2: Oct 6 17:11:50 storageqe-109 kernel: loop2: Oct 6 17:11:50 storageqe-109 kernel: loop2: Oct 6 17:11:51 storageqe-109 kernel: loop2: Oct 6 17:11:52 storageqe-109 kernel: loop2: Oct 6 17:11:53 storageqe-109 kernel: loop2: Oct 6 17:11:54 storageqe-109 kernel: loop2: Oct 6 17:11:55 storageqe-109 kernel: loop2: Oct 6 17:11:55 storageqe-109 kernel: loop2: Oct 6 17:11:55 storageqe-109 kernel: loop2: Oct 6 17:11:55 storageqe-109 kernel: loop2: Oct 6 17:11:56 storageqe-109 kernel: loop2: Oct 6 17:11:56 storageqe-109 kernel: loop2: Oct 6 17:11:57 storageqe-109 kernel: loop2: Oct 6 17:11:59 storageqe-109 kernel: loop2: Oct 6 17:11:59 storageqe-109 kernel: loop2: Oct 6 17:12:00 storageqe-109 kernel: loop2: Oct 6 17:12:00 storageqe-109 kernel: loop2: Oct 6 17:12:01 storageqe-109 kernel: loop2: Oct 6 17:12:01 storageqe-109 kernel: loop2: Oct 6 17:12:01 storageqe-109 kernel: loop2: Oct 6 17:12:02 storageqe-109 kernel: loop2: Oct 6 17:12:03 storageqe-109 kernel: loop2: Oct 6 17:12:03 storageqe-109 kernel: loop2: Oct 6 17:12:05 storageqe-109 kernel: loop2: Oct 6 17:12:05 storageqe-109 kernel: loop2: Oct 6 17:12:06 storageqe-109 kernel: loop2: Oct 6 17:12:06 storageqe-109 kernel: loop2: Oct 6 17:12:07 storageqe-109 kernel: loop2: Oct 6 17:12:07 storageqe-109 kernel: loop2: Oct 6 17:12:07 storageqe-109 kernel: loop2: Oct 6 17:12:07 storageqe-109 kernel: loop2: Oct 6 17:12:09 storageqe-109 kernel: loop2: Oct 6 17:12:09 storageqe-109 kernel: loop2: Oct 6 17:12:10 storageqe-109 kernel: loop2: Oct 6 17:12:10 storageqe-109 kernel: loop2: Oct 6 17:12:12 storageqe-109 kernel: loop2: Oct 6 17:12:12 storageqe-109 kernel: loop2: Oct 6 17:12:12 storageqe-109 kernel: loop2: Oct 6 17:12:12 storageqe-109 kernel: loop2: Oct 6 17:12:13 storageqe-109 kernel: loop2: Oct 6 17:12:13 storageqe-109 kernel: loop2: Oct 6 17:12:15 storageqe-109 kernel: loop2: Oct 6 17:12:15 storageqe-109 kernel: loop2: Oct 6 17:12:16 storageqe-109 kernel: loop2: Oct 6 17:12:16 storageqe-109 kernel: loop2: Oct 6 17:12:17 storageqe-109 kernel: loop2: Oct 6 17:12:17 storageqe-109 kernel: loop2: Oct 6 17:12:18 storageqe-109 kernel: loop2: Oct 6 17:12:18 storageqe-109 kernel: loop2: Oct 6 17:12:19 storageqe-109 kernel: loop2: Oct 6 17:12:19 storageqe-109 kernel: loop2: INFO: start Cleaning up error handling test: test_force_udisks2_crash INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:12:20 storageqe-109 journal: Oct 6 17:12:20 storageqe-109 INFO: start Cleaning up error handling test: test_force_udisks2_crash Oct 6 17:12:20 storageqe-109 journal: Oct 6 17:12:20 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 6 17:12:20 storageqe-109 journal: Oct 6 17:12:20 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:12:20 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_force_crash.img) Oct 6 17:12:20 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_force_udisks2_crash #### INFO: #### will start test_context_assignment_crash ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:12:25 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:12:25 storageqe-109 INFO: #### END test_force_udisks2_crash #### Oct 6 17:12:25 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:25 storageqe-109 INFO: #### will start test_context_assignment_crash ##### Oct 6 17:12:25 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:25 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:25 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:12:25 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:25 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:25 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:25 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:25 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:25 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:25 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:25 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:25 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:25 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:25 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:26 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:28 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:29 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 6 17:12:31 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:12:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_context_test_0.img) Oct 6 17:12:31 storageqe-109 kernel: loop2: Oct 6 17:12:32 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 17:12:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/error_test_context_test_1.img) Oct 6 17:12:32 storageqe-109 kernel: loop3: Oct 6 17:12:33 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 6 17:12:33 storageqe-109 udisksd[5174]: Set up loop device /dev/loop4 (backed by /home/error_test_context_test_2.img) Oct 6 17:12:33 storageqe-109 kernel: loop4: Oct 6 17:12:34 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 6 17:12:34 storageqe-109 udisksd[5174]: Set up loop device /dev/loop5 (backed by /home/error_test_context_test_3.img) Oct 6 17:12:34 storageqe-109 kernel: loop5: Oct 6 17:12:35 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 6 17:12:35 storageqe-109 udisksd[5174]: Set up loop device /dev/loop6 (backed by /home/error_test_context_test_4.img) Oct 6 17:12:35 storageqe-109 kernel: loop6: Oct 6 17:12:36 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 6 17:12:36 storageqe-109 udisksd[5174]: Set up loop device /dev/loop7 (backed by /home/error_test_context_test_5.img) Oct 6 17:12:36 storageqe-109 kernel: loop7: Oct 6 17:12:37 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 6 17:12:37 storageqe-109 udisksd[5174]: Set up loop device /dev/loop8 (backed by /home/error_test_context_test_6.img) Oct 6 17:12:37 storageqe-109 kernel: loop8: Oct 6 17:12:38 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 6 17:12:38 storageqe-109 udisksd[5174]: Set up loop device /dev/loop9 (backed by /home/error_test_context_test_7.img) Oct 6 17:12:38 storageqe-109 kernel: loop9: Oct 6 17:12:39 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 6 17:12:39 storageqe-109 udisksd[5174]: Set up loop device /dev/loop10 (backed by /home/error_test_context_test_8.img) Oct 6 17:12:39 storageqe-109 kernel: loop10: Oct 6 17:12:40 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 6 17:12:40 storageqe-109 udisksd[5174]: Set up loop device /dev/loop11 (backed by /home/error_test_context_test_9.img) Oct 6 17:12:40 storageqe-109 kernel: loop11: Oct 6 17:12:41 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 6 17:12:41 storageqe-109 udisksd[5174]: Set up loop device /dev/loop12 (backed by /home/error_test_context_test_10.img) Oct 6 17:12:41 storageqe-109 kernel: loop12: Oct 6 17:12:42 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 6 17:12:42 storageqe-109 udisksd[5174]: Set up loop device /dev/loop13 (backed by /home/error_test_context_test_11.img) Oct 6 17:12:42 storageqe-109 kernel: loop13: Oct 6 17:12:43 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 6 17:12:43 storageqe-109 udisksd[5174]: Set up loop device /dev/loop14 (backed by /home/error_test_context_test_12.img) Oct 6 17:12:43 storageqe-109 kernel: loop14: Oct 6 17:12:44 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 6 17:12:44 storageqe-109 udisksd[5174]: Set up loop device /dev/loop15 (backed by /home/error_test_context_test_13.img) Oct 6 17:12:44 storageqe-109 kernel: loop15: Oct 6 17:12:45 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 6 17:12:45 storageqe-109 udisksd[5174]: Set up loop device /dev/loop16 (backed by /home/error_test_context_test_14.img) Oct 6 17:12:46 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 6 17:12:46 storageqe-109 udisksd[5174]: Set up loop device /dev/loop17 (backed by /home/error_test_context_test_15.img) Oct 6 17:12:46 storageqe-109 kernel: loop17: Oct 6 17:12:47 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 6 17:12:47 storageqe-109 udisksd[5174]: Set up loop device /dev/loop18 (backed by /home/error_test_context_test_16.img) Oct 6 17:12:47 storageqe-109 kernel: loop18: Oct 6 17:12:48 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 6 17:12:48 storageqe-109 udisksd[5174]: Set up loop device /dev/loop19 (backed by /home/error_test_context_test_17.img) Oct 6 17:12:48 storageqe-109 kernel: loop19: Oct 6 17:12:49 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 6 17:12:49 storageqe-109 udisksd[5174]: Set up loop device /dev/loop20 (backed by /home/error_test_context_test_18.img) Oct 6 17:12:49 storageqe-109 kernel: loop20: Oct 6 17:12:51 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 6 17:12:51 storageqe-109 udisksd[5174]: Set up loop device /dev/loop21 (backed by /home/error_test_context_test_19.img) Oct 6 17:12:51 storageqe-109 kernel: loop21: Oct 6 17:12:51 storageqe-109 kernel: loop8: Oct 6 17:12:51 storageqe-109 kernel: loop14: Oct 6 17:12:51 storageqe-109 kernel: loop2: Oct 6 17:12:52 storageqe-109 udisksd[5174]: [fdisk] Failed to add partition 1 to system Oct 6 17:12:52 storageqe-109 kernel: loop9: Oct 6 17:12:52 storageqe-109 kernel: loop3: Oct 6 17:12:52 storageqe-109 udisksd[5174]: [fdisk] Failed to add partition 1 to system Oct 6 17:12:53 storageqe-109 kernel: loop10: Oct 6 17:12:57 storageqe-109 kernel: loop10: Oct 6 17:12:57 storageqe-109 kernel: loop14: Oct 6 17:12:58 storageqe-109 kernel: loop14: Oct 6 17:12:58 storageqe-109 kernel: loop10: Oct 6 17:13:03 storageqe-109 kernel: loop10: Oct 6 17:13:03 storageqe-109 kernel: loop14: Oct 6 17:13:03 storageqe-109 kernel: loop4: Oct 6 17:13:04 storageqe-109 kernel: loop5: Oct 6 17:13:04 storageqe-109 kernel: loop4: Oct 6 17:13:04 storageqe-109 kernel: loop10: Oct 6 17:13:08 storageqe-109 kernel: loop10: Oct 6 17:13:09 storageqe-109 kernel: loop14: Oct 6 17:13:10 storageqe-109 kernel: loop14: Oct 6 17:13:10 storageqe-109 kernel: loop10: Oct 6 17:13:14 storageqe-109 kernel: loop10: Oct 6 17:13:14 storageqe-109 kernel: loop5: Oct 6 17:13:15 storageqe-109 kernel: loop5: Oct 6 17:13:15 storageqe-109 kernel: loop10: Oct 6 17:13:19 storageqe-109 kernel: loop10: Oct 6 17:13:19 storageqe-109 kernel: loop14: Oct 6 17:13:21 storageqe-109 kernel: loop14: Oct 6 17:13:21 storageqe-109 kernel: loop10: Oct 6 17:13:25 storageqe-109 kernel: loop10: Oct 6 17:13:25 storageqe-109 kernel: loop5: Oct 6 17:13:26 storageqe-109 kernel: loop5: Oct 6 17:13:26 storageqe-109 kernel: loop10: Oct 6 17:13:30 storageqe-109 kernel: loop10: Oct 6 17:13:30 storageqe-109 kernel: loop14: Oct 6 17:13:32 storageqe-109 kernel: loop14: Oct 6 17:13:32 storageqe-109 kernel: loop10: Oct 6 17:13:36 storageqe-109 kernel: loop10: Oct 6 17:13:36 storageqe-109 kernel: loop5: Oct 6 17:13:38 storageqe-109 kernel: loop5: Oct 6 17:13:38 storageqe-109 kernel: loop10: Oct 6 17:13:41 storageqe-109 kernel: loop10: Oct 6 17:13:41 storageqe-109 kernel: loop14: Oct 6 17:13:43 storageqe-109 kernel: loop14: Oct 6 17:13:43 storageqe-109 kernel: loop10: Oct 6 17:13:46 storageqe-109 kernel: loop10: Oct 6 17:13:46 storageqe-109 kernel: loop14: Oct 6 17:13:47 storageqe-109 kernel: loop6: Oct 6 17:13:49 storageqe-109 kernel: loop6: Oct 6 17:13:49 storageqe-109 kernel: loop11: Oct 6 17:13:52 storageqe-109 kernel: loop11: Oct 6 17:13:52 storageqe-109 kernel: loop14: Oct 6 17:13:53 storageqe-109 kernel: loop14: Oct 6 17:13:53 storageqe-109 kernel: loop6: Oct 6 17:13:54 storageqe-109 kernel: loop6: Oct 6 17:13:54 storageqe-109 kernel: loop11: Oct 6 17:13:57 storageqe-109 kernel: loop11: Oct 6 17:13:58 storageqe-109 kernel: loop14: Oct 6 17:13:59 storageqe-109 kernel: loop14: Oct 6 17:13:59 storageqe-109 kernel: loop6: Oct 6 17:14:00 storageqe-109 kernel: loop6: Oct 6 17:14:00 storageqe-109 kernel: loop11: Oct 6 17:14:03 storageqe-109 kernel: loop11: Oct 6 17:14:03 storageqe-109 kernel: loop15: Oct 6 17:14:04 storageqe-109 kernel: loop15: Oct 6 17:14:04 storageqe-109 kernel: loop6: Oct 6 17:14:05 storageqe-109 kernel: loop6: Oct 6 17:14:05 storageqe-109 kernel: loop11: Oct 6 17:14:09 storageqe-109 kernel: loop11: Oct 6 17:14:09 storageqe-109 kernel: loop15: Oct 6 17:14:10 storageqe-109 kernel: loop15: Oct 6 17:14:10 storageqe-109 kernel: loop6: Oct 6 17:14:11 storageqe-109 kernel: loop6: Oct 6 17:14:11 storageqe-109 kernel: loop11: Oct 6 17:14:14 storageqe-109 kernel: loop11: Oct 6 17:14:14 storageqe-109 kernel: loop15: Oct 6 17:14:15 storageqe-109 kernel: loop15: Oct 6 17:14:15 storageqe-109 kernel: loop6: Oct 6 17:14:17 storageqe-109 kernel: loop6: Oct 6 17:14:20 storageqe-109 kernel: loop11: Oct 6 17:14:20 storageqe-109 kernel: loop15: Oct 6 17:14:21 storageqe-109 kernel: loop15: Oct 6 17:14:21 storageqe-109 kernel: loop6: INFO: start Cleaning up error handling test: test_context_assignment_crash INFO: start Cleaning _cleanup_automounts Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop21 (was backed by /home/error_test_context_test_19.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop21 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop20 (was backed by /home/error_test_context_test_18.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop20 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop19 (was backed by /home/error_test_context_test_17.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop19 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop18 (was backed by /home/error_test_context_test_16.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop18 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop17 (was backed by /home/error_test_context_test_15.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop17 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop16 (was backed by /home/error_test_context_test_14.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop16 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop15 (was backed by /home/error_test_context_test_13.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop15 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop14 (was backed by /home/error_test_context_test_12.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop14 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop13 (was backed by /home/error_test_context_test_11.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop13 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop12 (was backed by /home/error_test_context_test_10.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop12 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop11 (was backed by /home/error_test_context_test_9.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop11 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop10 (was backed by /home/error_test_context_test_8.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop10 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop9 (was backed by /home/error_test_context_test_7.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop9 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop8 (was backed by /home/error_test_context_test_6.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop8 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop7 (was backed by /home/error_test_context_test_5.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop7 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop6 (was backed by /home/error_test_context_test_4.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop6 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop5 (was backed by /home/error_test_context_test_3.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop5 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop4 (was backed by /home/error_test_context_test_2.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop4 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop3 (was backed by /home/error_test_context_test_1.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 Oct 6 17:14:22 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_context_test_0.img) Oct 6 17:14:22 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:14:22 storageqe-109 journal: Oct 6 17:14:22 storageqe-109 INFO: start Cleaning up error handling test: test_context_assignment_crash Oct 6 17:14:22 storageqe-109 journal: Oct 6 17:14:22 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_context_assignment_crash #### INFO: #### will start test_dbus_method_abuse_crash ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:14:27 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:14:27 storageqe-109 INFO: #### END test_context_assignment_crash #### Oct 6 17:14:27 storageqe-109 INFO: #### will start test_dbus_method_abuse_crash ##### Oct 6 17:14:27 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:14:27 storageqe-109 kernel: blk_print_req_error: 366 callbacks suppressed Oct 6 17:14:27 storageqe-109 kernel: I/O error, dev loop12, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop12': Invalid argument Oct 6 17:14:27 storageqe-109 kernel: I/O error, dev loop13, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:27 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop13': Invalid argument Oct 6 17:14:30 storageqe-109 kernel: I/O error, dev loop16, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:30 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop16': Invalid argument Oct 6 17:14:30 storageqe-109 kernel: I/O error, dev loop17, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:30 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop17': Invalid argument Oct 6 17:14:30 storageqe-109 kernel: I/O error, dev loop18, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:30 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop18': Invalid argument Oct 6 17:14:30 storageqe-109 kernel: I/O error, dev loop19, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:30 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop19': Invalid argument Oct 6 17:14:30 storageqe-109 kernel: I/O error, dev loop20, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:30 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop20': Invalid argument Oct 6 17:14:30 storageqe-109 kernel: I/O error, dev loop21, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:30 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop21': Invalid argument Oct 6 17:14:32 storageqe-109 kernel: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 6 17:14:32 storageqe-109 udisksd[5174]: Failed to assign the new context to disk '/dev/loop7': Invalid argument INFO: start Cleaning up error handling test: test_dbus_method_abuse_crash INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:14:32 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:14:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/error_test_dbus_abuse.img) Oct 6 17:14:32 storageqe-109 journal: Oct 6 17:14:32 storageqe-109 INFO: start Cleaning up error handling test: test_dbus_method_abuse_crash Oct 6 17:14:32 storageqe-109 journal: Oct 6 17:14:32 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 6 17:14:32 storageqe-109 journal: Oct 6 17:14:32 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 6 17:14:32 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop2 (was backed by /home/error_test_dbus_abuse.img) Oct 6 17:14:32 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_dbus_method_abuse_crash #### INFO: #### will start test_iscsi_session_properties ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:14:37 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:14:37 storageqe-109 INFO: #### END test_dbus_method_abuse_crash #### Oct 6 17:14:37 storageqe-109 INFO: #### will start test_iscsi_session_properties ##### Oct 6 17:14:37 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 Oct 6 17:14:43 storageqe-109 INFO: Setting up local iSCSI target... Oct 6 17:14:43 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 6 17:14:43 storageqe-109 INFO: Creating test disk files... Oct 6 17:14:43 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 6 17:14:43 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 17:14:43 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 17:14:43 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 6 17:14:43 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 17:14:43 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 6 17:14:43 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 17:14:44 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 17:14:46 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 17:14:46 storageqe-109 kernel: dev[000000005422450a]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:14:46 storageqe-109 kernel: dev[00000000bdc6d537]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:14:46 storageqe-109 kernel: dev[00000000f2722835]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:14:46 storageqe-109 kernel: dev[000000008460b8a8]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:14:46 storageqe-109 kernel: dev[000000000b1d2e11]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:14:46 storageqe-109 kernel: dev[000000009e2355a6]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:14:46 storageqe-109 kernel: dev[00000000c56b68ab]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:14:46 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 6 17:14:46 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:14:46 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:14:46 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 6 17:14:46 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 6 17:14:46 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:14:46 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 6 17:14:46 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 6 17:14:46 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 6 17:14:46 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 6 17:14:46 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:14:46 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 6 17:14:46 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 6 17:14:46 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:14:46 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 6 17:14:46 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 6 17:14:46 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 6 17:14:46 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 6 17:14:46 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 6 17:14:46 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:14:46 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 6 17:14:46 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 6 17:14:46 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:14:46 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 6 17:14:46 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 6 17:14:46 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 6 17:14:46 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 6 17:14:46 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 6 17:14:46 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:14:46 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:14:46 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 6 17:14:46 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:14:46 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 6 17:14:46 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 6 17:14:46 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 6 17:14:46 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 6 17:14:46 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:46 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 6 17:14:46 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 6 17:14:56 storageqe-109 INFO: Verifying iSCSI target setup... Oct 6 17:14:56 storageqe-109 INFO: Found 4 LIO target(s) Oct 6 17:14:56 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 6 17:14:56 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 17:14:56 storageqe-109 iscsid[1142526]: iscsid shutting down. Oct 6 17:14:56 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 17:14:56 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 17:14:56 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 17:14:56 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 17:14:56 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 17:14:56 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 17:14:56 storageqe-109 iscsid[1160080]: iscsid: Connection6:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 6 17:14:56 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 6 17:14:56 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 6 17:14:56 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 6 17:14:56 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 6 17:14:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:14:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 6 17:14:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:14:56 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 6 17:14:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 6 17:14:56 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:14:56 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: Fetching all properties for ISCSI.Session interface... INFO: Checking property 'target_name'... INFO: Checking property 'tpgt'... INFO: Checking property 'address'... INFO: Checking property 'port'... INFO: Checking property 'persistent_address'... INFO: Checking property 'persistent_port'... INFO: Checking property 'abort_timeout'... INFO: Checking property 'lu_reset_timeout'... INFO: Checking property 'recovery_timeout'... INFO: Checking property 'tgt_reset_timeout'... INFO: Checking specific property values... INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 6 17:14:57 storageqe-109 INFO: Fetching all properties for ISCSI.Session interface... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'target_name'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'tpgt'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'address'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'port'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'persistent_address'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'persistent_port'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'abort_timeout'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'lu_reset_timeout'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'recovery_timeout'... Oct 6 17:14:57 storageqe-109 INFO: Checking property 'tgt_reset_timeout'... Oct 6 17:14:57 storageqe-109 INFO: Checking specific property values... Oct 6 17:14:57 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 6 17:14:57 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 6 17:14:57 storageqe-109 iscsid[1160080]: iscsid: Connection6:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 6 17:14:57 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 6 17:14:57 storageqe-109 INFO: Clearing targetcli configuration... Oct 6 17:14:57 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 6 17:14:57 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 6 17:14:57 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 6 17:14:57 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 6 17:14:57 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 6 17:14:57 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 6 17:14:57 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 6 17:14:57 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 6 17:14:57 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 6 17:14:57 storageqe-109 INFO: Removing test disk files... Oct 6 17:14:57 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 6 17:14:57 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 6 17:14:57 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 6 17:14:57 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 6 17:14:57 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 6 17:14:57 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 6 17:14:58 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 6 17:14:58 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_iscsi_session_properties #### INFO: #### will start test_iscsi_session_logout_methods ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:15:03 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:15:03 storageqe-109 INFO: #### END test_iscsi_session_properties #### Oct 6 17:15:03 storageqe-109 INFO: #### will start test_iscsi_session_logout_methods ##### Oct 6 17:15:03 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 17:15:08 storageqe-109 INFO: Setting up local iSCSI target... Oct 6 17:15:08 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 6 17:15:08 storageqe-109 INFO: Creating test disk files... Oct 6 17:15:08 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 6 17:15:08 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 17:15:08 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 6 17:15:08 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 6 17:15:08 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 17:15:08 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 6 17:15:08 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 17:15:09 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 17:15:11 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 17:15:11 storageqe-109 kernel: dev[00000000e080fe0d]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:11 storageqe-109 kernel: dev[000000007a30c20d]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:11 storageqe-109 kernel: dev[00000000fd006757]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:11 storageqe-109 kernel: dev[000000001f893953]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:11 storageqe-109 kernel: dev[00000000832fa5ad]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:11 storageqe-109 kernel: dev[0000000041b5c874]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:11 storageqe-109 kernel: dev[0000000031a19591]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:11 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 6 17:15:11 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:11 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:11 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 6 17:15:11 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 6 17:15:11 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:11 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 6 17:15:11 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 6 17:15:11 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 6 17:15:11 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 6 17:15:11 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:11 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:11 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:11 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 6 17:15:11 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 6 17:15:11 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 6 17:15:11 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 6 17:15:11 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 6 17:15:11 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:11 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 6 17:15:11 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:11 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 6 17:15:11 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 6 17:15:11 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:11 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 6 17:15:11 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 6 17:15:11 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:11 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 6 17:15:11 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:11 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 6 17:15:11 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:11 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 6 17:15:11 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 6 17:15:11 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:11 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 6 17:15:11 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 6 17:15:11 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:11 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 6 17:15:11 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 6 17:15:21 storageqe-109 INFO: Verifying iSCSI target setup... Oct 6 17:15:21 storageqe-109 INFO: Found 4 LIO target(s) Oct 6 17:15:21 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 6 17:15:21 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 17:15:21 storageqe-109 iscsid[1160080]: iscsid shutting down. Oct 6 17:15:21 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 17:15:21 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 17:15:21 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 17:15:21 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 17:15:21 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 17:15:21 storageqe-109 iscsid[1160385]: iscsid: Connection7:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 6 17:15:21 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 17:15:21 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:21 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 6 17:15:21 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 6 17:15:21 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 6 17:15:21 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:21 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 6 17:15:21 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:21 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:21 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 6 17:15:21 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 6 17:15:21 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:21 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: Testing Logout() method... Oct 6 17:15:22 storageqe-109 INFO: Testing Logout() method... Oct 6 17:15:22 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 6 17:15:22 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 6 17:15:22 storageqe-109 iscsid[1160385]: iscsid: Connection7:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 6 17:15:25 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 6 17:15:25 storageqe-109 INFO: Clearing targetcli configuration... Oct 6 17:15:25 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 6 17:15:25 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 6 17:15:25 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 6 17:15:25 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 6 17:15:25 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 6 17:15:25 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 6 17:15:25 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 6 17:15:25 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 6 17:15:25 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 6 17:15:25 storageqe-109 INFO: Removing test disk files... Oct 6 17:15:25 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 6 17:15:25 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 6 17:15:25 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 6 17:15:25 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 6 17:15:25 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 6 17:15:25 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 6 17:15:26 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 6 17:15:26 storageqe-109 INFO: Local iSCSI target cleanup completed Oct 6 17:15:26 storageqe-109 INFO: Setting up local iSCSI target... Oct 6 17:15:26 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 6 17:15:26 storageqe-109 INFO: Creating test disk files... Oct 6 17:15:26 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 6 17:15:26 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 6 17:15:26 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 Oct 6 17:15:26 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 6 17:15:26 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 17:15:26 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 6 17:15:26 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 6 17:15:26 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 17:15:29 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 6 17:15:29 storageqe-109 kernel: dev[0000000051f075a1]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:29 storageqe-109 kernel: dev[000000006551088a]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:29 storageqe-109 kernel: dev[000000005dd609c7]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:29 storageqe-109 kernel: dev[00000000fd1ba8bf]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:29 storageqe-109 kernel: dev[00000000b3ef4680]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:29 storageqe-109 kernel: dev[00000000e080fe0d]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:29 storageqe-109 kernel: dev[0000000031a19591]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 6 17:15:29 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 6 17:15:29 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:29 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:29 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 6 17:15:29 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 6 17:15:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:29 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 6 17:15:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 6 17:15:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 6 17:15:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 6 17:15:29 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:29 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 6 17:15:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:29 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 6 17:15:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 6 17:15:29 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 6 17:15:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 6 17:15:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 6 17:15:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 6 17:15:29 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:29 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 6 17:15:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:29 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 6 17:15:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 6 17:15:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 6 17:15:29 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 6 17:15:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 6 17:15:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 6 17:15:29 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:29 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 6 17:15:29 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 6 17:15:29 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 6 17:15:29 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 6 17:15:29 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 6 17:15:29 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 6 17:15:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 6 17:15:29 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:29 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 6 17:15:29 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 6 17:15:39 storageqe-109 INFO: Verifying iSCSI target setup... Oct 6 17:15:39 storageqe-109 INFO: Found 4 LIO target(s) Oct 6 17:15:39 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 6 17:15:39 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 6 17:15:39 storageqe-109 iscsid[1160385]: iscsid shutting down. Oct 6 17:15:39 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 6 17:15:39 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 6 17:15:39 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 6 17:15:39 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 6 17:15:39 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 6 17:15:39 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 6 17:15:39 storageqe-109 iscsid[1160611]: iscsid: Connection8:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 6 17:15:39 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 6 17:15:39 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 6 17:15:39 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 6 17:15:39 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 6 17:15:39 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 6 17:15:39 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 6 17:15:39 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 6 17:15:39 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:39 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 6 17:15:39 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 6 17:15:39 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 6 17:15:39 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: Testing LogoutInterface() method... Oct 6 17:15:40 storageqe-109 INFO: Testing LogoutInterface() method... Oct 6 17:15:40 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 6 17:15:40 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 6 17:15:40 storageqe-109 iscsid[1160611]: iscsid: Connection8:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 6 17:15:43 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 6 17:15:43 storageqe-109 INFO: Clearing targetcli configuration... Oct 6 17:15:43 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 6 17:15:43 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 6 17:15:43 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 6 17:15:43 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 6 17:15:43 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 6 17:15:43 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 6 17:15:43 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 6 17:15:43 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 6 17:15:43 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 6 17:15:43 storageqe-109 INFO: Removing test disk files... Oct 6 17:15:43 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 6 17:15:43 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 6 17:15:43 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 6 17:15:43 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 6 17:15:43 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 6 17:15:43 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 6 17:15:43 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 6 17:15:43 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_iscsi_session_logout_methods #### INFO: #### will start test_plain_lv_properties_and_methods ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:15:48 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 6 17:15:48 storageqe-109 INFO: #### END test_iscsi_session_logout_methods #### Oct 6 17:15:48 storageqe-109 INFO: #### will start test_plain_lv_properties_and_methods ##### Oct 6 17:15:48 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: Creating VG 'udisks_test_vg' on device /dev/sdd Oct 6 17:15:53 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/sdd INFO: VG object for 'udisks_test_vg' is now live. INFO: Validating LV properties... Oct 6 17:15:55 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. Oct 6 17:15:55 storageqe-109 INFO: Validating LV properties... INFO: Testing Rename()... Oct 6 17:15:59 storageqe-109 INFO: Testing Rename()... INFO: Testing Resize()... Oct 6 17:18:03 storageqe-109 INFO: Testing Resize()... INFO: Testing Delete()... Oct 6 17:18:06 storageqe-109 INFO: Testing Delete()... INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 6 17:18:07 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_plain_lv_properties_and_methods #### INFO: #### will start test_lv_snapshot_creation_and_properties ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 6 17:18:13 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 6 17:18:13 storageqe-109 INFO: #### END test_plain_lv_properties_and_methods #### Oct 6 17:18:13 storageqe-109 INFO: #### will start test_lv_snapshot_creation_and_properties ##### Oct 6 17:18:13 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: Creating VG 'udisks_test_vg' on device /dev/sde Oct 6 17:18:18 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/sde INFO: VG object for 'udisks_test_vg' is now live. Oct 6 17:18:19 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. Oct 6 17:18:20 storageqe-109 INFO: Creating snapshot 'test_snapshot'... INFO: Creating snapshot 'test_snapshot'... Oct 6 17:18:20 storageqe-109 dmeventd[1119988]: Monitoring snapshot udisks_test_vg-test_snapshot. INFO: Validating snapshot properties... Oct 6 17:18:20 storageqe-109 INFO: Validating snapshot properties... INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 6 17:18:21 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 6 17:18:22 storageqe-109 dmeventd[1119988]: No longer monitoring snapshot udisks_test_vg-test_snapshot. INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_lv_snapshot_creation_and_properties #### INFO: #### will start test_logical_volume_all_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:18:27 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 6 17:18:27 storageqe-109 INFO: #### END test_lv_snapshot_creation_and_properties #### Oct 6 17:18:27 storageqe-109 INFO: #### will start test_logical_volume_all_properties ##### Oct 6 17:18:27 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: Creating VG 'udisks_test_vg' on device /dev/nvme0n1 Oct 6 17:18:32 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/nvme0n1 INFO: VG object for 'udisks_test_vg' is now live. Oct 6 17:18:34 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. INFO: Fetching all properties for LogicalVolume interface... INFO: Checking property 'VolumeGroup'... INFO: Checking property 'Name'... INFO: Checking property 'Active'... INFO: Checking property 'UUID'... INFO: Checking property 'Size'... INFO: Checking property 'DataAllocatedRatio'... INFO: Checking property 'MetadataAllocatedRatio'... INFO: Checking property 'Type'... INFO: Checking property 'Layout'... INFO: Checking property 'Structure'... INFO: Checking property 'SyncRatio'... INFO: Checking property 'ThinPool'... INFO: Checking property 'Origin'... INFO: Checking property 'ChildConfiguration'... INFO: Checking property 'BlockDevice'... INFO: Checking specific property values... INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 6 17:18:39 storageqe-109 INFO: Fetching all properties for LogicalVolume interface... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'VolumeGroup'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'Name'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'Active'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'UUID'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'Size'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'DataAllocatedRatio'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'MetadataAllocatedRatio'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'Type'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'Layout'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'Structure'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'SyncRatio'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'ThinPool'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'Origin'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'ChildConfiguration'... Oct 6 17:18:39 storageqe-109 INFO: Checking property 'BlockDevice'... Oct 6 17:18:39 storageqe-109 INFO: Checking specific property values... Oct 6 17:18:39 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_logical_volume_all_properties #### INFO: #### will start test_lvm_cache_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 6 17:18:45 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 6 17:18:45 storageqe-109 INFO: #### END test_logical_volume_all_properties #### Oct 6 17:18:45 storageqe-109 INFO: #### will start test_lvm_cache_operations ##### Oct 6 17:18:45 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Starting LVM cache operations test with enhanced error handling INFO: Creating VG 'udisks_test_vg' on device /dev/sdb Oct 6 17:18:50 storageqe-109 INFO: Starting LVM cache operations test with enhanced error handling Oct 6 17:18:50 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/sdb INFO: VG object for 'udisks_test_vg' is now live. INFO: Getting cache device... Oct 6 17:18:52 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. Oct 6 17:18:52 storageqe-109 INFO: Getting cache device... INFO: Cache device /dev/sdc ready INFO: Creating logical volume of size 536870912 bytes... Oct 6 17:18:54 storageqe-109 INFO: Cache device /dev/sdc ready Oct 6 17:18:54 storageqe-109 INFO: Creating logical volume of size 536870912 bytes... INFO: Waiting for object /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv to be ready... Oct 6 17:18:54 storageqe-109 INFO: Waiting for object /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv to be ready... INFO: Object at /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv is now live with name='udisks_test_lv', active=1 INFO: === Testing LVM Cache Attach/Detach === INFO: Verifying initial state (no cache)... INFO: Attaching cache... INFO: Executing CacheAttach operation... Oct 6 17:18:55 storageqe-109 INFO: Object at /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv is now live with name='udisks_test_lv', active=1 Oct 6 17:18:55 storageqe-109 INFO: === Testing LVM Cache Attach/Detach === Oct 6 17:18:55 storageqe-109 INFO: Verifying initial state (no cache)... Oct 6 17:18:55 storageqe-109 INFO: Attaching cache... Oct 6 17:18:55 storageqe-109 INFO: Executing CacheAttach operation... INFO: Cache device name: sdc INFO: Cache device path: /dev/sdc INFO: Cache device object: /org/freedesktop/UDisks2/block_devices/sdc ERROR: CacheAttach failed: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdc not found. INFO: Cache operation failed as expected - cache pool not found: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdc not found. INFO: This indicates the D-Bus interface is working correctly INFO: Skipping remaining cache tests due to cache pool requirement INFO: Performing cleanup... INFO: Releasing cache device /dev/sdc INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 6 17:18:56 storageqe-109 INFO: Cache device name: sdc Oct 6 17:18:56 storageqe-109 INFO: Cache device path: /dev/sdc Oct 6 17:18:56 storageqe-109 INFO: Cache device object: /org/freedesktop/UDisks2/block_devices/sdc Oct 6 17:18:56 storageqe-109 ERROR: CacheAttach failed: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdc not found. Oct 6 17:18:56 storageqe-109 journal: Oct 6 17:18:56 storageqe-109 INFO: Cache operation failed as expected - cache pool not found: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdc not found. Oct 6 17:18:56 storageqe-109 journal: Oct 6 17:18:56 storageqe-109 INFO: This indicates the D-Bus interface is working correctly Oct 6 17:18:56 storageqe-109 INFO: Skipping remaining cache tests due to cache pool requirement Oct 6 17:18:56 storageqe-109 INFO: Performing cleanup... Oct 6 17:18:56 storageqe-109 INFO: Releasing cache device /dev/sdc Oct 6 17:18:56 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_lvm_cache_operations #### INFO: #### will start test_mdraid_properties_by_level[raid0-2-None] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:19:02 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:19:02 storageqe-109 INFO: #### END test_lvm_cache_operations #### Oct 6 17:19:02 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid0-2-None] ##### Oct 6 17:19:02 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:19:08 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:19:08 storageqe-109 udisksd[5174]: udisks_state_check_loop_entry: unexpected name for /dev/loop0 - expected `/home/error_test_concurrent_test.img' but got `/home/error_test_concurrent_test.img (deleted)' Oct 6 17:19:08 storageqe-109 udisksd[5174]: udisks_state_check_loop_entry: unexpected name for /dev/loop0 - expected `/home/error_test_concurrent_test.img' but got `/home/error_test_concurrent_test.img (deleted)' Oct 6 17:19:08 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:19:09 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:19:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid0_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_raid0 INFO: raid chunk 65536 INFO: raid bitmap None INFO: raid version None Oct 6 17:19:09 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:19:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid0_1.img) Oct 6 17:19:09 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 17:19:09 storageqe-109 INFO: raid level raid0 Oct 6 17:19:09 storageqe-109 INFO: raid name test_raid0 Oct 6 17:19:09 storageqe-109 INFO: raid chunk 65536 Oct 6 17:19:09 storageqe-109 INFO: raid bitmap None Oct 6 17:19:09 storageqe-109 INFO: raid version None Oct 6 17:19:09 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 17:19:26 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 17:19:26 storageqe-109 kernel: md: md127 stopped. Oct 6 17:19:26 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 17:19:30 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:19:30 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_mdraid_properties_by_level[raid0-2-None] #### INFO: #### will start test_mdraid_properties_by_level[raid1-2-None] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:19:37 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:19:37 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid0-2-None] #### Oct 6 17:19:37 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid1-2-None] ##### Oct 6 17:19:37 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:19:43 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:19:43 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid1_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_raid1 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version None Oct 6 17:19:44 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:19:44 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid1_1.img) Oct 6 17:19:44 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 17:19:44 storageqe-109 INFO: raid level raid1 Oct 6 17:19:44 storageqe-109 INFO: raid name test_raid1 Oct 6 17:19:44 storageqe-109 INFO: raid chunk 0 Oct 6 17:19:44 storageqe-109 INFO: raid bitmap None Oct 6 17:19:44 storageqe-109 INFO: raid version None Oct 6 17:19:44 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 17:19:44 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 17:19:44 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 17:19:44 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 17:19:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:19:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:19:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:19:49 storageqe-109 kernel: md: md127: resync done. Oct 6 17:20:09 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 17:20:09 storageqe-109 kernel: md: md127 stopped. Oct 6 17:20:09 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 17:20:13 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:20:13 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_mdraid_properties_by_level[raid1-2-None] #### INFO: #### will start test_mdraid_properties_by_level[raid1-2-internal] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:20:19 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:20:19 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid1-2-None] #### Oct 6 17:20:19 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid1-2-internal] ##### Oct 6 17:20:19 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:20:26 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:20:26 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid1_bitmap_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_raid1_bitmap INFO: raid chunk 0 INFO: raid bitmap internal INFO: raid version None Oct 6 17:20:26 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:20:26 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid1_bitmap_1.img) Oct 6 17:20:26 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 6 17:20:26 storageqe-109 INFO: raid level raid1 Oct 6 17:20:26 storageqe-109 INFO: raid name test_raid1_bitmap Oct 6 17:20:26 storageqe-109 INFO: raid chunk 0 Oct 6 17:20:26 storageqe-109 INFO: raid bitmap internal Oct 6 17:20:26 storageqe-109 INFO: raid version None Oct 6 17:20:26 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 6 17:20:26 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 6 17:20:26 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 6 17:20:26 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 17:20:26 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:20:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:20:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:20:32 storageqe-109 kernel: md: md127: resync done. Oct 6 17:20:52 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 6 17:20:52 storageqe-109 kernel: md: md127 stopped. Oct 6 17:20:52 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 17:20:56 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:20:56 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_mdraid_properties_by_level[raid1-2-internal] #### INFO: #### will start test_mdraid_properties_by_level[raid5-3-internal] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:21:02 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:21:02 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid1-2-internal] #### Oct 6 17:21:02 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid5-3-internal] ##### Oct 6 17:21:02 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:21:09 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:21:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid5_bitmap_0.img) Oct 6 17:21:09 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:21:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid5_bitmap_1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_raid5_bitmap INFO: raid chunk 65536 INFO: raid bitmap internal INFO: raid version None Oct 6 17:21:09 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:21:09 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop_test_raid5_bitmap_2.img) Oct 6 17:21:09 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 6 17:21:09 storageqe-109 INFO: raid level raid5 Oct 6 17:21:09 storageqe-109 INFO: raid name test_raid5_bitmap Oct 6 17:21:09 storageqe-109 INFO: raid chunk 65536 Oct 6 17:21:09 storageqe-109 INFO: raid bitmap internal Oct 6 17:21:09 storageqe-109 INFO: raid version None Oct 6 17:21:10 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 17:21:10 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 17:21:10 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 6 17:21:10 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 17:21:10 storageqe-109 kernel: md: recover of RAID array md127 Oct 6 17:21:10 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:21:10 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:21:10 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:21:15 storageqe-109 kernel: md: md127: recover done. Oct 6 17:21:31 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 17:21:31 storageqe-109 kernel: md: md127 stopped. Oct 6 17:21:31 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 17:21:31 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 17:21:31 storageqe-109 dnf[1163562]: Updating Subscription Management repositories. Oct 6 17:21:31 storageqe-109 dnf[1163562]: Unable to read consumer identity Oct 6 17:21:31 storageqe-109 dnf[1163562]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-AppStream 555 kB/s | 2.8 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-AppStream-debuginfo 449 kB/s | 1.5 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-BaseOS 786 kB/s | 2.7 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-BaseOS-debuginfo 532 kB/s | 1.5 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-CRB 677 kB/s | 2.7 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-CRB-debuginfo 458 kB/s | 1.5 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-HighAvailability 799 kB/s | 2.8 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-HighAvailability-debuginfo 491 kB/s | 1.5 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-NFV 688 kB/s | 2.7 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-NFV-debuginfo 452 kB/s | 1.5 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-RT 685 kB/s | 2.7 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-RT-debuginfo 475 kB/s | 1.5 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-SAP 771 kB/s | 2.7 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-SAP-debuginfo 444 kB/s | 1.5 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-SAPHANA 814 kB/s | 2.7 kB 00:00 Oct 6 17:21:31 storageqe-109 dnf[1163562]: beaker-SAPHANA-debuginfo 474 kB/s | 1.5 kB 00:00 Oct 6 17:21:32 storageqe-109 dnf[1163562]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 6 17:21:34 storageqe-109 dnf[1163562]: beaker-harness 757 B/s | 1.3 kB 00:01 Oct 6 17:21:34 storageqe-109 dnf[1163562]: Google Cloud CLI 3.9 kB/s | 1.4 kB 00:00 Oct 6 17:21:35 storageqe-109 dnf[1163562]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 6 17:21:35 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:21:35 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:21:35 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:21:36 storageqe-109 dnf[1163562]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 6 17:21:36 storageqe-109 dnf[1163562]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 6 17:21:36 storageqe-109 dnf[1163562]: Metadata cache created. Oct 6 17:21:36 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 17:21:36 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 17:21:36 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 332ms CPU time, 76.9M memory peak. INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_mdraid_properties_by_level[raid5-3-internal] #### INFO: #### will start test_mdraid_properties_by_level[raid6-4-None] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:21:41 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:21:41 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid5-3-internal] #### Oct 6 17:21:41 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid6-4-None] ##### Oct 6 17:21:41 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:21:48 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:21:48 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid6_0.img) Oct 6 17:21:48 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:21:48 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid6_1.img) Oct 6 17:21:49 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:21:49 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop_test_raid6_2.img) Oct 6 17:21:49 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid6 INFO: raid name test_raid6 INFO: raid chunk 65536 INFO: raid bitmap None INFO: raid version None Oct 6 17:21:49 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/loop_test_raid6_3.img) Oct 6 17:21:49 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 6 17:21:49 storageqe-109 INFO: raid level raid6 Oct 6 17:21:49 storageqe-109 INFO: raid name test_raid6 Oct 6 17:21:49 storageqe-109 INFO: raid chunk 65536 Oct 6 17:21:49 storageqe-109 INFO: raid bitmap None Oct 6 17:21:49 storageqe-109 INFO: raid version None Oct 6 17:21:49 storageqe-109 kernel: md/raid:md127: not clean -- starting background reconstruction Oct 6 17:21:49 storageqe-109 kernel: md/raid:md127: device loop3 operational as raid disk 3 Oct 6 17:21:49 storageqe-109 kernel: md/raid:md127: device loop2 operational as raid disk 2 Oct 6 17:21:49 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 6 17:21:49 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 6 17:21:49 storageqe-109 kernel: md/raid:md127: raid level 6 active with 4 out of 4 devices, algorithm 2 Oct 6 17:21:49 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 17:21:49 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 17:21:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:21:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:21:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:21:55 storageqe-109 kernel: md: md127: resync done. Oct 6 17:22:14 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 17:22:14 storageqe-109 kernel: md: md127 stopped. Oct 6 17:22:14 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 17:22:18 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:22:18 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:22:18 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:22:18 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_mdraid_properties_by_level[raid6-4-None] #### INFO: #### will start test_mdraid_properties_by_level[raid10-4-None] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:22:24 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:22:24 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid6-4-None] #### Oct 6 17:22:24 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid10-4-None] ##### Oct 6 17:22:24 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:22:31 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:22:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid10_0.img) Oct 6 17:22:31 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 6 17:22:31 storageqe-109 udisksd[5174]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid10_1.img) Oct 6 17:22:32 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 6 17:22:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop2 (backed by /home/loop_test_raid10_2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid10 INFO: raid name test_raid10 INFO: raid chunk 65536 INFO: raid bitmap None INFO: raid version None Oct 6 17:22:32 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 6 17:22:32 storageqe-109 udisksd[5174]: Set up loop device /dev/loop3 (backed by /home/loop_test_raid10_3.img) Oct 6 17:22:32 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 6 17:22:32 storageqe-109 INFO: raid level raid10 Oct 6 17:22:32 storageqe-109 INFO: raid name test_raid10 Oct 6 17:22:32 storageqe-109 INFO: raid chunk 65536 Oct 6 17:22:32 storageqe-109 INFO: raid bitmap None Oct 6 17:22:32 storageqe-109 INFO: raid version None Oct 6 17:22:32 storageqe-109 kernel: md/raid10:md127: not clean -- starting background reconstruction Oct 6 17:22:32 storageqe-109 kernel: md/raid10:md127: active with 4 out of 4 devices Oct 6 17:22:32 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 6 17:22:32 storageqe-109 kernel: md: resync of RAID array md127 Oct 6 17:22:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:22:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:22:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 6 17:22:42 storageqe-109 kernel: md: md127: resync done. Oct 6 17:23:01 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 6 17:23:01 storageqe-109 kernel: md: md127 stopped. Oct 6 17:23:02 storageqe-109 udisksd[5174]: No longer watching mdraid device 9:127 Oct 6 17:23:06 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop1 Oct 6 17:23:06 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop2 Oct 6 17:23:06 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 Oct 6 17:23:06 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop3 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_mdraid_properties_by_level[raid10-4-None] #### INFO: #### will start test_udisks2_nvme_ay_type_read_write_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:23:12 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:23:12 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid10-4-None] #### Oct 6 17:23:12 storageqe-109 INFO: #### will start test_udisks2_nvme_ay_type_read_write_operations ##### Oct 6 17:23:12 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_ay_type_read_write_operations #### INFO: #### will start test_udisks2_nvme_set_host_nqn ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:23:35 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:23:35 storageqe-109 INFO: #### END test_udisks2_nvme_ay_type_read_write_operations #### Oct 6 17:23:35 storageqe-109 INFO: #### will start test_udisks2_nvme_set_host_nqn ##### Oct 6 17:23:35 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_set_host_nqn #### INFO: #### will start test_udisks2_nvme_set_host_id ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:23:54 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:23:54 storageqe-109 INFO: #### END test_udisks2_nvme_set_host_nqn #### Oct 6 17:23:54 storageqe-109 INFO: #### will start test_udisks2_nvme_set_host_id ##### Oct 6 17:23:54 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_set_host_id #### INFO: #### will start test_udisks2_nvme_connect_tcp ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:24:13 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:24:13 storageqe-109 INFO: #### END test_udisks2_nvme_set_host_id #### Oct 6 17:24:13 storageqe-109 INFO: #### will start test_udisks2_nvme_connect_tcp ##### Oct 6 17:24:13 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:24:21 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2025-01.udisks2.test:nvme-tcp-mkpvdJFD Oct 6 17:24:21 storageqe-109 kernel: nvmet_tcp: enabling port 4440 (127.0.0.1:4440) Oct 6 17:24:21 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2025-01.udisks2.test:nvme-tcp-mkpvdJFD for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 6 17:24:21 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 6 17:24:21 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 6 17:24:21 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2025-01.udisks2.test:nvme-tcp-mkpvdJFD", addr 127.0.0.1:4440, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 6 17:24:41 storageqe-109 kernel: nvme nvme1: starting error recovery Oct 6 17:24:41 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 6 17:24:41 storageqe-109 kernel: nvme nvme1: Reconnecting in 10 seconds... Oct 6 17:24:42 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2025-01.udisks2.test:nvme-tcp-mkpvdJFD" Oct 6 17:24:42 storageqe-109 kernel: nvme nvme1: Property Set error: 880, offset 0x14 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_connect_tcp #### INFO: #### will start test_udisks2_nvme_comprehensive_workflow ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:24:53 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:24:53 storageqe-109 INFO: #### END test_udisks2_nvme_connect_tcp #### Oct 6 17:24:53 storageqe-109 INFO: #### will start test_udisks2_nvme_comprehensive_workflow ##### Oct 6 17:24:53 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:25:07 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2025-01.udisks2.workflow:target-hTgFqX Oct 6 17:25:07 storageqe-109 kernel: nvmet_tcp: enabling port 4450 (127.0.0.1:4450) Oct 6 17:25:10 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2025-01.udisks2.workflow:target-hTgFqX for NQN nqn.2025-01.udisks2.workflow:uuid:11111111-2222-3333-4444-555555555555. Oct 6 17:25:10 storageqe-109 kernel: nvme nvme1: creating 2 I/O queues. Oct 6 17:25:10 storageqe-109 kernel: nvme nvme1: mapped 2/0/0 default/read/poll queues. Oct 6 17:25:10 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2025-01.udisks2.workflow:target-hTgFqX", addr 127.0.0.1:4450, hostnqn: nqn.2025-01.udisks2.workflow:uuid:11111111-2222-3333-4444-555555555555 Oct 6 17:25:29 storageqe-109 kernel: nvme nvme1: starting error recovery Oct 6 17:25:29 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 6 17:25:29 storageqe-109 kernel: nvme nvme1: queue 1 socket state 11 Oct 6 17:25:29 storageqe-109 kernel: nvme nvme1: Reconnecting in 10 seconds... Oct 6 17:25:30 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2025-01.udisks2.workflow:target-hTgFqX" Oct 6 17:25:30 storageqe-109 kernel: nvme nvme1: Property Set error: 880, offset 0x14 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_comprehensive_workflow #### INFO: #### will start test_udisks2_nvme_connect_all_parameters ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:25:41 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:25:41 storageqe-109 INFO: #### END test_udisks2_nvme_comprehensive_workflow #### Oct 6 17:25:41 storageqe-109 INFO: #### will start test_udisks2_nvme_connect_all_parameters ##### Oct 6 17:25:41 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:25:49 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2025-01.udisks2.test:all-params-xELHhNwC Oct 6 17:25:49 storageqe-109 kernel: nvmet_tcp: enabling port 4460 (127.0.0.1:4460) Oct 6 17:25:52 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2025-01.udisks2.test:all-params-xELHhNwC for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 6 17:25:52 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 6 17:25:52 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 6 17:25:52 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2025-01.udisks2.test:all-params-xELHhNwC", addr 127.0.0.1:4460, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 6 17:26:11 storageqe-109 kernel: nvme nvme1: starting error recovery Oct 6 17:26:11 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 6 17:26:11 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 6 17:26:11 storageqe-109 kernel: nvme nvme1: queue 1 socket state 11 Oct 6 17:26:11 storageqe-109 kernel: nvme nvme1: Reconnecting in 10 seconds... Oct 6 17:26:12 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2025-01.udisks2.test:all-params-xELHhNwC" Oct 6 17:26:12 storageqe-109 kernel: nvme nvme1: Property Set error: 880, offset 0x14 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_connect_all_parameters #### INFO: #### will start test_udisks2_nvme_error_scenarios ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:26:21 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:26:21 storageqe-109 INFO: #### END test_udisks2_nvme_connect_all_parameters #### Oct 6 17:26:21 storageqe-109 INFO: #### will start test_udisks2_nvme_error_scenarios ##### Oct 6 17:26:21 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:26:28 storageqe-109 kernel: nvme_fabrics: unknown parameter or missing value 'nqn=' in ctrl creation request Oct 6 17:26:28 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:28 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:28 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:28 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:28 storageqe-109 kernel: nvme_fabrics: missing parameter 'transport=%s' Oct 6 17:26:28 storageqe-109 kernel: nvme_fabrics: no handler found for transport invalid. Oct 6 17:26:28 storageqe-109 kernel: nvme_fabrics: no handler found for transport udp. Oct 6 17:26:28 storageqe-109 kernel: nvme nvme1: rdma_resolve_addr failed (-19). Oct 6 17:26:28 storageqe-109 kernel: nvme_fabrics: missing parameter 'host_traddr=%s' Oct 6 17:26:28 storageqe-109 kernel: nvme nvme1: failed to create socket: -97 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -110 Oct 6 17:26:31 storageqe-109 kernel: nvme_tcp: malformed address passed: 127.0.0.1:99999 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme_tcp: malformed address passed: 127.0.0.1:-1 Oct 6 17:26:31 storageqe-109 kernel: nvme_tcp: malformed address passed: 127.0.0.1:invalid Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme_fabrics: found same hostnqn nqn.2014-08.org.nvmexpress:uuid:0f2ebd10-8378-46fe-a049-5c343d4007d4 but different hostid 4c4c4544-0039-5210-804d-c6c04f463534 Oct 6 17:26:31 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:31 storageqe-109 kernel: nvme_fabrics: found same hostid 0f2ebd10-8378-46fe-a049-5c343d4007d4 but different hostnqn nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 6 17:26:32 storageqe-109 kernel: nvme_fabrics: Invalid hostid invalid-uuid Oct 6 17:26:32 storageqe-109 kernel: nvme_tcp: malformed src address passed: 999.999.999.999 Oct 6 17:26:32 storageqe-109 kernel: nvme_tcp: invalid interface passed: nonexistent_interface Oct 6 17:26:32 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:32 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:32 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:32 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:32 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 Oct 6 17:26:32 storageqe-109 kernel: nvme nvme1: failed to connect socket: -111 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_error_scenarios #### INFO: #### will start test_udisks2_nvme_fabrics_interface_properties ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:27:01 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:27:01 storageqe-109 INFO: #### END test_udisks2_nvme_error_scenarios #### Oct 6 17:27:01 storageqe-109 INFO: #### will start test_udisks2_nvme_fabrics_interface_properties ##### Oct 6 17:27:01 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:27:10 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2025-01.fabrics.test:properties-kQmAbcOZ Oct 6 17:27:10 storageqe-109 kernel: nvmet_tcp: enabling port 4490 (127.0.0.1:4490) Oct 6 17:27:14 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2025-01.fabrics.test:properties-kQmAbcOZ for NQN nqn.2025-01.fabrics.test:uuid:fab11c51-0000-1111-2222-333344445555. Oct 6 17:27:14 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 6 17:27:14 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 6 17:27:14 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2025-01.fabrics.test:properties-kQmAbcOZ", addr 127.0.0.1:4490, hostnqn: nqn.2025-01.fabrics.test:uuid:fab11c51-0000-1111-2222-333344445555 Oct 6 17:27:34 storageqe-109 kernel: nvme nvme1: starting error recovery Oct 6 17:27:34 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 6 17:27:34 storageqe-109 kernel: nvme nvme1: queue 1 socket state 11 Oct 6 17:27:34 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 6 17:27:34 storageqe-109 kernel: nvme nvme1: Reconnecting in 10 seconds... Oct 6 17:27:35 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2025-01.fabrics.test:properties-kQmAbcOZ" Oct 6 17:27:35 storageqe-109 kernel: nvme nvme1: Property Set error: 880, offset 0x14 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_fabrics_interface_properties #### INFO: #### will start test_udisks2_nvme_multipath_namespace_persistence ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:27:47 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:27:47 storageqe-109 INFO: #### END test_udisks2_nvme_fabrics_interface_properties #### Oct 6 17:27:47 storageqe-109 INFO: #### will start test_udisks2_nvme_multipath_namespace_persistence ##### Oct 6 17:27:47 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_multipath_namespace_persistence #### Oct 6 17:28:05 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:28:05 storageqe-109 INFO: #### END test_udisks2_nvme_multipath_namespace_persistence #### INFO: #### will start test_udisks2_nvme_multipath_controller_failover ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:28:05 storageqe-109 INFO: #### will start test_udisks2_nvme_multipath_controller_failover ##### Oct 6 17:28:05 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:28:12 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2025-01.multipath.test:controller-failover-vLdKONHz-ctrl1 Oct 6 17:28:12 storageqe-109 kernel: nvmet_tcp: enabling port 4480 (127.0.0.1:4480) Oct 6 17:28:15 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2025-01.multipath.test:controller-failover-vLdKONHz-ctrl1 for NQN nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534. Oct 6 17:28:15 storageqe-109 kernel: nvme nvme1: creating 4 I/O queues. Oct 6 17:28:15 storageqe-109 kernel: nvme nvme1: mapped 4/0/0 default/read/poll queues. Oct 6 17:28:15 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2025-01.multipath.test:controller-failover-vLdKONHz-ctrl1", addr 127.0.0.1:4480, hostnqn: nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 6 17:28:35 storageqe-109 kernel: nvme nvme1: starting error recovery Oct 6 17:28:35 storageqe-109 kernel: nvme nvme1: Reconnecting in 10 seconds... Oct 6 17:28:36 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2025-01.multipath.test:controller-failover-vLdKONHz-ctrl1" Oct 6 17:28:36 storageqe-109 kernel: nvme nvme1: Property Set error: 880, offset 0x14 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisks2_nvme_multipath_controller_failover #### INFO: #### will start test_udisksctl_invalid_commands ##### Oct 6 17:28:45 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:28:45 storageqe-109 INFO: #### END test_udisks2_nvme_multipath_controller_failover #### Oct 6 17:28:45 storageqe-109 INFO: #### will start test_udisksctl_invalid_commands ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:28:45 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_invalid_commands #### INFO: #### will start test_udisksctl_missing_required_parameters ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:28:55 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:28:55 storageqe-109 INFO: #### END test_udisksctl_invalid_commands #### Oct 6 17:28:55 storageqe-109 INFO: #### will start test_udisksctl_missing_required_parameters ##### Oct 6 17:28:55 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_missing_required_parameters #### INFO: #### will start test_udisksctl_invalid_parameter_values ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:05 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:05 storageqe-109 INFO: #### END test_udisksctl_missing_required_parameters #### Oct 6 17:29:05 storageqe-109 INFO: #### will start test_udisksctl_invalid_parameter_values ##### Oct 6 17:29:05 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_invalid_parameter_values #### INFO: #### will start test_udisksctl_invalid_option_combinations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:16 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:16 storageqe-109 INFO: #### END test_udisksctl_invalid_parameter_values #### Oct 6 17:29:16 storageqe-109 INFO: #### will start test_udisksctl_invalid_option_combinations ##### Oct 6 17:29:16 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_invalid_option_combinations #### INFO: #### will start test_udisksctl_malformed_device_paths ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:26 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:26 storageqe-109 INFO: #### END test_udisksctl_invalid_option_combinations #### Oct 6 17:29:26 storageqe-109 INFO: #### will start test_udisksctl_malformed_device_paths ##### Oct 6 17:29:26 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_malformed_device_paths #### INFO: #### will start test_udisksctl_resource_limits ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:37 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:37 storageqe-109 INFO: #### END test_udisksctl_malformed_device_paths #### Oct 6 17:29:37 storageqe-109 INFO: #### will start test_udisksctl_resource_limits ##### Oct 6 17:29:37 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:42 storageqe-109 kernel: loop0: detected capacity change from 0 to 209715200 Oct 6 17:29:42 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /tmp/udisks_large_test.img) Oct 6 17:29:42 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_large_test.img) Oct 6 17:29:42 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_resource_limits #### INFO: #### will start test_udisksctl_concurrent_error_operations ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:47 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:47 storageqe-109 INFO: #### END test_udisksctl_resource_limits #### Oct 6 17:29:47 storageqe-109 INFO: #### will start test_udisksctl_concurrent_error_operations ##### Oct 6 17:29:47 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_concurrent_error_operations #### INFO: #### will start test_udisksctl_permission_errors ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:57 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:29:57 storageqe-109 INFO: #### END test_udisksctl_concurrent_error_operations #### Oct 6 17:29:57 storageqe-109 INFO: #### will start test_udisksctl_permission_errors ##### Oct 6 17:29:57 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_permission_errors #### INFO: #### will start test_udisksctl_signal_interruption ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:07 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:07 storageqe-109 INFO: #### END test_udisksctl_permission_errors #### Oct 6 17:30:08 storageqe-109 INFO: #### will start test_udisksctl_signal_interruption ##### Oct 6 17:30:08 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_signal_interruption #### INFO: #### will start test_udisksctl_environment_variable_injection ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:18 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:18 storageqe-109 INFO: #### END test_udisksctl_signal_interruption #### Oct 6 17:30:18 storageqe-109 INFO: #### will start test_udisksctl_environment_variable_injection ##### Oct 6 17:30:18 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_environment_variable_injection #### INFO: #### will start test_udisksctl_dbus_error_handling ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:28 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:28 storageqe-109 INFO: #### END test_udisksctl_environment_variable_injection #### Oct 6 17:30:28 storageqe-109 INFO: #### will start test_udisksctl_dbus_error_handling ##### Oct 6 17:30:28 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_dbus_error_handling #### INFO: #### will start test_udisksctl_memory_stress ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:38 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:38 storageqe-109 INFO: #### END test_udisksctl_dbus_error_handling #### Oct 6 17:30:38 storageqe-109 INFO: #### will start test_udisksctl_memory_stress ##### Oct 6 17:30:38 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_udisksctl_memory_stress #### INFO: #### will start test_partition_table_and_partition_lifecycle ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:49 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:30:49 storageqe-109 INFO: #### END test_udisksctl_memory_stress #### Oct 6 17:30:49 storageqe-109 INFO: #### will start test_partition_table_and_partition_lifecycle ##### Oct 6 17:30:49 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: Creating GPT partition table... Oct 6 17:30:56 storageqe-109 INFO: Creating GPT partition table... Oct 6 17:30:56 storageqe-109 kernel: sdd: INFO: Creating a new partition... Oct 6 17:30:59 storageqe-109 INFO: Creating a new partition... INFO: Validating PartitionTable properties... INFO: Validating Partition properties... INFO: Testing SetName, SetType, SetFlags, and SetUUID... Oct 6 17:31:04 storageqe-109 INFO: Validating PartitionTable properties... Oct 6 17:31:04 storageqe-109 INFO: Validating Partition properties... Oct 6 17:31:04 storageqe-109 INFO: Testing SetName, SetType, SetFlags, and SetUUID... INFO: Testing Resize... Oct 6 17:31:10 storageqe-109 INFO: Testing Resize... Oct 6 17:31:10 storageqe-109 kernel: sdd: sdd1 INFO: Testing Delete... Oct 6 17:31:14 storageqe-109 INFO: Testing Delete... Oct 6 17:31:14 storageqe-109 kernel: sdd: INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### INFO: #### END test_partition_table_and_partition_lifecycle #### INFO: #### will start test_physical_volume_properties ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### Oct 6 17:31:22 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### Oct 6 17:31:22 storageqe-109 INFO: #### END test_partition_table_and_partition_lifecycle #### Oct 6 17:31:22 storageqe-109 INFO: #### will start test_physical_volume_properties ##### Oct 6 17:31:22 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### INFO: Creating VG 'udisks_test_pv_vg' on device /dev/sde to create a PV Oct 6 17:31:27 storageqe-109 INFO: Creating VG 'udisks_test_pv_vg' on device /dev/sde to create a PV INFO: Fetching all properties for PhysicalVolume interface... INFO: Checking property 'Size'... INFO: Checking property 'FreeSize'... INFO: Checking property 'VolumeGroup'... INFO: Checking specific property values... INFO: Cleaning up Volume Group 'udisks_test_pv_vg' Oct 6 17:31:33 storageqe-109 INFO: Fetching all properties for PhysicalVolume interface... Oct 6 17:31:33 storageqe-109 INFO: Checking property 'Size'... Oct 6 17:31:33 storageqe-109 INFO: Checking property 'FreeSize'... Oct 6 17:31:33 storageqe-109 INFO: Checking property 'VolumeGroup'... Oct 6 17:31:33 storageqe-109 INFO: Checking specific property values... Oct 6 17:31:33 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_pv_vg' INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_physical_volume_properties #### INFO: #### will start test_invalid_filesystem_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:31:39 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:31:39 storageqe-109 INFO: #### END test_physical_volume_properties #### Oct 6 17:31:39 storageqe-109 INFO: #### will start test_invalid_filesystem_operations ##### Oct 6 17:31:39 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_invalid_filesystem_operations #### INFO: #### will start test_invalid_partition_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:31:49 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:31:49 storageqe-109 INFO: #### END test_invalid_filesystem_operations #### Oct 6 17:31:49 storageqe-109 INFO: #### will start test_invalid_partition_operations ##### Oct 6 17:31:49 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:31:54 storageqe-109 kernel: sde: INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_invalid_partition_operations #### INFO: #### will start test_invalid_lvm_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:00 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:00 storageqe-109 INFO: #### END test_invalid_partition_operations #### Oct 6 17:32:00 storageqe-109 INFO: #### will start test_invalid_lvm_operations ##### Oct 6 17:32:00 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_invalid_lvm_operations #### INFO: #### will start test_invalid_luks_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:10 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:10 storageqe-109 INFO: #### END test_invalid_lvm_operations #### Oct 6 17:32:10 storageqe-109 INFO: #### will start test_invalid_luks_operations ##### Oct 6 17:32:10 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_invalid_luks_operations #### INFO: #### will start test_invalid_mount_operations ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:20 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:20 storageqe-109 INFO: #### END test_invalid_luks_operations #### Oct 6 17:32:20 storageqe-109 INFO: #### will start test_invalid_mount_operations ##### Oct 6 17:32:20 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_invalid_mount_operations #### INFO: #### will start test_empty_string_parameters ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:30 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:30 storageqe-109 INFO: #### END test_invalid_mount_operations #### Oct 6 17:32:30 storageqe-109 INFO: #### will start test_empty_string_parameters ##### Oct 6 17:32:30 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_empty_string_parameters #### INFO: #### will start test_basic_cleanup_after_errors ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:40 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:40 storageqe-109 INFO: #### END test_empty_string_parameters #### Oct 6 17:32:40 storageqe-109 INFO: #### will start test_basic_cleanup_after_errors ##### Oct 6 17:32:40 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:45 storageqe-109 kernel: sde: Oct 6 17:32:47 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 6 17:32:47 storageqe-109 udisksd[5174]: Set up loop device /dev/loop0 (backed by /home/tmpyrixg4m0.img) Oct 6 17:32:47 storageqe-109 udisksd[5174]: Deleted loop device /dev/loop0 (was backed by /home/tmpyrixg4m0.img) Oct 6 17:32:47 storageqe-109 udisksd[5174]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_basic_cleanup_after_errors #### INFO: #### will start test_dbus_connection_errors ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:52 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:32:52 storageqe-109 INFO: #### END test_basic_cleanup_after_errors #### Oct 6 17:32:52 storageqe-109 INFO: #### will start test_dbus_connection_errors ##### Oct 6 17:32:52 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dbus_connection_errors #### INFO: #### will start test_error_message_quality ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:33:02 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:33:02 storageqe-109 INFO: #### END test_dbus_connection_errors #### Oct 6 17:33:02 storageqe-109 INFO: #### will start test_error_message_quality ##### Oct 6 17:33:02 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_error_message_quality #### INFO: #### will start test_thin_pool_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:33:12 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### Oct 6 17:33:12 storageqe-109 INFO: #### END test_error_message_quality #### Oct 6 17:33:12 storageqe-109 INFO: #### will start test_thin_pool_properties ##### Oct 6 17:33:12 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde'] #### INFO: Creating VG 'udisks_test_thin_vg' on device /dev/nvme0n1 Oct 6 17:33:17 storageqe-109 INFO: Creating VG 'udisks_test_thin_vg' on device /dev/nvme0n1 INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 6 17:33:21 storageqe-109 INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 6 17:33:23 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Validating thin pool properties... INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 6 17:33:30 storageqe-109 INFO: Validating thin pool properties... Oct 6 17:33:30 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 6 17:33:30 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 6 17:33:30 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 6 17:33:31 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 6 17:33:31 storageqe-109 INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down INFO: #### after available_disks ['/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_thin_pool_properties #### INFO: #### will start test_thin_volume_properties ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 6 17:33:37 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 6 17:33:37 storageqe-109 INFO: #### END test_thin_pool_properties #### Oct 6 17:33:37 storageqe-109 INFO: #### will start test_thin_volume_properties ##### Oct 6 17:33:37 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdc Oct 6 17:33:42 storageqe-109 INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdc INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 6 17:33:45 storageqe-109 INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 6 17:33:47 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 6 17:33:47 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Creating thin volume 'udisks_test_thin_lv' in pool 'udisks_test_thin_pool' Oct 6 17:33:54 storageqe-109 INFO: Creating thin volume 'udisks_test_thin_lv' in pool 'udisks_test_thin_pool' Oct 6 17:33:56 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 6 17:33:57 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 6 17:33:57 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. INFO: Validating thin volume properties... INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 6 17:34:03 storageqe-109 INFO: Validating thin volume properties... Oct 6 17:34:03 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 6 17:34:03 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 6 17:34:03 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 6 17:34:03 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 6 17:34:03 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 6 17:34:04 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 6 17:34:04 storageqe-109 INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc'] #### INFO: #### END test_thin_volume_properties #### INFO: #### will start test_thin_pool_cleanup_verification ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc'] #### Oct 6 17:34:09 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc'] #### Oct 6 17:34:09 storageqe-109 INFO: #### END test_thin_volume_properties #### Oct 6 17:34:09 storageqe-109 INFO: #### will start test_thin_pool_cleanup_verification ##### Oct 6 17:34:09 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc'] #### INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdb Oct 6 17:34:14 storageqe-109 INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdb INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 6 17:34:18 storageqe-109 INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 6 17:34:19 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 6 17:34:19 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Testing thin pool cleanup verification... INFO: Thin pool objects verified successfully INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 6 17:34:27 storageqe-109 INFO: Testing thin pool cleanup verification... Oct 6 17:34:27 storageqe-109 INFO: Thin pool objects verified successfully Oct 6 17:34:27 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 6 17:34:27 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 6 17:34:27 storageqe-109 dmeventd[1119988]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 6 17:34:28 storageqe-109 dmeventd[1119988]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 6 17:34:28 storageqe-109 INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 6 17:34:28 storageqe-109 INFO: Verifying VG cleanup... INFO: Verifying VG cleanup... INFO: VG udisks_test_thin_vg successfully removed Oct 6 17:34:30 storageqe-109 INFO: VG udisks_test_thin_vg successfully removed INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: #### END test_thin_pool_cleanup_verification #### INFO: #### will start test_vdovolume_properties ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:34:35 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### Oct 6 17:34:35 storageqe-109 INFO: #### END test_thin_pool_cleanup_verification #### Oct 6 17:34:35 storageqe-109 INFO: #### will start test_vdovolume_properties ##### Oct 6 17:34:35 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb'] #### INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/sdd'] Oct 6 17:34:40 storageqe-109 INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/sdd'] INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' Oct 6 17:34:41 storageqe-109 INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' Oct 6 17:34:42 storageqe-109 UDS/vdoformat[1168909]: INFO (vdoformat/1168909) Using 2 indexing zones for concurrency. Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo21:lvm: table line: V4 /dev/dm-3 193100800 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo21:lvm: loading device '253:4' Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo21:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo21:lvm: starting device '253:4' Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo: dm_vdo21:physQ0: VDO commencing normal operation Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo: dm_vdo21:journa: Setting UDS index target state to online Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo: dm_vdo21:dedupe: creating index: 253:3 Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo21:lvm: device '253:4' started Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo: dm_vdo21:dedupe: Using 2 indexing zones for concurrency. Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo21:lvm: resuming device '253:4' Oct 6 17:34:42 storageqe-109 kernel: device-mapper: vdo21:lvm: device '253:4' resumed Oct 6 17:34:42 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Fetching all properties for VDOVolume interface... INFO: Checking property 'VDOPool'... INFO: Checking property 'OperatingMode'... INFO: Checking property 'CompressionState'... INFO: Checking property 'IndexState'... INFO: Checking property 'UsedSize'... INFO: Checking property 'Compression'... INFO: Checking property 'Deduplication'... INFO: Checking initial property values... INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 6 17:34:47 storageqe-109 INFO: Fetching all properties for VDOVolume interface... Oct 6 17:34:47 storageqe-109 INFO: Checking property 'VDOPool'... Oct 6 17:34:47 storageqe-109 INFO: Checking property 'OperatingMode'... Oct 6 17:34:47 storageqe-109 INFO: Checking property 'CompressionState'... Oct 6 17:34:47 storageqe-109 INFO: Checking property 'IndexState'... Oct 6 17:34:47 storageqe-109 INFO: Checking property 'UsedSize'... Oct 6 17:34:47 storageqe-109 INFO: Checking property 'Compression'... Oct 6 17:34:47 storageqe-109 INFO: Checking property 'Deduplication'... Oct 6 17:34:47 storageqe-109 INFO: Checking initial property values... Oct 6 17:34:47 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 6 17:34:48 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:34:48 storageqe-109 kernel: device-mapper: vdo21:lvm: suspending device '253:4' Oct 6 17:34:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo21:journa: beginning save (vcn 18446744073709551615) Oct 6 17:34:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo21:journa: finished save (vcn 18446744073709551615) Oct 6 17:34:48 storageqe-109 kernel: device-mapper: vdo21:lvm: device '253:4' suspended Oct 6 17:34:48 storageqe-109 kernel: device-mapper: vdo21:lvm: stopping device '253:4' Oct 6 17:34:49 storageqe-109 kernel: device-mapper: vdo21:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### INFO: #### END test_vdovolume_properties #### INFO: #### will start test_vdovolume_methods ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### Oct 6 17:34:54 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### Oct 6 17:34:54 storageqe-109 INFO: #### END test_vdovolume_properties #### Oct 6 17:34:54 storageqe-109 INFO: #### will start test_vdovolume_methods ##### Oct 6 17:34:54 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdc', '/dev/sdb', '/dev/sdd'] #### INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/sde', '/dev/nvme0n1'] Oct 6 17:34:59 storageqe-109 INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/sde', '/dev/nvme0n1'] INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' Oct 6 17:34:59 storageqe-109 INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' Oct 6 17:35:00 storageqe-109 UDS/vdoformat[1169207]: INFO (vdoformat/1169207) Using 2 indexing zones for concurrency. Oct 6 17:35:00 storageqe-109 kernel: device-mapper: vdo22:lvm: table line: V4 /dev/dm-3 505684992 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:35:00 storageqe-109 kernel: device-mapper: vdo22:lvm: loading device '253:4' Oct 6 17:35:00 storageqe-109 kernel: device-mapper: vdo22:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 6 17:35:00 storageqe-109 kernel: device-mapper: vdo22:lvm: starting device '253:4' Oct 6 17:35:01 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:physQ0: VDO commencing normal operation Oct 6 17:35:01 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:journa: Setting UDS index target state to online Oct 6 17:35:01 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:dedupe: creating index: 253:3 Oct 6 17:35:01 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' started Oct 6 17:35:01 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:dedupe: Using 2 indexing zones for concurrency. Oct 6 17:35:01 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:01 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:01 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing EnableDeduplication/EnableCompression... Oct 6 17:35:06 storageqe-109 INFO: Testing EnableDeduplication/EnableCompression... Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: table line: V4 /dev/dm-3 505684992 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: preparing to modify device '253:4' Oct 6 17:35:06 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:dedupe: beginning save (vcn 18446744073709551615) Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:packer: compression is enabled Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:dedupe: finished save (vcn 18446744073709551615) Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:06 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: table line: V4 /dev/dm-3 505684992 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: preparing to modify device '253:4' Oct 6 17:35:06 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:packer: compression is disabled Oct 6 17:35:06 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:06 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: table line: V4 /dev/dm-3 505684992 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: preparing to modify device '253:4' Oct 6 17:35:10 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:dedupe: loading or rebuilding index: 253:3 Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:packer: compression is disabled Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:dedupe: Using 2 indexing zones for concurrency. Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:10 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:dedupe: loaded index from chapter 0 through chapter 0 Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: table line: V4 /dev/dm-3 505684992 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: preparing to modify device '253:4' Oct 6 17:35:10 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:packer: compression is enabled Oct 6 17:35:10 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:10 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing ResizeLogical... Oct 6 17:35:13 storageqe-109 INFO: Testing ResizeLogical... Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: table line: V4 /dev/dm-3 505684992 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: preparing to modify device '253:4' Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: Preparing to resize logical to 5077821696 Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: Done preparing to resize logical Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: Resizing logical to 5077821696 Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: Logical blocks now 5077821696 Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:packer: compression is enabled Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:14 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:packer: compression is enabled Oct 6 17:35:14 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:14 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing ResizePhysical... Oct 6 17:35:16 storageqe-109 INFO: Testing ResizePhysical... Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: table line: V4 /dev/dm-3 506209280 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: preparing to modify device '253:4' Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: Preparing to resize physical to 506209280 Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: Done preparing to resize physical Oct 6 17:35:18 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: resuming device '253:4' Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: Physical block count was 505684992, now 506209280 Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo22:packer: compression is enabled Oct 6 17:35:18 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' resumed Oct 6 17:35:18 storageqe-109 dmeventd[1119988]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing GetStatistics... INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 6 17:35:24 storageqe-109 INFO: Testing GetStatistics... Oct 6 17:35:24 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 6 17:35:25 storageqe-109 dmeventd[1119988]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 6 17:35:25 storageqe-109 kernel: device-mapper: vdo22:lvm: suspending device '253:4' Oct 6 17:35:25 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' suspended Oct 6 17:35:25 storageqe-109 kernel: device-mapper: vdo22:lvm: stopping device '253:4' Oct 6 17:35:26 storageqe-109 kernel: device-mapper: vdo22:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_vdovolume_methods #### Oct 6 17:35:31 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdb', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 6 17:35:31 storageqe-109 INFO: #### END test_vdovolume_methods #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 17:35:33 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 6 17:35:33 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 6 17:35:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 6 17:35:45 storageqe-109 systemd[1]: session-4.scope: Deactivated successfully. Oct 6 17:35:45 storageqe-109 systemd[1]: session-4.scope: Consumed 8h 9min 56.504s CPU time, 13.9G memory peak, 304M memory swap peak. Oct 6 17:35:45 storageqe-109 systemd-logind[1011]: Removed session 4. Oct 6 17:36:03 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 6 17:40:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 17:40:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 17:40:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 18:29:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 18:29:40 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 18:29:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 18:29:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 18:29:40 storageqe-109 dnf[1170024]: Updating Subscription Management repositories. Oct 6 18:29:40 storageqe-109 dnf[1170024]: Unable to read consumer identity Oct 6 18:29:40 storageqe-109 dnf[1170024]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 18:29:40 storageqe-109 dnf[1170024]: Metadata cache refreshed recently. Oct 6 18:29:41 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 18:29:41 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 18:35:26 storageqe-109 dmeventd[1119988]: dmeventd was idle for 3600 second(s), exiting. Oct 6 18:35:26 storageqe-109 dmeventd[1119988]: dmeventd shutting down. Oct 6 18:35:26 storageqe-109 systemd[1]: dm-event.service: Deactivated successfully. Oct 6 19:38:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 19:38:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 19:38:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 20:00:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 20:00:53 storageqe-109 dnf[1170127]: Updating Subscription Management repositories. Oct 6 20:00:53 storageqe-109 dnf[1170127]: Unable to read consumer identity Oct 6 20:00:53 storageqe-109 dnf[1170127]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 20:00:53 storageqe-109 dnf[1170127]: Metadata cache refreshed recently. Oct 6 20:00:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 20:00:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 20:03:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 20:03:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 20:03:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 20:37:31 storageqe-109 NetworkManager[995]: [1759797451.6735] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 6 20:37:31 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 6 20:37:31 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 6 20:37:41 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 6 20:43:53 storageqe-109 systemd[1078]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories... Oct 6 20:43:53 storageqe-109 systemd[1078]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories. Oct 6 20:52:36 storageqe-109 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Oct 6 20:52:36 storageqe-109 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Oct 6 20:52:36 storageqe-109 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Oct 6 21:42:46 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 21:42:46 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 21:42:46 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 21:59:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 21:59:53 storageqe-109 dnf[1170309]: Updating Subscription Management repositories. Oct 6 21:59:53 storageqe-109 dnf[1170309]: Unable to read consumer identity Oct 6 21:59:53 storageqe-109 dnf[1170309]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 21:59:53 storageqe-109 dnf[1170309]: beaker-AppStream 533 kB/s | 2.8 kB 00:00 Oct 6 21:59:53 storageqe-109 dnf[1170309]: beaker-AppStream-debuginfo 506 kB/s | 1.5 kB 00:00 Oct 6 21:59:53 storageqe-109 dnf[1170309]: beaker-BaseOS 773 kB/s | 2.7 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-BaseOS-debuginfo 521 kB/s | 1.5 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-CRB 680 kB/s | 2.7 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-CRB-debuginfo 522 kB/s | 1.5 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-HighAvailability 838 kB/s | 2.8 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-HighAvailability-debuginfo 514 kB/s | 1.5 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-NFV 851 kB/s | 2.7 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-NFV-debuginfo 363 kB/s | 1.5 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-RT 824 kB/s | 2.7 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-RT-debuginfo 531 kB/s | 1.5 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-SAP 765 kB/s | 2.7 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-SAP-debuginfo 443 kB/s | 1.5 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-SAPHANA 876 kB/s | 2.7 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: beaker-SAPHANA-debuginfo 623 kB/s | 1.5 kB 00:00 Oct 6 21:59:54 storageqe-109 dnf[1170309]: Beaker Client - RedHatEnterpriseLinux10 1.6 kB/s | 1.3 kB 00:00 Oct 6 21:59:55 storageqe-109 dnf[1170309]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 6 21:59:55 storageqe-109 dnf[1170309]: Google Cloud CLI 3.9 kB/s | 1.4 kB 00:00 Oct 6 21:59:56 storageqe-109 dnf[1170309]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 6 21:59:57 storageqe-109 dnf[1170309]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 6 21:59:58 storageqe-109 dnf[1170309]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 6 21:59:58 storageqe-109 dnf[1170309]: Metadata cache created. Oct 6 21:59:58 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 21:59:58 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 21:59:58 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 331ms CPU time, 70.5M memory peak. Oct 6 22:27:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 22:27:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 22:27:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 6 23:35:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 6 23:35:53 storageqe-109 dnf[1170458]: Updating Subscription Management repositories. Oct 6 23:35:53 storageqe-109 dnf[1170458]: Unable to read consumer identity Oct 6 23:35:53 storageqe-109 dnf[1170458]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 6 23:35:53 storageqe-109 dnf[1170458]: Metadata cache refreshed recently. Oct 6 23:35:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 6 23:35:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 6 23:38:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 6 23:38:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 6 23:38:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 00:00:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 00:00:53 storageqe-109 systemd[1]: Starting unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound... Oct 7 00:00:53 storageqe-109 systemd[1]: unbound-anchor.service: Deactivated successfully. Oct 7 00:00:53 storageqe-109 systemd[1]: Finished unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound. Oct 7 00:00:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 00:00:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 00:18:52 storageqe-109 systemd[1]: Starting logrotate.service - Rotate log files... Oct 7 00:18:52 storageqe-109 systemd[1]: logrotate.service: Deactivated successfully. Oct 7 00:18:52 storageqe-109 systemd[1]: Finished logrotate.service - Rotate log files. Oct 7 00:56:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 00:56:53 storageqe-109 dnf[1170569]: Updating Subscription Management repositories. Oct 7 00:56:53 storageqe-109 dnf[1170569]: Unable to read consumer identity Oct 7 00:56:53 storageqe-109 dnf[1170569]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 00:56:53 storageqe-109 dnf[1170569]: Metadata cache refreshed recently. Oct 7 00:56:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 00:56:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 01:40:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 01:40:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 01:40:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 02:03:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 02:03:53 storageqe-109 dnf[1170662]: Updating Subscription Management repositories. Oct 7 02:03:53 storageqe-109 dnf[1170662]: Unable to read consumer identity Oct 7 02:03:53 storageqe-109 dnf[1170662]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 02:03:53 storageqe-109 dnf[1170662]: beaker-AppStream 491 kB/s | 2.8 kB 00:00 Oct 7 02:03:53 storageqe-109 dnf[1170662]: beaker-AppStream-debuginfo 508 kB/s | 1.5 kB 00:00 Oct 7 02:03:53 storageqe-109 dnf[1170662]: beaker-BaseOS 944 kB/s | 2.7 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-BaseOS-debuginfo 458 kB/s | 1.5 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-CRB 682 kB/s | 2.7 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-CRB-debuginfo 456 kB/s | 1.5 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-HighAvailability 730 kB/s | 2.8 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-HighAvailability-debuginfo 510 kB/s | 1.5 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-NFV 773 kB/s | 2.7 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-NFV-debuginfo 467 kB/s | 1.5 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-RT 754 kB/s | 2.7 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-RT-debuginfo 459 kB/s | 1.5 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-SAP 732 kB/s | 2.7 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-SAP-debuginfo 411 kB/s | 1.5 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-SAPHANA 670 kB/s | 2.7 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: beaker-SAPHANA-debuginfo 479 kB/s | 1.5 kB 00:00 Oct 7 02:03:54 storageqe-109 dnf[1170662]: Beaker Client - RedHatEnterpriseLinux10 1.6 kB/s | 1.3 kB 00:00 Oct 7 02:03:55 storageqe-109 dnf[1170662]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 7 02:03:55 storageqe-109 dnf[1170662]: Google Cloud CLI 3.7 kB/s | 1.4 kB 00:00 Oct 7 02:03:56 storageqe-109 dnf[1170662]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:00 Oct 7 02:03:57 storageqe-109 dnf[1170662]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 7 02:03:58 storageqe-109 dnf[1170662]: Storage-QE 1.9 kB/s | 951 B 00:00 Oct 7 02:03:58 storageqe-109 dnf[1170662]: Metadata cache created. Oct 7 02:03:58 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 02:03:58 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 02:14:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 02:14:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 02:14:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 03:32:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 03:32:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 03:32:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 03:47:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 03:47:53 storageqe-109 dnf[1170825]: Updating Subscription Management repositories. Oct 7 03:47:53 storageqe-109 dnf[1170825]: Unable to read consumer identity Oct 7 03:47:53 storageqe-109 dnf[1170825]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 03:47:53 storageqe-109 dnf[1170825]: Metadata cache refreshed recently. Oct 7 03:47:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 03:47:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 04:01:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 04:01:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 04:01:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 05:17:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 05:17:53 storageqe-109 dnf[1170932]: Updating Subscription Management repositories. Oct 7 05:17:53 storageqe-109 dnf[1170932]: Unable to read consumer identity Oct 7 05:17:53 storageqe-109 dnf[1170932]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 05:17:53 storageqe-109 dnf[1170932]: beaker-AppStream 521 kB/s | 2.8 kB 00:00 Oct 7 05:17:53 storageqe-109 dnf[1170932]: beaker-AppStream-debuginfo 513 kB/s | 1.5 kB 00:00 Oct 7 05:17:53 storageqe-109 dnf[1170932]: beaker-BaseOS 931 kB/s | 2.7 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-BaseOS-debuginfo 359 kB/s | 1.5 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-CRB 754 kB/s | 2.7 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-CRB-debuginfo 487 kB/s | 1.5 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-HighAvailability 796 kB/s | 2.8 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-HighAvailability-debuginfo 591 kB/s | 1.5 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-NFV 780 kB/s | 2.7 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-NFV-debuginfo 499 kB/s | 1.5 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-RT 796 kB/s | 2.7 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-RT-debuginfo 502 kB/s | 1.5 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-SAP 714 kB/s | 2.7 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-SAP-debuginfo 522 kB/s | 1.5 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-SAPHANA 838 kB/s | 2.7 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: beaker-SAPHANA-debuginfo 537 kB/s | 1.5 kB 00:00 Oct 7 05:17:54 storageqe-109 dnf[1170932]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 7 05:17:55 storageqe-109 dnf[1170932]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 7 05:17:55 storageqe-109 dnf[1170932]: Google Cloud CLI 3.5 kB/s | 1.4 kB 00:00 Oct 7 05:17:56 storageqe-109 dnf[1170932]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 7 05:17:57 storageqe-109 dnf[1170932]: repo14 2.9 kB/s | 2.3 kB 00:00 Oct 7 05:17:57 storageqe-109 dnf[1170932]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 7 05:17:57 storageqe-109 dnf[1170932]: Metadata cache created. Oct 7 05:17:57 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 05:17:57 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 05:51:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 05:51:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 05:51:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 06:19:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 06:19:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 06:19:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 06:32:29 storageqe-109 systemd-logind[1011]: New session 6 of user root. Oct 7 06:32:29 storageqe-109 systemd[1]: Started session-6.scope - Session 6 of User root. Oct 7 06:32:29 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 06:32:29 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 06:32:59 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 06:38:42 storageqe-109 systemd[1]: Started tangd@16-10.73.194.89:80-10.2.32.56:56308.service - Tang Server (10.2.32.56:56308). Oct 7 06:38:42 storageqe-109 tangd[1171125]: 10.2.32.56 GET /log => 404 (../src/http.c:128) Oct 7 06:39:06 storageqe-109 systemd[1]: Starting httpd.service - The Apache HTTP Server... Oct 7 06:39:06 storageqe-109 (httpd)[1171130]: httpd.service: Referenced but unset environment variable evaluates to an empty string: OPTIONS Oct 7 06:39:06 storageqe-109 httpd[1171130]: Server configured, listening on: port 8080 Oct 7 06:39:06 storageqe-109 systemd[1]: Started httpd.service - The Apache HTTP Server. Oct 7 06:39:09 storageqe-109 tangd[1171125]: 10.2.32.56 GET /log => 404 (../src/http.c:128) Oct 7 06:40:09 storageqe-109 systemd[1]: tangd@16-10.73.194.89:80-10.2.32.56:56308.service: Deactivated successfully. Oct 7 06:41:05 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 06:41:06 storageqe-109 dnf[1171314]: Updating Subscription Management repositories. Oct 7 06:41:06 storageqe-109 dnf[1171314]: Unable to read consumer identity Oct 7 06:41:06 storageqe-109 dnf[1171314]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 06:41:06 storageqe-109 dnf[1171314]: Metadata cache refreshed recently. Oct 7 06:41:06 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 06:41:06 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 07:25:28 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 07:25:28 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 07:25:28 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 08:07:51 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 08:07:51 storageqe-109 dnf[1171414]: Updating Subscription Management repositories. Oct 7 08:07:51 storageqe-109 dnf[1171414]: Unable to read consumer identity Oct 7 08:07:51 storageqe-109 dnf[1171414]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 08:07:51 storageqe-109 dnf[1171414]: Metadata cache refreshed recently. Oct 7 08:07:51 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 08:07:51 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 08:08:51 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 08:08:51 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 08:08:51 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 08:37:31 storageqe-109 NetworkManager[995]: [1759840651.6734] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 7 08:37:31 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 7 08:37:31 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 7 08:37:41 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 7 09:04:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 09:04:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 09:04:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 09:22:40 storageqe-109 systemd-logind[1011]: New session 7 of user root. Oct 7 09:22:40 storageqe-109 systemd[1]: Started session-7.scope - Session 7 of User root. Oct 7 09:22:40 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:22:40 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:23:10 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:25:00 storageqe-109 systemd-logind[1011]: New session 8 of user root. Oct 7 09:25:00 storageqe-109 systemd[1]: Started session-8.scope - Session 8 of User root. Oct 7 09:25:00 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:25:00 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:25:13 storageqe-109 systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 1171655 (claude) Oct 7 09:25:13 storageqe-109 systemd[1]: Mounting proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System... Oct 7 09:25:13 storageqe-109 systemd[1]: Mounted proc-sys-fs-binfmt_misc.mount - Arbitrary Executable File Formats File System. Oct 7 09:25:41 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:27:22 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:27:22 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:28:31 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:30:46 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:30:46 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:33:25 storageqe-109 systemd[1]: Stopping udisks2.service - Disk Manager... Oct 7 09:33:25 storageqe-109 udisksd[5174]: udisks daemon version 2.10.90 exiting Oct 7 09:33:25 storageqe-109 systemd[1]: udisks2.service: Deactivated successfully. Oct 7 09:33:25 storageqe-109 systemd[1]: Stopped udisks2.service - Disk Manager. Oct 7 09:33:25 storageqe-109 systemd[1]: udisks2.service: Consumed 10min 33.319s CPU time, 1G memory peak. Oct 7 09:33:25 storageqe-109 systemd[1]: Starting udisks2.service - Disk Manager... Oct 7 09:33:25 storageqe-109 udisksd[1174031]: udisks daemon version 2.10.90 starting Oct 7 09:33:25 storageqe-109 systemd[1]: Started udisks2.service - Disk Manager. Oct 7 09:33:25 storageqe-109 udisksd[1174031]: Unclean shutdown detected, reloading modules from previous session. Oct 7 09:33:25 storageqe-109 udisksd[1174031]: Loading module iscsi ... Oct 7 09:33:25 storageqe-109 udisksd[1174031]: Loading module lvm2 ... Oct 7 09:33:25 storageqe-109 udisksd[1174031]: Acquired the name org.freedesktop.UDisks2 on the system message bus Oct 7 09:34:15 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:35:10 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:35:10 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:35:38 storageqe-109 kernel: __vm_enough_memory: pid: 1171655, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 7 09:35:38 storageqe-109 kernel: __vm_enough_memory: pid: 1171655, comm: claude, bytes: 34354864128 not enough memory for the allocation Oct 7 09:35:38 storageqe-109 kernel: __vm_enough_memory: pid: 1171655, comm: claude, bytes: 34359873536 not enough memory for the allocation Oct 7 09:35:38 storageqe-109 kernel: __vm_enough_memory: pid: 1171655, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 7 09:35:38 storageqe-109 systemd-coredump[1174553]: Process 1171655 (claude) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 7 09:35:38 storageqe-109 systemd[1]: Created slice system-systemd\x2dcoredump.slice - Slice /system/systemd-coredump. Oct 7 09:35:38 storageqe-109 systemd[1]: Started systemd-coredump@0-1174553-0.service - Process Core Dump (PID 1174553/UID 0). Oct 7 09:35:40 storageqe-109 systemd-coredump[1174554]: Process 1171655 (claude) of user 0 dumped core.#012#012Module /usr/bin/node-22 from rpm nodejs22-22.19.0-2.el10_0.x86_64#012Stack trace of thread 1171655:#012#0 0x00007fd82b0bdfcc n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 7 09:35:40 storageqe-109 systemd[1]: systemd-coredump@0-1174553-0.service: Deactivated successfully. Oct 7 09:35:40 storageqe-109 systemd[1]: systemd-coredump@0-1174553-0.service: Consumed 1.086s CPU time, 1G memory peak. Oct 7 09:35:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:36:21 storageqe-109 systemd[1]: Stopping udisks2.service - Disk Manager... Oct 7 09:36:22 storageqe-109 udisksd[1174031]: udisks daemon version 2.10.90 exiting Oct 7 09:36:22 storageqe-109 systemd[1]: udisks2.service: Deactivated successfully. Oct 7 09:36:22 storageqe-109 systemd[1]: Stopped udisks2.service - Disk Manager. Oct 7 09:36:22 storageqe-109 systemd[1]: Starting udisks2.service - Disk Manager... Oct 7 09:36:22 storageqe-109 udisksd[1174574]: udisks daemon version 2.10.90 starting Oct 7 09:36:22 storageqe-109 systemd[1]: Started udisks2.service - Disk Manager. Oct 7 09:36:22 storageqe-109 udisksd[1174574]: Acquired the name org.freedesktop.UDisks2 on the system message bus Oct 7 09:36:29 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:36:29 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:36:59 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:38:25 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:38:25 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:39:35 storageqe-109 systemd[1]: Stopping udisks2.service - Disk Manager... Oct 7 09:39:35 storageqe-109 udisksd[1174574]: udisks daemon version 2.10.90 exiting Oct 7 09:39:35 storageqe-109 systemd[1]: udisks2.service: Deactivated successfully. Oct 7 09:39:35 storageqe-109 systemd[1]: Stopped udisks2.service - Disk Manager. Oct 7 09:39:44 storageqe-109 systemd[1]: Starting udisks2.service - Disk Manager... Oct 7 09:39:44 storageqe-109 udisksd[1175313]: udisks daemon version 2.10.90 starting Oct 7 09:39:44 storageqe-109 systemd[1]: Started udisks2.service - Disk Manager. Oct 7 09:39:44 storageqe-109 udisksd[1175313]: Acquired the name org.freedesktop.UDisks2 on the system message bus Oct 7 09:41:46 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:42:13 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:42:13 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:43:04 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:43:06 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:43:06 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:43:35 storageqe-109 udisksd[1175313]: Loading module iscsi ... Oct 7 09:43:35 storageqe-109 udisksd[1175313]: Loading module lsm ... Oct 7 09:43:35 storageqe-109 udisksd[1175313]: Error loading module: LSM: Failed to connect plugin via URI 'hpsa://', error code: -1, error message: (null) Oct 7 09:43:35 storageqe-109 udisksd[1175313]: Loading module lvm2 ... Oct 7 09:44:00 storageqe-109 kernel: __vm_enough_memory: pid: 1174583, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 7 09:44:00 storageqe-109 kernel: __vm_enough_memory: pid: 1174583, comm: claude, bytes: 34357563392 not enough memory for the allocation Oct 7 09:44:00 storageqe-109 kernel: __vm_enough_memory: pid: 1174583, comm: claude, bytes: 34359873536 not enough memory for the allocation Oct 7 09:44:00 storageqe-109 kernel: __vm_enough_memory: pid: 1174583, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 7 09:44:00 storageqe-109 systemd-coredump[1176515]: Process 1174583 (claude) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 7 09:44:00 storageqe-109 systemd[1]: Started systemd-coredump@1-1176515-0.service - Process Core Dump (PID 1176515/UID 0). Oct 7 09:44:01 storageqe-109 systemd-coredump[1176516]: Process 1174583 (claude) of user 0 dumped core.#012#012Module /usr/bin/node-22 from rpm nodejs22-22.19.0-2.el10_0.x86_64#012Stack trace of thread 1174583:#012#0 0x00007ff6d52bdfcc n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 7 09:44:01 storageqe-109 systemd[1]: systemd-coredump@1-1176515-0.service: Deactivated successfully. Oct 7 09:44:01 storageqe-109 systemd[1]: systemd-coredump@1-1176515-0.service: Consumed 1.243s CPU time, 1G memory peak. Oct 7 09:44:05 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:45:26 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:45:26 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:45:56 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:51:51 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:51:51 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:53:31 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:54:24 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:54:24 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:55:03 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 09:55:57 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 09:55:57 storageqe-109 dnf[1177511]: Updating Subscription Management repositories. Oct 7 09:55:57 storageqe-109 dnf[1177511]: Unable to read consumer identity Oct 7 09:55:57 storageqe-109 dnf[1177511]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 09:55:57 storageqe-109 dnf[1177511]: beaker-AppStream 631 kB/s | 2.8 kB 00:00 Oct 7 09:55:57 storageqe-109 dnf[1177511]: beaker-AppStream-debuginfo 794 kB/s | 1.5 kB 00:00 Oct 7 09:55:57 storageqe-109 dnf[1177511]: beaker-BaseOS 1.2 MB/s | 2.7 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-BaseOS-debuginfo 515 kB/s | 1.5 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-CRB 1.2 MB/s | 2.7 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-CRB-debuginfo 484 kB/s | 1.5 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-HighAvailability 837 kB/s | 2.8 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-HighAvailability-debuginfo 675 kB/s | 1.5 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-NFV 1.4 MB/s | 2.7 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-NFV-debuginfo 684 kB/s | 1.5 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-RT 806 kB/s | 2.7 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-RT-debuginfo 761 kB/s | 1.5 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-SAP 836 kB/s | 2.7 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-SAP-debuginfo 494 kB/s | 1.5 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-SAPHANA 913 kB/s | 2.7 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: beaker-SAPHANA-debuginfo 703 kB/s | 1.5 kB 00:00 Oct 7 09:55:58 storageqe-109 dnf[1177511]: Beaker Client - RedHatEnterpriseLinux10 1.5 kB/s | 1.3 kB 00:00 Oct 7 09:55:59 storageqe-109 dnf[1177511]: beaker-harness 2.5 kB/s | 1.3 kB 00:00 Oct 7 09:55:59 storageqe-109 dnf[1177511]: Google Cloud CLI 4.4 kB/s | 1.4 kB 00:00 Oct 7 09:56:01 storageqe-109 dnf[1177511]: Google Cloud CLI 579 kB/s | 877 kB 00:01 Oct 7 09:56:02 storageqe-109 dnf[1177511]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 7 09:56:03 storageqe-109 dnf[1177511]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 7 09:56:03 storageqe-109 dnf[1177511]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 7 09:56:03 storageqe-109 dnf[1177511]: Metadata cache created. Oct 7 09:56:03 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 09:56:03 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 09:56:03 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 593ms CPU time, 134.8M memory peak. Oct 7 09:58:57 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 09:58:57 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 09:59:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 10:09:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 10:09:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 10:09:46 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 10:13:00 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 7 10:15:48 storageqe-109 udisksd[1175313]: Loading module lsm ... Oct 7 10:15:48 storageqe-109 udisksd[1175313]: Error loading module: LSM: Failed to connect plugin via URI 'hpsa://', error code: -1, error message: (null) Oct 7 10:15:50 storageqe-109 systemd[1]: Reload requested from client PID 1178089 ('systemctl') (unit session-6.scope)... Oct 7 10:15:50 storageqe-109 systemd[1]: Reloading... Oct 7 10:15:50 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 7 10:15:50 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 7 10:15:50 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 7 10:15:50 storageqe-109 systemd[1]: Reloading finished in 156 ms. Oct 7 10:15:50 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 7 10:15:50 storageqe-109 iscsid[1160611]: iscsid shutting down. Oct 7 10:15:50 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 7 10:15:50 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 7 10:15:50 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 7 10:15:50 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 7 10:15:50 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 7 10:15:50 storageqe-109 multipathd[775]: Multipath configuration updated. Oct 7 10:15:50 storageqe-109 multipathd[775]: Reload multipathd for changes to take effect Oct 7 10:15:50 storageqe-109 systemd[1]: Reloading multipathd.service - Device-Mapper Multipath Device Controller... Oct 7 10:15:50 storageqe-109 multipathd[775]: reconfigure (operator) Oct 7 10:15:50 storageqe-109 multipathd[1178188]: ok Oct 7 10:15:50 storageqe-109 multipathd[775]: reconfigure: setting up paths and maps Oct 7 10:15:50 storageqe-109 systemd[1]: Reloaded multipathd.service - Device-Mapper Multipath Device Controller. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 10:15:52 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 10:15:52 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 10:15:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 10:16:03 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 10:16:14 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_aead_aes_gcm_modes[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:16:19 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:16:19 storageqe-109 INFO: #### will start test_aead_aes_gcm_modes[npo2_linear] ##### Oct 7 10:16:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_aead_aes_gcm_modes[npo2_linear] #### INFO: #### will start test_aead_chacha20_poly1305[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:16:29 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:16:29 storageqe-109 INFO: #### END test_aead_aes_gcm_modes[npo2_linear] #### Oct 7 10:16:30 storageqe-109 INFO: #### will start test_aead_chacha20_poly1305[npo2_linear] ##### Oct 7 10:16:30 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:16:33 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_aead_chacha20_poly1305[npo2_linear] #### INFO: #### will start test_advanced_iv_algorithms[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:16:40 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:16:40 storageqe-109 INFO: #### END test_aead_chacha20_poly1305[npo2_linear] #### Oct 7 10:16:40 storageqe-109 INFO: #### will start test_advanced_iv_algorithms[npo2_linear] ##### Oct 7 10:16:40 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:16:45 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:16:45 storageqe-109 stratisd[4947]: [2025-10-07T14:16:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:16:45 storageqe-109 stratisd[4947]: [2025-10-07T14:16:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear pcFkSEjPum -q Oct 7 10:16:55 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear pcFkSEjPum -q Oct 7 10:16:55 storageqe-109 stratisd[4947]: [2025-10-07T14:16:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:16:55 storageqe-109 stratisd[4947]: [2025-10-07T14:16:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status pcFkSEjPum -q Oct 7 10:17:05 storageqe-109 journal: cryptsetup status pcFkSEjPum -q INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs xfs in remove_crypt Oct 7 10:17:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.cnk2q7_zmount_test with fs xfs Oct 7 10:17:25 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3e64bdc3-f4d0-4f74-aa6d-8ff36fcd32d2 Oct 7 10:17:25 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:17:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cnk2q7_zmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext4 in remove_crypt Oct 7 10:17:30 storageqe-109 systemd[1]: tmp-libblockdev.cnk2q7_zmount_test.mount: Deactivated successfully. Oct 7 10:17:30 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3e64bdc3-f4d0-4f74-aa6d-8ff36fcd32d2 Oct 7 10:17:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs xfs in remove_crypt Oct 7 10:17:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f_fl7562mount_test with fs ext4 Oct 7 10:17:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 041aad1c-eab1-4786-81f0-87d2c9783c28 r/w with ordered data mode. Quota mode: none. Oct 7 10:17:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f_fl7562mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext3 in remove_crypt Oct 7 10:17:45 storageqe-109 systemd[1]: tmp-libblockdev.f_fl7562mount_test.mount: Deactivated successfully. Oct 7 10:17:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 041aad1c-eab1-4786-81f0-87d2c9783c28. Oct 7 10:17:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext4 in remove_crypt Oct 7 10:17:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fvx0kb11mount_test with fs ext3 Oct 7 10:17:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:17:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 473bec97-d5aa-456a-9654-27d6c77ca919 r/w with ordered data mode. Quota mode: none. Oct 7 10:17:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fvx0kb11mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext2 in remove_crypt Oct 7 10:18:00 storageqe-109 systemd[1]: tmp-libblockdev.fvx0kb11mount_test.mount: Deactivated successfully. Oct 7 10:18:00 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 473bec97-d5aa-456a-9654-27d6c77ca919. Oct 7 10:18:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext3 in remove_crypt Oct 7 10:18:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.sim1_skkmount_test with fs ext2 Oct 7 10:18:10 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:18:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c7eda7ae-9c0a-4480-8f3c-d8c12beb8333 r/w without journal. Quota mode: none. Oct 7 10:18:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sim1_skkmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext2 in remove_crypt INFO: remove crypt device pcFkSEjPum INFO: finishe the remove crypt device pcFkSEjPum cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:18:15 storageqe-109 systemd[1]: tmp-libblockdev.sim1_skkmount_test.mount: Deactivated successfully. Oct 7 10:18:15 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c7eda7ae-9c0a-4480-8f3c-d8c12beb8333. Oct 7 10:18:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pcFkSEjPum and fs ext2 in remove_crypt Oct 7 10:18:15 storageqe-109 INFO: remove crypt device pcFkSEjPum Oct 7 10:18:15 storageqe-109 INFO: finishe the remove crypt device pcFkSEjPum Oct 7 10:18:15 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:18:15 storageqe-109 stratisd[4947]: [2025-10-07T14:18:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:18:15 storageqe-109 stratisd[4947]: [2025-10-07T14:18:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear zBVfTyKogq -q Oct 7 10:18:25 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear zBVfTyKogq -q Oct 7 10:18:25 storageqe-109 stratisd[4947]: [2025-10-07T14:18:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:18:25 storageqe-109 stratisd[4947]: [2025-10-07T14:18:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status zBVfTyKogq -q Oct 7 10:18:35 storageqe-109 journal: cryptsetup status zBVfTyKogq -q INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs xfs in remove_crypt Oct 7 10:18:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.bz1rb7qhmount_test with fs xfs Oct 7 10:18:55 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 2b51eaf7-3f0a-4bd8-b604-2d6e7b3f379a Oct 7 10:18:55 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:18:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bz1rb7qhmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext4 in remove_crypt Oct 7 10:19:00 storageqe-109 systemd[1]: tmp-libblockdev.bz1rb7qhmount_test.mount: Deactivated successfully. Oct 7 10:19:00 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 2b51eaf7-3f0a-4bd8-b604-2d6e7b3f379a Oct 7 10:19:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs xfs in remove_crypt Oct 7 10:19:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pq2lmbeumount_test with fs ext4 Oct 7 10:19:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bb757e03-5047-42df-b242-a800ec7dfa95 r/w with ordered data mode. Quota mode: none. Oct 7 10:19:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pq2lmbeumount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext3 in remove_crypt Oct 7 10:19:15 storageqe-109 systemd[1]: tmp-libblockdev.pq2lmbeumount_test.mount: Deactivated successfully. Oct 7 10:19:15 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bb757e03-5047-42df-b242-a800ec7dfa95. Oct 7 10:19:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext4 in remove_crypt Oct 7 10:19:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext3 in remove_crypt Oct 7 10:19:25 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.e0m067famount_test with fs ext3 Oct 7 10:19:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6a3291b6-695e-4583-b344-334feac5a1ab r/w with ordered data mode. Quota mode: none. Oct 7 10:19:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e0m067famount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext2 in remove_crypt Oct 7 10:19:30 storageqe-109 systemd[1]: tmp-libblockdev.e0m067famount_test.mount: Deactivated successfully. Oct 7 10:19:30 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6a3291b6-695e-4583-b344-334feac5a1ab. Oct 7 10:19:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext3 in remove_crypt Oct 7 10:19:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.skqaj2yrmount_test with fs ext2 Oct 7 10:19:40 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:19:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f45536eb-37be-4d13-8240-319045134d8b r/w without journal. Quota mode: none. Oct 7 10:19:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.skqaj2yrmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext2 in remove_crypt INFO: remove crypt device zBVfTyKogq INFO: finishe the remove crypt device zBVfTyKogq cryptsetup --type 'luks2' --cipher 'aes-cbc-plain' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:19:45 storageqe-109 systemd[1]: tmp-libblockdev.skqaj2yrmount_test.mount: Deactivated successfully. Oct 7 10:19:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f45536eb-37be-4d13-8240-319045134d8b. Oct 7 10:19:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/zBVfTyKogq and fs ext2 in remove_crypt Oct 7 10:19:45 storageqe-109 INFO: remove crypt device zBVfTyKogq Oct 7 10:19:45 storageqe-109 INFO: finishe the remove crypt device zBVfTyKogq Oct 7 10:19:45 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:19:46 storageqe-109 stratisd[4947]: [2025-10-07T14:19:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:19:46 storageqe-109 stratisd[4947]: [2025-10-07T14:19:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear ztGAvqXVbB -q Oct 7 10:19:56 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear ztGAvqXVbB -q Oct 7 10:19:56 storageqe-109 stratisd[4947]: [2025-10-07T14:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:19:56 storageqe-109 stratisd[4947]: [2025-10-07T14:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status ztGAvqXVbB -q Oct 7 10:20:06 storageqe-109 journal: cryptsetup status ztGAvqXVbB -q INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs xfs in remove_crypt Oct 7 10:20:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.unimtbz1mount_test with fs xfs Oct 7 10:20:26 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 638d5022-5a63-4905-9a11-3c65a54a3bac Oct 7 10:20:26 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:20:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.unimtbz1mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext4 in remove_crypt Oct 7 10:20:31 storageqe-109 systemd[1]: tmp-libblockdev.unimtbz1mount_test.mount: Deactivated successfully. Oct 7 10:20:31 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 638d5022-5a63-4905-9a11-3c65a54a3bac Oct 7 10:20:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs xfs in remove_crypt Oct 7 10:20:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qz1e7z3_mount_test with fs ext4 Oct 7 10:20:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0cba3390-f49d-4608-b5d1-2da3c1c8a37b r/w with ordered data mode. Quota mode: none. Oct 7 10:20:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qz1e7z3_mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext3 in remove_crypt Oct 7 10:20:46 storageqe-109 systemd[1]: tmp-libblockdev.qz1e7z3_mount_test.mount: Deactivated successfully. Oct 7 10:20:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0cba3390-f49d-4608-b5d1-2da3c1c8a37b. Oct 7 10:20:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext4 in remove_crypt Oct 7 10:20:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.39nvec4xmount_test with fs ext3 Oct 7 10:20:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:20:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8e9032a6-f727-4ce9-b1af-40c2c8c33144 r/w with ordered data mode. Quota mode: none. Oct 7 10:20:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.39nvec4xmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext2 in remove_crypt Oct 7 10:21:01 storageqe-109 systemd[1]: tmp-libblockdev.39nvec4xmount_test.mount: Deactivated successfully. Oct 7 10:21:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8e9032a6-f727-4ce9-b1af-40c2c8c33144. Oct 7 10:21:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext3 in remove_crypt Oct 7 10:21:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3qqq5hzpmount_test with fs ext2 Oct 7 10:21:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:21:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 89e9a6fa-070a-4a9a-a64f-f7a6ee67dee0 r/w without journal. Quota mode: none. Oct 7 10:21:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3qqq5hzpmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext2 in remove_crypt INFO: remove crypt device ztGAvqXVbB INFO: finishe the remove crypt device ztGAvqXVbB cryptsetup --type 'luks2' --cipher 'aes-xts-benbi' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:21:16 storageqe-109 systemd[1]: tmp-libblockdev.3qqq5hzpmount_test.mount: Deactivated successfully. Oct 7 10:21:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 89e9a6fa-070a-4a9a-a64f-f7a6ee67dee0. Oct 7 10:21:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ztGAvqXVbB and fs ext2 in remove_crypt Oct 7 10:21:16 storageqe-109 INFO: remove crypt device ztGAvqXVbB Oct 7 10:21:17 storageqe-109 INFO: finishe the remove crypt device ztGAvqXVbB Oct 7 10:21:17 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-benbi' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:21:17 storageqe-109 stratisd[4947]: [2025-10-07T14:21:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:21:17 storageqe-109 stratisd[4947]: [2025-10-07T14:21:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear OCUlQdHTXS -q Oct 7 10:21:27 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear OCUlQdHTXS -q Oct 7 10:21:27 storageqe-109 stratisd[4947]: [2025-10-07T14:21:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:21:27 storageqe-109 stratisd[4947]: [2025-10-07T14:21:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status OCUlQdHTXS -q Oct 7 10:21:37 storageqe-109 journal: cryptsetup status OCUlQdHTXS -q INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs xfs in remove_crypt Oct 7 10:21:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.kmz7g7tfmount_test with fs xfs Oct 7 10:21:57 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 92b067d7-c1a7-42a3-8178-614c805661a5 Oct 7 10:21:57 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:21:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kmz7g7tfmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext4 in remove_crypt Oct 7 10:22:02 storageqe-109 systemd[1]: tmp-libblockdev.kmz7g7tfmount_test.mount: Deactivated successfully. Oct 7 10:22:02 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 92b067d7-c1a7-42a3-8178-614c805661a5 Oct 7 10:22:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs xfs in remove_crypt Oct 7 10:22:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.v6blwbz4mount_test with fs ext4 Oct 7 10:22:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem eb8d7cb6-6299-4476-a962-5d21cea0a7ab r/w with ordered data mode. Quota mode: none. Oct 7 10:22:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v6blwbz4mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext4 in remove_crypt Oct 7 10:22:16 storageqe-109 systemd[1]: tmp-libblockdev.v6blwbz4mount_test.mount: Deactivated successfully. Oct 7 10:22:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem eb8d7cb6-6299-4476-a962-5d21cea0a7ab. Oct 7 10:22:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext3 in remove_crypt Oct 7 10:22:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mwy7y88ymount_test with fs ext3 Oct 7 10:22:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:22:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2e99e2e0-5dab-4bb6-b773-ea2631933a1b r/w with ordered data mode. Quota mode: none. Oct 7 10:22:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mwy7y88ymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext2 in remove_crypt Oct 7 10:22:32 storageqe-109 systemd[1]: tmp-libblockdev.mwy7y88ymount_test.mount: Deactivated successfully. Oct 7 10:22:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2e99e2e0-5dab-4bb6-b773-ea2631933a1b. Oct 7 10:22:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext3 in remove_crypt Oct 7 10:22:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4_sivuimmount_test with fs ext2 Oct 7 10:22:42 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:22:42 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 99e3b916-66f6-45bd-802b-c84288df0c33 r/w without journal. Quota mode: none. Oct 7 10:22:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4_sivuimmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext2 in remove_crypt INFO: remove crypt device OCUlQdHTXS Oct 7 10:22:46 storageqe-109 systemd[1]: tmp-libblockdev.4_sivuimmount_test.mount: Deactivated successfully. Oct 7 10:22:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 99e3b916-66f6-45bd-802b-c84288df0c33. Oct 7 10:22:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/OCUlQdHTXS and fs ext2 in remove_crypt Oct 7 10:22:46 storageqe-109 INFO: remove crypt device OCUlQdHTXS INFO: finishe the remove crypt device OCUlQdHTXS Oct 7 10:22:47 storageqe-109 INFO: finishe the remove crypt device OCUlQdHTXS cryptsetup --type 'luks2' --cipher 'twofish-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:22:49 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'twofish-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:22:49 storageqe-109 stratisd[4947]: [2025-10-07T14:22:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:22:49 storageqe-109 stratisd[4947]: [2025-10-07T14:22:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear vVICHKnDwR -q Oct 7 10:22:59 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear vVICHKnDwR -q Oct 7 10:22:59 storageqe-109 stratisd[4947]: [2025-10-07T14:22:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:22:59 storageqe-109 stratisd[4947]: [2025-10-07T14:22:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vVICHKnDwR -q Oct 7 10:23:09 storageqe-109 journal: cryptsetup status vVICHKnDwR -q INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs xfs in remove_crypt Oct 7 10:23:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.84cp4onymount_test with fs xfs Oct 7 10:23:29 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 331ce7d0-4928-429b-8518-337f145dfc5a Oct 7 10:23:29 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:23:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.84cp4onymount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext4 in remove_crypt Oct 7 10:23:35 storageqe-109 systemd[1]: tmp-libblockdev.84cp4onymount_test.mount: Deactivated successfully. Oct 7 10:23:35 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 331ce7d0-4928-429b-8518-337f145dfc5a Oct 7 10:23:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs xfs in remove_crypt Oct 7 10:23:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ym9l5vncmount_test with fs ext4 Oct 7 10:23:45 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6dc6b56f-8f84-4471-a7f9-e5da2a6396a8 r/w with ordered data mode. Quota mode: none. Oct 7 10:23:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ym9l5vncmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext3 in remove_crypt Oct 7 10:23:51 storageqe-109 systemd[1]: tmp-libblockdev.ym9l5vncmount_test.mount: Deactivated successfully. Oct 7 10:23:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6dc6b56f-8f84-4471-a7f9-e5da2a6396a8. Oct 7 10:23:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext4 in remove_crypt Oct 7 10:23:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.96jo4h95mount_test with fs ext3 Oct 7 10:24:01 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:24:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 10a9b7a4-85a0-41a4-8b4e-3e94d51db25d r/w with ordered data mode. Quota mode: none. Oct 7 10:24:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.96jo4h95mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext2 in remove_crypt Oct 7 10:24:07 storageqe-109 systemd[1]: tmp-libblockdev.96jo4h95mount_test.mount: Deactivated successfully. Oct 7 10:24:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 10a9b7a4-85a0-41a4-8b4e-3e94d51db25d. Oct 7 10:24:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext3 in remove_crypt Oct 7 10:24:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1bset847mount_test with fs ext2 Oct 7 10:24:17 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:24:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 640d3613-7b8d-496f-82e4-cabee034671e r/w without journal. Quota mode: none. Oct 7 10:24:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1bset847mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext2 in remove_crypt INFO: remove crypt device vVICHKnDwR INFO: finishe the remove crypt device vVICHKnDwR Oct 7 10:24:23 storageqe-109 systemd[1]: tmp-libblockdev.1bset847mount_test.mount: Deactivated successfully. Oct 7 10:24:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 640d3613-7b8d-496f-82e4-cabee034671e. Oct 7 10:24:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/vVICHKnDwR and fs ext2 in remove_crypt Oct 7 10:24:23 storageqe-109 INFO: remove crypt device vVICHKnDwR Oct 7 10:24:23 storageqe-109 INFO: finishe the remove crypt device vVICHKnDwR cryptsetup --type 'luks2' --cipher 'serpent-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:24:25 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-cbc-plain64' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:24:25 storageqe-109 stratisd[4947]: [2025-10-07T14:24:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:24:25 storageqe-109 stratisd[4947]: [2025-10-07T14:24:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear dOFJAtYqow -q Oct 7 10:24:35 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear dOFJAtYqow -q Oct 7 10:24:35 storageqe-109 stratisd[4947]: [2025-10-07T14:24:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:24:35 storageqe-109 stratisd[4947]: [2025-10-07T14:24:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status dOFJAtYqow -q Oct 7 10:24:45 storageqe-109 journal: cryptsetup status dOFJAtYqow -q INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs xfs in remove_crypt Oct 7 10:24:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ixixm0dlmount_test with fs xfs Oct 7 10:25:06 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f490a292-9276-4a71-9f07-fd013bdf483c Oct 7 10:25:06 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:25:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ixixm0dlmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext4 in remove_crypt Oct 7 10:25:12 storageqe-109 systemd[1]: tmp-libblockdev.ixixm0dlmount_test.mount: Deactivated successfully. Oct 7 10:25:12 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f490a292-9276-4a71-9f07-fd013bdf483c Oct 7 10:25:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs xfs in remove_crypt Oct 7 10:25:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z1bcs_00mount_test with fs ext4 Oct 7 10:25:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 91ba8853-d6a3-4edf-840a-f93d2d3e6843 r/w with ordered data mode. Quota mode: none. Oct 7 10:25:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z1bcs_00mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext3 in remove_crypt Oct 7 10:25:28 storageqe-109 systemd[1]: tmp-libblockdev.z1bcs_00mount_test.mount: Deactivated successfully. Oct 7 10:25:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 91ba8853-d6a3-4edf-840a-f93d2d3e6843. Oct 7 10:25:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext4 in remove_crypt Oct 7 10:25:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qqq_bzyqmount_test with fs ext3 Oct 7 10:25:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:25:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 20b2c2db-f11d-4a2b-8a28-294bec60d4d6 r/w with ordered data mode. Quota mode: none. Oct 7 10:25:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qqq_bzyqmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext2 in remove_crypt Oct 7 10:25:45 storageqe-109 systemd[1]: tmp-libblockdev.qqq_bzyqmount_test.mount: Deactivated successfully. Oct 7 10:25:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 20b2c2db-f11d-4a2b-8a28-294bec60d4d6. Oct 7 10:25:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext3 in remove_crypt Oct 7 10:25:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tg4r79znmount_test with fs ext2 Oct 7 10:25:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:25:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 45cfab5e-aa62-4d3a-9e35-a208ff60e46f r/w without journal. Quota mode: none. Oct 7 10:25:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tg4r79znmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext2 in remove_crypt INFO: remove crypt device dOFJAtYqow INFO: finishe the remove crypt device dOFJAtYqow Oct 7 10:26:02 storageqe-109 systemd[1]: tmp-libblockdev.tg4r79znmount_test.mount: Deactivated successfully. Oct 7 10:26:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 45cfab5e-aa62-4d3a-9e35-a208ff60e46f. Oct 7 10:26:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dOFJAtYqow and fs ext2 in remove_crypt Oct 7 10:26:02 storageqe-109 INFO: remove crypt device dOFJAtYqow Oct 7 10:26:02 storageqe-109 INFO: finishe the remove crypt device dOFJAtYqow INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_advanced_iv_algorithms[npo2_linear] #### INFO: #### will start test_performance_optimizations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:26:07 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:26:07 storageqe-109 INFO: #### END test_advanced_iv_algorithms[npo2_linear] #### Oct 7 10:26:07 storageqe-109 INFO: #### will start test_performance_optimizations[npo2_linear] ##### Oct 7 10:26:07 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_performance_optimizations[npo2_linear] #### INFO: #### will start test_sector_size_variations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:26:17 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:26:17 storageqe-109 INFO: #### END test_performance_optimizations[npo2_linear] #### Oct 7 10:26:17 storageqe-109 INFO: #### will start test_sector_size_variations[npo2_linear] ##### Oct 7 10:26:17 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:26:22 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:26:22 storageqe-109 stratisd[4947]: [2025-10-07T14:26:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:26:22 storageqe-109 stratisd[4947]: [2025-10-07T14:26:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear SMFIAPdcZL -q Oct 7 10:26:32 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear SMFIAPdcZL -q Oct 7 10:26:32 storageqe-109 stratisd[4947]: [2025-10-07T14:26:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:26:32 storageqe-109 stratisd[4947]: [2025-10-07T14:26:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status SMFIAPdcZL -q Oct 7 10:26:42 storageqe-109 journal: cryptsetup status SMFIAPdcZL -q INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs xfs in remove_crypt Oct 7 10:26:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.yycgl_vmmount_test with fs xfs Oct 7 10:27:02 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 625e90c5-7a36-4a0a-a872-8c350f0619fb Oct 7 10:27:02 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:27:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yycgl_vmmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext4 in remove_crypt Oct 7 10:27:07 storageqe-109 systemd[1]: tmp-libblockdev.yycgl_vmmount_test.mount: Deactivated successfully. Oct 7 10:27:07 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 625e90c5-7a36-4a0a-a872-8c350f0619fb Oct 7 10:27:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs xfs in remove_crypt Oct 7 10:27:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cnvwm628mount_test with fs ext4 Oct 7 10:27:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7e7357a4-db15-446c-864f-c32d91678c04 r/w with ordered data mode. Quota mode: none. Oct 7 10:27:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cnvwm628mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext3 in remove_crypt Oct 7 10:27:22 storageqe-109 systemd[1]: tmp-libblockdev.cnvwm628mount_test.mount: Deactivated successfully. Oct 7 10:27:22 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7e7357a4-db15-446c-864f-c32d91678c04. Oct 7 10:27:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext4 in remove_crypt Oct 7 10:27:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rwysfr1lmount_test with fs ext3 Oct 7 10:27:32 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:27:32 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e75bfb4d-b536-412d-b074-630fb8a1ea14 r/w with ordered data mode. Quota mode: none. Oct 7 10:27:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rwysfr1lmount_test with fs ext3 Oct 7 10:27:37 storageqe-109 systemd[1]: tmp-libblockdev.rwysfr1lmount_test.mount: Deactivated successfully. Oct 7 10:27:37 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e75bfb4d-b536-412d-b074-630fb8a1ea14. INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext2 in remove_crypt Oct 7 10:27:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext3 in remove_crypt Oct 7 10:27:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ln__5x6tmount_test with fs ext2 Oct 7 10:27:47 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:27:47 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e2dd540b-48b7-4bf9-9c41-44a6f284585a r/w without journal. Quota mode: none. Oct 7 10:27:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ln__5x6tmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext2 in remove_crypt Oct 7 10:27:52 storageqe-109 systemd[1]: tmp-libblockdev.ln__5x6tmount_test.mount: Deactivated successfully. Oct 7 10:27:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e2dd540b-48b7-4bf9-9c41-44a6f284585a. Oct 7 10:27:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SMFIAPdcZL and fs ext2 in remove_crypt INFO: remove crypt device SMFIAPdcZL INFO: finishe the remove crypt device SMFIAPdcZL cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:27:52 storageqe-109 INFO: remove crypt device SMFIAPdcZL Oct 7 10:27:52 storageqe-109 INFO: finishe the remove crypt device SMFIAPdcZL Oct 7 10:27:52 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:27:52 storageqe-109 stratisd[4947]: [2025-10-07T14:27:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:27:52 storageqe-109 stratisd[4947]: [2025-10-07T14:27:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear UpZQyFivoq -q Oct 7 10:28:02 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear UpZQyFivoq -q Oct 7 10:28:02 storageqe-109 stratisd[4947]: [2025-10-07T14:28:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:28:02 storageqe-109 stratisd[4947]: [2025-10-07T14:28:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status UpZQyFivoq -q Oct 7 10:28:12 storageqe-109 journal: cryptsetup status UpZQyFivoq -q INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs xfs in remove_crypt Oct 7 10:28:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.0f_b138umount_test with fs xfs Oct 7 10:28:32 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem dfd4fa97-ff3b-40eb-99a1-8b6321eecc49 Oct 7 10:28:32 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:28:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0f_b138umount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext4 in remove_crypt Oct 7 10:28:37 storageqe-109 systemd[1]: tmp-libblockdev.0f_b138umount_test.mount: Deactivated successfully. Oct 7 10:28:37 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem dfd4fa97-ff3b-40eb-99a1-8b6321eecc49 Oct 7 10:28:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs xfs in remove_crypt Oct 7 10:28:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x9069wyymount_test with fs ext4 Oct 7 10:28:47 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5de41110-7409-4758-b321-e1599e8bc35e r/w with ordered data mode. Quota mode: none. Oct 7 10:28:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x9069wyymount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext3 in remove_crypt Oct 7 10:28:52 storageqe-109 systemd[1]: tmp-libblockdev.x9069wyymount_test.mount: Deactivated successfully. Oct 7 10:28:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5de41110-7409-4758-b321-e1599e8bc35e. Oct 7 10:28:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext4 in remove_crypt Oct 7 10:28:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rur3h5n_mount_test with fs ext3 Oct 7 10:29:02 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:29:02 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d2e644e1-8b9b-4be7-a6be-383a2d35188e r/w with ordered data mode. Quota mode: none. Oct 7 10:29:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rur3h5n_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext2 in remove_crypt Oct 7 10:29:07 storageqe-109 systemd[1]: tmp-libblockdev.rur3h5n_mount_test.mount: Deactivated successfully. Oct 7 10:29:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d2e644e1-8b9b-4be7-a6be-383a2d35188e. Oct 7 10:29:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext3 in remove_crypt Oct 7 10:29:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.sgq8twnxmount_test with fs ext2 Oct 7 10:29:17 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:29:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dabf1918-849f-458f-848a-3ca6ccb7ee4c r/w without journal. Quota mode: none. Oct 7 10:29:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sgq8twnxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext2 in remove_crypt Oct 7 10:29:22 storageqe-109 systemd[1]: tmp-libblockdev.sgq8twnxmount_test.mount: Deactivated successfully. Oct 7 10:29:22 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dabf1918-849f-458f-848a-3ca6ccb7ee4c. Oct 7 10:29:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UpZQyFivoq and fs ext2 in remove_crypt INFO: remove crypt device UpZQyFivoq INFO: finishe the remove crypt device UpZQyFivoq cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:29:22 storageqe-109 INFO: remove crypt device UpZQyFivoq Oct 7 10:29:22 storageqe-109 INFO: finishe the remove crypt device UpZQyFivoq Oct 7 10:29:22 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:29:22 storageqe-109 stratisd[4947]: [2025-10-07T14:29:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:29:22 storageqe-109 stratisd[4947]: [2025-10-07T14:29:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear KeYEkvOSda -q Oct 7 10:29:32 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear KeYEkvOSda -q Oct 7 10:29:32 storageqe-109 stratisd[4947]: [2025-10-07T14:29:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:29:32 storageqe-109 stratisd[4947]: [2025-10-07T14:29:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status KeYEkvOSda -q Oct 7 10:29:42 storageqe-109 journal: cryptsetup status KeYEkvOSda -q INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs xfs in remove_crypt Oct 7 10:29:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8ls7fc8lmount_test with fs xfs Oct 7 10:30:02 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f6341bcb-969c-4db3-90c8-7e923effc713 Oct 7 10:30:02 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:30:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8ls7fc8lmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext4 in remove_crypt Oct 7 10:30:07 storageqe-109 systemd[1]: tmp-libblockdev.8ls7fc8lmount_test.mount: Deactivated successfully. Oct 7 10:30:07 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f6341bcb-969c-4db3-90c8-7e923effc713 Oct 7 10:30:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs xfs in remove_crypt Oct 7 10:30:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3whaofsamount_test with fs ext4 Oct 7 10:30:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 44b8fc0e-364c-4de7-a002-f59127b5a34a r/w with ordered data mode. Quota mode: none. Oct 7 10:30:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3whaofsamount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext3 in remove_crypt Oct 7 10:30:23 storageqe-109 systemd[1]: tmp-libblockdev.3whaofsamount_test.mount: Deactivated successfully. Oct 7 10:30:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 44b8fc0e-364c-4de7-a002-f59127b5a34a. Oct 7 10:30:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext4 in remove_crypt Oct 7 10:30:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.du3_mt1rmount_test with fs ext3 Oct 7 10:30:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:30:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem befa3a4c-ff59-4a48-85b4-afa25ffa6f44 r/w with ordered data mode. Quota mode: none. Oct 7 10:30:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.du3_mt1rmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext2 in remove_crypt Oct 7 10:30:38 storageqe-109 systemd[1]: tmp-libblockdev.du3_mt1rmount_test.mount: Deactivated successfully. Oct 7 10:30:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem befa3a4c-ff59-4a48-85b4-afa25ffa6f44. Oct 7 10:30:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext3 in remove_crypt Oct 7 10:30:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x1xu_08xmount_test with fs ext2 Oct 7 10:30:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:30:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9c95ecc7-84d3-4415-b83a-9cff684de271 r/w without journal. Quota mode: none. Oct 7 10:30:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x1xu_08xmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext2 in remove_crypt INFO: remove crypt device KeYEkvOSda INFO: finishe the remove crypt device KeYEkvOSda cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:30:53 storageqe-109 systemd[1]: tmp-libblockdev.x1xu_08xmount_test.mount: Deactivated successfully. Oct 7 10:30:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9c95ecc7-84d3-4415-b83a-9cff684de271. Oct 7 10:30:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KeYEkvOSda and fs ext2 in remove_crypt Oct 7 10:30:53 storageqe-109 INFO: remove crypt device KeYEkvOSda Oct 7 10:30:53 storageqe-109 INFO: finishe the remove crypt device KeYEkvOSda Oct 7 10:30:53 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --sector-size '4096' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:30:53 storageqe-109 stratisd[4947]: [2025-10-07T14:30:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:30:53 storageqe-109 stratisd[4947]: [2025-10-07T14:30:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear JNjWvcalfd -q Oct 7 10:31:03 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear JNjWvcalfd -q Oct 7 10:31:03 storageqe-109 stratisd[4947]: [2025-10-07T14:31:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:31:03 storageqe-109 stratisd[4947]: [2025-10-07T14:31:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status JNjWvcalfd -q Oct 7 10:31:14 storageqe-109 journal: cryptsetup status JNjWvcalfd -q INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs xfs in remove_crypt Oct 7 10:31:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.f3aog71_mount_test with fs xfs Oct 7 10:31:34 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 5d592d9a-523f-49c2-8c0e-da628e4ed92f Oct 7 10:31:34 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:31:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f3aog71_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext4 in remove_crypt Oct 7 10:31:38 storageqe-109 systemd[1]: tmp-libblockdev.f3aog71_mount_test.mount: Deactivated successfully. Oct 7 10:31:38 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 5d592d9a-523f-49c2-8c0e-da628e4ed92f Oct 7 10:31:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs xfs in remove_crypt Oct 7 10:31:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ko22iz6nmount_test with fs ext4 Oct 7 10:31:49 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 907c09e1-ae75-4a84-8751-2aa0ccd016fe r/w with ordered data mode. Quota mode: none. Oct 7 10:31:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ko22iz6nmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext3 in remove_crypt Oct 7 10:31:54 storageqe-109 systemd[1]: tmp-libblockdev.ko22iz6nmount_test.mount: Deactivated successfully. Oct 7 10:31:54 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 907c09e1-ae75-4a84-8751-2aa0ccd016fe. Oct 7 10:31:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext4 in remove_crypt Oct 7 10:31:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r6pok_m7mount_test with fs ext3 Oct 7 10:32:04 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:32:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem af28bd2e-792f-4353-8b17-807f5cc6b4a5 r/w with ordered data mode. Quota mode: none. Oct 7 10:32:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r6pok_m7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext2 in remove_crypt Oct 7 10:32:09 storageqe-109 systemd[1]: tmp-libblockdev.r6pok_m7mount_test.mount: Deactivated successfully. Oct 7 10:32:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem af28bd2e-792f-4353-8b17-807f5cc6b4a5. Oct 7 10:32:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext3 in remove_crypt Oct 7 10:32:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1ybbn7fqmount_test with fs ext2 Oct 7 10:32:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:32:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 60f0f6cd-0a1a-4129-9813-85607c257f57 r/w without journal. Quota mode: none. Oct 7 10:32:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1ybbn7fqmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext2 in remove_crypt INFO: remove crypt device JNjWvcalfd INFO: finishe the remove crypt device JNjWvcalfd Oct 7 10:32:24 storageqe-109 systemd[1]: tmp-libblockdev.1ybbn7fqmount_test.mount: Deactivated successfully. Oct 7 10:32:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 60f0f6cd-0a1a-4129-9813-85607c257f57. Oct 7 10:32:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JNjWvcalfd and fs ext2 in remove_crypt Oct 7 10:32:24 storageqe-109 INFO: remove crypt device JNjWvcalfd Oct 7 10:32:24 storageqe-109 INFO: finishe the remove crypt device JNjWvcalfd INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_sector_size_variations[npo2_linear] #### INFO: #### will start test_cipher_combinations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:32:29 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:32:29 storageqe-109 INFO: #### END test_sector_size_variations[npo2_linear] #### Oct 7 10:32:29 storageqe-109 INFO: #### will start test_cipher_combinations[npo2_linear] ##### Oct 7 10:32:29 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --cipher 'aes-cbc-essiv:sha256' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:32:36 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-essiv:sha256' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:32:36 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 10:32:36 storageqe-109 stratisd[4947]: [2025-10-07T14:32:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:32:36 storageqe-109 stratisd[4947]: [2025-10-07T14:32:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:32:36 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 10:32:36 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. cryptsetup open /dev/mapper/npo2linear KDCaZhjPkA -q Oct 7 10:32:46 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear KDCaZhjPkA -q Oct 7 10:32:46 storageqe-109 stratisd[4947]: [2025-10-07T14:32:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:32:46 storageqe-109 stratisd[4947]: [2025-10-07T14:32:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs xfs in remove_crypt Oct 7 10:32:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.22iwuk5smount_test with fs xfs Oct 7 10:33:07 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem beddc5c8-1e76-4c9d-b9ce-c039f4e632a1 Oct 7 10:33:07 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:33:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.22iwuk5smount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext4 in remove_crypt Oct 7 10:33:11 storageqe-109 systemd[1]: tmp-libblockdev.22iwuk5smount_test.mount: Deactivated successfully. Oct 7 10:33:11 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem beddc5c8-1e76-4c9d-b9ce-c039f4e632a1 Oct 7 10:33:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs xfs in remove_crypt Oct 7 10:33:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6gvuqq_5mount_test with fs ext4 Oct 7 10:33:21 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d0c01f4d-6cf2-4d93-9926-c0c5abe1122d r/w with ordered data mode. Quota mode: none. Oct 7 10:33:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6gvuqq_5mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext3 in remove_crypt Oct 7 10:33:27 storageqe-109 systemd[1]: tmp-libblockdev.6gvuqq_5mount_test.mount: Deactivated successfully. Oct 7 10:33:27 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d0c01f4d-6cf2-4d93-9926-c0c5abe1122d. Oct 7 10:33:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext4 in remove_crypt Oct 7 10:33:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.to2tgajamount_test with fs ext3 Oct 7 10:33:37 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:33:37 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1dc6a975-0246-48d2-a22b-562059126d5b r/w with ordered data mode. Quota mode: none. Oct 7 10:33:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.to2tgajamount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext2 in remove_crypt Oct 7 10:33:42 storageqe-109 systemd[1]: tmp-libblockdev.to2tgajamount_test.mount: Deactivated successfully. Oct 7 10:33:42 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1dc6a975-0246-48d2-a22b-562059126d5b. Oct 7 10:33:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext3 in remove_crypt Oct 7 10:33:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.b2sqi69pmount_test with fs ext2 Oct 7 10:33:52 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:33:52 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem aef59063-1d58-436d-9f5b-d0f94088c2b2 r/w without journal. Quota mode: none. Oct 7 10:33:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b2sqi69pmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext2 in remove_crypt INFO: remove crypt device KDCaZhjPkA Oct 7 10:33:57 storageqe-109 systemd[1]: tmp-libblockdev.b2sqi69pmount_test.mount: Deactivated successfully. Oct 7 10:33:57 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem aef59063-1d58-436d-9f5b-d0f94088c2b2. Oct 7 10:33:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KDCaZhjPkA and fs ext2 in remove_crypt Oct 7 10:33:57 storageqe-109 INFO: remove crypt device KDCaZhjPkA INFO: finishe the remove crypt device KDCaZhjPkA cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:33:57 storageqe-109 INFO: finishe the remove crypt device KDCaZhjPkA Oct 7 10:33:57 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-xts-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:33:57 storageqe-109 stratisd[4947]: [2025-10-07T14:33:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:33:57 storageqe-109 stratisd[4947]: [2025-10-07T14:33:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear sVhEqfbyDK -q Oct 7 10:34:07 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear sVhEqfbyDK -q Oct 7 10:34:07 storageqe-109 stratisd[4947]: [2025-10-07T14:34:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:34:07 storageqe-109 stratisd[4947]: [2025-10-07T14:34:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs xfs in remove_crypt Oct 7 10:34:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.l86puy10mount_test with fs xfs Oct 7 10:34:27 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem e09dca5f-fc62-4c84-ad86-0b12d5c1acb6 Oct 7 10:34:27 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:34:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l86puy10mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext4 in remove_crypt Oct 7 10:34:32 storageqe-109 systemd[1]: tmp-libblockdev.l86puy10mount_test.mount: Deactivated successfully. Oct 7 10:34:32 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem e09dca5f-fc62-4c84-ad86-0b12d5c1acb6 Oct 7 10:34:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs xfs in remove_crypt Oct 7 10:34:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.c701p46hmount_test with fs ext4 Oct 7 10:34:42 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 578f09fe-4757-48c9-9fde-1646a447e75b r/w with ordered data mode. Quota mode: none. Oct 7 10:34:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c701p46hmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext3 in remove_crypt Oct 7 10:34:47 storageqe-109 systemd[1]: tmp-libblockdev.c701p46hmount_test.mount: Deactivated successfully. Oct 7 10:34:47 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 578f09fe-4757-48c9-9fde-1646a447e75b. Oct 7 10:34:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext4 in remove_crypt Oct 7 10:34:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wzv8glc9mount_test with fs ext3 Oct 7 10:34:57 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:34:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ca85903d-5ebd-468f-bf07-68f840705134 r/w with ordered data mode. Quota mode: none. Oct 7 10:34:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wzv8glc9mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext2 in remove_crypt Oct 7 10:35:02 storageqe-109 systemd[1]: tmp-libblockdev.wzv8glc9mount_test.mount: Deactivated successfully. Oct 7 10:35:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ca85903d-5ebd-468f-bf07-68f840705134. Oct 7 10:35:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext3 in remove_crypt Oct 7 10:35:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nq7s7dbimount_test with fs ext2 Oct 7 10:35:12 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:35:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 57a55e37-1a1c-4ea2-897d-4626d3e87e50 r/w without journal. Quota mode: none. Oct 7 10:35:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nq7s7dbimount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext2 in remove_crypt INFO: remove crypt device sVhEqfbyDK Oct 7 10:35:17 storageqe-109 systemd[1]: tmp-libblockdev.nq7s7dbimount_test.mount: Deactivated successfully. Oct 7 10:35:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 57a55e37-1a1c-4ea2-897d-4626d3e87e50. Oct 7 10:35:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/sVhEqfbyDK and fs ext2 in remove_crypt Oct 7 10:35:17 storageqe-109 INFO: remove crypt device sVhEqfbyDK INFO: finishe the remove crypt device sVhEqfbyDK cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:35:17 storageqe-109 INFO: finishe the remove crypt device sVhEqfbyDK Oct 7 10:35:17 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'aes-cbc-plain64' --key-size '256' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:35:17 storageqe-109 stratisd[4947]: [2025-10-07T14:35:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:35:17 storageqe-109 stratisd[4947]: [2025-10-07T14:35:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear NlLWoZJTqH -q Oct 7 10:35:27 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear NlLWoZJTqH -q Oct 7 10:35:27 storageqe-109 stratisd[4947]: [2025-10-07T14:35:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:35:27 storageqe-109 stratisd[4947]: [2025-10-07T14:35:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs xfs in remove_crypt Oct 7 10:35:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.akw1dxdhmount_test with fs xfs Oct 7 10:35:47 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 5c22cb14-cb00-4a76-9406-8690e315b864 Oct 7 10:35:47 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:35:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.akw1dxdhmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext4 in remove_crypt Oct 7 10:35:52 storageqe-109 systemd[1]: tmp-libblockdev.akw1dxdhmount_test.mount: Deactivated successfully. Oct 7 10:35:52 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 5c22cb14-cb00-4a76-9406-8690e315b864 Oct 7 10:35:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs xfs in remove_crypt Oct 7 10:35:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3d2x24a5mount_test with fs ext4 Oct 7 10:36:02 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 20ba51a7-3391-4ca0-976d-49eea5e6f7aa r/w with ordered data mode. Quota mode: none. Oct 7 10:36:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3d2x24a5mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext3 in remove_crypt Oct 7 10:36:07 storageqe-109 systemd[1]: tmp-libblockdev.3d2x24a5mount_test.mount: Deactivated successfully. Oct 7 10:36:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 20ba51a7-3391-4ca0-976d-49eea5e6f7aa. Oct 7 10:36:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext4 in remove_crypt Oct 7 10:36:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bcgfecapmount_test with fs ext3 Oct 7 10:36:18 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:36:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 07c3964a-248d-4748-bc21-783663958269 r/w with ordered data mode. Quota mode: none. Oct 7 10:36:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bcgfecapmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext2 in remove_crypt Oct 7 10:36:22 storageqe-109 systemd[1]: tmp-libblockdev.bcgfecapmount_test.mount: Deactivated successfully. Oct 7 10:36:22 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 07c3964a-248d-4748-bc21-783663958269. Oct 7 10:36:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext3 in remove_crypt Oct 7 10:36:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jwy6ryommount_test with fs ext2 Oct 7 10:36:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:36:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 75759df7-21d6-4f84-a0ea-9013ef3e14f1 r/w without journal. Quota mode: none. Oct 7 10:36:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jwy6ryommount_test with fs ext2 Oct 7 10:36:37 storageqe-109 systemd[1]: tmp-libblockdev.jwy6ryommount_test.mount: Deactivated successfully. Oct 7 10:36:37 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 75759df7-21d6-4f84-a0ea-9013ef3e14f1. INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext2 in remove_crypt INFO: remove crypt device NlLWoZJTqH INFO: finishe the remove crypt device NlLWoZJTqH cryptsetup --type 'luks2' --cipher 'twofish-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:36:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/NlLWoZJTqH and fs ext2 in remove_crypt Oct 7 10:36:38 storageqe-109 INFO: remove crypt device NlLWoZJTqH Oct 7 10:36:38 storageqe-109 INFO: finishe the remove crypt device NlLWoZJTqH Oct 7 10:36:38 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'twofish-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:36:38 storageqe-109 stratisd[4947]: [2025-10-07T14:36:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:36:38 storageqe-109 stratisd[4947]: [2025-10-07T14:36:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear BszCvQbjJX -q Oct 7 10:36:48 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear BszCvQbjJX -q Oct 7 10:36:48 storageqe-109 stratisd[4947]: [2025-10-07T14:36:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:36:48 storageqe-109 stratisd[4947]: [2025-10-07T14:36:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs xfs in remove_crypt Oct 7 10:36:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.0fwws8vpmount_test with fs xfs Oct 7 10:37:08 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 63ed2f9c-ce86-426a-8f97-8f7580fa3be6 Oct 7 10:37:08 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:37:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0fwws8vpmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext4 in remove_crypt Oct 7 10:37:13 storageqe-109 systemd[1]: tmp-libblockdev.0fwws8vpmount_test.mount: Deactivated successfully. Oct 7 10:37:13 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 63ed2f9c-ce86-426a-8f97-8f7580fa3be6 Oct 7 10:37:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs xfs in remove_crypt Oct 7 10:37:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uv0n1w1umount_test with fs ext4 Oct 7 10:37:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 44187530-35cb-41c0-a0d3-12c4aa0de863 r/w with ordered data mode. Quota mode: none. Oct 7 10:37:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uv0n1w1umount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext3 in remove_crypt Oct 7 10:37:29 storageqe-109 systemd[1]: tmp-libblockdev.uv0n1w1umount_test.mount: Deactivated successfully. Oct 7 10:37:29 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 44187530-35cb-41c0-a0d3-12c4aa0de863. Oct 7 10:37:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext4 in remove_crypt Oct 7 10:37:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext3 in remove_crypt Oct 7 10:37:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.z66zee32mount_test with fs ext3 Oct 7 10:37:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 67d5f3a8-2f08-4035-a3a3-8aeec7a4b1e7 r/w with ordered data mode. Quota mode: none. Oct 7 10:37:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z66zee32mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext2 in remove_crypt Oct 7 10:37:45 storageqe-109 systemd[1]: tmp-libblockdev.z66zee32mount_test.mount: Deactivated successfully. Oct 7 10:37:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 67d5f3a8-2f08-4035-a3a3-8aeec7a4b1e7. Oct 7 10:37:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext3 in remove_crypt Oct 7 10:37:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3lxincj1mount_test with fs ext2 Oct 7 10:37:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:37:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 82af1065-7e4e-44c4-ab16-774a9de3afd2 r/w without journal. Quota mode: none. Oct 7 10:37:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3lxincj1mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext2 in remove_crypt INFO: remove crypt device BszCvQbjJX INFO: finishe the remove crypt device BszCvQbjJX cryptsetup --type 'luks2' --cipher 'serpent-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:38:00 storageqe-109 systemd[1]: tmp-libblockdev.3lxincj1mount_test.mount: Deactivated successfully. Oct 7 10:38:00 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 82af1065-7e4e-44c4-ab16-774a9de3afd2. Oct 7 10:38:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BszCvQbjJX and fs ext2 in remove_crypt Oct 7 10:38:00 storageqe-109 INFO: remove crypt device BszCvQbjJX Oct 7 10:38:00 storageqe-109 INFO: finishe the remove crypt device BszCvQbjJX Oct 7 10:38:00 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain64' --key-size '512' --hash 'sha256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 10:38:00 storageqe-109 stratisd[4947]: [2025-10-07T14:38:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:38:00 storageqe-109 stratisd[4947]: [2025-10-07T14:38:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear xyGVjsuSfn -q Oct 7 10:38:10 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear xyGVjsuSfn -q Oct 7 10:38:10 storageqe-109 stratisd[4947]: [2025-10-07T14:38:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:38:10 storageqe-109 stratisd[4947]: [2025-10-07T14:38:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs xfs in remove_crypt Oct 7 10:38:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ohc7bmgxmount_test with fs xfs Oct 7 10:38:30 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ae13fe87-c5dd-4860-9f6b-44b68510d099 Oct 7 10:38:31 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:38:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ohc7bmgxmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext4 in remove_crypt Oct 7 10:38:36 storageqe-109 systemd[1]: tmp-libblockdev.ohc7bmgxmount_test.mount: Deactivated successfully. Oct 7 10:38:36 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ae13fe87-c5dd-4860-9f6b-44b68510d099 Oct 7 10:38:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs xfs in remove_crypt Oct 7 10:38:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xj55s8e8mount_test with fs ext4 Oct 7 10:38:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f1b16243-27d7-4b1f-ace7-c5010ace3b4f r/w with ordered data mode. Quota mode: none. Oct 7 10:38:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xj55s8e8mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext3 in remove_crypt Oct 7 10:38:51 storageqe-109 systemd[1]: tmp-libblockdev.xj55s8e8mount_test.mount: Deactivated successfully. Oct 7 10:38:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f1b16243-27d7-4b1f-ace7-c5010ace3b4f. Oct 7 10:38:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext4 in remove_crypt Oct 7 10:38:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ho3uapakmount_test with fs ext3 Oct 7 10:39:02 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:39:02 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 68dea5d8-f7e0-42c0-8c9c-2ecc6c477cca r/w with ordered data mode. Quota mode: none. Oct 7 10:39:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ho3uapakmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext2 in remove_crypt Oct 7 10:39:07 storageqe-109 systemd[1]: tmp-libblockdev.ho3uapakmount_test.mount: Deactivated successfully. Oct 7 10:39:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 68dea5d8-f7e0-42c0-8c9c-2ecc6c477cca. Oct 7 10:39:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext3 in remove_crypt Oct 7 10:39:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m8xu6o0omount_test with fs ext2 Oct 7 10:39:17 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:39:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d3b4ed33-a15c-4f7b-9200-050875418960 r/w without journal. Quota mode: none. Oct 7 10:39:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m8xu6o0omount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext2 in remove_crypt INFO: remove crypt device xyGVjsuSfn INFO: finishe the remove crypt device xyGVjsuSfn Oct 7 10:39:23 storageqe-109 systemd[1]: tmp-libblockdev.m8xu6o0omount_test.mount: Deactivated successfully. Oct 7 10:39:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d3b4ed33-a15c-4f7b-9200-050875418960. Oct 7 10:39:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/xyGVjsuSfn and fs ext2 in remove_crypt Oct 7 10:39:23 storageqe-109 INFO: remove crypt device xyGVjsuSfn Oct 7 10:39:23 storageqe-109 INFO: finishe the remove crypt device xyGVjsuSfn INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_cipher_combinations[npo2_linear] #### INFO: #### will start test_keyslot_encryption_variations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:39:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:39:28 storageqe-109 INFO: #### END test_cipher_combinations[npo2_linear] #### Oct 7 10:39:28 storageqe-109 INFO: #### will start test_keyslot_encryption_variations[npo2_linear] ##### Oct 7 10:39:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileUfW Oct 7 10:39:35 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileUfW Oct 7 10:39:35 storageqe-109 stratisd[4947]: [2025-10-07T14:39:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:39:35 storageqe-109 stratisd[4947]: [2025-10-07T14:39:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileUfW' open /dev/mapper/npo2linear yGawUsxpEo -q Oct 7 10:39:45 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileUfW' open /dev/mapper/npo2linear yGawUsxpEo -q Oct 7 10:39:45 storageqe-109 stratisd[4947]: [2025-10-07T14:39:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:39:45 storageqe-109 stratisd[4947]: [2025-10-07T14:39:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs xfs in remove_crypt Oct 7 10:39:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.cxxnd92imount_test with fs xfs Oct 7 10:40:05 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 4f4a9d54-838d-4815-b8c8-2c58251fb149 Oct 7 10:40:05 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:40:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cxxnd92imount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext4 in remove_crypt Oct 7 10:40:10 storageqe-109 systemd[1]: tmp-libblockdev.cxxnd92imount_test.mount: Deactivated successfully. Oct 7 10:40:10 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 4f4a9d54-838d-4815-b8c8-2c58251fb149 Oct 7 10:40:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs xfs in remove_crypt Oct 7 10:40:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.todu1e41mount_test with fs ext4 Oct 7 10:40:20 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 71f8e3ea-d1bb-4aa8-a93c-3c2d854c2326 r/w with ordered data mode. Quota mode: none. Oct 7 10:40:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.todu1e41mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext3 in remove_crypt Oct 7 10:40:25 storageqe-109 systemd[1]: tmp-libblockdev.todu1e41mount_test.mount: Deactivated successfully. Oct 7 10:40:25 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 71f8e3ea-d1bb-4aa8-a93c-3c2d854c2326. Oct 7 10:40:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext4 in remove_crypt Oct 7 10:40:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6k1rz4kkmount_test with fs ext3 Oct 7 10:40:35 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:40:35 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c3c1f642-13c8-4be8-acb0-54a009de523b r/w with ordered data mode. Quota mode: none. Oct 7 10:40:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6k1rz4kkmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext2 in remove_crypt Oct 7 10:40:40 storageqe-109 systemd[1]: tmp-libblockdev.6k1rz4kkmount_test.mount: Deactivated successfully. Oct 7 10:40:40 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c3c1f642-13c8-4be8-acb0-54a009de523b. Oct 7 10:40:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext3 in remove_crypt Oct 7 10:40:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cvrs0j_2mount_test with fs ext2 Oct 7 10:40:50 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:40:50 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 77970708-443a-4c4e-b772-c2ac95e51c1d r/w without journal. Quota mode: none. Oct 7 10:40:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cvrs0j_2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext2 in remove_crypt INFO: remove crypt device yGawUsxpEo INFO: finishe the remove crypt device yGawUsxpEo Oct 7 10:40:55 storageqe-109 systemd[1]: tmp-libblockdev.cvrs0j_2mount_test.mount: Deactivated successfully. Oct 7 10:40:55 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 77970708-443a-4c4e-b772-c2ac95e51c1d. Oct 7 10:40:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yGawUsxpEo and fs ext2 in remove_crypt Oct 7 10:40:55 storageqe-109 INFO: remove crypt device yGawUsxpEo Oct 7 10:40:55 storageqe-109 INFO: finishe the remove crypt device yGawUsxpEo cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileMSB Oct 7 10:40:57 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileMSB Oct 7 10:40:57 storageqe-109 stratisd[4947]: [2025-10-07T14:40:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:40:57 storageqe-109 stratisd[4947]: [2025-10-07T14:40:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileMSB' open /dev/mapper/npo2linear XWsyjDhHve -q Oct 7 10:41:07 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileMSB' open /dev/mapper/npo2linear XWsyjDhHve -q Oct 7 10:41:07 storageqe-109 stratisd[4947]: [2025-10-07T14:41:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:41:07 storageqe-109 stratisd[4947]: [2025-10-07T14:41:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs xfs in remove_crypt Oct 7 10:41:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.jgl26ncdmount_test with fs xfs Oct 7 10:41:27 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 4e321ef5-e582-4116-99b3-d65f9ce3a171 Oct 7 10:41:27 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:41:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jgl26ncdmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext4 in remove_crypt Oct 7 10:41:32 storageqe-109 systemd[1]: tmp-libblockdev.jgl26ncdmount_test.mount: Deactivated successfully. Oct 7 10:41:32 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 4e321ef5-e582-4116-99b3-d65f9ce3a171 Oct 7 10:41:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs xfs in remove_crypt Oct 7 10:41:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1r1eyzd0mount_test with fs ext4 Oct 7 10:41:42 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a3bdb129-305e-4c83-b52b-bb5b62b4e961 r/w with ordered data mode. Quota mode: none. Oct 7 10:41:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1r1eyzd0mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext3 in remove_crypt Oct 7 10:41:47 storageqe-109 systemd[1]: tmp-libblockdev.1r1eyzd0mount_test.mount: Deactivated successfully. Oct 7 10:41:47 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a3bdb129-305e-4c83-b52b-bb5b62b4e961. Oct 7 10:41:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext4 in remove_crypt Oct 7 10:41:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1yh7uv1qmount_test with fs ext3 Oct 7 10:41:57 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:41:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c6b47eb6-5fb4-41e7-96be-5fd1ffb3ae5d r/w with ordered data mode. Quota mode: none. Oct 7 10:41:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1yh7uv1qmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext2 in remove_crypt Oct 7 10:42:02 storageqe-109 systemd[1]: tmp-libblockdev.1yh7uv1qmount_test.mount: Deactivated successfully. Oct 7 10:42:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c6b47eb6-5fb4-41e7-96be-5fd1ffb3ae5d. Oct 7 10:42:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext3 in remove_crypt Oct 7 10:42:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0lqra0x6mount_test with fs ext2 Oct 7 10:42:12 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:42:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f5527e2a-a3c9-4b6b-a3c6-4a36698ae16d r/w without journal. Quota mode: none. Oct 7 10:42:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0lqra0x6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext2 in remove_crypt INFO: remove crypt device XWsyjDhHve INFO: finishe the remove crypt device XWsyjDhHve Oct 7 10:42:17 storageqe-109 systemd[1]: tmp-libblockdev.0lqra0x6mount_test.mount: Deactivated successfully. Oct 7 10:42:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f5527e2a-a3c9-4b6b-a3c6-4a36698ae16d. Oct 7 10:42:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/XWsyjDhHve and fs ext2 in remove_crypt Oct 7 10:42:17 storageqe-109 INFO: remove crypt device XWsyjDhHve Oct 7 10:42:17 storageqe-109 INFO: finishe the remove crypt device XWsyjDhHve cryptsetup --type 'luks2' --keyslot-cipher 'aes-xts-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilevVK Oct 7 10:42:19 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'aes-xts-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilevVK Oct 7 10:42:19 storageqe-109 stratisd[4947]: [2025-10-07T14:42:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:42:19 storageqe-109 stratisd[4947]: [2025-10-07T14:42:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilevVK' open /dev/mapper/npo2linear bXZOtTzknS -q Oct 7 10:42:29 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilevVK' open /dev/mapper/npo2linear bXZOtTzknS -q Oct 7 10:42:29 storageqe-109 stratisd[4947]: [2025-10-07T14:42:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:42:29 storageqe-109 stratisd[4947]: [2025-10-07T14:42:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs xfs in remove_crypt Oct 7 10:42:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._d_l5ayjmount_test with fs xfs Oct 7 10:42:49 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 892dccdb-0db3-479f-beb4-60c039f3ff0a Oct 7 10:42:49 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:42:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev._d_l5ayjmount_test with fs xfs Oct 7 10:42:54 storageqe-109 systemd[1]: tmp-libblockdev._d_l5ayjmount_test.mount: Deactivated successfully. Oct 7 10:42:54 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 892dccdb-0db3-479f-beb4-60c039f3ff0a INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext4 in remove_crypt Oct 7 10:42:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs xfs in remove_crypt Oct 7 10:42:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.baf7i0_emount_test with fs ext4 Oct 7 10:43:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f480c3ec-55dd-40f1-a28c-06f8f618c412 r/w with ordered data mode. Quota mode: none. Oct 7 10:43:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.baf7i0_emount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext3 in remove_crypt Oct 7 10:43:09 storageqe-109 systemd[1]: tmp-libblockdev.baf7i0_emount_test.mount: Deactivated successfully. Oct 7 10:43:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f480c3ec-55dd-40f1-a28c-06f8f618c412. Oct 7 10:43:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext4 in remove_crypt Oct 7 10:43:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jqf2pbdgmount_test with fs ext3 Oct 7 10:43:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:43:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3ced912e-f9f7-4f4a-a505-4fd045c4bf72 r/w with ordered data mode. Quota mode: none. Oct 7 10:43:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jqf2pbdgmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext2 in remove_crypt Oct 7 10:43:24 storageqe-109 systemd[1]: tmp-libblockdev.jqf2pbdgmount_test.mount: Deactivated successfully. Oct 7 10:43:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3ced912e-f9f7-4f4a-a505-4fd045c4bf72. Oct 7 10:43:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext3 in remove_crypt Oct 7 10:43:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3__v4lh0mount_test with fs ext2 Oct 7 10:43:34 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:43:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3da3729e-976c-4038-a2d1-b4f1e5c4c088 r/w without journal. Quota mode: none. Oct 7 10:43:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3__v4lh0mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext2 in remove_crypt INFO: remove crypt device bXZOtTzknS INFO: finishe the remove crypt device bXZOtTzknS Oct 7 10:43:39 storageqe-109 systemd[1]: tmp-libblockdev.3__v4lh0mount_test.mount: Deactivated successfully. Oct 7 10:43:39 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3da3729e-976c-4038-a2d1-b4f1e5c4c088. Oct 7 10:43:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bXZOtTzknS and fs ext2 in remove_crypt Oct 7 10:43:39 storageqe-109 INFO: remove crypt device bXZOtTzknS Oct 7 10:43:39 storageqe-109 INFO: finishe the remove crypt device bXZOtTzknS cryptsetup --type 'luks2' --keyslot-cipher 'twofish-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileGpv Oct 7 10:43:41 storageqe-109 journal: cryptsetup --type 'luks2' --keyslot-cipher 'twofish-cbc-plain64' --keyslot-key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfileGpv Oct 7 10:43:41 storageqe-109 stratisd[4947]: [2025-10-07T14:43:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:43:41 storageqe-109 stratisd[4947]: [2025-10-07T14:43:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileGpv' open /dev/mapper/npo2linear ebYGDnICOR -q Oct 7 10:43:51 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileGpv' open /dev/mapper/npo2linear ebYGDnICOR -q Oct 7 10:43:51 storageqe-109 stratisd[4947]: [2025-10-07T14:43:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:43:51 storageqe-109 stratisd[4947]: [2025-10-07T14:43:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs xfs in remove_crypt Oct 7 10:44:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.c0m1snxemount_test with fs xfs Oct 7 10:44:11 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b953c613-dc2f-492a-9b31-db9ade0a25db Oct 7 10:44:11 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 10:44:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c0m1snxemount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext4 in remove_crypt Oct 7 10:44:16 storageqe-109 systemd[1]: tmp-libblockdev.c0m1snxemount_test.mount: Deactivated successfully. Oct 7 10:44:16 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b953c613-dc2f-492a-9b31-db9ade0a25db Oct 7 10:44:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs xfs in remove_crypt Oct 7 10:44:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kpttkvfmmount_test with fs ext4 Oct 7 10:44:26 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 413060d8-164e-4905-b205-8bd4a71ddd92 r/w with ordered data mode. Quota mode: none. Oct 7 10:44:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kpttkvfmmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext3 in remove_crypt Oct 7 10:44:31 storageqe-109 systemd[1]: tmp-libblockdev.kpttkvfmmount_test.mount: Deactivated successfully. Oct 7 10:44:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 413060d8-164e-4905-b205-8bd4a71ddd92. Oct 7 10:44:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext4 in remove_crypt Oct 7 10:44:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jgo9nsfxmount_test with fs ext3 Oct 7 10:44:41 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 10:44:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 31e01520-256b-493a-9f9f-e995a6aeec1e r/w with ordered data mode. Quota mode: none. Oct 7 10:44:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jgo9nsfxmount_test with fs ext3 Oct 7 10:44:46 storageqe-109 systemd[1]: tmp-libblockdev.jgo9nsfxmount_test.mount: Deactivated successfully. Oct 7 10:44:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 31e01520-256b-493a-9f9f-e995a6aeec1e. INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext2 in remove_crypt Oct 7 10:44:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext3 in remove_crypt Oct 7 10:44:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.55z8ejzmmount_test with fs ext2 Oct 7 10:44:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 10:44:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 231c4f73-ea40-4344-a22d-f899c81d6cf9 r/w without journal. Quota mode: none. Oct 7 10:44:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.55z8ejzmmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext2 in remove_crypt INFO: remove crypt device ebYGDnICOR Oct 7 10:45:01 storageqe-109 systemd[1]: tmp-libblockdev.55z8ejzmmount_test.mount: Deactivated successfully. Oct 7 10:45:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 231c4f73-ea40-4344-a22d-f899c81d6cf9. Oct 7 10:45:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ebYGDnICOR and fs ext2 in remove_crypt Oct 7 10:45:01 storageqe-109 INFO: remove crypt device ebYGDnICOR INFO: finishe the remove crypt device ebYGDnICOR Oct 7 10:45:01 storageqe-109 INFO: finishe the remove crypt device ebYGDnICOR INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_keyslot_encryption_variations[npo2_linear] #### Oct 7 10:45:06 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:45:06 storageqe-109 INFO: #### END test_keyslot_encryption_variations[npo2_linear] #### Oct 7 10:45:06 storageqe-109 stratisd[4947]: [2025-10-07T14:45:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:45:06 storageqe-109 stratisd[4947]: [2025-10-07T14:45:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:45:06 storageqe-109 stratisd[4947]: [2025-10-07T14:45:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:45:06 storageqe-109 stratisd[4947]: [2025-10-07T14:45:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 10:45:07 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 10:45:08 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 10:45:08 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 10:45:08 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 10:45:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 10:45:19 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_integrity_stress_scenarios[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:45:24 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:45:24 storageqe-109 INFO: #### will start test_integrity_stress_scenarios[npo2_linear] ##### Oct 7 10:45:24 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' format /dev/mapper/npo2linear -q Oct 7 10:45:31 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' format /dev/mapper/npo2linear -q Oct 7 10:45:38 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. integritysetup --integrity 'sha256' open /dev/mapper/npo2linear yDgpsdZcrx -q Oct 7 10:45:44 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear yDgpsdZcrx -q integritysetup close yDgpsdZcrx -q Oct 7 10:45:54 storageqe-109 journal: integritysetup close yDgpsdZcrx -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --tag-size '32' --integrity-key-file '/tmp/testfilesgY' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 10:46:05 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --tag-size '32' --integrity-key-file '/tmp/testfilesgY' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilesgY' --integrity-key-size '32' open /dev/mapper/npo2linear yDgpsdZcrx -q Oct 7 10:46:19 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilesgY' --integrity-key-size '32' open /dev/mapper/npo2linear yDgpsdZcrx -q integritysetup close yDgpsdZcrx -q Oct 7 10:46:29 storageqe-109 journal: integritysetup close yDgpsdZcrx -q integritysetup --integrity 'crc32c' --sector-size '4096' --tag-size '4' format /dev/mapper/npo2linear -q Oct 7 10:46:40 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' --tag-size '4' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear yDgpsdZcrx -q Oct 7 10:46:53 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear yDgpsdZcrx -q integritysetup close yDgpsdZcrx -q Oct 7 10:47:03 storageqe-109 journal: integritysetup close yDgpsdZcrx -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_stress_scenarios[npo2_linear] #### INFO: #### will start test_advanced_journal_parameters[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:47:18 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:47:18 storageqe-109 INFO: #### END test_integrity_stress_scenarios[npo2_linear] #### Oct 7 10:47:18 storageqe-109 INFO: #### will start test_advanced_journal_parameters[npo2_linear] ##### Oct 7 10:47:18 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' --journal-watermark '5' --journal-commit-time '50' format /dev/mapper/npo2linear -q Oct 7 10:47:24 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' --journal-watermark '5' --journal-commit-time '50' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' --journal-watermark '5' --journal-commit-time '50' open /dev/mapper/npo2linear oruwgQHyqX -q Oct 7 10:47:38 storageqe-109 journal: integritysetup --integrity 'sha256' --journal-watermark '5' --journal-commit-time '50' open /dev/mapper/npo2linear oruwgQHyqX -q integritysetup status oruwgQHyqX -q Oct 7 10:47:48 storageqe-109 journal: integritysetup status oruwgQHyqX -q integritysetup close oruwgQHyqX -q Oct 7 10:47:59 storageqe-109 journal: integritysetup close oruwgQHyqX -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '2048' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileKoV' --integrity-key-size '64' format /dev/mapper/npo2linear -q Oct 7 10:48:10 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '2048' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileKoV' --integrity-key-size '64' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileKoV' --integrity-key-size '64' open /dev/mapper/npo2linear HeyvZSPLFJ -q Oct 7 10:48:25 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --journal-watermark '95' --journal-commit-time '30000' --integrity-key-file '/tmp/testfileKoV' --integrity-key-size '64' open /dev/mapper/npo2linear HeyvZSPLFJ -q integritysetup status HeyvZSPLFJ -q Oct 7 10:48:35 storageqe-109 journal: integritysetup status HeyvZSPLFJ -q integritysetup close HeyvZSPLFJ -q Oct 7 10:49:16 storageqe-109 journal: integritysetup close HeyvZSPLFJ -q integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '1024' --journal-watermark '33' --journal-commit-time '1337' format /dev/mapper/npo2linear -q Oct 7 10:49:27 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '1024' --journal-watermark '33' --journal-commit-time '1337' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' --journal-watermark '33' --journal-commit-time '1337' open /dev/mapper/npo2linear KxeFPaLnDf -q Oct 7 10:49:40 storageqe-109 journal: integritysetup --integrity 'crc32c' --journal-watermark '33' --journal-commit-time '1337' open /dev/mapper/npo2linear KxeFPaLnDf -q integritysetup status KxeFPaLnDf -q Oct 7 10:49:50 storageqe-109 journal: integritysetup status KxeFPaLnDf -q integritysetup close KxeFPaLnDf -q Oct 7 10:50:02 storageqe-109 journal: integritysetup close KxeFPaLnDf -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_advanced_journal_parameters[npo2_linear] #### INFO: #### will start test_bitmap_mode_advanced[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:50:17 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 10:50:17 storageqe-109 INFO: #### END test_advanced_journal_parameters[npo2_linear] #### Oct 7 10:50:17 storageqe-109 INFO: #### will start test_bitmap_mode_advanced[npo2_linear] ##### Oct 7 10:50:17 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb Oct 7 10:50:22 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb integritysetup --integrity 'crc32c' --bitmap-sectors-per-bit '32768' --bitmap-flush-time '1000' open /dev/mapper/npo2linear eDWjcRKQmt -q --integrity-bitmap-mode Oct 7 10:50:35 storageqe-109 journal: integritysetup --integrity 'crc32c' --bitmap-sectors-per-bit '32768' --bitmap-flush-time '1000' open /dev/mapper/npo2linear eDWjcRKQmt -q --integrity-bitmap-mode integritysetup status eDWjcRKQmt -q Oct 7 10:50:45 storageqe-109 journal: integritysetup status eDWjcRKQmt -q integritysetup status eDWjcRKQmt -q Oct 7 10:50:55 storageqe-109 journal: integritysetup status eDWjcRKQmt -q integritysetup close eDWjcRKQmt -q Oct 7 10:51:07 storageqe-109 journal: integritysetup close eDWjcRKQmt -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb Oct 7 10:51:18 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/sdb integritysetup --integrity 'sha256' --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear QlsPDvfEYS -q --integrity-bitmap-mode Oct 7 10:51:31 storageqe-109 journal: integritysetup --integrity 'sha256' --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear QlsPDvfEYS -q --integrity-bitmap-mode integritysetup status QlsPDvfEYS -q Oct 7 10:51:41 storageqe-109 journal: integritysetup status QlsPDvfEYS -q integritysetup status QlsPDvfEYS -q Oct 7 10:51:51 storageqe-109 journal: integritysetup status QlsPDvfEYS -q integritysetup close QlsPDvfEYS -q Oct 7 10:52:08 storageqe-109 journal: integritysetup close QlsPDvfEYS -q INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### INFO: #### END test_bitmap_mode_advanced[npo2_linear] #### INFO: #### will start test_metadata_device_configurations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### Oct 7 10:52:23 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### Oct 7 10:52:23 storageqe-109 INFO: #### END test_bitmap_mode_advanced[npo2_linear] #### Oct 7 10:52:23 storageqe-109 INFO: #### will start test_metadata_device_configurations[npo2_linear] ##### Oct 7 10:52:23 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdb'] #### integritysetup --data-device '/dev/sdc' --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 10:52:30 storageqe-109 journal: integritysetup --data-device '/dev/sdc' --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 11:00:41 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 11:00:41 storageqe-109 dnf[1188629]: Updating Subscription Management repositories. Oct 7 11:00:41 storageqe-109 dnf[1188629]: Unable to read consumer identity Oct 7 11:00:41 storageqe-109 dnf[1188629]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 11:00:41 storageqe-109 dnf[1188629]: Metadata cache refreshed recently. Oct 7 11:00:41 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 11:00:41 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. integritysetup --integrity 'crc32c' --data-device '/dev/sdc' open /dev/mapper/npo2linear ueGsWBnFHU -q Oct 7 11:04:27 storageqe-109 journal: integritysetup --integrity 'crc32c' --data-device '/dev/sdc' open /dev/mapper/npo2linear ueGsWBnFHU -q integritysetup status ueGsWBnFHU -q Oct 7 11:04:37 storageqe-109 journal: integritysetup status ueGsWBnFHU -q integritysetup close ueGsWBnFHU -q Oct 7 11:04:47 storageqe-109 journal: integritysetup close ueGsWBnFHU -q integritysetup --data-device '/dev/sdd' --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 11:04:59 storageqe-109 journal: integritysetup --data-device '/dev/sdd' --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 11:16:12 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 11:16:12 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 11:16:12 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. integritysetup --integrity 'sha256' --data-device '/dev/sdd' open /dev/mapper/npo2linear osAXiBbuxm -q Oct 7 11:16:57 storageqe-109 journal: integritysetup --integrity 'sha256' --data-device '/dev/sdd' open /dev/mapper/npo2linear osAXiBbuxm -q integritysetup status osAXiBbuxm -q Oct 7 11:17:07 storageqe-109 journal: integritysetup status osAXiBbuxm -q integritysetup close osAXiBbuxm -q Oct 7 11:17:17 storageqe-109 journal: integritysetup close osAXiBbuxm -q INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_metadata_device_configurations[npo2_linear] #### INFO: #### will start test_concurrent_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 7 11:17:32 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 7 11:17:32 storageqe-109 INFO: #### END test_metadata_device_configurations[npo2_linear] #### Oct 7 11:17:32 storageqe-109 INFO: #### will start test_concurrent_operations[npo2_linear] ##### Oct 7 11:17:32 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 11:17:38 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear jXMkhcedHw -q Oct 7 11:17:51 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear jXMkhcedHw -q integritysetup close jXMkhcedHw -q Oct 7 11:18:05 storageqe-109 journal: integritysetup close jXMkhcedHw -q INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_concurrent_operations[npo2_linear] #### INFO: #### will start test_large_device_parameters[npo2_linear] ##### INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 7 11:18:20 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 7 11:18:20 storageqe-109 INFO: #### END test_concurrent_operations[npo2_linear] #### Oct 7 11:18:20 storageqe-109 INFO: #### will start test_large_device_parameters[npo2_linear] ##### Oct 7 11:18:20 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '4096' format /dev/sde -q Oct 7 11:18:27 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '4096' format /dev/sde -q integritysetup --integrity 'crc32c' open /dev/sde StvDrgQOeo -q Oct 7 11:33:34 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/sde StvDrgQOeo -q integritysetup close StvDrgQOeo -q Oct 7 11:33:45 storageqe-109 journal: integritysetup close StvDrgQOeo -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/sdb -q Oct 7 11:33:57 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/sdb -q integritysetup --integrity 'sha256' open /dev/sdb lkYnUIaRcP -q Oct 7 11:45:58 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/sdb lkYnUIaRcP -q integritysetup close lkYnUIaRcP -q Oct 7 11:46:08 storageqe-109 journal: integritysetup close lkYnUIaRcP -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '1024' --integrity-key-file '/tmp/testfilenzd' --integrity-key-size '32' format /dev/sdc -q Oct 7 11:46:20 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '1024' --integrity-key-file '/tmp/testfilenzd' --integrity-key-size '32' format /dev/sdc -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilenzd' --integrity-key-size '32' open /dev/sdc vTuLpFgiHA -q Oct 7 11:59:01 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfilenzd' --integrity-key-size '32' open /dev/sdc vTuLpFgiHA -q integritysetup close vTuLpFgiHA -q Oct 7 11:59:11 storageqe-109 journal: integritysetup close vTuLpFgiHA -q INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_large_device_parameters[npo2_linear] #### INFO: #### will start test_all_supported_sector_sizes[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 7 11:59:26 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 7 11:59:26 storageqe-109 INFO: #### END test_large_device_parameters[npo2_linear] #### Oct 7 11:59:26 storageqe-109 INFO: #### will start test_all_supported_sector_sizes[npo2_linear] ##### Oct 7 11:59:26 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 11:59:32 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear dsvpctoUTq -q Oct 7 11:59:45 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear dsvpctoUTq -q integritysetup status dsvpctoUTq -q Oct 7 11:59:55 storageqe-109 journal: integritysetup status dsvpctoUTq -q integritysetup close dsvpctoUTq -q Oct 7 12:00:05 storageqe-109 journal: integritysetup close dsvpctoUTq -q integritysetup --integrity 'sha1' --tag-size '20' --sector-size '1024' format /dev/mapper/npo2linear -q Oct 7 12:00:16 storageqe-109 journal: integritysetup --integrity 'sha1' --tag-size '20' --sector-size '1024' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear hUXSnHkDIK -q Oct 7 12:00:31 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear hUXSnHkDIK -q integritysetup status hUXSnHkDIK -q Oct 7 12:00:41 storageqe-109 journal: integritysetup status hUXSnHkDIK -q integritysetup close hUXSnHkDIK -q Oct 7 12:00:51 storageqe-109 journal: integritysetup close hUXSnHkDIK -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/mapper/npo2linear -q Oct 7 12:01:02 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '2048' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear phlMxCmWyS -q Oct 7 12:01:16 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear phlMxCmWyS -q integritysetup status phlMxCmWyS -q Oct 7 12:01:26 storageqe-109 journal: integritysetup status phlMxCmWyS -q integritysetup close phlMxCmWyS -q Oct 7 12:01:36 storageqe-109 journal: integritysetup close phlMxCmWyS -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfileRkM' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 12:01:47 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfileRkM' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileRkM' --integrity-key-size '32' open /dev/mapper/npo2linear tiFPfdcDJQ -q Oct 7 12:02:01 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileRkM' --integrity-key-size '32' open /dev/mapper/npo2linear tiFPfdcDJQ -q integritysetup status tiFPfdcDJQ -q Oct 7 12:02:11 storageqe-109 journal: integritysetup status tiFPfdcDJQ -q integritysetup close tiFPfdcDJQ -q Oct 7 12:02:21 storageqe-109 journal: integritysetup close tiFPfdcDJQ -q INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_all_supported_sector_sizes[npo2_linear] #### INFO: #### will start test_recovery_mode_advanced[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 7 12:02:36 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 7 12:02:37 storageqe-109 INFO: #### END test_all_supported_sector_sizes[npo2_linear] #### Oct 7 12:02:37 storageqe-109 INFO: #### will start test_recovery_mode_advanced[npo2_linear] ##### Oct 7 12:02:37 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### integritysetup --integrity 'sha256' format /dev/mapper/npo2linear -q --no-wipe Oct 7 12:02:42 storageqe-109 journal: integritysetup --integrity 'sha256' format /dev/mapper/npo2linear -q --no-wipe integritysetup --integrity 'sha256' open /dev/mapper/npo2linear tfcVWswTxM -q --integrity-recovery-mode Oct 7 12:02:52 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear tfcVWswTxM -q --integrity-recovery-mode integritysetup status tfcVWswTxM -q Oct 7 12:03:02 storageqe-109 journal: integritysetup status tfcVWswTxM -q integritysetup close tfcVWswTxM -q Oct 7 12:03:12 storageqe-109 journal: integritysetup close tfcVWswTxM -q INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_recovery_mode_advanced[npo2_linear] #### Oct 7 12:03:27 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/sdb', '/dev/sdc'] #### Oct 7 12:03:27 storageqe-109 INFO: #### END test_recovery_mode_advanced[npo2_linear] #### Oct 7 12:03:28 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 12:03:29 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 12:03:29 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 12:03:29 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 12:03:29 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 12:03:40 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_signature_verification_basic[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:03:46 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:03:46 storageqe-109 INFO: #### will start test_signature_verification_basic[npo2_linear] ##### Oct 7 12:03:46 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 Oct 7 12:03:51 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 7 12:03:51 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 Oct 7 12:03:59 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. veritysetup verify /dev/mapper/npo2linear /dev/loop0 737144acfa54caab61c8220518dfc2443bcb2e3b83b10c238f3c34f2410d873a /tmp/verity_certs/signature.sig Oct 7 12:04:06 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop0 737144acfa54caab61c8220518dfc2443bcb2e3b83b10c238f3c34f2410d873a /tmp/verity_certs/signature.sig INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_verification_basic[npo2_linear] #### INFO: #### will start test_signature_verification_invalid[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:04:26 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:04:26 storageqe-109 INFO: #### END test_signature_verification_basic[npo2_linear] #### Oct 7 12:04:26 storageqe-109 INFO: #### will start test_signature_verification_invalid[npo2_linear] ##### Oct 7 12:04:26 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop1 Oct 7 12:04:31 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 7 12:04:31 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop1 veritysetup verify /dev/mapper/npo2linear /dev/loop1 812dcf21bb5928f938ded70bda037e08c867eb4132404aeabc466cc5c51bd9c7 /tmp/verity_certs/signature.sig Oct 7 12:04:46 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop1 812dcf21bb5928f938ded70bda037e08c867eb4132404aeabc466cc5c51bd9c7 /tmp/verity_certs/signature.sig INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_verification_invalid[npo2_linear] #### INFO: #### will start test_signature_keyring_integration[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:05:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:05:11 storageqe-109 INFO: #### END test_signature_verification_invalid[npo2_linear] #### Oct 7 12:05:11 storageqe-109 INFO: #### will start test_signature_keyring_integration[npo2_linear] ##### Oct 7 12:05:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop2 Oct 7 12:05:16 storageqe-109 kernel: loop2: detected capacity change from 0 to 12582912 Oct 7 12:05:16 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop2 veritysetup verify /dev/mapper/npo2linear /dev/loop2 c70a6e892dd8478feffafec41e3ee8138f265c18c52d595a826c66b3759c5669 /tmp/verity_certs/signature.sig verity_test Oct 7 12:05:32 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop2 c70a6e892dd8478feffafec41e3ee8138f265c18c52d595a826c66b3759c5669 /tmp/verity_certs/signature.sig verity_test INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_keyring_integration[npo2_linear] #### INFO: #### will start test_signature_multiple_algorithms[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:05:52 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:05:52 storageqe-109 INFO: #### END test_signature_keyring_integration[npo2_linear] #### Oct 7 12:05:52 storageqe-109 INFO: #### will start test_signature_multiple_algorithms[npo2_linear] ##### Oct 7 12:05:52 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop3 Oct 7 12:05:57 storageqe-109 kernel: loop3: detected capacity change from 0 to 12582912 Oct 7 12:05:57 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop3 veritysetup verify /dev/mapper/npo2linear /dev/loop3 e3b8c22d6010307022a11f561ac6abd12cd8907859e9ea17e6331acfb2c062af /tmp/verity_certs/signature.sig Oct 7 12:06:12 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop3 e3b8c22d6010307022a11f561ac6abd12cd8907859e9ea17e6331acfb2c062af /tmp/verity_certs/signature.sig veritysetup --hash 'sha512' format /dev/mapper/npo2linear /dev/loop4 Oct 7 12:06:27 storageqe-109 kernel: loop4: detected capacity change from 0 to 12582912 Oct 7 12:06:27 storageqe-109 journal: veritysetup --hash 'sha512' format /dev/mapper/npo2linear /dev/loop4 veritysetup verify /dev/mapper/npo2linear /dev/loop4 9fb3074b2da6f0119458bdbd0e845585027e02433b111d8279412583b313fb62de95b12ea94f10ae31895f608b7713a5a86b24f3b80e700319c6fcfe61cb9c51 /tmp/verity_certs/signature.sig Oct 7 12:06:47 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop4 9fb3074b2da6f0119458bdbd0e845585027e02433b111d8279412583b313fb62de95b12ea94f10ae31895f608b7713a5a86b24f3b80e700319c6fcfe61cb9c51 /tmp/verity_certs/signature.sig veritysetup --hash 'sha1' format /dev/mapper/npo2linear /dev/loop5 Oct 7 12:07:06 storageqe-109 kernel: loop5: detected capacity change from 0 to 12582912 Oct 7 12:07:06 storageqe-109 journal: veritysetup --hash 'sha1' format /dev/mapper/npo2linear /dev/loop5 veritysetup verify /dev/mapper/npo2linear /dev/loop5 ef44f3b9dec3dedf9fce7ca160da1dabfb02d9f6 /tmp/verity_certs/signature.sig Oct 7 12:07:21 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/loop5 ef44f3b9dec3dedf9fce7ca160da1dabfb02d9f6 /tmp/verity_certs/signature.sig INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_multiple_algorithms[npo2_linear] #### INFO: #### will start test_signature_enforcement_module_param[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:07:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:07:41 storageqe-109 INFO: #### END test_signature_multiple_algorithms[npo2_linear] #### Oct 7 12:07:41 storageqe-109 INFO: #### will start test_signature_enforcement_module_param[npo2_linear] ##### Oct 7 12:07:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop6 Oct 7 12:07:46 storageqe-109 kernel: loop6: detected capacity change from 0 to 12582912 Oct 7 12:07:46 storageqe-109 journal: veritysetup --hash 'sha256' format /dev/mapper/npo2linear /dev/loop6 veritysetup create kOscofXFEi /dev/mapper/npo2linear /dev/loop6 9f2be47040a493ee2de355dac40b1bec74eea39398019a469992cace61a4b839 Oct 7 12:08:01 storageqe-109 journal: veritysetup create kOscofXFEi /dev/mapper/npo2linear /dev/loop6 9f2be47040a493ee2de355dac40b1bec74eea39398019a469992cace61a4b839 Oct 7 12:08:01 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close kOscofXFEi Oct 7 12:08:11 storageqe-109 journal: veritysetup close kOscofXFEi INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_enforcement_module_param[npo2_linear] #### INFO: #### will start test_signature_platform_keyring[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:08:26 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:08:26 storageqe-109 INFO: #### END test_signature_enforcement_module_param[npo2_linear] #### Oct 7 12:08:26 storageqe-109 INFO: #### will start test_signature_platform_keyring[npo2_linear] ##### Oct 7 12:08:26 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_signature_platform_keyring[npo2_linear] #### Oct 7 12:08:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:08:36 storageqe-109 INFO: #### END test_signature_platform_keyring[npo2_linear] #### Oct 7 12:08:37 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 12:08:38 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 12:08:39 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 12:08:39 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 12:08:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 12:08:49 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_dm_crypt_module_parameters[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:08:55 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:08:55 storageqe-109 INFO: #### will start test_dm_crypt_module_parameters[npo2_linear] ##### Oct 7 12:08:55 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 12:09:00 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 12:09:00 storageqe-109 stratisd[4947]: [2025-10-07T16:09:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:09:00 storageqe-109 stratisd[4947]: [2025-10-07T16:09:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:09:09 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/mapper/npo2linear gbIpqMEkxP -q Oct 7 12:09:10 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear gbIpqMEkxP -q Oct 7 12:09:10 storageqe-109 stratisd[4947]: [2025-10-07T16:09:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:09:10 storageqe-109 stratisd[4947]: [2025-10-07T16:09:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs xfs in remove_crypt Oct 7 12:09:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.6defr3mpmount_test with fs xfs Oct 7 12:09:30 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 899b92c9-13ba-4829-9cb4-dc515456d4d0 Oct 7 12:09:30 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 12:09:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6defr3mpmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext4 in remove_crypt Oct 7 12:09:36 storageqe-109 systemd[1]: tmp-libblockdev.6defr3mpmount_test.mount: Deactivated successfully. Oct 7 12:09:36 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 899b92c9-13ba-4829-9cb4-dc515456d4d0 Oct 7 12:09:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs xfs in remove_crypt Oct 7 12:09:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.go8spf17mount_test with fs ext4 Oct 7 12:09:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a62ada5d-0d4d-43ce-8a65-7a2fa2cd7fca r/w with ordered data mode. Quota mode: none. Oct 7 12:09:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.go8spf17mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext3 in remove_crypt Oct 7 12:09:51 storageqe-109 systemd[1]: tmp-libblockdev.go8spf17mount_test.mount: Deactivated successfully. Oct 7 12:09:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a62ada5d-0d4d-43ce-8a65-7a2fa2cd7fca. Oct 7 12:09:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext4 in remove_crypt Oct 7 12:09:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jvk6pw2ymount_test with fs ext3 Oct 7 12:10:01 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 12:10:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4301446f-7ad2-45d3-82c3-e417d2c03a14 r/w with ordered data mode. Quota mode: none. Oct 7 12:10:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jvk6pw2ymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext2 in remove_crypt Oct 7 12:10:06 storageqe-109 systemd[1]: tmp-libblockdev.jvk6pw2ymount_test.mount: Deactivated successfully. Oct 7 12:10:06 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4301446f-7ad2-45d3-82c3-e417d2c03a14. Oct 7 12:10:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext3 in remove_crypt Oct 7 12:10:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3kko3pn3mount_test with fs ext2 Oct 7 12:10:16 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 12:10:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 55c18b78-76dd-4477-bdd3-c9acf14e4181 r/w without journal. Quota mode: none. Oct 7 12:10:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3kko3pn3mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext2 in remove_crypt INFO: remove crypt device gbIpqMEkxP INFO: finishe the remove crypt device gbIpqMEkxP Oct 7 12:10:21 storageqe-109 systemd[1]: tmp-libblockdev.3kko3pn3mount_test.mount: Deactivated successfully. Oct 7 12:10:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 55c18b78-76dd-4477-bdd3-c9acf14e4181. Oct 7 12:10:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/gbIpqMEkxP and fs ext2 in remove_crypt Oct 7 12:10:21 storageqe-109 INFO: remove crypt device gbIpqMEkxP Oct 7 12:10:21 storageqe-109 INFO: finishe the remove crypt device gbIpqMEkxP INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_crypt_module_parameters[npo2_linear] #### INFO: #### will start test_dm_verity_loadpin_integration[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:10:26 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:10:26 storageqe-109 INFO: #### END test_dm_crypt_module_parameters[npo2_linear] #### Oct 7 12:10:26 storageqe-109 INFO: #### will start test_dm_verity_loadpin_integration[npo2_linear] ##### Oct 7 12:10:26 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 Oct 7 12:10:31 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 7 12:10:31 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' format /dev/mapper/npo2linear /dev/loop0 veritysetup create UVsytuCejB /dev/mapper/npo2linear /dev/loop0 be4acd32effaff48f8cf0d11b4337b43ceeb1d734b3a8e21afd0b9057f2cb634 Oct 7 12:10:46 storageqe-109 journal: veritysetup create UVsytuCejB /dev/mapper/npo2linear /dev/loop0 be4acd32effaff48f8cf0d11b4337b43ceeb1d734b3a8e21afd0b9057f2cb634 Oct 7 12:10:46 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close UVsytuCejB Oct 7 12:10:56 storageqe-109 journal: veritysetup close UVsytuCejB INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_loadpin_integration[npo2_linear] #### INFO: #### will start test_memory_pressure_scenarios[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:11:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:11:11 storageqe-109 INFO: #### END test_dm_verity_loadpin_integration[npo2_linear] #### Oct 7 12:11:11 storageqe-109 INFO: #### will start test_memory_pressure_scenarios[npo2_linear] ##### Oct 7 12:11:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 12:11:16 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 12:11:16 storageqe-109 stratisd[4947]: [2025-10-07T16:11:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:11:16 storageqe-109 stratisd[4947]: [2025-10-07T16:11:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear pfhHnsFaIg -q Oct 7 12:11:26 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear pfhHnsFaIg -q Oct 7 12:11:26 storageqe-109 stratisd[4947]: [2025-10-07T16:11:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:11:26 storageqe-109 stratisd[4947]: [2025-10-07T16:11:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs xfs in remove_crypt Oct 7 12:11:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.r5odop30mount_test with fs xfs Oct 7 12:11:47 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 72aed2c7-e473-4b14-b134-18ce00343f97 Oct 7 12:11:47 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 12:11:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r5odop30mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext4 in remove_crypt Oct 7 12:11:52 storageqe-109 systemd[1]: tmp-libblockdev.r5odop30mount_test.mount: Deactivated successfully. Oct 7 12:11:52 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 72aed2c7-e473-4b14-b134-18ce00343f97 Oct 7 12:11:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs xfs in remove_crypt Oct 7 12:11:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3rnj1_wzmount_test with fs ext4 Oct 7 12:12:02 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1ca691ac-3678-47cf-9a26-8c012cb8409e r/w with ordered data mode. Quota mode: none. Oct 7 12:12:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3rnj1_wzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext3 in remove_crypt Oct 7 12:12:07 storageqe-109 systemd[1]: tmp-libblockdev.3rnj1_wzmount_test.mount: Deactivated successfully. Oct 7 12:12:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1ca691ac-3678-47cf-9a26-8c012cb8409e. Oct 7 12:12:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext4 in remove_crypt Oct 7 12:12:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.frwr_e9emount_test with fs ext3 Oct 7 12:12:17 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 12:12:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1519e51b-46e6-4e83-aaee-286bb19db907 r/w with ordered data mode. Quota mode: none. Oct 7 12:12:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.frwr_e9emount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext2 in remove_crypt Oct 7 12:12:22 storageqe-109 systemd[1]: tmp-libblockdev.frwr_e9emount_test.mount: Deactivated successfully. Oct 7 12:12:22 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1519e51b-46e6-4e83-aaee-286bb19db907. Oct 7 12:12:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext3 in remove_crypt Oct 7 12:12:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dx9ecfckmount_test with fs ext2 Oct 7 12:12:32 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 12:12:32 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a5377863-843e-4fa9-8e18-eadd0742b07f r/w without journal. Quota mode: none. Oct 7 12:12:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dx9ecfckmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext2 in remove_crypt INFO: remove crypt device pfhHnsFaIg INFO: finishe the remove crypt device pfhHnsFaIg Oct 7 12:12:37 storageqe-109 systemd[1]: tmp-libblockdev.dx9ecfckmount_test.mount: Deactivated successfully. Oct 7 12:12:37 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a5377863-843e-4fa9-8e18-eadd0742b07f. Oct 7 12:12:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/pfhHnsFaIg and fs ext2 in remove_crypt Oct 7 12:12:37 storageqe-109 INFO: remove crypt device pfhHnsFaIg Oct 7 12:12:37 storageqe-109 INFO: finishe the remove crypt device pfhHnsFaIg INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_memory_pressure_scenarios[npo2_linear] #### INFO: #### will start test_io_error_injection[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:12:42 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:12:42 storageqe-109 INFO: #### END test_memory_pressure_scenarios[npo2_linear] #### Oct 7 12:12:42 storageqe-109 INFO: #### will start test_io_error_injection[npo2_linear] ##### Oct 7 12:12:42 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/koXBRGTwin -q Oct 7 12:12:47 storageqe-109 stratisd[4947]: [2025-10-07T16:12:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:12:47 storageqe-109 stratisd[4947]: [2025-10-07T16:12:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:12:47 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/koXBRGTwin -q Oct 7 12:12:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, lost async page write Oct 7 12:12:47 storageqe-109 stratisd[4947]: [2025-10-07T16:12:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:12:47 storageqe-109 stratisd[4947]: [2025-10-07T16:12:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:12:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, lost async page write Oct 7 12:12:47 storageqe-109 stratisd[4947]: [2025-10-07T16:12:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:12:47 storageqe-109 stratisd[4947]: [2025-10-07T16:12:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_io_error_injection[npo2_linear] #### INFO: #### will start test_device_removal_scenarios[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:12:52 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:12:52 storageqe-109 INFO: #### END test_io_error_injection[npo2_linear] #### Oct 7 12:12:52 storageqe-109 INFO: #### will start test_device_removal_scenarios[npo2_linear] ##### Oct 7 12:12:52 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q Oct 7 12:12:57 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 7 12:12:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q Oct 7 12:12:57 storageqe-109 stratisd[4947]: [2025-10-07T16:12:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:12:57 storageqe-109 stratisd[4947]: [2025-10-07T16:12:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/loop1 fgIGEZoJFH -q Oct 7 12:13:07 storageqe-109 journal: cryptsetup open /dev/loop1 fgIGEZoJFH -q Oct 7 12:13:07 storageqe-109 stratisd[4947]: [2025-10-07T16:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:07 storageqe-109 stratisd[4947]: [2025-10-07T16:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status fgIGEZoJFH -q Oct 7 12:13:17 storageqe-109 journal: cryptsetup status fgIGEZoJFH -q Oct 7 12:13:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1568752, async page read INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_device_removal_scenarios[npo2_linear] #### INFO: #### will start test_concurrent_device_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:13:32 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:13:32 storageqe-109 INFO: #### END test_device_removal_scenarios[npo2_linear] #### Oct 7 12:13:32 storageqe-109 INFO: #### will start test_concurrent_device_operations[npo2_linear] ##### Oct 7 12:13:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop3 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop4 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop2 -q Oct 7 12:13:37 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 7 12:13:37 storageqe-109 kernel: loop2: detected capacity change from 0 to 12582912 Oct 7 12:13:37 storageqe-109 kernel: loop3: detected capacity change from 0 to 12582912 Oct 7 12:13:37 storageqe-109 kernel: loop4: detected capacity change from 0 to 12582912 Oct 7 12:13:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop4 -q Oct 7 12:13:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop2 -q Oct 7 12:13:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop3 -q Oct 7 12:13:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/loop1 -q Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:37 storageqe-109 stratisd[4947]: [2025-10-07T16:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/loop3 zefKBLItAx -q cryptsetup open /dev/loop1 AarChqRnwV -q cryptsetup open /dev/loop4 TqKtwxPrHa -q cryptsetup open /dev/loop2 VoCZMjUBKP -q Oct 7 12:13:47 storageqe-109 journal: cryptsetup open /dev/loop3 zefKBLItAx -q Oct 7 12:13:47 storageqe-109 journal: cryptsetup open /dev/loop1 AarChqRnwV -q Oct 7 12:13:47 storageqe-109 stratisd[4947]: [2025-10-07T16:13:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:47 storageqe-109 stratisd[4947]: [2025-10-07T16:13:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:47 storageqe-109 journal: cryptsetup open /dev/loop4 TqKtwxPrHa -q Oct 7 12:13:48 storageqe-109 stratisd[4947]: [2025-10-07T16:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:48 storageqe-109 stratisd[4947]: [2025-10-07T16:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:48 storageqe-109 stratisd[4947]: [2025-10-07T16:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:48 storageqe-109 stratisd[4947]: [2025-10-07T16:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:48 storageqe-109 journal: cryptsetup open /dev/loop2 VoCZMjUBKP -q Oct 7 12:13:48 storageqe-109 stratisd[4947]: [2025-10-07T16:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:13:48 storageqe-109 stratisd[4947]: [2025-10-07T16:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_concurrent_device_operations[npo2_linear] #### Oct 7 12:14:03 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:14:03 storageqe-109 INFO: #### END test_concurrent_device_operations[npo2_linear] #### Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:03 storageqe-109 stratisd[4947]: [2025-10-07T16:14:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:04 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 12:14:05 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 12:14:05 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 12:14:05 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 12:14:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 12:14:16 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_luks[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:14:21 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:14:21 storageqe-109 INFO: #### will start test_luks[npo2_linear] ##### Oct 7 12:14:21 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 12:14:26 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 12:14:34 storageqe-109 stratisd[4947]: [2025-10-07T16:14:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:34 storageqe-109 stratisd[4947]: [2025-10-07T16:14:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:35 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --key-description 'mykey' --token-id '10' token add /dev/mapper/npo2linear -q Oct 7 12:14:44 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '10' token add /dev/mapper/npo2linear -q Oct 7 12:14:44 storageqe-109 stratisd[4947]: [2025-10-07T16:14:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:44 storageqe-109 stratisd[4947]: [2025-10-07T16:14:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear hxvk -q --allow-discards --token-only --token-id 10 Oct 7 12:14:54 storageqe-109 stratisd[4947]: [2025-10-07T16:14:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:54 storageqe-109 stratisd[4947]: [2025-10-07T16:14:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:54 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear hxvk -q --allow-discards --token-only --token-id 10 Oct 7 12:14:56 storageqe-109 stratisd[4947]: [2025-10-07T16:14:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:14:56 storageqe-109 stratisd[4947]: [2025-10-07T16:14:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:08 storageqe-109 stratisd[4947]: [2025-10-07T16:15:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:08 storageqe-109 stratisd[4947]: [2025-10-07T16:15:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:08 storageqe-109 stratisd[4947]: [2025-10-07T16:15:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:08 storageqe-109 stratisd[4947]: [2025-10-07T16:15:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device hxvk INFO: finishe the remove crypt device hxvk Oct 7 12:15:10 storageqe-109 stratisd[4947]: [2025-10-07T16:15:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:10 storageqe-109 stratisd[4947]: [2025-10-07T16:15:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:10 storageqe-109 INFO: remove crypt device hxvk Oct 7 12:15:10 storageqe-109 INFO: finishe the remove crypt device hxvk INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks[npo2_linear] #### INFO: #### will start test_luks_bz2003748[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:15:15 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:15:15 storageqe-109 INFO: #### END test_luks[npo2_linear] #### Oct 7 12:15:15 storageqe-109 INFO: #### will start test_luks_bz2003748[npo2_linear] ##### Oct 7 12:15:15 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup erase /dev/mapper/npo2linear -q Oct 7 12:15:20 storageqe-109 journal: cryptsetup erase /dev/mapper/npo2linear -q Oct 7 12:15:20 storageqe-109 stratisd[4947]: [2025-10-07T16:15:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:20 storageqe-109 stratisd[4947]: [2025-10-07T16:15:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '32m' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 12:15:30 storageqe-109 journal: cryptsetup --reduce-device-size '32m' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 12:15:39 storageqe-109 stratisd[4947]: [2025-10-07T16:15:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:39 storageqe-109 stratisd[4947]: [2025-10-07T16:15:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:45 storageqe-109 stratisd[4947]: [2025-10-07T16:15:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:15:45 storageqe-109 stratisd[4947]: [2025-10-07T16:15:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --header 'key1-key2' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 7 12:15:55 storageqe-109 journal: cryptsetup --header 'key1-key2' reencrypt /dev/mapper/npo2linear -q --decrypt INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:16:20 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz2003748[npo2_linear] #### INFO: #### will start test_luks_paramter[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:16:20 storageqe-109 INFO: #### END test_luks_bz2003748[npo2_linear] #### Oct 7 12:16:20 storageqe-109 INFO: #### will start test_luks_paramter[npo2_linear] ##### Oct 7 12:16:20 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:16:25 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:16:27 storageqe-109 stratisd[4947]: [2025-10-07T16:16:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:16:27 storageqe-109 stratisd[4947]: [2025-10-07T16:16:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:16:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:16:37 storageqe-109 stratisd[4947]: [2025-10-07T16:16:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:16:37 storageqe-109 stratisd[4947]: [2025-10-07T16:16:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:16:48 storageqe-109 stratisd[4947]: [2025-10-07T16:16:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:16:48 storageqe-109 stratisd[4947]: [2025-10-07T16:16:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:16:48 storageqe-109 stratisd[4947]: [2025-10-07T16:16:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:16:48 storageqe-109 stratisd[4947]: [2025-10-07T16:16:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:16:48 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:16:48 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:16:48 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:16:50 storageqe-109 stratisd[4947]: [2025-10-07T16:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:16:50 storageqe-109 stratisd[4947]: [2025-10-07T16:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:17:00 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:17:00 storageqe-109 stratisd[4947]: [2025-10-07T16:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:17:00 storageqe-109 stratisd[4947]: [2025-10-07T16:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:17:11 storageqe-109 stratisd[4947]: [2025-10-07T16:17:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:17:11 storageqe-109 stratisd[4947]: [2025-10-07T16:17:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:17:11 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:17:11 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:17:11 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:18:36 storageqe-109 stratisd[4947]: [2025-10-07T16:18:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:18:36 storageqe-109 stratisd[4947]: [2025-10-07T16:18:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:18:46 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:19:16 storageqe-109 stratisd[4947]: [2025-10-07T16:19:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:19:16 storageqe-109 stratisd[4947]: [2025-10-07T16:19:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:19:46 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 12:19:46 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 12:19:46 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:19:56 storageqe-109 stratisd[4947]: [2025-10-07T16:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:19:56 storageqe-109 stratisd[4947]: [2025-10-07T16:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:19:56 storageqe-109 stratisd[4947]: [2025-10-07T16:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:19:56 storageqe-109 stratisd[4947]: [2025-10-07T16:19:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:19:56 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:19:56 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:19:56 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:21:21 storageqe-109 stratisd[4947]: [2025-10-07T16:21:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:21:21 storageqe-109 stratisd[4947]: [2025-10-07T16:21:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:21:31 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:22:01 storageqe-109 stratisd[4947]: [2025-10-07T16:22:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:22:01 storageqe-109 stratisd[4947]: [2025-10-07T16:22:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:22:41 storageqe-109 stratisd[4947]: [2025-10-07T16:22:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:22:41 storageqe-109 stratisd[4947]: [2025-10-07T16:22:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:22:41 storageqe-109 stratisd[4947]: [2025-10-07T16:22:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:22:41 storageqe-109 stratisd[4947]: [2025-10-07T16:22:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:22:41 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:22:41 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:22:41 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:22:43 storageqe-109 stratisd[4947]: [2025-10-07T16:22:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:22:43 storageqe-109 stratisd[4947]: [2025-10-07T16:22:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:22:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:22:54 storageqe-109 stratisd[4947]: [2025-10-07T16:22:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:22:54 storageqe-109 stratisd[4947]: [2025-10-07T16:22:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:23:04 storageqe-109 stratisd[4947]: [2025-10-07T16:23:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:04 storageqe-109 stratisd[4947]: [2025-10-07T16:23:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:04 storageqe-109 stratisd[4947]: [2025-10-07T16:23:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:04 storageqe-109 stratisd[4947]: [2025-10-07T16:23:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:04 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:23:04 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:23:04 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:23:06 storageqe-109 stratisd[4947]: [2025-10-07T16:23:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:06 storageqe-109 stratisd[4947]: [2025-10-07T16:23:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:23:16 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:23:17 storageqe-109 stratisd[4947]: [2025-10-07T16:23:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:17 storageqe-109 stratisd[4947]: [2025-10-07T16:23:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:23:27 storageqe-109 stratisd[4947]: [2025-10-07T16:23:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:27 storageqe-109 stratisd[4947]: [2025-10-07T16:23:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:27 storageqe-109 stratisd[4947]: [2025-10-07T16:23:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:27 storageqe-109 stratisd[4947]: [2025-10-07T16:23:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:23:27 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:23:27 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:23:27 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:24:52 storageqe-109 stratisd[4947]: [2025-10-07T16:24:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:24:52 storageqe-109 stratisd[4947]: [2025-10-07T16:24:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:25:02 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:25:32 storageqe-109 stratisd[4947]: [2025-10-07T16:25:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:25:32 storageqe-109 stratisd[4947]: [2025-10-07T16:25:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:26:13 storageqe-109 stratisd[4947]: [2025-10-07T16:26:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:26:13 storageqe-109 stratisd[4947]: [2025-10-07T16:26:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:26:13 storageqe-109 stratisd[4947]: [2025-10-07T16:26:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:26:13 storageqe-109 stratisd[4947]: [2025-10-07T16:26:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:26:13 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:26:13 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:26:13 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:27:38 storageqe-109 stratisd[4947]: [2025-10-07T16:27:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:27:38 storageqe-109 stratisd[4947]: [2025-10-07T16:27:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:27:48 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:28:18 storageqe-109 stratisd[4947]: [2025-10-07T16:28:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:28:18 storageqe-109 stratisd[4947]: [2025-10-07T16:28:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:28:58 storageqe-109 stratisd[4947]: [2025-10-07T16:28:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:28:58 storageqe-109 stratisd[4947]: [2025-10-07T16:28:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:28:58 storageqe-109 stratisd[4947]: [2025-10-07T16:28:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:28:58 storageqe-109 stratisd[4947]: [2025-10-07T16:28:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:28:58 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:28:58 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:28:59 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:29:01 storageqe-109 stratisd[4947]: [2025-10-07T16:29:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:01 storageqe-109 stratisd[4947]: [2025-10-07T16:29:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:29:11 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:29:11 storageqe-109 stratisd[4947]: [2025-10-07T16:29:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:11 storageqe-109 stratisd[4947]: [2025-10-07T16:29:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:21 storageqe-109 stratisd[4947]: [2025-10-07T16:29:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:21 storageqe-109 stratisd[4947]: [2025-10-07T16:29:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:21 storageqe-109 stratisd[4947]: [2025-10-07T16:29:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:21 storageqe-109 stratisd[4947]: [2025-10-07T16:29:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:29:21 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:29:21 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:29:22 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:29:24 storageqe-109 stratisd[4947]: [2025-10-07T16:29:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:24 storageqe-109 stratisd[4947]: [2025-10-07T16:29:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:29:34 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:29:34 storageqe-109 stratisd[4947]: [2025-10-07T16:29:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:34 storageqe-109 stratisd[4947]: [2025-10-07T16:29:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:29:44 storageqe-109 stratisd[4947]: [2025-10-07T16:29:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:44 storageqe-109 stratisd[4947]: [2025-10-07T16:29:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:44 storageqe-109 stratisd[4947]: [2025-10-07T16:29:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:44 storageqe-109 stratisd[4947]: [2025-10-07T16:29:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:29:44 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:29:45 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:29:45 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:31:09 storageqe-109 stratisd[4947]: [2025-10-07T16:31:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:31:09 storageqe-109 stratisd[4947]: [2025-10-07T16:31:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:31:20 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:31:50 storageqe-109 stratisd[4947]: [2025-10-07T16:31:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:31:50 storageqe-109 stratisd[4947]: [2025-10-07T16:31:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:32:30 storageqe-109 stratisd[4947]: [2025-10-07T16:32:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:32:30 storageqe-109 stratisd[4947]: [2025-10-07T16:32:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:32:30 storageqe-109 stratisd[4947]: [2025-10-07T16:32:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:32:30 storageqe-109 stratisd[4947]: [2025-10-07T16:32:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:32:30 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:32:30 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:32:30 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:33:55 storageqe-109 stratisd[4947]: [2025-10-07T16:33:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:33:55 storageqe-109 stratisd[4947]: [2025-10-07T16:33:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:34:05 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:34:35 storageqe-109 stratisd[4947]: [2025-10-07T16:34:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:34:35 storageqe-109 stratisd[4947]: [2025-10-07T16:34:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:35:15 storageqe-109 stratisd[4947]: [2025-10-07T16:35:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:15 storageqe-109 stratisd[4947]: [2025-10-07T16:35:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:15 storageqe-109 stratisd[4947]: [2025-10-07T16:35:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:15 storageqe-109 stratisd[4947]: [2025-10-07T16:35:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:16 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:35:16 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:35:16 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:35:18 storageqe-109 stratisd[4947]: [2025-10-07T16:35:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:18 storageqe-109 stratisd[4947]: [2025-10-07T16:35:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:35:28 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:35:28 storageqe-109 stratisd[4947]: [2025-10-07T16:35:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:28 storageqe-109 stratisd[4947]: [2025-10-07T16:35:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:35:38 storageqe-109 stratisd[4947]: [2025-10-07T16:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:38 storageqe-109 stratisd[4947]: [2025-10-07T16:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:38 storageqe-109 stratisd[4947]: [2025-10-07T16:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:38 storageqe-109 stratisd[4947]: [2025-10-07T16:35:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:38 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:35:39 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:35:39 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:35:41 storageqe-109 stratisd[4947]: [2025-10-07T16:35:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:41 storageqe-109 stratisd[4947]: [2025-10-07T16:35:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:35:51 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:35:51 storageqe-109 stratisd[4947]: [2025-10-07T16:35:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:35:51 storageqe-109 stratisd[4947]: [2025-10-07T16:35:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:36:01 storageqe-109 stratisd[4947]: [2025-10-07T16:36:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:36:01 storageqe-109 stratisd[4947]: [2025-10-07T16:36:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:36:01 storageqe-109 stratisd[4947]: [2025-10-07T16:36:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:36:01 storageqe-109 stratisd[4947]: [2025-10-07T16:36:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:36:01 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:36:02 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:36:02 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:37:27 storageqe-109 stratisd[4947]: [2025-10-07T16:37:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:37:27 storageqe-109 stratisd[4947]: [2025-10-07T16:37:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:37:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:38:07 storageqe-109 stratisd[4947]: [2025-10-07T16:38:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:38:07 storageqe-109 stratisd[4947]: [2025-10-07T16:38:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:38:47 storageqe-109 stratisd[4947]: [2025-10-07T16:38:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:38:47 storageqe-109 stratisd[4947]: [2025-10-07T16:38:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:38:47 storageqe-109 stratisd[4947]: [2025-10-07T16:38:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:38:47 storageqe-109 stratisd[4947]: [2025-10-07T16:38:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:38:47 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:38:47 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:38:47 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:40:12 storageqe-109 stratisd[4947]: [2025-10-07T16:40:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:40:12 storageqe-109 stratisd[4947]: [2025-10-07T16:40:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:40:22 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:40:52 storageqe-109 stratisd[4947]: [2025-10-07T16:40:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:40:52 storageqe-109 stratisd[4947]: [2025-10-07T16:40:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:41:32 storageqe-109 stratisd[4947]: [2025-10-07T16:41:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:32 storageqe-109 stratisd[4947]: [2025-10-07T16:41:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:32 storageqe-109 stratisd[4947]: [2025-10-07T16:41:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:32 storageqe-109 stratisd[4947]: [2025-10-07T16:41:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:32 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:41:32 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:41:32 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:41:34 storageqe-109 stratisd[4947]: [2025-10-07T16:41:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:34 storageqe-109 stratisd[4947]: [2025-10-07T16:41:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:41:44 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:41:45 storageqe-109 stratisd[4947]: [2025-10-07T16:41:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:45 storageqe-109 stratisd[4947]: [2025-10-07T16:41:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:41:55 storageqe-109 stratisd[4947]: [2025-10-07T16:41:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:55 storageqe-109 stratisd[4947]: [2025-10-07T16:41:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:55 storageqe-109 stratisd[4947]: [2025-10-07T16:41:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:55 storageqe-109 stratisd[4947]: [2025-10-07T16:41:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:55 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:41:55 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:41:55 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:41:57 storageqe-109 stratisd[4947]: [2025-10-07T16:41:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:41:57 storageqe-109 stratisd[4947]: [2025-10-07T16:41:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:42:07 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:42:08 storageqe-109 stratisd[4947]: [2025-10-07T16:42:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:42:08 storageqe-109 stratisd[4947]: [2025-10-07T16:42:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:42:18 storageqe-109 stratisd[4947]: [2025-10-07T16:42:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:42:18 storageqe-109 stratisd[4947]: [2025-10-07T16:42:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:42:18 storageqe-109 stratisd[4947]: [2025-10-07T16:42:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:42:18 storageqe-109 stratisd[4947]: [2025-10-07T16:42:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:42:18 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:42:18 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:42:18 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:43:43 storageqe-109 stratisd[4947]: [2025-10-07T16:43:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:43:43 storageqe-109 stratisd[4947]: [2025-10-07T16:43:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:43:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:44:23 storageqe-109 stratisd[4947]: [2025-10-07T16:44:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:44:23 storageqe-109 stratisd[4947]: [2025-10-07T16:44:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:45:04 storageqe-109 stratisd[4947]: [2025-10-07T16:45:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:45:04 storageqe-109 stratisd[4947]: [2025-10-07T16:45:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:45:04 storageqe-109 stratisd[4947]: [2025-10-07T16:45:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:45:04 storageqe-109 stratisd[4947]: [2025-10-07T16:45:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:45:04 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:45:04 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:45:04 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:46:29 storageqe-109 stratisd[4947]: [2025-10-07T16:46:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:46:29 storageqe-109 stratisd[4947]: [2025-10-07T16:46:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:46:39 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:47:09 storageqe-109 stratisd[4947]: [2025-10-07T16:47:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:47:09 storageqe-109 stratisd[4947]: [2025-10-07T16:47:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg Oct 7 12:47:49 storageqe-109 stratisd[4947]: [2025-10-07T16:47:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:47:49 storageqe-109 stratisd[4947]: [2025-10-07T16:47:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:47:49 storageqe-109 stratisd[4947]: [2025-10-07T16:47:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:47:49 storageqe-109 stratisd[4947]: [2025-10-07T16:47:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:47:49 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:47:49 storageqe-109 INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:47:49 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:47:51 storageqe-109 stratisd[4947]: [2025-10-07T16:47:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:47:51 storageqe-109 stratisd[4947]: [2025-10-07T16:47:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:48:01 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:48:01 storageqe-109 stratisd[4947]: [2025-10-07T16:48:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:01 storageqe-109 stratisd[4947]: [2025-10-07T16:48:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:48:11 storageqe-109 stratisd[4947]: [2025-10-07T16:48:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:11 storageqe-109 stratisd[4947]: [2025-10-07T16:48:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:11 storageqe-109 stratisd[4947]: [2025-10-07T16:48:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:11 storageqe-109 stratisd[4947]: [2025-10-07T16:48:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:11 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:48:11 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:48:11 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:48:14 storageqe-109 stratisd[4947]: [2025-10-07T16:48:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:14 storageqe-109 stratisd[4947]: [2025-10-07T16:48:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:48:24 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:48:24 storageqe-109 stratisd[4947]: [2025-10-07T16:48:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:24 storageqe-109 stratisd[4947]: [2025-10-07T16:48:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:48:34 storageqe-109 stratisd[4947]: [2025-10-07T16:48:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:34 storageqe-109 stratisd[4947]: [2025-10-07T16:48:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:34 storageqe-109 stratisd[4947]: [2025-10-07T16:48:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:34 storageqe-109 stratisd[4947]: [2025-10-07T16:48:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:48:34 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:48:34 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:48:34 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:49:59 storageqe-109 stratisd[4947]: [2025-10-07T16:49:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:49:59 storageqe-109 stratisd[4947]: [2025-10-07T16:49:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:50:09 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:50:39 storageqe-109 stratisd[4947]: [2025-10-07T16:50:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:50:39 storageqe-109 stratisd[4947]: [2025-10-07T16:50:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:51:19 storageqe-109 stratisd[4947]: [2025-10-07T16:51:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:51:19 storageqe-109 stratisd[4947]: [2025-10-07T16:51:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:51:19 storageqe-109 stratisd[4947]: [2025-10-07T16:51:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:51:19 storageqe-109 stratisd[4947]: [2025-10-07T16:51:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:51:19 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:51:19 storageqe-109 INFO: finishe the remove crypt device GIbg Oct 7 12:51:19 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 12:52:44 storageqe-109 stratisd[4947]: [2025-10-07T16:52:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:52:44 storageqe-109 stratisd[4947]: [2025-10-07T16:52:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:52:54 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear GIbg -q --allow-discards Oct 7 12:53:24 storageqe-109 stratisd[4947]: [2025-10-07T16:53:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:53:24 storageqe-109 stratisd[4947]: [2025-10-07T16:53:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: remove crypt device GIbg INFO: finishe the remove crypt device GIbg Oct 7 12:54:04 storageqe-109 stratisd[4947]: [2025-10-07T16:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:54:04 storageqe-109 stratisd[4947]: [2025-10-07T16:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:54:04 storageqe-109 stratisd[4947]: [2025-10-07T16:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:54:04 storageqe-109 stratisd[4947]: [2025-10-07T16:54:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:54:04 storageqe-109 INFO: remove crypt device GIbg Oct 7 12:54:04 storageqe-109 INFO: finishe the remove crypt device GIbg INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_paramter[npo2_linear] #### INFO: #### will start test_luks_bz1750680[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:54:10 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:54:10 storageqe-109 INFO: #### END test_luks_paramter[npo2_linear] #### Oct 7 12:54:10 storageqe-109 INFO: #### will start test_luks_bz1750680[npo2_linear] ##### Oct 7 12:54:10 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 12:54:15 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 12:54:22 storageqe-109 stratisd[4947]: [2025-10-07T16:54:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:54:22 storageqe-109 stratisd[4947]: [2025-10-07T16:54:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear UENT -q --disable-keyring Oct 7 12:54:32 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear UENT -q --disable-keyring Oct 7 12:54:34 storageqe-109 stratisd[4947]: [2025-10-07T16:54:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:54:34 storageqe-109 stratisd[4947]: [2025-10-07T16:54:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/UENT and fs xfs in remove_crypt Oct 7 12:54:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UENT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.j8n8056qmount_test with fs xfs Oct 7 12:54:54 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem be4fa0d6-0456-4717-9b5e-c92ef775980d Oct 7 12:54:54 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 12:54:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j8n8056qmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/UENT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/UENT and fs ext4 in remove_crypt Oct 7 12:54:59 storageqe-109 systemd[1]: tmp-libblockdev.j8n8056qmount_test.mount: Deactivated successfully. Oct 7 12:54:59 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem be4fa0d6-0456-4717-9b5e-c92ef775980d Oct 7 12:54:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UENT and fs xfs in remove_crypt Oct 7 12:54:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UENT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gdp7q7mlmount_test with fs ext4 Oct 7 12:55:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0d86850f-b8bd-4fd9-8c92-168407e215d2 r/w with ordered data mode. Quota mode: none. Oct 7 12:55:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gdp7q7mlmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/UENT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/UENT and fs ext3 in remove_crypt Oct 7 12:55:14 storageqe-109 systemd[1]: tmp-libblockdev.gdp7q7mlmount_test.mount: Deactivated successfully. Oct 7 12:55:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0d86850f-b8bd-4fd9-8c92-168407e215d2. Oct 7 12:55:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UENT and fs ext4 in remove_crypt Oct 7 12:55:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UENT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._dtmj7sxmount_test with fs ext3 Oct 7 12:55:24 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 12:55:24 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a1936d1e-a188-4a0a-a092-46ad2a3094e1 r/w with ordered data mode. Quota mode: none. Oct 7 12:55:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev._dtmj7sxmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/UENT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/UENT and fs ext2 in remove_crypt Oct 7 12:55:29 storageqe-109 systemd[1]: tmp-libblockdev._dtmj7sxmount_test.mount: Deactivated successfully. Oct 7 12:55:29 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a1936d1e-a188-4a0a-a092-46ad2a3094e1. Oct 7 12:55:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UENT and fs ext3 in remove_crypt Oct 7 12:55:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/UENT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0i0q4tv7mount_test with fs ext2 Oct 7 12:55:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 12:55:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bbc5f233-24ae-4f9b-b002-4edd885fbed4 r/w without journal. Quota mode: none. Oct 7 12:55:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0i0q4tv7mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/UENT and fs ext2 in remove_crypt INFO: remove crypt device UENT INFO: finishe the remove crypt device UENT Oct 7 12:55:44 storageqe-109 systemd[1]: tmp-libblockdev.0i0q4tv7mount_test.mount: Deactivated successfully. Oct 7 12:55:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bbc5f233-24ae-4f9b-b002-4edd885fbed4. Oct 7 12:55:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/UENT and fs ext2 in remove_crypt Oct 7 12:55:44 storageqe-109 INFO: remove crypt device UENT Oct 7 12:55:44 storageqe-109 INFO: finishe the remove crypt device UENT INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz1750680[npo2_linear] #### INFO: #### will start test_luks_bz2073433[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:55:49 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 12:55:49 storageqe-109 INFO: #### END test_luks_bz1750680[npo2_linear] #### Oct 7 12:55:49 storageqe-109 INFO: #### will start test_luks_bz2073433[npo2_linear] ##### Oct 7 12:55:49 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 7 12:55:54 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear bGWY -q --perf-no_read_workqueue --perf-no_write_workqueue Oct 7 12:56:09 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear bGWY -q --perf-no_read_workqueue --perf-no_write_workqueue cryptsetup refresh bGWY -q --perf-no_write_workqueue Oct 7 12:56:21 storageqe-109 journal: cryptsetup refresh bGWY -q --perf-no_write_workqueue cryptsetup refresh bGWY -q --perf-no_read_workqueue Oct 7 12:56:33 storageqe-109 journal: cryptsetup refresh bGWY -q --perf-no_read_workqueue cryptsetup refresh bGWY -q --perf-no_write_workqueue --perf-no_read_workqueue Oct 7 12:56:45 storageqe-109 journal: cryptsetup refresh bGWY -q --perf-no_write_workqueue --perf-no_read_workqueue INFO: start IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt Oct 7 12:56:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.vyhd4q8pmount_test with fs xfs Oct 7 12:57:07 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 30cb8da6-e14a-49c6-9d10-2b0fd8c9b75a Oct 7 12:57:07 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 12:57:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vyhd4q8pmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt Oct 7 12:57:12 storageqe-109 systemd[1]: tmp-libblockdev.vyhd4q8pmount_test.mount: Deactivated successfully. Oct 7 12:57:12 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 30cb8da6-e14a-49c6-9d10-2b0fd8c9b75a Oct 7 12:57:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt Oct 7 12:57:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6c6oihlnmount_test with fs ext4 Oct 7 12:57:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dcd12469-fcbf-4e42-8987-fda3db6a4bcf r/w with ordered data mode. Quota mode: none. Oct 7 12:57:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6c6oihlnmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt Oct 7 12:57:27 storageqe-109 systemd[1]: tmp-libblockdev.6c6oihlnmount_test.mount: Deactivated successfully. Oct 7 12:57:27 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dcd12469-fcbf-4e42-8987-fda3db6a4bcf. Oct 7 12:57:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt Oct 7 12:57:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.s0j4v366mount_test with fs ext3 Oct 7 12:57:37 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 12:57:37 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3990b1ea-b29e-4957-a231-8a1da1de34bb r/w with ordered data mode. Quota mode: none. Oct 7 12:57:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s0j4v366mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt Oct 7 12:57:42 storageqe-109 systemd[1]: tmp-libblockdev.s0j4v366mount_test.mount: Deactivated successfully. Oct 7 12:57:42 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3990b1ea-b29e-4957-a231-8a1da1de34bb. Oct 7 12:57:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt Oct 7 12:57:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i0azsuw8mount_test with fs ext2 Oct 7 12:57:52 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 12:57:52 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1175fce1-bce2-4080-96d4-c6533af99410 r/w without journal. Quota mode: none. Oct 7 12:57:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i0azsuw8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt INFO: remove crypt device bGWY INFO: finishe the remove crypt device bGWY cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 12:57:57 storageqe-109 systemd[1]: tmp-libblockdev.i0azsuw8mount_test.mount: Deactivated successfully. Oct 7 12:57:57 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1175fce1-bce2-4080-96d4-c6533af99410. Oct 7 12:57:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt Oct 7 12:57:57 storageqe-109 INFO: remove crypt device bGWY Oct 7 12:57:57 storageqe-109 INFO: finishe the remove crypt device bGWY Oct 7 12:57:57 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 12:58:04 storageqe-109 stratisd[4947]: [2025-10-07T16:58:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:04 storageqe-109 stratisd[4947]: [2025-10-07T16:58:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear bGWY -q --perf-no_read_workqueue --perf-no_write_workqueue --persistent Oct 7 12:58:14 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear bGWY -q --perf-no_read_workqueue --perf-no_write_workqueue --persistent Oct 7 12:58:16 storageqe-109 stratisd[4947]: [2025-10-07T16:58:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:16 storageqe-109 stratisd[4947]: [2025-10-07T16:58:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:16 storageqe-109 stratisd[4947]: [2025-10-07T16:58:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:16 storageqe-109 stratisd[4947]: [2025-10-07T16:58:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup refresh bGWY -q --perf-no_write_workqueue Oct 7 12:58:27 storageqe-109 journal: cryptsetup refresh bGWY -q --perf-no_write_workqueue Oct 7 12:58:29 storageqe-109 stratisd[4947]: [2025-10-07T16:58:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:29 storageqe-109 stratisd[4947]: [2025-10-07T16:58:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup refresh bGWY -q --perf-no_read_workqueue Oct 7 12:58:39 storageqe-109 journal: cryptsetup refresh bGWY -q --perf-no_read_workqueue Oct 7 12:58:41 storageqe-109 stratisd[4947]: [2025-10-07T16:58:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:41 storageqe-109 stratisd[4947]: [2025-10-07T16:58:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:48 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 12:58:48 storageqe-109 dnf[1389495]: Updating Subscription Management repositories. Oct 7 12:58:48 storageqe-109 dnf[1389495]: Unable to read consumer identity Oct 7 12:58:48 storageqe-109 dnf[1389495]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-AppStream 709 kB/s | 2.8 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-AppStream-debuginfo 545 kB/s | 1.5 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-BaseOS 669 kB/s | 2.7 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-BaseOS-debuginfo 479 kB/s | 1.5 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-CRB 723 kB/s | 2.7 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-CRB-debuginfo 584 kB/s | 1.5 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-HighAvailability 813 kB/s | 2.8 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-HighAvailability-debuginfo 573 kB/s | 1.5 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-NFV 629 kB/s | 2.7 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-NFV-debuginfo 470 kB/s | 1.5 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-RT 763 kB/s | 2.7 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-RT-debuginfo 446 kB/s | 1.5 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-SAP 764 kB/s | 2.7 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-SAP-debuginfo 485 kB/s | 1.5 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-SAPHANA 790 kB/s | 2.7 kB 00:00 Oct 7 12:58:48 storageqe-109 dnf[1389495]: beaker-SAPHANA-debuginfo 509 kB/s | 1.5 kB 00:00 Oct 7 12:58:49 storageqe-109 dnf[1389495]: Beaker Client - RedHatEnterpriseLinux10 1.6 kB/s | 1.3 kB 00:00 Oct 7 12:58:50 storageqe-109 dnf[1389495]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 7 12:58:50 storageqe-109 dnf[1389495]: Google Cloud CLI 3.3 kB/s | 1.4 kB 00:00 cryptsetup refresh bGWY -q --perf-no_write_workqueue --perf-no_read_workqueue Oct 7 12:58:51 storageqe-109 journal: cryptsetup refresh bGWY -q --perf-no_write_workqueue --perf-no_read_workqueue Oct 7 12:58:51 storageqe-109 dnf[1389495]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 7 12:58:52 storageqe-109 dnf[1389495]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 7 12:58:53 storageqe-109 dnf[1389495]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 7 12:58:53 storageqe-109 dnf[1389495]: Metadata cache created. Oct 7 12:58:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 12:58:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 12:58:53 storageqe-109 stratisd[4947]: [2025-10-07T16:58:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 12:58:53 storageqe-109 stratisd[4947]: [2025-10-07T16:58:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt Oct 7 12:59:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2cyyuk1jmount_test with fs xfs Oct 7 12:59:13 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 65cbf7f5-17fd-4ca3-ba39-bab68d1c585e Oct 7 12:59:13 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 12:59:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2cyyuk1jmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt Oct 7 12:59:17 storageqe-109 systemd[1]: tmp-libblockdev.2cyyuk1jmount_test.mount: Deactivated successfully. Oct 7 12:59:17 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 65cbf7f5-17fd-4ca3-ba39-bab68d1c585e Oct 7 12:59:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs xfs in remove_crypt Oct 7 12:59:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f375jtimmount_test with fs ext4 Oct 7 12:59:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 784ec10c-6302-496c-affa-988e9be8015c r/w with ordered data mode. Quota mode: none. Oct 7 12:59:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f375jtimmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt Oct 7 12:59:32 storageqe-109 systemd[1]: tmp-libblockdev.f375jtimmount_test.mount: Deactivated successfully. Oct 7 12:59:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 784ec10c-6302-496c-affa-988e9be8015c. Oct 7 12:59:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext4 in remove_crypt Oct 7 12:59:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.17fesu3tmount_test with fs ext3 Oct 7 12:59:42 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 12:59:42 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8ab3045a-354a-4923-9b85-9e5089615d96 r/w with ordered data mode. Quota mode: none. Oct 7 12:59:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.17fesu3tmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt Oct 7 12:59:47 storageqe-109 systemd[1]: tmp-libblockdev.17fesu3tmount_test.mount: Deactivated successfully. Oct 7 12:59:47 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8ab3045a-354a-4923-9b85-9e5089615d96. Oct 7 12:59:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext3 in remove_crypt Oct 7 12:59:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jt_4m97hmount_test with fs ext2 Oct 7 12:59:57 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 12:59:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 34b82d14-5d63-4c2a-a93b-b0cf9482e08f r/w without journal. Quota mode: none. Oct 7 12:59:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jt_4m97hmount_test with fs ext2 Oct 7 13:00:02 storageqe-109 systemd[1]: tmp-libblockdev.jt_4m97hmount_test.mount: Deactivated successfully. Oct 7 13:00:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 34b82d14-5d63-4c2a-a93b-b0cf9482e08f. INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt INFO: remove crypt device bGWY INFO: finishe the remove crypt device bGWY Oct 7 13:00:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/bGWY and fs ext2 in remove_crypt Oct 7 13:00:02 storageqe-109 INFO: remove crypt device bGWY Oct 7 13:00:02 storageqe-109 INFO: finishe the remove crypt device bGWY INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz2073433[npo2_linear] #### INFO: #### will start test_luks_conversion[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:00:07 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:00:07 storageqe-109 INFO: #### END test_luks_bz2073433[npo2_linear] #### Oct 7 13:00:07 storageqe-109 INFO: #### will start test_luks_conversion[npo2_linear] ##### Oct 7 13:00:07 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 7 13:00:12 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 13:00:27 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 13:00:27 storageqe-109 stratisd[4947]: [2025-10-07T17:00:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:00:27 storageqe-109 stratisd[4947]: [2025-10-07T17:00:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear hrDH -q Oct 7 13:00:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear hrDH -q Oct 7 13:00:39 storageqe-109 stratisd[4947]: [2025-10-07T17:00:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:00:39 storageqe-109 stratisd[4947]: [2025-10-07T17:00:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt Oct 7 13:00:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.rrynomxmmount_test with fs xfs Oct 7 13:00:59 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 45206d42-f6d8-466e-b8b5-898bda841485 Oct 7 13:00:59 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:00:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rrynomxmmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt Oct 7 13:01:04 storageqe-109 systemd[1]: tmp-libblockdev.rrynomxmmount_test.mount: Deactivated successfully. Oct 7 13:01:04 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 45206d42-f6d8-466e-b8b5-898bda841485 Oct 7 13:01:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt Oct 7 13:01:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.13jhiq1umount_test with fs ext4 Oct 7 13:01:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 18fde9cd-6312-4622-9262-af9ceddc9cec r/w with ordered data mode. Quota mode: none. Oct 7 13:01:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.13jhiq1umount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt Oct 7 13:01:19 storageqe-109 systemd[1]: tmp-libblockdev.13jhiq1umount_test.mount: Deactivated successfully. Oct 7 13:01:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 18fde9cd-6312-4622-9262-af9ceddc9cec. Oct 7 13:01:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt Oct 7 13:01:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m2a3l26smount_test with fs ext3 Oct 7 13:01:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:01:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem aad47b63-d3ff-4bd6-9d1b-fe5ff50334ba r/w with ordered data mode. Quota mode: none. Oct 7 13:01:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m2a3l26smount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt Oct 7 13:01:34 storageqe-109 systemd[1]: tmp-libblockdev.m2a3l26smount_test.mount: Deactivated successfully. Oct 7 13:01:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem aad47b63-d3ff-4bd6-9d1b-fe5ff50334ba. Oct 7 13:01:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt Oct 7 13:01:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.d6lfo1j9mount_test with fs ext2 Oct 7 13:01:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:01:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 81417737-93f4-49d1-8edd-39513835ee29 r/w without journal. Quota mode: none. Oct 7 13:01:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d6lfo1j9mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt INFO: remove crypt device hrDH INFO: finishe the remove crypt device hrDH cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 7 13:01:49 storageqe-109 systemd[1]: tmp-libblockdev.d6lfo1j9mount_test.mount: Deactivated successfully. Oct 7 13:01:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 81417737-93f4-49d1-8edd-39513835ee29. Oct 7 13:01:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt Oct 7 13:01:49 storageqe-109 INFO: remove crypt device hrDH Oct 7 13:01:49 storageqe-109 INFO: finishe the remove crypt device hrDH Oct 7 13:01:49 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear hrDH -q Oct 7 13:01:59 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear hrDH -q INFO: start IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt Oct 7 13:02:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8lb2403dmount_test with fs xfs Oct 7 13:02:21 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 83aa836a-dbf2-43a5-9d0e-e8b20b06d0a5 Oct 7 13:02:21 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:02:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8lb2403dmount_test with fs xfs Oct 7 13:02:26 storageqe-109 systemd[1]: tmp-libblockdev.8lb2403dmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt Oct 7 13:02:26 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 83aa836a-dbf2-43a5-9d0e-e8b20b06d0a5 Oct 7 13:02:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt Oct 7 13:02:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hfeauj5mmount_test with fs ext4 Oct 7 13:02:36 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 74258441-22c9-4807-b12e-acc4361609de r/w with ordered data mode. Quota mode: none. Oct 7 13:02:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hfeauj5mmount_test with fs ext4 Oct 7 13:02:41 storageqe-109 systemd[1]: tmp-libblockdev.hfeauj5mmount_test.mount: Deactivated successfully. Oct 7 13:02:41 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 74258441-22c9-4807-b12e-acc4361609de. INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt Oct 7 13:02:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt Oct 7 13:02:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt Oct 7 13:02:51 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:02:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9471cb9b-49e8-44b1-9abb-3a7a4db4087e r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.2jrj9qy4mount_test with fs ext3 Oct 7 13:02:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2jrj9qy4mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt Oct 7 13:02:56 storageqe-109 systemd[1]: tmp-libblockdev.2jrj9qy4mount_test.mount: Deactivated successfully. Oct 7 13:02:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9471cb9b-49e8-44b1-9abb-3a7a4db4087e. Oct 7 13:02:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt Oct 7 13:02:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.10xj1iy4mount_test with fs ext2 Oct 7 13:03:06 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:03:06 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 87946590-b7cf-44bd-8cdf-547d4c3f90a3 r/w without journal. Quota mode: none. Oct 7 13:03:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.10xj1iy4mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt INFO: remove crypt device hrDH INFO: finishe the remove crypt device hrDH cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 13:03:11 storageqe-109 systemd[1]: tmp-libblockdev.10xj1iy4mount_test.mount: Deactivated successfully. Oct 7 13:03:11 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 87946590-b7cf-44bd-8cdf-547d4c3f90a3. Oct 7 13:03:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt Oct 7 13:03:11 storageqe-109 INFO: remove crypt device hrDH Oct 7 13:03:11 storageqe-109 INFO: finishe the remove crypt device hrDH Oct 7 13:03:11 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 13:03:11 storageqe-109 stratisd[4947]: [2025-10-07T17:03:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:03:11 storageqe-109 stratisd[4947]: [2025-10-07T17:03:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear hrDH -q Oct 7 13:03:21 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear hrDH -q Oct 7 13:03:24 storageqe-109 stratisd[4947]: [2025-10-07T17:03:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:03:24 storageqe-109 stratisd[4947]: [2025-10-07T17:03:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt Oct 7 13:03:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2gto83utmount_test with fs xfs Oct 7 13:03:44 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ffdc0307-3b64-40e9-bbde-b47a0d730f00 Oct 7 13:03:44 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:03:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2gto83utmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt Oct 7 13:03:48 storageqe-109 systemd[1]: tmp-libblockdev.2gto83utmount_test.mount: Deactivated successfully. Oct 7 13:03:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ffdc0307-3b64-40e9-bbde-b47a0d730f00 Oct 7 13:03:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt Oct 7 13:03:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.itd6hyk0mount_test with fs ext4 Oct 7 13:03:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1954b47b-31fe-4d64-bf93-108882237e39 r/w with ordered data mode. Quota mode: none. Oct 7 13:03:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.itd6hyk0mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt Oct 7 13:04:03 storageqe-109 systemd[1]: tmp-libblockdev.itd6hyk0mount_test.mount: Deactivated successfully. Oct 7 13:04:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1954b47b-31fe-4d64-bf93-108882237e39. Oct 7 13:04:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext4 in remove_crypt Oct 7 13:04:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.n3o826homount_test with fs ext3 Oct 7 13:04:14 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:04:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a5f0c04f-5800-4835-9d1a-dc8e02f53aca r/w with ordered data mode. Quota mode: none. Oct 7 13:04:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n3o826homount_test with fs ext3 Oct 7 13:04:18 storageqe-109 systemd[1]: tmp-libblockdev.n3o826homount_test.mount: Deactivated successfully. Oct 7 13:04:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a5f0c04f-5800-4835-9d1a-dc8e02f53aca. INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt Oct 7 13:04:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext3 in remove_crypt Oct 7 13:04:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.enbpxsqsmount_test with fs ext2 Oct 7 13:04:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:04:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b7ed0e79-f65e-4c2a-8274-f3975c14970a r/w without journal. Quota mode: none. Oct 7 13:04:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.enbpxsqsmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt Oct 7 13:04:33 storageqe-109 systemd[1]: tmp-libblockdev.enbpxsqsmount_test.mount: Deactivated successfully. Oct 7 13:04:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b7ed0e79-f65e-4c2a-8274-f3975c14970a. Oct 7 13:04:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hrDH and fs ext2 in remove_crypt INFO: remove crypt device hrDH INFO: finishe the remove crypt device hrDH Oct 7 13:04:34 storageqe-109 INFO: remove crypt device hrDH Oct 7 13:04:34 storageqe-109 INFO: finishe the remove crypt device hrDH INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_conversion[npo2_linear] #### INFO: #### will start test_luks_bz1862173[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:04:39 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:04:39 storageqe-109 INFO: #### END test_luks_conversion[npo2_linear] #### Oct 7 13:04:39 storageqe-109 INFO: #### will start test_luks_bz1862173[npo2_linear] ##### Oct 7 13:04:39 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:04:44 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:04:51 storageqe-109 stratisd[4947]: [2025-10-07T17:04:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:04:51 storageqe-109 stratisd[4947]: [2025-10-07T17:04:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' token add /dev/mapper/npo2linear -q Oct 7 13:05:01 storageqe-109 journal: cryptsetup --key-description 'mykey' token add /dev/mapper/npo2linear -q Oct 7 13:05:01 storageqe-109 stratisd[4947]: [2025-10-07T17:05:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:05:01 storageqe-109 stratisd[4947]: [2025-10-07T17:05:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear TBqp -q --allow-discards --token-only Oct 7 13:05:11 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear TBqp -q --allow-discards --token-only Oct 7 13:05:13 storageqe-109 stratisd[4947]: [2025-10-07T17:05:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:05:13 storageqe-109 stratisd[4947]: [2025-10-07T17:05:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt Oct 7 13:05:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2tpq3iptmount_test with fs xfs Oct 7 13:05:34 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem cd8e59da-337e-4988-b198-b13e45146758 Oct 7 13:05:34 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:05:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2tpq3iptmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt Oct 7 13:05:39 storageqe-109 systemd[1]: tmp-libblockdev.2tpq3iptmount_test.mount: Deactivated successfully. Oct 7 13:05:39 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem cd8e59da-337e-4988-b198-b13e45146758 Oct 7 13:05:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt Oct 7 13:05:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3axad6akmount_test with fs ext4 Oct 7 13:05:49 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 58d7e999-42d3-4099-8a4f-08da4a73892a r/w with ordered data mode. Quota mode: none. Oct 7 13:05:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3axad6akmount_test with fs ext4 Oct 7 13:05:54 storageqe-109 systemd[1]: tmp-libblockdev.3axad6akmount_test.mount: Deactivated successfully. Oct 7 13:05:54 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 58d7e999-42d3-4099-8a4f-08da4a73892a. INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt Oct 7 13:05:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt Oct 7 13:05:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8csyz4z1mount_test with fs ext3 Oct 7 13:06:04 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:06:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b147f91b-6878-4681-9ef2-cc1ccc903aef r/w with ordered data mode. Quota mode: none. Oct 7 13:06:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8csyz4z1mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt Oct 7 13:06:09 storageqe-109 systemd[1]: tmp-libblockdev.8csyz4z1mount_test.mount: Deactivated successfully. Oct 7 13:06:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b147f91b-6878-4681-9ef2-cc1ccc903aef. Oct 7 13:06:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt Oct 7 13:06:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ra085nrcmount_test with fs ext2 Oct 7 13:06:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:06:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 87504d86-494d-4ceb-9883-18f47c2ced31 r/w without journal. Quota mode: none. Oct 7 13:06:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ra085nrcmount_test with fs ext2 Oct 7 13:06:24 storageqe-109 systemd[1]: tmp-libblockdev.ra085nrcmount_test.mount: Deactivated successfully. Oct 7 13:06:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 87504d86-494d-4ceb-9883-18f47c2ced31. INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt INFO: remove crypt device TBqp INFO: finishe the remove crypt device TBqp Oct 7 13:06:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt Oct 7 13:06:24 storageqe-109 INFO: remove crypt device TBqp Oct 7 13:06:24 storageqe-109 INFO: finishe the remove crypt device TBqp cryptsetup --key-description 'mykey1' --key-slot '1' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 13:06:34 storageqe-109 stratisd[4947]: [2025-10-07T17:06:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:06:34 storageqe-109 stratisd[4947]: [2025-10-07T17:06:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:06:35 storageqe-109 journal: cryptsetup --key-description 'mykey1' --key-slot '1' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 13:06:35 storageqe-109 stratisd[4947]: [2025-10-07T17:06:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:06:35 storageqe-109 stratisd[4947]: [2025-10-07T17:06:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:06:35 storageqe-109 stratisd[4947]: [2025-10-07T17:06:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 13:06:35 storageqe-109 stratisd[4947]: [2025-10-07T17:06:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:06:35 storageqe-109 stratisd[4947]: [2025-10-07T17:06:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:06:35 storageqe-109 stratisd[4947]: [2025-10-07T17:06:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear TBqp -q --allow-discards --token-only Oct 7 13:06:45 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear TBqp -q --allow-discards --token-only Oct 7 13:06:47 storageqe-109 stratisd[4947]: [2025-10-07T17:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:06:47 storageqe-109 stratisd[4947]: [2025-10-07T17:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:06:47 storageqe-109 stratisd[4947]: [2025-10-07T17:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 13:06:47 storageqe-109 stratisd[4947]: [2025-10-07T17:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:06:47 storageqe-109 stratisd[4947]: [2025-10-07T17:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:06:47 storageqe-109 stratisd[4947]: [2025-10-07T17:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 7 13:06:57 storageqe-109 journal: cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 7 13:07:05 storageqe-109 stratisd[4947]: [2025-10-07T17:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:07:05 storageqe-109 stratisd[4947]: [2025-10-07T17:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:07:05 storageqe-109 stratisd[4947]: [2025-10-07T17:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 13:07:05 storageqe-109 stratisd[4947]: [2025-10-07T17:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:07:05 storageqe-109 stratisd[4947]: [2025-10-07T17:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:07:05 storageqe-109 stratisd[4947]: [2025-10-07T17:07:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only /tmp/testfileURA Oct 7 13:07:15 storageqe-109 journal: cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only /tmp/testfileURA Oct 7 13:07:23 storageqe-109 stratisd[4947]: [2025-10-07T17:07:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:07:23 storageqe-109 stratisd[4947]: [2025-10-07T17:07:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:07:23 storageqe-109 stratisd[4947]: [2025-10-07T17:07:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 13:07:23 storageqe-109 stratisd[4947]: [2025-10-07T17:07:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:07:23 storageqe-109 stratisd[4947]: [2025-10-07T17:07:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:07:23 storageqe-109 stratisd[4947]: [2025-10-07T17:07:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup luksRemoveKey /dev/mapper/npo2linear -q --token-only /tmp/testfileURA Oct 7 13:07:33 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q --token-only /tmp/testfileURA Oct 7 13:07:41 storageqe-109 stratisd[4947]: [2025-10-07T17:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:07:41 storageqe-109 stratisd[4947]: [2025-10-07T17:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:07:41 storageqe-109 stratisd[4947]: [2025-10-07T17:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 13:07:41 storageqe-109 stratisd[4947]: [2025-10-07T17:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 13:07:41 storageqe-109 stratisd[4947]: [2025-10-07T17:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 13:07:41 storageqe-109 stratisd[4947]: [2025-10-07T17:07:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt Oct 7 13:07:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.jqkt4utmmount_test with fs xfs Oct 7 13:08:01 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ccad5176-19fd-49e8-a4fc-763fc25649da Oct 7 13:08:01 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:08:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jqkt4utmmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt Oct 7 13:08:06 storageqe-109 systemd[1]: tmp-libblockdev.jqkt4utmmount_test.mount: Deactivated successfully. Oct 7 13:08:06 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ccad5176-19fd-49e8-a4fc-763fc25649da Oct 7 13:08:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs xfs in remove_crypt Oct 7 13:08:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8_71syg1mount_test with fs ext4 Oct 7 13:08:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e6f0c3cd-6a5a-46e3-9466-5f6c8a878879 r/w with ordered data mode. Quota mode: none. Oct 7 13:08:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8_71syg1mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt Oct 7 13:08:21 storageqe-109 systemd[1]: tmp-libblockdev.8_71syg1mount_test.mount: Deactivated successfully. Oct 7 13:08:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e6f0c3cd-6a5a-46e3-9466-5f6c8a878879. Oct 7 13:08:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext4 in remove_crypt Oct 7 13:08:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.oc2nqly2mount_test with fs ext3 Oct 7 13:08:31 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:08:31 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 50e19957-61c5-4d7a-ad8b-0a37b9303b8e r/w with ordered data mode. Quota mode: none. Oct 7 13:08:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.oc2nqly2mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt Oct 7 13:08:36 storageqe-109 systemd[1]: tmp-libblockdev.oc2nqly2mount_test.mount: Deactivated successfully. Oct 7 13:08:36 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 50e19957-61c5-4d7a-ad8b-0a37b9303b8e. Oct 7 13:08:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext3 in remove_crypt Oct 7 13:08:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.s5_nbyxlmount_test with fs ext2 Oct 7 13:08:46 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:08:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1b52537a-ce74-4a66-95e1-d81af94f4429 r/w without journal. Quota mode: none. Oct 7 13:08:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s5_nbyxlmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt INFO: remove crypt device TBqp INFO: finishe the remove crypt device TBqp Oct 7 13:08:51 storageqe-109 systemd[1]: tmp-libblockdev.s5_nbyxlmount_test.mount: Deactivated successfully. Oct 7 13:08:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1b52537a-ce74-4a66-95e1-d81af94f4429. Oct 7 13:08:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TBqp and fs ext2 in remove_crypt Oct 7 13:08:51 storageqe-109 INFO: remove crypt device TBqp Oct 7 13:08:51 storageqe-109 INFO: finishe the remove crypt device TBqp INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_bz1862173[npo2_linear] #### INFO: #### will start test_luks_passphrases[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:08:56 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:08:56 storageqe-109 INFO: #### END test_luks_bz1862173[npo2_linear] #### Oct 7 13:08:56 storageqe-109 INFO: #### will start test_luks_passphrases[npo2_linear] ##### Oct 7 13:08:56 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 7 13:09:01 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear aJtO -q --allow-discards Oct 7 13:09:16 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear aJtO -q --allow-discards INFO: will run io in dir /tmp/libblockdev.vobudhw0mount_test with fs xfs Oct 7 13:10:34 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 84d2f6c2-a853-4f8f-a8d3-062f04b1a121 Oct 7 13:10:34 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:10:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vobudhw0mount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/aJtO and fs xfs in remove_crypt Oct 7 13:10:39 storageqe-109 systemd[1]: tmp-libblockdev.vobudhw0mount_test.mount: Deactivated successfully. Oct 7 13:10:39 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 84d2f6c2-a853-4f8f-a8d3-062f04b1a121 Oct 7 13:10:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aJtO and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.tcvzvhmlmount_test with fs xfs Oct 7 13:10:49 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 044e8fb1-5451-45fb-8db1-6b49d87196e9 Oct 7 13:10:49 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:10:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tcvzvhmlmount_test with fs xfs Oct 7 13:10:54 storageqe-109 systemd[1]: tmp-libblockdev.tcvzvhmlmount_test.mount: Deactivated successfully. Oct 7 13:10:54 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 044e8fb1-5451-45fb-8db1-6b49d87196e9 INFO: End IO testing with the luks device /dev/mapper/aJtO and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/aJtO and fs ext4 in remove_crypt Oct 7 13:10:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aJtO and fs xfs in remove_crypt Oct 7 13:10:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aJtO and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7988ymotmount_test with fs ext4 Oct 7 13:11:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2fa3ed8c-b3a5-4d9e-8daf-7bcccef42053 r/w with ordered data mode. Quota mode: none. Oct 7 13:11:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7988ymotmount_test with fs ext4 Oct 7 13:11:09 storageqe-109 systemd[1]: tmp-libblockdev.7988ymotmount_test.mount: Deactivated successfully. Oct 7 13:11:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2fa3ed8c-b3a5-4d9e-8daf-7bcccef42053. Oct 7 13:11:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aJtO and fs ext4 in remove_crypt INFO: End IO testing with the luks device /dev/mapper/aJtO and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/aJtO and fs ext3 in remove_crypt Oct 7 13:11:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aJtO and fs ext3 in remove_crypt Oct 7 13:11:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.8ewp_bswmount_test with fs ext3 Oct 7 13:11:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5a7f892e-498c-4f8a-98ee-857693128eb4 r/w with ordered data mode. Quota mode: none. Oct 7 13:11:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8ewp_bswmount_test with fs ext3 Oct 7 13:11:24 storageqe-109 systemd[1]: tmp-libblockdev.8ewp_bswmount_test.mount: Deactivated successfully. Oct 7 13:11:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5a7f892e-498c-4f8a-98ee-857693128eb4. INFO: End IO testing with the luks device /dev/mapper/aJtO and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/aJtO and fs ext2 in remove_crypt Oct 7 13:11:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aJtO and fs ext3 in remove_crypt Oct 7 13:11:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/aJtO and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5wjbfwmomount_test with fs ext2 Oct 7 13:11:34 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:11:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f1091ae6-11ae-4437-b25c-62c3185a660c r/w without journal. Quota mode: none. Oct 7 13:11:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5wjbfwmomount_test with fs ext2 Oct 7 13:11:39 storageqe-109 systemd[1]: tmp-libblockdev.5wjbfwmomount_test.mount: Deactivated successfully. Oct 7 13:11:39 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f1091ae6-11ae-4437-b25c-62c3185a660c. INFO: End IO testing with the luks device /dev/mapper/aJtO and fs ext2 in remove_crypt INFO: remove crypt device aJtO INFO: finishe the remove crypt device aJtO cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:11:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/aJtO and fs ext2 in remove_crypt Oct 7 13:11:39 storageqe-109 INFO: remove crypt device aJtO Oct 7 13:11:39 storageqe-109 INFO: finishe the remove crypt device aJtO Oct 7 13:11:39 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:11:47 storageqe-109 stratisd[4947]: [2025-10-07T17:11:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:11:47 storageqe-109 stratisd[4947]: [2025-10-07T17:11:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear yBwY -q --allow-discards Oct 7 13:11:57 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear yBwY -q --allow-discards Oct 7 13:11:59 storageqe-109 stratisd[4947]: [2025-10-07T17:11:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:11:59 storageqe-109 stratisd[4947]: [2025-10-07T17:11:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:17 storageqe-109 stratisd[4947]: [2025-10-07T17:12:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:17 storageqe-109 stratisd[4947]: [2025-10-07T17:12:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:25 storageqe-109 stratisd[4947]: [2025-10-07T17:12:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:25 storageqe-109 stratisd[4947]: [2025-10-07T17:12:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:34 storageqe-109 stratisd[4947]: [2025-10-07T17:12:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:34 storageqe-109 stratisd[4947]: [2025-10-07T17:12:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:42 storageqe-109 stratisd[4947]: [2025-10-07T17:12:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:42 storageqe-109 stratisd[4947]: [2025-10-07T17:12:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:50 storageqe-109 stratisd[4947]: [2025-10-07T17:12:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:50 storageqe-109 stratisd[4947]: [2025-10-07T17:12:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:59 storageqe-109 stratisd[4947]: [2025-10-07T17:12:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:12:59 storageqe-109 stratisd[4947]: [2025-10-07T17:12:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:07 storageqe-109 stratisd[4947]: [2025-10-07T17:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:07 storageqe-109 stratisd[4947]: [2025-10-07T17:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:15 storageqe-109 stratisd[4947]: [2025-10-07T17:13:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:15 storageqe-109 stratisd[4947]: [2025-10-07T17:13:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:24 storageqe-109 stratisd[4947]: [2025-10-07T17:13:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:24 storageqe-109 stratisd[4947]: [2025-10-07T17:13:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:32 storageqe-109 stratisd[4947]: [2025-10-07T17:13:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:32 storageqe-109 stratisd[4947]: [2025-10-07T17:13:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:40 storageqe-109 stratisd[4947]: [2025-10-07T17:13:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:40 storageqe-109 stratisd[4947]: [2025-10-07T17:13:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:48 storageqe-109 stratisd[4947]: [2025-10-07T17:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:48 storageqe-109 stratisd[4947]: [2025-10-07T17:13:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:57 storageqe-109 stratisd[4947]: [2025-10-07T17:13:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:13:57 storageqe-109 stratisd[4947]: [2025-10-07T17:13:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:05 storageqe-109 stratisd[4947]: [2025-10-07T17:14:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:05 storageqe-109 stratisd[4947]: [2025-10-07T17:14:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:13 storageqe-109 stratisd[4947]: [2025-10-07T17:14:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:13 storageqe-109 stratisd[4947]: [2025-10-07T17:14:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:22 storageqe-109 stratisd[4947]: [2025-10-07T17:14:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:22 storageqe-109 stratisd[4947]: [2025-10-07T17:14:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:30 storageqe-109 stratisd[4947]: [2025-10-07T17:14:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:30 storageqe-109 stratisd[4947]: [2025-10-07T17:14:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:38 storageqe-109 stratisd[4947]: [2025-10-07T17:14:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:38 storageqe-109 stratisd[4947]: [2025-10-07T17:14:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:47 storageqe-109 stratisd[4947]: [2025-10-07T17:14:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:47 storageqe-109 stratisd[4947]: [2025-10-07T17:14:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:55 storageqe-109 stratisd[4947]: [2025-10-07T17:14:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:14:55 storageqe-109 stratisd[4947]: [2025-10-07T17:14:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:03 storageqe-109 stratisd[4947]: [2025-10-07T17:15:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:03 storageqe-109 stratisd[4947]: [2025-10-07T17:15:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:12 storageqe-109 stratisd[4947]: [2025-10-07T17:15:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:12 storageqe-109 stratisd[4947]: [2025-10-07T17:15:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:20 storageqe-109 stratisd[4947]: [2025-10-07T17:15:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:20 storageqe-109 stratisd[4947]: [2025-10-07T17:15:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:28 storageqe-109 stratisd[4947]: [2025-10-07T17:15:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:28 storageqe-109 stratisd[4947]: [2025-10-07T17:15:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:36 storageqe-109 stratisd[4947]: [2025-10-07T17:15:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:36 storageqe-109 stratisd[4947]: [2025-10-07T17:15:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:45 storageqe-109 stratisd[4947]: [2025-10-07T17:15:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:45 storageqe-109 stratisd[4947]: [2025-10-07T17:15:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:53 storageqe-109 stratisd[4947]: [2025-10-07T17:15:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:15:53 storageqe-109 stratisd[4947]: [2025-10-07T17:15:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:01 storageqe-109 stratisd[4947]: [2025-10-07T17:16:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:01 storageqe-109 stratisd[4947]: [2025-10-07T17:16:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:10 storageqe-109 stratisd[4947]: [2025-10-07T17:16:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:10 storageqe-109 stratisd[4947]: [2025-10-07T17:16:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:18 storageqe-109 stratisd[4947]: [2025-10-07T17:16:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:18 storageqe-109 stratisd[4947]: [2025-10-07T17:16:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:26 storageqe-109 stratisd[4947]: [2025-10-07T17:16:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:26 storageqe-109 stratisd[4947]: [2025-10-07T17:16:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:30 storageqe-109 stratisd[4947]: [2025-10-07T17:16:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:30 storageqe-109 stratisd[4947]: [2025-10-07T17:16:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:34 storageqe-109 stratisd[4947]: [2025-10-07T17:16:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:34 storageqe-109 stratisd[4947]: [2025-10-07T17:16:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:38 storageqe-109 stratisd[4947]: [2025-10-07T17:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:38 storageqe-109 stratisd[4947]: [2025-10-07T17:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:42 storageqe-109 stratisd[4947]: [2025-10-07T17:16:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:42 storageqe-109 stratisd[4947]: [2025-10-07T17:16:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:46 storageqe-109 stratisd[4947]: [2025-10-07T17:16:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:46 storageqe-109 stratisd[4947]: [2025-10-07T17:16:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:50 storageqe-109 stratisd[4947]: [2025-10-07T17:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:50 storageqe-109 stratisd[4947]: [2025-10-07T17:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:54 storageqe-109 stratisd[4947]: [2025-10-07T17:16:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:54 storageqe-109 stratisd[4947]: [2025-10-07T17:16:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:58 storageqe-109 stratisd[4947]: [2025-10-07T17:16:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:16:58 storageqe-109 stratisd[4947]: [2025-10-07T17:16:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:02 storageqe-109 stratisd[4947]: [2025-10-07T17:17:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:02 storageqe-109 stratisd[4947]: [2025-10-07T17:17:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:06 storageqe-109 stratisd[4947]: [2025-10-07T17:17:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:06 storageqe-109 stratisd[4947]: [2025-10-07T17:17:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:10 storageqe-109 stratisd[4947]: [2025-10-07T17:17:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:10 storageqe-109 stratisd[4947]: [2025-10-07T17:17:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:14 storageqe-109 stratisd[4947]: [2025-10-07T17:17:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:14 storageqe-109 stratisd[4947]: [2025-10-07T17:17:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:18 storageqe-109 stratisd[4947]: [2025-10-07T17:17:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:18 storageqe-109 stratisd[4947]: [2025-10-07T17:17:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:22 storageqe-109 stratisd[4947]: [2025-10-07T17:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:22 storageqe-109 stratisd[4947]: [2025-10-07T17:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:26 storageqe-109 stratisd[4947]: [2025-10-07T17:17:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:26 storageqe-109 stratisd[4947]: [2025-10-07T17:17:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:30 storageqe-109 stratisd[4947]: [2025-10-07T17:17:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:30 storageqe-109 stratisd[4947]: [2025-10-07T17:17:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:34 storageqe-109 stratisd[4947]: [2025-10-07T17:17:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:34 storageqe-109 stratisd[4947]: [2025-10-07T17:17:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:38 storageqe-109 stratisd[4947]: [2025-10-07T17:17:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:38 storageqe-109 stratisd[4947]: [2025-10-07T17:17:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:42 storageqe-109 stratisd[4947]: [2025-10-07T17:17:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:42 storageqe-109 stratisd[4947]: [2025-10-07T17:17:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:46 storageqe-109 stratisd[4947]: [2025-10-07T17:17:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:46 storageqe-109 stratisd[4947]: [2025-10-07T17:17:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:50 storageqe-109 stratisd[4947]: [2025-10-07T17:17:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:50 storageqe-109 stratisd[4947]: [2025-10-07T17:17:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:54 storageqe-109 stratisd[4947]: [2025-10-07T17:17:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:54 storageqe-109 stratisd[4947]: [2025-10-07T17:17:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:58 storageqe-109 stratisd[4947]: [2025-10-07T17:17:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:17:58 storageqe-109 stratisd[4947]: [2025-10-07T17:17:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:02 storageqe-109 stratisd[4947]: [2025-10-07T17:18:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:02 storageqe-109 stratisd[4947]: [2025-10-07T17:18:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:06 storageqe-109 stratisd[4947]: [2025-10-07T17:18:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:06 storageqe-109 stratisd[4947]: [2025-10-07T17:18:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:10 storageqe-109 stratisd[4947]: [2025-10-07T17:18:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:10 storageqe-109 stratisd[4947]: [2025-10-07T17:18:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:14 storageqe-109 stratisd[4947]: [2025-10-07T17:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:14 storageqe-109 stratisd[4947]: [2025-10-07T17:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:18 storageqe-109 stratisd[4947]: [2025-10-07T17:18:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:18 storageqe-109 stratisd[4947]: [2025-10-07T17:18:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:22 storageqe-109 stratisd[4947]: [2025-10-07T17:18:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:22 storageqe-109 stratisd[4947]: [2025-10-07T17:18:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:26 storageqe-109 stratisd[4947]: [2025-10-07T17:18:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:26 storageqe-109 stratisd[4947]: [2025-10-07T17:18:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:30 storageqe-109 stratisd[4947]: [2025-10-07T17:18:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:18:30 storageqe-109 stratisd[4947]: [2025-10-07T17:18:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: will run io in dir /tmp/libblockdev.2w8puksymount_test with fs xfs Oct 7 13:18:40 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 81b1ca09-f7b3-4704-86ea-5b941642b18b Oct 7 13:18:40 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:18:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2w8puksymount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/yBwY and fs xfs in remove_crypt Oct 7 13:18:44 storageqe-109 systemd[1]: tmp-libblockdev.2w8puksymount_test.mount: Deactivated successfully. Oct 7 13:18:44 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 81b1ca09-f7b3-4704-86ea-5b941642b18b Oct 7 13:18:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yBwY and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._9sijjyjmount_test with fs xfs Oct 7 13:18:55 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem a897a295-834c-4379-bf9e-f8ecbf03841e Oct 7 13:18:55 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:18:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev._9sijjyjmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/yBwY and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yBwY and fs ext4 in remove_crypt Oct 7 13:18:59 storageqe-109 systemd[1]: tmp-libblockdev._9sijjyjmount_test.mount: Deactivated successfully. Oct 7 13:18:59 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem a897a295-834c-4379-bf9e-f8ecbf03841e Oct 7 13:18:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yBwY and fs xfs in remove_crypt Oct 7 13:18:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yBwY and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tkklm756mount_test with fs ext4 Oct 7 13:19:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6b89bc8b-6702-43d3-b30a-bef4c14846ba r/w with ordered data mode. Quota mode: none. Oct 7 13:19:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tkklm756mount_test with fs ext4 Oct 7 13:19:14 storageqe-109 systemd[1]: tmp-libblockdev.tkklm756mount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/yBwY and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yBwY and fs ext3 in remove_crypt Oct 7 13:19:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6b89bc8b-6702-43d3-b30a-bef4c14846ba. Oct 7 13:19:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yBwY and fs ext4 in remove_crypt Oct 7 13:19:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yBwY and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xap2rhwmmount_test with fs ext3 Oct 7 13:19:24 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:19:24 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4c0ba47a-2101-4d3d-9e72-ec5cf1caf80a r/w with ordered data mode. Quota mode: none. Oct 7 13:19:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xap2rhwmmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/yBwY and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yBwY and fs ext2 in remove_crypt Oct 7 13:19:29 storageqe-109 systemd[1]: tmp-libblockdev.xap2rhwmmount_test.mount: Deactivated successfully. Oct 7 13:19:29 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4c0ba47a-2101-4d3d-9e72-ec5cf1caf80a. Oct 7 13:19:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yBwY and fs ext3 in remove_crypt Oct 7 13:19:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yBwY and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mtffi3ofmount_test with fs ext2 Oct 7 13:19:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:19:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fc442239-59b8-4175-977e-a693ff3f0885 r/w without journal. Quota mode: none. Oct 7 13:19:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mtffi3ofmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/yBwY and fs ext2 in remove_crypt INFO: remove crypt device yBwY INFO: finishe the remove crypt device yBwY Oct 7 13:19:44 storageqe-109 systemd[1]: tmp-libblockdev.mtffi3ofmount_test.mount: Deactivated successfully. Oct 7 13:19:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fc442239-59b8-4175-977e-a693ff3f0885. Oct 7 13:19:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yBwY and fs ext2 in remove_crypt Oct 7 13:19:44 storageqe-109 INFO: remove crypt device yBwY Oct 7 13:19:44 storageqe-109 INFO: finishe the remove crypt device yBwY INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_passphrases[npo2_linear] #### INFO: #### will start test_integrity_setup[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:19:49 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:19:49 storageqe-109 INFO: #### END test_luks_passphrases[npo2_linear] #### Oct 7 13:19:49 storageqe-109 INFO: #### will start test_integrity_setup[npo2_linear] ##### Oct 7 13:19:49 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --progress-frequency '5' --integrity 'sha1' --tag-size '20' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 13:19:55 storageqe-109 journal: integritysetup --progress-frequency '5' --integrity 'sha1' --tag-size '20' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear usJr -q --integrity-no-journal Oct 7 13:20:08 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear usJr -q --integrity-no-journal INFO: will run io in dir /tmp/libblockdev.74co1hgtmount_test with fs xfs Oct 7 13:20:28 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 39ba1761-5361-4d8c-a647-189d18d2c6be Oct 7 13:20:28 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:20:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.74co1hgtmount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/usJr and fs xfs in remove_crypt Oct 7 13:20:33 storageqe-109 systemd[1]: tmp-libblockdev.74co1hgtmount_test.mount: Deactivated successfully. Oct 7 13:20:33 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 39ba1761-5361-4d8c-a647-189d18d2c6be Oct 7 13:20:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/usJr and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.bhv9tnbomount_test with fs xfs Oct 7 13:20:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 472e9705-9f36-45ba-a853-8a41002ae2f4 Oct 7 13:20:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:20:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bhv9tnbomount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/usJr and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/usJr and fs ext4 in remove_crypt Oct 7 13:20:48 storageqe-109 systemd[1]: tmp-libblockdev.bhv9tnbomount_test.mount: Deactivated successfully. Oct 7 13:20:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 472e9705-9f36-45ba-a853-8a41002ae2f4 Oct 7 13:20:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/usJr and fs xfs in remove_crypt Oct 7 13:20:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/usJr and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.76yk5zjhmount_test with fs ext4 Oct 7 13:20:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 41053cd9-1cfb-4b64-bfbb-b5bd85ca7aeb r/w with ordered data mode. Quota mode: none. Oct 7 13:20:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.76yk5zjhmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/usJr and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/usJr and fs ext3 in remove_crypt Oct 7 13:21:03 storageqe-109 systemd[1]: tmp-libblockdev.76yk5zjhmount_test.mount: Deactivated successfully. Oct 7 13:21:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 41053cd9-1cfb-4b64-bfbb-b5bd85ca7aeb. Oct 7 13:21:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/usJr and fs ext4 in remove_crypt Oct 7 13:21:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/usJr and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xao2qbclmount_test with fs ext3 Oct 7 13:21:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:21:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 284457b0-89bf-4b4f-9dc2-642279aac19a r/w with ordered data mode. Quota mode: none. Oct 7 13:21:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xao2qbclmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/usJr and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/usJr and fs ext2 in remove_crypt Oct 7 13:21:18 storageqe-109 systemd[1]: tmp-libblockdev.xao2qbclmount_test.mount: Deactivated successfully. Oct 7 13:21:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 284457b0-89bf-4b4f-9dc2-642279aac19a. Oct 7 13:21:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/usJr and fs ext3 in remove_crypt Oct 7 13:21:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/usJr and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m41mhn8umount_test with fs ext2 Oct 7 13:21:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:21:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a9a779de-6d52-406f-9c41-6184cadc3c76 r/w without journal. Quota mode: none. Oct 7 13:21:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m41mhn8umount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/usJr and fs ext2 in remove_crypt INFO: remove crypt device usJr INFO: finishe the remove crypt device usJr Oct 7 13:21:33 storageqe-109 systemd[1]: tmp-libblockdev.m41mhn8umount_test.mount: Deactivated successfully. Oct 7 13:21:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a9a779de-6d52-406f-9c41-6184cadc3c76. Oct 7 13:21:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/usJr and fs ext2 in remove_crypt Oct 7 13:21:33 storageqe-109 INFO: remove crypt device usJr Oct 7 13:21:33 storageqe-109 INFO: finishe the remove crypt device usJr INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_setup[npo2_linear] #### INFO: #### will start test_reencrypt_online[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:21:38 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:21:38 storageqe-109 INFO: #### END test_integrity_setup[npo2_linear] #### Oct 7 13:21:38 storageqe-109 INFO: #### will start test_reencrypt_online[npo2_linear] ##### Oct 7 13:21:38 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:21:43 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:21:51 storageqe-109 stratisd[4947]: [2025-10-07T17:21:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:21:51 storageqe-109 stratisd[4947]: [2025-10-07T17:21:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear IXgN -q --allow-discards Oct 7 13:22:01 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear IXgN -q --allow-discards Oct 7 13:22:03 storageqe-109 stratisd[4947]: [2025-10-07T17:22:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:22:03 storageqe-109 stratisd[4947]: [2025-10-07T17:22:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IXgN and fs xfs in remove_crypt Oct 7 13:22:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IXgN and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.pcv30xrpmount_test with fs xfs Oct 7 13:22:24 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 05d548d2-9efe-466e-96e9-3f366db737c7 Oct 7 13:22:24 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:22:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pcv30xrpmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IXgN and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IXgN and fs ext4 in remove_crypt Oct 7 13:22:29 storageqe-109 systemd[1]: tmp-libblockdev.pcv30xrpmount_test.mount: Deactivated successfully. Oct 7 13:22:29 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 05d548d2-9efe-466e-96e9-3f366db737c7 Oct 7 13:22:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IXgN and fs xfs in remove_crypt Oct 7 13:22:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IXgN and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2ahwyifrmount_test with fs ext4 Oct 7 13:22:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 09e3968d-11a9-4141-99a9-8c89e71ef54f r/w with ordered data mode. Quota mode: none. Oct 7 13:22:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2ahwyifrmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IXgN and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IXgN and fs ext3 in remove_crypt Oct 7 13:22:44 storageqe-109 systemd[1]: tmp-libblockdev.2ahwyifrmount_test.mount: Deactivated successfully. Oct 7 13:22:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 09e3968d-11a9-4141-99a9-8c89e71ef54f. Oct 7 13:22:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IXgN and fs ext4 in remove_crypt Oct 7 13:22:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IXgN and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7l46ry10mount_test with fs ext3 Oct 7 13:22:54 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:22:54 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7c7d3097-73b1-41e6-bd4d-45b916c2d1dc r/w with ordered data mode. Quota mode: none. Oct 7 13:22:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7l46ry10mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IXgN and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IXgN and fs ext2 in remove_crypt Oct 7 13:22:59 storageqe-109 systemd[1]: tmp-libblockdev.7l46ry10mount_test.mount: Deactivated successfully. Oct 7 13:22:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7c7d3097-73b1-41e6-bd4d-45b916c2d1dc. Oct 7 13:22:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IXgN and fs ext3 in remove_crypt Oct 7 13:22:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IXgN and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hnglw2jrmount_test with fs ext2 Oct 7 13:23:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:23:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 06b928f3-fbed-478f-91b9-eb1ddd9ca0de r/w without journal. Quota mode: none. Oct 7 13:23:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hnglw2jrmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IXgN and fs ext2 in remove_crypt INFO: remove crypt device IXgN INFO: finishe the remove crypt device IXgN Oct 7 13:23:14 storageqe-109 systemd[1]: tmp-libblockdev.hnglw2jrmount_test.mount: Deactivated successfully. Oct 7 13:23:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 06b928f3-fbed-478f-91b9-eb1ddd9ca0de. Oct 7 13:23:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IXgN and fs ext2 in remove_crypt Oct 7 13:23:14 storageqe-109 INFO: remove crypt device IXgN Oct 7 13:23:14 storageqe-109 INFO: finishe the remove crypt device IXgN cryptsetup --header '/tmp/testheaderuDh' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 7 13:23:14 storageqe-109 journal: cryptsetup --header '/tmp/testheaderuDh' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --type 'luks2' --header '/tmp/testheaderuDh' open /dev/mapper/npo2linear IXgN --allow-discards -q Oct 7 13:23:33 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderuDh' open /dev/mapper/npo2linear IXgN --allow-discards -q cryptsetup --active-name 'IXgN' --resilience 'none' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderuDh' reencrypt /dev/mapper/npo2linear -q Oct 7 13:23:45 storageqe-109 journal: cryptsetup --active-name 'IXgN' --resilience 'none' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderuDh' reencrypt /dev/mapper/npo2linear -q cryptsetup --active-name 'IXgN' --header '/tmp/testheaderuDh' reencrypt /dev/mapper/npo2linear --decrypt -q Oct 7 13:24:07 storageqe-109 journal: cryptsetup --active-name 'IXgN' --header '/tmp/testheaderuDh' reencrypt /dev/mapper/npo2linear --decrypt -q cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:24:30 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:24:38 storageqe-109 stratisd[4947]: [2025-10-07T17:24:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:24:38 storageqe-109 stratisd[4947]: [2025-10-07T17:24:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear BpeK -q --allow-discards Oct 7 13:24:48 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear BpeK -q --allow-discards Oct 7 13:24:50 storageqe-109 stratisd[4947]: [2025-10-07T17:24:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:24:50 storageqe-109 stratisd[4947]: [2025-10-07T17:24:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/BpeK and fs xfs in remove_crypt Oct 7 13:25:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BpeK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ozzye2ijmount_test with fs xfs Oct 7 13:25:10 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 1b87ffe5-91b8-4c6e-bbd2-2382d591b757 Oct 7 13:25:10 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:25:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ozzye2ijmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/BpeK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BpeK and fs ext4 in remove_crypt Oct 7 13:25:16 storageqe-109 systemd[1]: tmp-libblockdev.ozzye2ijmount_test.mount: Deactivated successfully. Oct 7 13:25:16 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 1b87ffe5-91b8-4c6e-bbd2-2382d591b757 Oct 7 13:25:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BpeK and fs xfs in remove_crypt Oct 7 13:25:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BpeK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xwns375amount_test with fs ext4 Oct 7 13:25:26 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 330a0e3f-9c01-4626-8cce-e554fce9c170 r/w with ordered data mode. Quota mode: none. Oct 7 13:25:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xwns375amount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/BpeK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BpeK and fs ext3 in remove_crypt Oct 7 13:25:31 storageqe-109 systemd[1]: tmp-libblockdev.xwns375amount_test.mount: Deactivated successfully. Oct 7 13:25:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 330a0e3f-9c01-4626-8cce-e554fce9c170. Oct 7 13:25:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BpeK and fs ext4 in remove_crypt Oct 7 13:25:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BpeK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mn38bhl3mount_test with fs ext3 Oct 7 13:25:41 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:25:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem acbb03da-ca11-4fff-8ace-924eee5c0971 r/w with ordered data mode. Quota mode: none. Oct 7 13:25:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mn38bhl3mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/BpeK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/BpeK and fs ext2 in remove_crypt Oct 7 13:25:46 storageqe-109 systemd[1]: tmp-libblockdev.mn38bhl3mount_test.mount: Deactivated successfully. Oct 7 13:25:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem acbb03da-ca11-4fff-8ace-924eee5c0971. Oct 7 13:25:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BpeK and fs ext3 in remove_crypt Oct 7 13:25:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/BpeK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.utnrpqqymount_test with fs ext2 Oct 7 13:25:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:25:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ce4dde5a-3aa0-4971-a0f3-01cb6ea79b3a r/w without journal. Quota mode: none. Oct 7 13:25:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.utnrpqqymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/BpeK and fs ext2 in remove_crypt INFO: remove crypt device BpeK INFO: finishe the remove crypt device BpeK Oct 7 13:26:01 storageqe-109 systemd[1]: tmp-libblockdev.utnrpqqymount_test.mount: Deactivated successfully. Oct 7 13:26:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ce4dde5a-3aa0-4971-a0f3-01cb6ea79b3a. Oct 7 13:26:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/BpeK and fs ext2 in remove_crypt Oct 7 13:26:01 storageqe-109 INFO: remove crypt device BpeK Oct 7 13:26:01 storageqe-109 INFO: finishe the remove crypt device BpeK cryptsetup --header '/tmp/testheaderYXo' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 7 13:26:01 storageqe-109 journal: cryptsetup --header '/tmp/testheaderYXo' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --type 'luks2' --header '/tmp/testheaderYXo' open /dev/mapper/npo2linear BpeK --allow-discards -q Oct 7 13:26:20 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderYXo' open /dev/mapper/npo2linear BpeK --allow-discards -q cryptsetup --active-name 'BpeK' --resilience 'checksum' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderYXo' reencrypt /dev/mapper/npo2linear -q Oct 7 13:26:32 storageqe-109 journal: cryptsetup --active-name 'BpeK' --resilience 'checksum' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderYXo' reencrypt /dev/mapper/npo2linear -q cryptsetup --active-name 'BpeK' --header '/tmp/testheaderYXo' reencrypt /dev/mapper/npo2linear --decrypt -q Oct 7 13:26:56 storageqe-109 journal: cryptsetup --active-name 'BpeK' --header '/tmp/testheaderYXo' reencrypt /dev/mapper/npo2linear --decrypt -q cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:27:19 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:27:27 storageqe-109 stratisd[4947]: [2025-10-07T17:27:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:27:27 storageqe-109 stratisd[4947]: [2025-10-07T17:27:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear WFyO -q --allow-discards Oct 7 13:27:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear WFyO -q --allow-discards Oct 7 13:27:39 storageqe-109 stratisd[4947]: [2025-10-07T17:27:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:27:39 storageqe-109 stratisd[4947]: [2025-10-07T17:27:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/WFyO and fs xfs in remove_crypt Oct 7 13:27:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WFyO and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.0254qs4_mount_test with fs xfs Oct 7 13:27:59 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 2c209677-c928-4634-a513-0bfeaa663700 Oct 7 13:27:59 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:27:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0254qs4_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/WFyO and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WFyO and fs ext4 in remove_crypt Oct 7 13:28:04 storageqe-109 systemd[1]: tmp-libblockdev.0254qs4_mount_test.mount: Deactivated successfully. Oct 7 13:28:04 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 2c209677-c928-4634-a513-0bfeaa663700 Oct 7 13:28:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WFyO and fs xfs in remove_crypt Oct 7 13:28:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WFyO and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i4ww4269mount_test with fs ext4 Oct 7 13:28:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6ddc8688-42d9-41e0-9c7a-31e37b8df311 r/w with ordered data mode. Quota mode: none. Oct 7 13:28:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i4ww4269mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/WFyO and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WFyO and fs ext3 in remove_crypt Oct 7 13:28:19 storageqe-109 systemd[1]: tmp-libblockdev.i4ww4269mount_test.mount: Deactivated successfully. Oct 7 13:28:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6ddc8688-42d9-41e0-9c7a-31e37b8df311. Oct 7 13:28:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WFyO and fs ext4 in remove_crypt Oct 7 13:28:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WFyO and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9eaj09gnmount_test with fs ext3 Oct 7 13:28:30 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:28:30 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d48cfaf7-aa5e-45c9-a782-50f4df072d91 r/w with ordered data mode. Quota mode: none. Oct 7 13:28:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9eaj09gnmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/WFyO and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/WFyO and fs ext2 in remove_crypt Oct 7 13:28:35 storageqe-109 systemd[1]: tmp-libblockdev.9eaj09gnmount_test.mount: Deactivated successfully. Oct 7 13:28:35 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d48cfaf7-aa5e-45c9-a782-50f4df072d91. Oct 7 13:28:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WFyO and fs ext3 in remove_crypt Oct 7 13:28:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/WFyO and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.s1d8ih0lmount_test with fs ext2 Oct 7 13:28:45 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:28:45 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dba27539-cfdf-4b39-b055-de73d39bdd97 r/w without journal. Quota mode: none. Oct 7 13:28:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s1d8ih0lmount_test with fs ext2 Oct 7 13:28:49 storageqe-109 systemd[1]: tmp-libblockdev.s1d8ih0lmount_test.mount: Deactivated successfully. Oct 7 13:28:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dba27539-cfdf-4b39-b055-de73d39bdd97. INFO: End IO testing with the luks device /dev/mapper/WFyO and fs ext2 in remove_crypt INFO: remove crypt device WFyO INFO: finishe the remove crypt device WFyO cryptsetup --header '/tmp/testheaderjVd' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 7 13:28:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/WFyO and fs ext2 in remove_crypt Oct 7 13:28:50 storageqe-109 INFO: remove crypt device WFyO Oct 7 13:28:50 storageqe-109 INFO: finishe the remove crypt device WFyO Oct 7 13:28:50 storageqe-109 journal: cryptsetup --header '/tmp/testheaderjVd' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --type 'luks2' --header '/tmp/testheaderjVd' open /dev/mapper/npo2linear WFyO --allow-discards -q Oct 7 13:29:08 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderjVd' open /dev/mapper/npo2linear WFyO --allow-discards -q cryptsetup --active-name 'WFyO' --resilience 'journal' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderjVd' reencrypt /dev/mapper/npo2linear -q Oct 7 13:29:20 storageqe-109 journal: cryptsetup --active-name 'WFyO' --resilience 'journal' --hotzone-size '100M' --cipher 'serpent-cbc-essiv:sha256' --header '/tmp/testheaderjVd' reencrypt /dev/mapper/npo2linear -q cryptsetup --active-name 'WFyO' --header '/tmp/testheaderjVd' reencrypt /dev/mapper/npo2linear --decrypt -q Oct 7 13:29:47 storageqe-109 journal: cryptsetup --active-name 'WFyO' --header '/tmp/testheaderjVd' reencrypt /dev/mapper/npo2linear --decrypt -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_online[npo2_linear] #### INFO: #### will start test_bz2080516_fips[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:30:16 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:30:16 storageqe-109 INFO: #### END test_reencrypt_online[npo2_linear] #### Oct 7 13:30:16 storageqe-109 INFO: #### will start test_bz2080516_fips[npo2_linear] ##### Oct 7 13:30:16 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'argon2id' luksFormat /dev/mapper/npo2linear -q Oct 7 13:30:21 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'argon2id' luksFormat /dev/mapper/npo2linear -q Oct 7 13:30:28 storageqe-109 stratisd[4947]: [2025-10-07T17:30:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:30:28 storageqe-109 stratisd[4947]: [2025-10-07T17:30:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 13:30:38 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:30:48 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:30:52 storageqe-109 stratisd[4947]: [2025-10-07T17:30:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:30:52 storageqe-109 stratisd[4947]: [2025-10-07T17:30:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:30:57 storageqe-109 stratisd[4947]: [2025-10-07T17:30:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:30:57 storageqe-109 stratisd[4947]: [2025-10-07T17:30:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz2080516_fips[npo2_linear] #### INFO: #### will start test_luks_sche_test[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:31:12 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:31:12 storageqe-109 INFO: #### END test_bz2080516_fips[npo2_linear] #### Oct 7 13:31:12 storageqe-109 INFO: #### will start test_luks_sche_test[npo2_linear] ##### Oct 7 13:31:12 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 7 13:31:17 storageqe-109 journal: cryptsetup --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' open /dev/mapper/npo2linear frLF -q Oct 7 13:31:31 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear frLF -q INFO: start IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt Oct 7 13:32:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.lhllx9t9mount_test with fs xfs Oct 7 13:33:04 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 03a0490e-3cad-4932-a3b2-531208c30c7a Oct 7 13:33:04 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:33:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lhllx9t9mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt Oct 7 13:33:08 storageqe-109 systemd[1]: tmp-libblockdev.lhllx9t9mount_test.mount: Deactivated successfully. Oct 7 13:33:08 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 03a0490e-3cad-4932-a3b2-531208c30c7a Oct 7 13:33:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt Oct 7 13:33:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4yq9_ux1mount_test with fs ext4 Oct 7 13:33:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 98a92f58-19c5-4835-9233-5e95ec526c1e r/w with ordered data mode. Quota mode: none. Oct 7 13:33:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4yq9_ux1mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt Oct 7 13:33:23 storageqe-109 systemd[1]: tmp-libblockdev.4yq9_ux1mount_test.mount: Deactivated successfully. Oct 7 13:33:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 98a92f58-19c5-4835-9233-5e95ec526c1e. Oct 7 13:33:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt Oct 7 13:33:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hjrjf2h3mount_test with fs ext3 Oct 7 13:33:34 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:33:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e265c4c1-9d76-4bf0-82b0-f78de14821af r/w with ordered data mode. Quota mode: none. Oct 7 13:33:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hjrjf2h3mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt Oct 7 13:33:38 storageqe-109 systemd[1]: tmp-libblockdev.hjrjf2h3mount_test.mount: Deactivated successfully. Oct 7 13:33:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e265c4c1-9d76-4bf0-82b0-f78de14821af. Oct 7 13:33:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt Oct 7 13:33:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4sxm_qlimount_test with fs ext2 Oct 7 13:33:49 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:33:49 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d6a6a392-8aa9-416b-a18d-aff782363001 r/w without journal. Quota mode: none. Oct 7 13:33:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4sxm_qlimount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt INFO: remove crypt device frLF Oct 7 13:33:53 storageqe-109 systemd[1]: tmp-libblockdev.4sxm_qlimount_test.mount: Deactivated successfully. Oct 7 13:33:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d6a6a392-8aa9-416b-a18d-aff782363001. Oct 7 13:33:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt Oct 7 13:33:53 storageqe-109 INFO: remove crypt device frLF INFO: finishe the remove crypt device frLF cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:33:54 storageqe-109 INFO: finishe the remove crypt device frLF Oct 7 13:33:54 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/mapper/npo2linear -q Oct 7 13:34:00 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 13:34:00 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 13:34:00 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 13:34:01 storageqe-109 stratisd[4947]: [2025-10-07T17:34:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:34:01 storageqe-109 stratisd[4947]: [2025-10-07T17:34:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear frLF -q Oct 7 13:34:11 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear frLF -q Oct 7 13:34:13 storageqe-109 stratisd[4947]: [2025-10-07T17:34:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:34:13 storageqe-109 stratisd[4947]: [2025-10-07T17:34:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt Oct 7 13:35:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.n95e59egmount_test with fs xfs Oct 7 13:35:42 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem bb21237c-6509-4553-87d3-23687c298760 Oct 7 13:35:42 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:35:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n95e59egmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt Oct 7 13:35:47 storageqe-109 systemd[1]: tmp-libblockdev.n95e59egmount_test.mount: Deactivated successfully. Oct 7 13:35:47 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem bb21237c-6509-4553-87d3-23687c298760 Oct 7 13:35:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs xfs in remove_crypt Oct 7 13:35:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j3fgzc3smount_test with fs ext4 Oct 7 13:35:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3cd9af10-c41f-4d1c-b705-ed4db520f1fc r/w with ordered data mode. Quota mode: none. Oct 7 13:35:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j3fgzc3smount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt Oct 7 13:36:02 storageqe-109 systemd[1]: tmp-libblockdev.j3fgzc3smount_test.mount: Deactivated successfully. Oct 7 13:36:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3cd9af10-c41f-4d1c-b705-ed4db520f1fc. Oct 7 13:36:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext4 in remove_crypt Oct 7 13:36:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h6r0piztmount_test with fs ext3 Oct 7 13:36:12 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:36:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 61c23a23-9b4c-460e-bd2a-9e24142febd1 r/w with ordered data mode. Quota mode: none. Oct 7 13:36:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h6r0piztmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt Oct 7 13:36:17 storageqe-109 systemd[1]: tmp-libblockdev.h6r0piztmount_test.mount: Deactivated successfully. Oct 7 13:36:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 61c23a23-9b4c-460e-bd2a-9e24142febd1. Oct 7 13:36:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext3 in remove_crypt Oct 7 13:36:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cr8rr8phmount_test with fs ext2 Oct 7 13:36:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:36:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7ef35318-f61f-42d1-9c61-72ed6d402e71 r/w without journal. Quota mode: none. Oct 7 13:36:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cr8rr8phmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt INFO: remove crypt device frLF INFO: finishe the remove crypt device frLF Oct 7 13:36:32 storageqe-109 systemd[1]: tmp-libblockdev.cr8rr8phmount_test.mount: Deactivated successfully. Oct 7 13:36:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7ef35318-f61f-42d1-9c61-72ed6d402e71. Oct 7 13:36:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/frLF and fs ext2 in remove_crypt Oct 7 13:36:32 storageqe-109 INFO: remove crypt device frLF Oct 7 13:36:32 storageqe-109 INFO: finishe the remove crypt device frLF INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_sche_test[npo2_linear] #### INFO: #### will start test_bz2212771[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:36:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:36:37 storageqe-109 INFO: #### END test_luks_sche_test[npo2_linear] #### Oct 7 13:36:37 storageqe-109 INFO: #### will start test_bz2212771[npo2_linear] ##### Oct 7 13:36:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --cipher 'capi:xts(ecb(aes-generic))-plain64' luksFormat /dev/mapper/npo2linear -q Oct 7 13:36:43 storageqe-109 journal: cryptsetup --cipher 'capi:xts(ecb(aes-generic))-plain64' luksFormat /dev/mapper/npo2linear -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_bz2212771[npo2_linear] #### INFO: #### will start test_RHEL_29679[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:36:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:36:58 storageqe-109 INFO: #### END test_bz2212771[npo2_linear] #### Oct 7 13:36:58 storageqe-109 INFO: #### will start test_RHEL_29679[npo2_linear] ##### Oct 7 13:36:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_RHEL_29679[npo2_linear] #### INFO: #### will start test_RHEL_41238[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:37:08 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:37:08 storageqe-109 INFO: #### END test_RHEL_29679[npo2_linear] #### Oct 7 13:37:08 storageqe-109 INFO: #### will start test_RHEL_41238[npo2_linear] ##### Oct 7 13:37:08 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_RHEL_41238[npo2_linear] #### Oct 7 13:37:18 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:37:18 storageqe-109 INFO: #### END test_RHEL_41238[npo2_linear] #### Oct 7 13:37:18 storageqe-109 stratisd[4947]: [2025-10-07T17:37:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:37:18 storageqe-109 stratisd[4947]: [2025-10-07T17:37:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:37:18 storageqe-109 stratisd[4947]: [2025-10-07T17:37:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:37:18 storageqe-109 stratisd[4947]: [2025-10-07T17:37:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 13:37:19 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 13:37:20 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 13:37:20 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 13:37:20 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 13:37:20 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 13:37:31 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_compat_test[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:37:37 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 13:37:37 storageqe-109 INFO: #### will start test_compat_test[npo2_linear] ##### Oct 7 13:37:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 13:37:42 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 13:37:50 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 13:37:52 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 13:38:02 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' luksFormat /dev/mapper/npo2linear -q Oct 7 13:38:12 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderiCO' open /dev/mapper/npo2linear --test-passphrase -q Oct 7 13:38:22 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 13:38:32 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 13:38:42 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 13:38:52 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q cryptsetup --header-backup-file '/tmp/testheadergHGnew' luksHeaderBackup /dev/mapper/npo2linear -q Oct 7 13:39:02 storageqe-109 journal: cryptsetup --header-backup-file '/tmp/testheadergHGnew' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q Oct 7 13:39:12 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 13:39:22 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --header-backup-file '/tmp/testheadergHGnew' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 13:39:32 storageqe-109 journal: cryptsetup --header-backup-file '/tmp/testheadergHGnew' luksHeaderRestore /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 13:39:42 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --uuid '12345678-1234-1234-1234-123456789abc' luksFormat /dev/mapper/npo2linear -q Oct 7 13:39:52 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --uuid '12345678-1234-1234-1234-123456789abc' luksFormat /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key Oct 7 13:40:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key Oct 7 13:40:12 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q --dump-master-key cryptsetup --type 'luks1' open /dev/mapper/npo2linear DRFK -q Oct 7 13:40:22 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear DRFK -q INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:40:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.wi7t3l29mount_test with fs xfs Oct 7 13:40:42 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 6cdf8dc5-bc3f-4983-a3ac-855555dcf100 Oct 7 13:40:42 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:40:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wi7t3l29mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:40:47 storageqe-109 systemd[1]: tmp-libblockdev.wi7t3l29mount_test.mount: Deactivated successfully. Oct 7 13:40:47 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 6cdf8dc5-bc3f-4983-a3ac-855555dcf100 Oct 7 13:40:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:40:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p33mmjdomount_test with fs ext4 Oct 7 13:40:57 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 44884e95-61b6-4b2b-a575-61ba5d6d7df8 r/w with ordered data mode. Quota mode: none. Oct 7 13:40:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p33mmjdomount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:41:02 storageqe-109 systemd[1]: tmp-libblockdev.p33mmjdomount_test.mount: Deactivated successfully. Oct 7 13:41:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 44884e95-61b6-4b2b-a575-61ba5d6d7df8. Oct 7 13:41:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:41:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.561p1ws3mount_test with fs ext3 Oct 7 13:41:12 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:41:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3915f449-56c1-4124-92db-4b3d79987754 r/w with ordered data mode. Quota mode: none. Oct 7 13:41:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.561p1ws3mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:41:17 storageqe-109 systemd[1]: tmp-libblockdev.561p1ws3mount_test.mount: Deactivated successfully. Oct 7 13:41:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3915f449-56c1-4124-92db-4b3d79987754. Oct 7 13:41:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:41:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1ihl1awcmount_test with fs ext2 Oct 7 13:41:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:41:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6d7eed62-027d-494d-9b0c-6ad232067bbe r/w without journal. Quota mode: none. Oct 7 13:41:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1ihl1awcmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK Oct 7 13:41:32 storageqe-109 systemd[1]: tmp-libblockdev.1ihl1awcmount_test.mount: Deactivated successfully. Oct 7 13:41:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6d7eed62-027d-494d-9b0c-6ad232067bbe. Oct 7 13:41:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:41:32 storageqe-109 INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --type 'luks1' open /dev/mapper/npo2linear DRFK -q Oct 7 13:41:32 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:41:32 storageqe-109 journal: cryptsetup --type 'luks1' open /dev/mapper/npo2linear DRFK -q cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' luksFormat /dev/mapper/npo2linear -q Oct 7 13:41:42 storageqe-109 journal: cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' luksFormat /dev/mapper/npo2linear -q cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q Oct 7 13:41:56 storageqe-109 journal: cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --key-file '/tmp/testfilebOL' luksFormat /dev/mapper/npo2linear -q Oct 7 13:42:09 storageqe-109 journal: cryptsetup --iter-time '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --type 'luks1' --key-file '/tmp/testfilebOL' luksFormat /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q Oct 7 13:42:21 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:42:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8ek9gtqrmount_test with fs xfs Oct 7 13:42:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 0aca5379-8b58-4449-98f3-7b8b1f1327a2 Oct 7 13:42:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:42:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8ek9gtqrmount_test with fs xfs Oct 7 13:42:47 storageqe-109 systemd[1]: tmp-libblockdev.8ek9gtqrmount_test.mount: Deactivated successfully. Oct 7 13:42:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 0aca5379-8b58-4449-98f3-7b8b1f1327a2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:42:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:42:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.d5nwslzwmount_test with fs ext4 Oct 7 13:42:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 342a5db2-5bcd-4a75-aecd-4ce60fef4068 r/w with ordered data mode. Quota mode: none. Oct 7 13:42:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d5nwslzwmount_test with fs ext4 Oct 7 13:43:02 storageqe-109 systemd[1]: tmp-libblockdev.d5nwslzwmount_test.mount: Deactivated successfully. Oct 7 13:43:02 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 342a5db2-5bcd-4a75-aecd-4ce60fef4068. INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:43:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:43:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:43:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.kyjcdijumount_test with fs ext3 Oct 7 13:43:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9c26a0f9-0f99-44d8-b380-507f8d485155 r/w with ordered data mode. Quota mode: none. Oct 7 13:43:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kyjcdijumount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:43:18 storageqe-109 systemd[1]: tmp-libblockdev.kyjcdijumount_test.mount: Deactivated successfully. Oct 7 13:43:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9c26a0f9-0f99-44d8-b380-507f8d485155. Oct 7 13:43:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:43:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jdi78v8umount_test with fs ext2 Oct 7 13:43:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:43:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9767601f-7e85-4eb5-80e8-970f051459fe r/w without journal. Quota mode: none. Oct 7 13:43:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jdi78v8umount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 13:43:33 storageqe-109 systemd[1]: tmp-libblockdev.jdi78v8umount_test.mount: Deactivated successfully. Oct 7 13:43:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9767601f-7e85-4eb5-80e8-970f051459fe. Oct 7 13:43:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:43:33 storageqe-109 INFO: remove crypt device DRFK Oct 7 13:43:33 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:43:33 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear DRFK -q Oct 7 13:43:43 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear DRFK -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/DRFK -q Oct 7 13:43:53 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/DRFK -q cryptsetup open /dev/mapper/DRFK dummy -q Oct 7 13:44:03 storageqe-109 journal: cryptsetup open /dev/mapper/DRFK dummy -q INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 7 13:44:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.i0yc9p6dmount_test with fs xfs Oct 7 13:44:23 storageqe-109 kernel: XFS (dm-5): Mounting V5 Filesystem 92580cd1-4da3-442d-962e-a715490aad31 Oct 7 13:44:23 storageqe-109 kernel: XFS (dm-5): Ending clean mount Oct 7 13:44:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i0yc9p6dmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 7 13:44:29 storageqe-109 systemd[1]: tmp-libblockdev.i0yc9p6dmount_test.mount: Deactivated successfully. Oct 7 13:44:29 storageqe-109 kernel: XFS (dm-5): Unmounting Filesystem 92580cd1-4da3-442d-962e-a715490aad31 Oct 7 13:44:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 7 13:44:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ng9hbmwjmount_test with fs ext4 Oct 7 13:44:39 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 870fa29a-d8cd-442b-9c6d-dcf919f02a0f r/w with ordered data mode. Quota mode: none. Oct 7 13:44:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ng9hbmwjmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 7 13:44:44 storageqe-109 systemd[1]: tmp-libblockdev.ng9hbmwjmount_test.mount: Deactivated successfully. Oct 7 13:44:44 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 870fa29a-d8cd-442b-9c6d-dcf919f02a0f. Oct 7 13:44:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 7 13:44:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jol9pj0tmount_test with fs ext3 Oct 7 13:44:54 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext3 file system using the ext4 subsystem Oct 7 13:44:54 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 4ceadc7b-e282-4c17-b488-1755c83c1d58 r/w with ordered data mode. Quota mode: none. Oct 7 13:44:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jol9pj0tmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 7 13:45:00 storageqe-109 systemd[1]: tmp-libblockdev.jol9pj0tmount_test.mount: Deactivated successfully. Oct 7 13:45:00 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 4ceadc7b-e282-4c17-b488-1755c83c1d58. Oct 7 13:45:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 7 13:45:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z9vmyy66mount_test with fs ext2 Oct 7 13:45:10 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext2 file system using the ext4 subsystem Oct 7 13:45:10 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 002fe1c8-2849-44ec-90e7-098f069115a5 r/w without journal. Quota mode: none. Oct 7 13:45:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z9vmyy66mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: remove crypt device dummy INFO: finishe the remove crypt device dummy INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:45:15 storageqe-109 systemd[1]: tmp-libblockdev.z9vmyy66mount_test.mount: Deactivated successfully. Oct 7 13:45:15 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 002fe1c8-2849-44ec-90e7-098f069115a5. Oct 7 13:45:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 7 13:45:15 storageqe-109 INFO: remove crypt device dummy Oct 7 13:45:15 storageqe-109 INFO: finishe the remove crypt device dummy Oct 7 13:45:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.oxi5yh44mount_test with fs xfs Oct 7 13:45:26 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3e4f84dc-a58e-4acf-a11f-6f314f08ff61 Oct 7 13:45:26 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:45:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.oxi5yh44mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:45:30 storageqe-109 systemd[1]: tmp-libblockdev.oxi5yh44mount_test.mount: Deactivated successfully. Oct 7 13:45:30 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3e4f84dc-a58e-4acf-a11f-6f314f08ff61 Oct 7 13:45:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:45:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f1ywm9j_mount_test with fs ext4 Oct 7 13:45:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0abae8ae-b6fa-4691-b043-61828690aa2f r/w with ordered data mode. Quota mode: none. Oct 7 13:45:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f1ywm9j_mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:45:46 storageqe-109 systemd[1]: tmp-libblockdev.f1ywm9j_mount_test.mount: Deactivated successfully. Oct 7 13:45:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0abae8ae-b6fa-4691-b043-61828690aa2f. Oct 7 13:45:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:45:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bks8vwp6mount_test with fs ext3 Oct 7 13:45:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:45:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f1bcc831-12fa-48eb-bab9-6b7d66ccf055 r/w with ordered data mode. Quota mode: none. Oct 7 13:45:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bks8vwp6mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:46:01 storageqe-109 systemd[1]: tmp-libblockdev.bks8vwp6mount_test.mount: Deactivated successfully. Oct 7 13:46:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f1bcc831-12fa-48eb-bab9-6b7d66ccf055. Oct 7 13:46:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:46:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8224ppazmount_test with fs ext2 Oct 7 13:46:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:46:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem be1828b6-d8ad-48c2-8a31-51bc6430252d r/w without journal. Quota mode: none. Oct 7 13:46:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8224ppazmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:46:16 storageqe-109 systemd[1]: tmp-libblockdev.8224ppazmount_test.mount: Deactivated successfully. Oct 7 13:46:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem be1828b6-d8ad-48c2-8a31-51bc6430252d. Oct 7 13:46:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:46:16 storageqe-109 INFO: remove crypt device DRFK Oct 7 13:46:16 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:46:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.c6oj5strmount_test with fs xfs Oct 7 13:46:26 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b63ef414-23a9-47e6-9841-7d6a3a404e14 Oct 7 13:46:26 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:46:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c6oj5strmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:46:31 storageqe-109 systemd[1]: tmp-libblockdev.c6oj5strmount_test.mount: Deactivated successfully. Oct 7 13:46:31 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b63ef414-23a9-47e6-9841-7d6a3a404e14 Oct 7 13:46:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:46:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nb8b8o2smount_test with fs ext4 Oct 7 13:46:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 67392315-528d-47d6-b788-cbabec19a377 r/w with ordered data mode. Quota mode: none. Oct 7 13:46:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nb8b8o2smount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:46:46 storageqe-109 systemd[1]: tmp-libblockdev.nb8b8o2smount_test.mount: Deactivated successfully. Oct 7 13:46:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 67392315-528d-47d6-b788-cbabec19a377. Oct 7 13:46:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:46:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.a4p98vobmount_test with fs ext3 Oct 7 13:46:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:46:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7c7972bb-ab6d-42a2-9498-15df71a4c1f1 r/w with ordered data mode. Quota mode: none. Oct 7 13:46:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a4p98vobmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:47:01 storageqe-109 systemd[1]: tmp-libblockdev.a4p98vobmount_test.mount: Deactivated successfully. Oct 7 13:47:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7c7972bb-ab6d-42a2-9498-15df71a4c1f1. Oct 7 13:47:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:47:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mlg8fbajmount_test with fs ext2 Oct 7 13:47:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:47:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a1295895-b351-47ff-b21a-84dc4ba44a24 r/w without journal. Quota mode: none. Oct 7 13:47:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mlg8fbajmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --hash 'sha256' --cipher 'aes-cbc-essiv:sha256' --offset '8' --skip '4' create DRFK /dev/mapper/npo2linear -q --readonly Oct 7 13:47:16 storageqe-109 systemd[1]: tmp-libblockdev.mlg8fbajmount_test.mount: Deactivated successfully. Oct 7 13:47:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a1295895-b351-47ff-b21a-84dc4ba44a24. Oct 7 13:47:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:47:16 storageqe-109 INFO: remove crypt device DRFK Oct 7 13:47:16 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:47:16 storageqe-109 journal: cryptsetup --hash 'sha256' --cipher 'aes-cbc-essiv:sha256' --offset '8' --skip '4' create DRFK /dev/mapper/npo2linear -q --readonly cryptsetup status DRFK -q Oct 7 13:47:26 storageqe-109 journal: cryptsetup status DRFK -q cryptsetup status DRFK -q Oct 7 13:47:36 storageqe-109 journal: cryptsetup status DRFK -q cryptsetup status DRFK -q Oct 7 13:47:46 storageqe-109 journal: cryptsetup status DRFK -q cryptsetup status DRFK -q Oct 7 13:47:56 storageqe-109 journal: cryptsetup status DRFK -q cryptsetup --size '409600' resize DRFK -q Oct 7 13:48:06 storageqe-109 journal: cryptsetup --size '409600' resize DRFK -q cryptsetup status DRFK -q Oct 7 13:48:16 storageqe-109 journal: cryptsetup status DRFK -q cryptsetup resize DRFK -q Oct 7 13:48:26 storageqe-109 journal: cryptsetup resize DRFK -q cryptsetup resize DRFK -q Oct 7 13:48:36 storageqe-109 journal: cryptsetup resize DRFK -q cryptsetup remove DRFK -q Oct 7 13:48:46 storageqe-109 journal: cryptsetup remove DRFK -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q Oct 7 13:48:56 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q cryptsetup --key-slot '4' open /dev/mapper/npo2linear DRFK -q Oct 7 13:49:06 storageqe-109 journal: cryptsetup --key-slot '4' open /dev/mapper/npo2linear DRFK -q cryptsetup --key-slot '5' open /dev/mapper/npo2linear DRFK -q Oct 7 13:49:16 storageqe-109 journal: cryptsetup --key-slot '5' open /dev/mapper/npo2linear DRFK -q INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:49:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ag_21vc_mount_test with fs xfs Oct 7 13:49:37 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 290a1ffc-a300-4475-803f-75fd6ab66326 Oct 7 13:49:37 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:49:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ag_21vc_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:49:41 storageqe-109 systemd[1]: tmp-libblockdev.ag_21vc_mount_test.mount: Deactivated successfully. Oct 7 13:49:41 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 290a1ffc-a300-4475-803f-75fd6ab66326 Oct 7 13:49:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:49:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8ihd9m9rmount_test with fs ext4 Oct 7 13:49:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e828aaba-d01a-43b4-97da-3aeada01be04 r/w with ordered data mode. Quota mode: none. Oct 7 13:49:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8ihd9m9rmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:49:56 storageqe-109 systemd[1]: tmp-libblockdev.8ihd9m9rmount_test.mount: Deactivated successfully. Oct 7 13:49:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e828aaba-d01a-43b4-97da-3aeada01be04. Oct 7 13:49:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:49:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6m0rur3_mount_test with fs ext3 Oct 7 13:50:07 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:50:07 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6b9c4a77-5aa3-4641-a7cf-046f8ad26a90 r/w with ordered data mode. Quota mode: none. Oct 7 13:50:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6m0rur3_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:50:12 storageqe-109 systemd[1]: tmp-libblockdev.6m0rur3_mount_test.mount: Deactivated successfully. Oct 7 13:50:12 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6b9c4a77-5aa3-4641-a7cf-046f8ad26a90. Oct 7 13:50:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:50:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vskf9z16mount_test with fs ext2 Oct 7 13:50:22 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:50:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6ae4d2cb-9250-402d-96e9-704b0fd2d2e8 r/w without journal. Quota mode: none. Oct 7 13:50:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vskf9z16mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup open /dev/mapper/npo2linear DRFK -q Oct 7 13:50:27 storageqe-109 systemd[1]: tmp-libblockdev.vskf9z16mount_test.mount: Deactivated successfully. Oct 7 13:50:27 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6ae4d2cb-9250-402d-96e9-704b0fd2d2e8. Oct 7 13:50:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:50:27 storageqe-109 INFO: remove crypt device DRFK Oct 7 13:50:27 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:50:27 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear DRFK -q cryptsetup open /dev/mapper/npo2linear DRFK -q Oct 7 13:50:37 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear DRFK -q INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:50:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.zkpnqq_wmount_test with fs xfs Oct 7 13:50:57 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 0d77042f-297f-4cc7-b326-74d305d426bb Oct 7 13:50:57 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:50:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zkpnqq_wmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:51:02 storageqe-109 systemd[1]: tmp-libblockdev.zkpnqq_wmount_test.mount: Deactivated successfully. Oct 7 13:51:02 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 0d77042f-297f-4cc7-b326-74d305d426bb Oct 7 13:51:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:51:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fs0k70uzmount_test with fs ext4 Oct 7 13:51:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7132167e-2268-4018-b8e9-833d3018c3fd r/w with ordered data mode. Quota mode: none. Oct 7 13:51:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fs0k70uzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:51:17 storageqe-109 systemd[1]: tmp-libblockdev.fs0k70uzmount_test.mount: Deactivated successfully. Oct 7 13:51:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7132167e-2268-4018-b8e9-833d3018c3fd. Oct 7 13:51:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:51:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.65md_kl7mount_test with fs ext3 Oct 7 13:51:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:51:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0b97a6e1-bbd4-477e-9b2d-dc683c3b9d4a r/w with ordered data mode. Quota mode: none. Oct 7 13:51:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.65md_kl7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:51:32 storageqe-109 systemd[1]: tmp-libblockdev.65md_kl7mount_test.mount: Deactivated successfully. Oct 7 13:51:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0b97a6e1-bbd4-477e-9b2d-dc683c3b9d4a. Oct 7 13:51:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:51:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bk2r09o9mount_test with fs ext2 Oct 7 13:51:42 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:51:42 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6c7221a6-86d6-4555-8533-c544d06be2df r/w without journal. Quota mode: none. Oct 7 13:51:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bk2r09o9mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --type 'luks1' --key-slot '5' --key-file '/tmp/testfileiBT' luksFormat /dev/mapper/npo2linear -q Oct 7 13:51:47 storageqe-109 systemd[1]: tmp-libblockdev.bk2r09o9mount_test.mount: Deactivated successfully. Oct 7 13:51:47 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6c7221a6-86d6-4555-8533-c544d06be2df. Oct 7 13:51:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:51:47 storageqe-109 INFO: remove crypt device DRFK Oct 7 13:51:47 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:51:47 storageqe-109 journal: cryptsetup --type 'luks1' --key-slot '5' --key-file '/tmp/testfileiBT' luksFormat /dev/mapper/npo2linear -q cryptsetup --key-slot '5' --key-file '/tmp/testfileiBT' open /dev/mapper/npo2linear DRFK -q Oct 7 13:52:01 storageqe-109 journal: cryptsetup --key-slot '5' --key-file '/tmp/testfileiBT' open /dev/mapper/npo2linear DRFK -q INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:52:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.hc3uljodmount_test with fs xfs Oct 7 13:52:23 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 81a201a9-3b64-4a0b-aafa-0db87d3b2135 Oct 7 13:52:23 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:52:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hc3uljodmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:52:28 storageqe-109 systemd[1]: tmp-libblockdev.hc3uljodmount_test.mount: Deactivated successfully. Oct 7 13:52:28 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 81a201a9-3b64-4a0b-aafa-0db87d3b2135 Oct 7 13:52:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:52:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.itlcg7n3mount_test with fs ext4 Oct 7 13:52:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem fe0c493d-f69f-4509-9124-44fb324c9dd9 r/w with ordered data mode. Quota mode: none. Oct 7 13:52:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.itlcg7n3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:52:43 storageqe-109 systemd[1]: tmp-libblockdev.itlcg7n3mount_test.mount: Deactivated successfully. Oct 7 13:52:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem fe0c493d-f69f-4509-9124-44fb324c9dd9. Oct 7 13:52:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:52:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.95nb2zr4mount_test with fs ext3 Oct 7 13:52:53 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:52:53 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 46396bbd-ba57-4f80-b5f8-421cf5cf6dfc r/w with ordered data mode. Quota mode: none. Oct 7 13:52:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.95nb2zr4mount_test with fs ext3 Oct 7 13:52:58 storageqe-109 systemd[1]: tmp-libblockdev.95nb2zr4mount_test.mount: Deactivated successfully. Oct 7 13:52:58 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 46396bbd-ba57-4f80-b5f8-421cf5cf6dfc. INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:52:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:52:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.d2flerdkmount_test with fs ext2 Oct 7 13:53:08 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:53:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 46293998-e442-4ce6-90cb-c79f88833910 r/w without journal. Quota mode: none. Oct 7 13:53:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d2flerdkmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK Oct 7 13:53:13 storageqe-109 systemd[1]: tmp-libblockdev.d2flerdkmount_test.mount: Deactivated successfully. Oct 7 13:53:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 46293998-e442-4ce6-90cb-c79f88833910. Oct 7 13:53:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:53:13 storageqe-109 INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' luksFormat /dev/mapper/npo2linear -q Oct 7 13:53:13 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:53:13 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '1' luksFormat /dev/mapper/npo2linear -q Oct 7 13:53:23 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '8192' luksFormat /dev/mapper/npo2linear -q Oct 7 13:53:33 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '0' luksFormat /dev/mapper/npo2linear -q Oct 7 13:53:44 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '0' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '8192' --offset '8192' luksFormat /dev/mapper/npo2linear -q Oct 7 13:53:54 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --align-payload '8192' --offset '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --key-slot '7' luksFormat /dev/mapper/npo2linear -q Oct 7 13:54:04 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --key-slot '7' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --offset '80000' luksFormat /dev/mapper/npo2linear -q Oct 7 13:54:14 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --offset '80000' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --offset '8192' luksFormat /dev/mapper/npo2linear -q Oct 7 13:54:24 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --offset '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --offset '0' luksFormat /dev/mapper/npo2linear -q Oct 7 13:54:34 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' --offset '0' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderiCO' open /dev/mapper/npo2linear DRFK -q Oct 7 13:54:44 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' open /dev/mapper/npo2linear DRFK -q cryptsetup --size '409600' --header '/tmp/testheaderiCO' resize DRFK -q Oct 7 13:54:54 storageqe-109 journal: cryptsetup --size '409600' --header '/tmp/testheaderiCO' resize DRFK -q cryptsetup --header '/tmp/testheaderiCO' status DRFK -q Oct 7 13:55:04 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' status DRFK -q cryptsetup --header '/tmp/testheaderiCO' status DRFK -q Oct 7 13:55:14 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' status DRFK -q cryptsetup status DRFK -q Oct 7 13:55:24 storageqe-109 journal: cryptsetup status DRFK -q cryptsetup --header '/tmp/testheaderiCO' luksSuspend DRFK -q Oct 7 13:55:34 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' luksSuspend DRFK -q cryptsetup --header '/tmp/testheaderiCO' luksResume DRFK -q Oct 7 13:55:44 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' luksResume DRFK -q INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --type 'luks1' --key-slot '5' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' luksAddKey _fake_dev_ /tmp/testfileiBT -q Oct 7 13:55:54 storageqe-109 INFO: remove crypt device DRFK Oct 7 13:55:54 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:55:54 storageqe-109 journal: cryptsetup --type 'luks1' --key-slot '5' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderiCO' luksAddKey _fake_dev_ /tmp/testfileiBT -q cryptsetup --header '/tmp/testheaderiCO' luksDump _fake_dev_ -q Oct 7 13:56:04 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' luksDump _fake_dev_ -q cryptsetup --header '/tmp/testheaderiCO' luksDump _fake_dev_ -q Oct 7 13:56:14 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' luksDump _fake_dev_ -q cryptsetup --header '/tmp/testheaderiCO' luksKillSlot _fake_dev_ 5 -q Oct 7 13:56:24 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' luksKillSlot _fake_dev_ 5 -q cryptsetup --header '/tmp/testheaderiCO' luksDump _fake_dev_ -q Oct 7 13:56:34 storageqe-109 journal: cryptsetup --header '/tmp/testheaderiCO' luksDump _fake_dev_ -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' luksFormat /dev/mapper/npo2linear /tmp/testfilebOL -q Oct 7 13:56:44 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' luksFormat /dev/mapper/npo2linear /tmp/testfilebOL -q cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q Oct 7 13:56:54 storageqe-109 udisksd[1175313]: Error getting '/dev/dm-3' metadata_size: Unknown or unsupported LUKS version (g-bd-crypto-error-quark, 0) Oct 7 13:56:54 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q cryptsetup repair /dev/mapper/npo2linear -q Oct 7 13:57:04 storageqe-109 journal: cryptsetup repair /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q Oct 7 13:57:16 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:57:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.khcn35msmount_test with fs xfs Oct 7 13:57:36 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem efeb6d1c-7843-4d7f-918c-4588062dcf5b Oct 7 13:57:36 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:57:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.khcn35msmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:57:40 storageqe-109 systemd[1]: tmp-libblockdev.khcn35msmount_test.mount: Deactivated successfully. Oct 7 13:57:40 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem efeb6d1c-7843-4d7f-918c-4588062dcf5b Oct 7 13:57:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:57:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.90le582ymount_test with fs ext4 Oct 7 13:57:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 176e34be-463c-4f9b-97aa-91a3f52fc29b r/w with ordered data mode. Quota mode: none. Oct 7 13:57:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.90le582ymount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:57:56 storageqe-109 systemd[1]: tmp-libblockdev.90le582ymount_test.mount: Deactivated successfully. Oct 7 13:57:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 176e34be-463c-4f9b-97aa-91a3f52fc29b. Oct 7 13:57:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:57:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dv0_w90imount_test with fs ext3 Oct 7 13:58:06 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:58:06 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3c8e00d8-45db-4d4b-9471-3186f1c9690f r/w with ordered data mode. Quota mode: none. Oct 7 13:58:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dv0_w90imount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:58:11 storageqe-109 systemd[1]: tmp-libblockdev.dv0_w90imount_test.mount: Deactivated successfully. Oct 7 13:58:11 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3c8e00d8-45db-4d4b-9471-3186f1c9690f. Oct 7 13:58:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:58:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pjndjebtmount_test with fs ext2 Oct 7 13:58:21 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:58:21 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 34d88674-09b3-4915-b560-6002153b1fc7 r/w without journal. Quota mode: none. Oct 7 13:58:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pjndjebtmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK Oct 7 13:58:26 storageqe-109 systemd[1]: tmp-libblockdev.pjndjebtmount_test.mount: Deactivated successfully. Oct 7 13:58:26 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 34d88674-09b3-4915-b560-6002153b1fc7. Oct 7 13:58:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:58:26 storageqe-109 INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --hash 'sha256' --cipher 'aes-ecb' luksFormat /dev/mapper/npo2linear /tmp/testfilebOL -q Oct 7 13:58:26 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:58:26 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --hash 'sha256' --cipher 'aes-ecb' luksFormat /dev/mapper/npo2linear /tmp/testfilebOL -q cryptsetup repair /dev/mapper/npo2linear -q Oct 7 13:58:36 storageqe-109 journal: cryptsetup repair /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q Oct 7 13:58:47 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilebOL' open /dev/mapper/npo2linear DRFK -q INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:58:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.u93h4ro5mount_test with fs xfs Oct 7 13:59:07 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b7fd2266-ebe8-4383-b0d1-f3102a9a2f33 Oct 7 13:59:07 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 13:59:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u93h4ro5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:59:12 storageqe-109 systemd[1]: tmp-libblockdev.u93h4ro5mount_test.mount: Deactivated successfully. Oct 7 13:59:12 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b7fd2266-ebe8-4383-b0d1-f3102a9a2f33 Oct 7 13:59:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs xfs in remove_crypt Oct 7 13:59:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hxkmv0l6mount_test with fs ext4 Oct 7 13:59:22 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 83650fa5-0fcd-4d89-9c61-c9dba7151908 r/w with ordered data mode. Quota mode: none. Oct 7 13:59:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hxkmv0l6mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:59:27 storageqe-109 systemd[1]: tmp-libblockdev.hxkmv0l6mount_test.mount: Deactivated successfully. Oct 7 13:59:27 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 83650fa5-0fcd-4d89-9c61-c9dba7151908. Oct 7 13:59:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext4 in remove_crypt Oct 7 13:59:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wgnpeb1pmount_test with fs ext3 Oct 7 13:59:37 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 13:59:37 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1578b0d3-d287-4a3d-a69f-17eb87e595d8 r/w with ordered data mode. Quota mode: none. Oct 7 13:59:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wgnpeb1pmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:59:42 storageqe-109 systemd[1]: tmp-libblockdev.wgnpeb1pmount_test.mount: Deactivated successfully. Oct 7 13:59:42 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1578b0d3-d287-4a3d-a69f-17eb87e595d8. Oct 7 13:59:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext3 in remove_crypt Oct 7 13:59:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.12r8e0fmmount_test with fs ext2 Oct 7 13:59:52 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 13:59:52 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2f870bca-d4c6-430e-bab9-3f8f1854835b r/w without journal. Quota mode: none. Oct 7 13:59:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.12r8e0fmmount_test with fs ext2 Oct 7 13:59:57 storageqe-109 systemd[1]: tmp-libblockdev.12r8e0fmmount_test.mount: Deactivated successfully. Oct 7 13:59:57 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2f870bca-d4c6-430e-bab9-3f8f1854835b. INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt INFO: remove crypt device DRFK INFO: finishe the remove crypt device DRFK cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear /tmp/testfileiBT -q Oct 7 13:59:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/DRFK and fs ext2 in remove_crypt Oct 7 13:59:57 storageqe-109 INFO: remove crypt device DRFK Oct 7 13:59:57 storageqe-109 INFO: finishe the remove crypt device DRFK Oct 7 13:59:57 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear /tmp/testfileiBT -q cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --key-file '/tmp/testfileiBT' luksAddKey /dev/mapper/npo2linear /tmp/testfilebOL -q Oct 7 14:00:07 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --key-file '/tmp/testfileiBT' luksAddKey /dev/mapper/npo2linear /tmp/testfilebOL -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:00:17 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:00:27 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksErase /dev/mapper/npo2linear -q Oct 7 14:00:37 storageqe-109 journal: cryptsetup luksErase /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:00:48 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:00:58 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_compat_test[npo2_linear] #### Oct 7 14:01:13 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 14:01:13 storageqe-109 INFO: #### END test_compat_test[npo2_linear] #### Oct 7 14:01:14 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 14:01:14 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 14:01:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 14:01:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 14:01:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 14:01:26 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_compat_test2[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 14:01:31 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 14:01:31 storageqe-109 INFO: #### will start test_compat_test2[npo2_linear] ##### Oct 7 14:01:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:01:36 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:01:36 storageqe-109 stratisd[4947]: [2025-10-07T18:01:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:01:36 storageqe-109 stratisd[4947]: [2025-10-07T18:01:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:01:45 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:01:46 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:01:46 storageqe-109 stratisd[4947]: [2025-10-07T18:01:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:01:46 storageqe-109 stratisd[4947]: [2025-10-07T18:01:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:01:56 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 14:02:06 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:02:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.v1hur91kmount_test with fs xfs Oct 7 14:02:27 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem e9e5a660-1099-45ca-80be-dce942675144 Oct 7 14:02:27 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:02:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v1hur91kmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:02:31 storageqe-109 systemd[1]: tmp-libblockdev.v1hur91kmount_test.mount: Deactivated successfully. Oct 7 14:02:31 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem e9e5a660-1099-45ca-80be-dce942675144 Oct 7 14:02:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:02:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.parkjymbmount_test with fs ext4 Oct 7 14:02:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem aa35b074-f95f-497d-b2a6-f2834b77cdfb r/w with ordered data mode. Quota mode: none. Oct 7 14:02:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.parkjymbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:02:46 storageqe-109 systemd[1]: tmp-libblockdev.parkjymbmount_test.mount: Deactivated successfully. Oct 7 14:02:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem aa35b074-f95f-497d-b2a6-f2834b77cdfb. Oct 7 14:02:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:02:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ykd5ebommount_test with fs ext3 Oct 7 14:02:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:02:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 286888be-25f7-4c4c-a960-38bcbebcff3e r/w with ordered data mode. Quota mode: none. Oct 7 14:02:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ykd5ebommount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:03:01 storageqe-109 systemd[1]: tmp-libblockdev.ykd5ebommount_test.mount: Deactivated successfully. Oct 7 14:03:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 286888be-25f7-4c4c-a960-38bcbebcff3e. Oct 7 14:03:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:03:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.469td3a_mount_test with fs ext2 Oct 7 14:03:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:03:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f9f9a94b-cbcb-49eb-84f0-9c27d60ec037 r/w without journal. Quota mode: none. Oct 7 14:03:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.469td3a_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '1' luksFormat /dev/mapper/npo2linear -q Oct 7 14:03:16 storageqe-109 systemd[1]: tmp-libblockdev.469td3a_mount_test.mount: Deactivated successfully. Oct 7 14:03:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f9f9a94b-cbcb-49eb-84f0-9c27d60ec037. Oct 7 14:03:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:03:16 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:03:16 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:03:16 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16385' luksFormat /dev/mapper/npo2linear -q Oct 7 14:03:26 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16385' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '32' luksFormat /dev/mapper/npo2linear -q Oct 7 14:03:36 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '32' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --align-payload '16384' luksFormat /dev/mapper/npo2linear -q Oct 7 14:03:47 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --align-payload '16384' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' luksFormat /dev/mapper/npo2linear -q Oct 7 14:03:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' luksFormat /dev/mapper/npo2linear -q Oct 7 14:03:57 storageqe-109 stratisd[4947]: [2025-10-07T18:03:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:03:57 storageqe-109 stratisd[4947]: [2025-10-07T18:03:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:04:07 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --sector-size '1024' luksFormat /dev/mapper/npo2linear -q Oct 7 14:04:17 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '16384' --sector-size '1024' luksFormat /dev/mapper/npo2linear -q Oct 7 14:04:17 storageqe-109 stratisd[4947]: [2025-10-07T18:04:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:04:17 storageqe-109 stratisd[4947]: [2025-10-07T18:04:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:04:27 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '80000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q Oct 7 14:04:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --offset '80000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '511' luksFormat /dev/mapper/npo2linear -q Oct 7 14:04:47 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '511' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '256' luksFormat /dev/mapper/npo2linear -q Oct 7 14:04:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '256' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '8192' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:07 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '8192' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:17 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:17 storageqe-109 stratisd[4947]: [2025-10-07T18:05:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:05:17 storageqe-109 stratisd[4947]: [2025-10-07T18:05:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:27 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:27 storageqe-109 stratisd[4947]: [2025-10-07T18:05:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:05:27 storageqe-109 stratisd[4947]: [2025-10-07T18:05:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:37 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '5' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:37 storageqe-109 stratisd[4947]: [2025-10-07T18:05:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:05:37 storageqe-109 stratisd[4947]: [2025-10-07T18:05:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:47 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:47 storageqe-109 stratisd[4947]: [2025-10-07T18:05:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:05:47 storageqe-109 stratisd[4947]: [2025-10-07T18:05:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 14:05:57 storageqe-109 stratisd[4947]: [2025-10-07T18:05:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:05:57 storageqe-109 stratisd[4947]: [2025-10-07T18:05:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:07 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:08 storageqe-109 stratisd[4947]: [2025-10-07T18:06:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:06:08 storageqe-109 stratisd[4947]: [2025-10-07T18:06:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:06:18 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:28 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '2048' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:28 storageqe-109 stratisd[4947]: [2025-10-07T18:06:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:06:28 storageqe-109 stratisd[4947]: [2025-10-07T18:06:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:38 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --align-payload '32768' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:38 storageqe-109 stratisd[4947]: [2025-10-07T18:06:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:06:38 storageqe-109 stratisd[4947]: [2025-10-07T18:06:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:06:48 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:58 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 7 14:06:58 storageqe-109 stratisd[4947]: [2025-10-07T18:06:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:06:58 storageqe-109 stratisd[4947]: [2025-10-07T18:06:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --hash 'sha512' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 7 14:07:08 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '128' --hash 'sha512' --cipher 'aes-cbc-essiv:sha256' luksFormat /dev/mapper/npo2linear -q Oct 7 14:07:08 storageqe-109 stratisd[4947]: [2025-10-07T18:07:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:07:08 storageqe-109 stratisd[4947]: [2025-10-07T18:07:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:07:18 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear --dump-json-metadata -q Oct 7 14:07:28 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear --dump-json-metadata -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:07:38 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:07:48 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:07:58 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:07:58 storageqe-109 stratisd[4947]: [2025-10-07T18:07:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:07:58 storageqe-109 stratisd[4947]: [2025-10-07T18:07:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:08:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.wmxhl53xmount_test with fs xfs Oct 7 14:08:18 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem d5a1d2c7-9a98-4a15-bbf8-4e5919d10bd5 Oct 7 14:08:18 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:08:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wmxhl53xmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:08:23 storageqe-109 systemd[1]: tmp-libblockdev.wmxhl53xmount_test.mount: Deactivated successfully. Oct 7 14:08:23 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem d5a1d2c7-9a98-4a15-bbf8-4e5919d10bd5 Oct 7 14:08:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:08:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p6dj6ldgmount_test with fs ext4 Oct 7 14:08:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 46cebcfd-2fed-48dd-b1c4-563e8c5bb8ba r/w with ordered data mode. Quota mode: none. Oct 7 14:08:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p6dj6ldgmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:08:38 storageqe-109 systemd[1]: tmp-libblockdev.p6dj6ldgmount_test.mount: Deactivated successfully. Oct 7 14:08:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 46cebcfd-2fed-48dd-b1c4-563e8c5bb8ba. Oct 7 14:08:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:08:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8x9r403dmount_test with fs ext3 Oct 7 14:08:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:08:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1f048d0c-6830-4397-b7ee-24d6c107e5cb r/w with ordered data mode. Quota mode: none. Oct 7 14:08:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8x9r403dmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:08:53 storageqe-109 systemd[1]: tmp-libblockdev.8x9r403dmount_test.mount: Deactivated successfully. Oct 7 14:08:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1f048d0c-6830-4397-b7ee-24d6c107e5cb. Oct 7 14:08:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:08:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.syc7fudxmount_test with fs ext2 Oct 7 14:09:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:09:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bf1743c8-ac6d-47db-b3db-7321978c1dff r/w without journal. Quota mode: none. Oct 7 14:09:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.syc7fudxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:09:08 storageqe-109 systemd[1]: tmp-libblockdev.syc7fudxmount_test.mount: Deactivated successfully. Oct 7 14:09:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bf1743c8-ac6d-47db-b3db-7321978c1dff. Oct 7 14:09:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:09:08 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:09:08 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:09:08 storageqe-109 stratisd[4947]: [2025-10-07T18:09:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:09:08 storageqe-109 stratisd[4947]: [2025-10-07T18:09:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:09:08 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 7 14:09:18 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 7 14:09:28 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 7 14:09:28 storageqe-109 stratisd[4947]: [2025-10-07T18:09:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:09:28 storageqe-109 stratisd[4947]: [2025-10-07T18:09:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:09:38 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:09:48 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:09:48 storageqe-109 stratisd[4947]: [2025-10-07T18:09:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:09:48 storageqe-109 stratisd[4947]: [2025-10-07T18:09:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:09:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.6w9s8xkpmount_test with fs xfs Oct 7 14:10:09 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 40b6c50a-7846-4002-b2f2-ddb37833288c Oct 7 14:10:09 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:10:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6w9s8xkpmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:10:13 storageqe-109 systemd[1]: tmp-libblockdev.6w9s8xkpmount_test.mount: Deactivated successfully. Oct 7 14:10:13 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 40b6c50a-7846-4002-b2f2-ddb37833288c Oct 7 14:10:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:10:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x6fbb23gmount_test with fs ext4 Oct 7 14:10:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem eae09bec-10fd-4eb3-85e5-7617cde0a0b3 r/w with ordered data mode. Quota mode: none. Oct 7 14:10:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x6fbb23gmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:10:28 storageqe-109 systemd[1]: tmp-libblockdev.x6fbb23gmount_test.mount: Deactivated successfully. Oct 7 14:10:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem eae09bec-10fd-4eb3-85e5-7617cde0a0b3. Oct 7 14:10:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:10:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5lqsdnejmount_test with fs ext3 Oct 7 14:10:38 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:10:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 36fcb2b5-8c85-4707-b1b6-93935c8953a6 r/w with ordered data mode. Quota mode: none. Oct 7 14:10:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5lqsdnejmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:10:43 storageqe-109 systemd[1]: tmp-libblockdev.5lqsdnejmount_test.mount: Deactivated successfully. Oct 7 14:10:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 36fcb2b5-8c85-4707-b1b6-93935c8953a6. Oct 7 14:10:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:10:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7ewgw7eamount_test with fs ext2 Oct 7 14:10:53 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:10:53 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 521d97f3-6ce6-478b-9fc9-ce1937d11716 r/w without journal. Quota mode: none. Oct 7 14:10:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7ewgw7eamount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:10:58 storageqe-109 systemd[1]: tmp-libblockdev.7ewgw7eamount_test.mount: Deactivated successfully. Oct 7 14:10:58 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 521d97f3-6ce6-478b-9fc9-ce1937d11716. Oct 7 14:10:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:10:58 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:10:58 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:10:58 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:10:58 storageqe-109 stratisd[4947]: [2025-10-07T18:10:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:10:58 storageqe-109 stratisd[4947]: [2025-10-07T18:10:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:11:08 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:11:08 storageqe-109 stratisd[4947]: [2025-10-07T18:11:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:11:08 storageqe-109 stratisd[4947]: [2025-10-07T18:11:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:11:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.wkda6r74mount_test with fs xfs Oct 7 14:11:29 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 38c5b425-6a6d-438e-acce-832d874def40 Oct 7 14:11:29 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:11:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wkda6r74mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:11:33 storageqe-109 systemd[1]: tmp-libblockdev.wkda6r74mount_test.mount: Deactivated successfully. Oct 7 14:11:33 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 38c5b425-6a6d-438e-acce-832d874def40 Oct 7 14:11:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:11:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.n2tpikqsmount_test with fs ext4 Oct 7 14:11:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ec1b4248-f4f8-45df-96a2-61dfccccd9fb r/w with ordered data mode. Quota mode: none. Oct 7 14:11:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n2tpikqsmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:11:49 storageqe-109 systemd[1]: tmp-libblockdev.n2tpikqsmount_test.mount: Deactivated successfully. Oct 7 14:11:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ec1b4248-f4f8-45df-96a2-61dfccccd9fb. Oct 7 14:11:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:11:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.d__dh1q0mount_test with fs ext3 Oct 7 14:11:59 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:11:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dcc5362d-7045-44f7-9d95-1eda7915a565 r/w with ordered data mode. Quota mode: none. Oct 7 14:11:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d__dh1q0mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:12:04 storageqe-109 systemd[1]: tmp-libblockdev.d__dh1q0mount_test.mount: Deactivated successfully. Oct 7 14:12:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dcc5362d-7045-44f7-9d95-1eda7915a565. Oct 7 14:12:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:12:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rz48lqjwmount_test with fs ext2 Oct 7 14:12:14 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:12:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 59e6a9c9-49ff-4c5e-b023-6fb442d93a47 r/w without journal. Quota mode: none. Oct 7 14:12:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rz48lqjwmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:12:19 storageqe-109 systemd[1]: tmp-libblockdev.rz48lqjwmount_test.mount: Deactivated successfully. Oct 7 14:12:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 59e6a9c9-49ff-4c5e-b023-6fb442d93a47. Oct 7 14:12:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:12:19 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:12:19 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --key-file '/tmp/testfileOax' luksKillSlot /dev/mapper/npo2linear 0 -q Oct 7 14:12:19 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' luksKillSlot /dev/mapper/npo2linear 0 -q Oct 7 14:12:19 storageqe-109 stratisd[4947]: [2025-10-07T18:12:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:12:19 storageqe-109 stratisd[4947]: [2025-10-07T18:12:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:12:29 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:12:39 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:12:39 storageqe-109 stratisd[4947]: [2025-10-07T18:12:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:12:39 storageqe-109 stratisd[4947]: [2025-10-07T18:12:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:12:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.217bx57xmount_test with fs xfs Oct 7 14:12:59 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 2379e738-5abf-43be-961a-d87f629aa83f Oct 7 14:12:59 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:12:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.217bx57xmount_test with fs xfs Oct 7 14:13:04 storageqe-109 systemd[1]: tmp-libblockdev.217bx57xmount_test.mount: Deactivated successfully. Oct 7 14:13:04 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 2379e738-5abf-43be-961a-d87f629aa83f INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:13:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:13:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0wzcp5pwmount_test with fs ext4 Oct 7 14:13:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 104945d9-c6a1-4da8-a285-9d09d4a640df r/w with ordered data mode. Quota mode: none. Oct 7 14:13:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0wzcp5pwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:13:19 storageqe-109 systemd[1]: tmp-libblockdev.0wzcp5pwmount_test.mount: Deactivated successfully. Oct 7 14:13:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 104945d9-c6a1-4da8-a285-9d09d4a640df. Oct 7 14:13:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:13:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ljs682tkmount_test with fs ext3 Oct 7 14:13:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:13:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 076e5eff-ee3d-48d5-bca1-1ab923f3152c r/w with ordered data mode. Quota mode: none. Oct 7 14:13:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ljs682tkmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:13:34 storageqe-109 systemd[1]: tmp-libblockdev.ljs682tkmount_test.mount: Deactivated successfully. Oct 7 14:13:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 076e5eff-ee3d-48d5-bca1-1ab923f3152c. Oct 7 14:13:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:13:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wgjhixalmount_test with fs ext2 Oct 7 14:13:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:13:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0c1ca918-c80d-4762-a6d4-eed839b00c41 r/w without journal. Quota mode: none. Oct 7 14:13:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wgjhixalmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ Oct 7 14:13:49 storageqe-109 systemd[1]: tmp-libblockdev.wgjhixalmount_test.mount: Deactivated successfully. Oct 7 14:13:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0c1ca918-c80d-4762-a6d4-eed839b00c41. Oct 7 14:13:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:13:49 storageqe-109 INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:13:49 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:13:49 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:13:49 storageqe-109 stratisd[4947]: [2025-10-07T18:13:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:13:49 storageqe-109 stratisd[4947]: [2025-10-07T18:13:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksKillSlot /dev/mapper/npo2linear 0 -q Oct 7 14:13:59 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 0 -q Oct 7 14:13:59 storageqe-109 stratisd[4947]: [2025-10-07T18:13:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:13:59 storageqe-109 stratisd[4947]: [2025-10-07T18:13:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:14:09 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' luksFormat /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:14:19 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '128' luksFormat /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:14:19 storageqe-109 stratisd[4947]: [2025-10-07T18:14:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:14:19 storageqe-109 stratisd[4947]: [2025-10-07T18:14:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:14:29 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:14:29 storageqe-109 stratisd[4947]: [2025-10-07T18:14:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:14:29 storageqe-109 stratisd[4947]: [2025-10-07T18:14:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:14:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.cu_81624mount_test with fs xfs Oct 7 14:14:49 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 61c35cf8-c7b3-4af6-937e-0852c57b2c2c Oct 7 14:14:49 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:14:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cu_81624mount_test with fs xfs Oct 7 14:14:54 storageqe-109 systemd[1]: tmp-libblockdev.cu_81624mount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:14:54 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 61c35cf8-c7b3-4af6-937e-0852c57b2c2c Oct 7 14:14:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:14:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wofk4djwmount_test with fs ext4 Oct 7 14:15:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6af4aa6b-e624-4090-b836-1b12605dbdbe r/w with ordered data mode. Quota mode: none. Oct 7 14:15:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wofk4djwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:15:09 storageqe-109 systemd[1]: tmp-libblockdev.wofk4djwmount_test.mount: Deactivated successfully. Oct 7 14:15:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6af4aa6b-e624-4090-b836-1b12605dbdbe. Oct 7 14:15:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:15:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ktomtiztmount_test with fs ext3 Oct 7 14:15:19 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:15:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1abfabc9-19df-46c8-870e-9ab9d05d60f7 r/w with ordered data mode. Quota mode: none. Oct 7 14:15:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ktomtiztmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:15:24 storageqe-109 systemd[1]: tmp-libblockdev.ktomtiztmount_test.mount: Deactivated successfully. Oct 7 14:15:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1abfabc9-19df-46c8-870e-9ab9d05d60f7. Oct 7 14:15:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:15:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ra26vaxpmount_test with fs ext2 Oct 7 14:15:34 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:15:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4a8c5b13-5a71-4de3-b72a-f5af3efc4190 r/w without journal. Quota mode: none. Oct 7 14:15:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ra26vaxpmount_test with fs ext2 Oct 7 14:15:39 storageqe-109 systemd[1]: tmp-libblockdev.ra26vaxpmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:15:39 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4a8c5b13-5a71-4de3-b72a-f5af3efc4190. Oct 7 14:15:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:15:39 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:15:39 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:15:39 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:15:39 storageqe-109 stratisd[4947]: [2025-10-07T18:15:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:15:39 storageqe-109 stratisd[4947]: [2025-10-07T18:15:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:15:49 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:15:49 storageqe-109 stratisd[4947]: [2025-10-07T18:15:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:15:49 storageqe-109 stratisd[4947]: [2025-10-07T18:15:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/CcNRVLSvHQ -q Oct 7 14:15:59 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/CcNRVLSvHQ -q Oct 7 14:16:00 storageqe-109 stratisd[4947]: [2025-10-07T18:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:16:00 storageqe-109 stratisd[4947]: [2025-10-07T18:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/CcNRVLSvHQ dummy -q Oct 7 14:16:10 storageqe-109 journal: cryptsetup open /dev/mapper/CcNRVLSvHQ dummy -q Oct 7 14:16:10 storageqe-109 stratisd[4947]: [2025-10-07T18:16:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:16:10 storageqe-109 stratisd[4947]: [2025-10-07T18:16:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 7 14:16:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.5z5djdzvmount_test with fs xfs Oct 7 14:16:30 storageqe-109 kernel: XFS (dm-5): Mounting V5 Filesystem 09fad176-bd44-4473-a557-d848cab49dc5 Oct 7 14:16:30 storageqe-109 kernel: XFS (dm-5): Ending clean mount Oct 7 14:16:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5z5djdzvmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 7 14:16:35 storageqe-109 systemd[1]: tmp-libblockdev.5z5djdzvmount_test.mount: Deactivated successfully. Oct 7 14:16:35 storageqe-109 kernel: XFS (dm-5): Unmounting Filesystem 09fad176-bd44-4473-a557-d848cab49dc5 Oct 7 14:16:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs xfs in remove_crypt Oct 7 14:16:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.el39vv3_mount_test with fs ext4 Oct 7 14:16:45 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 480b584b-caad-4f0f-b8cf-47426a4cd58a r/w with ordered data mode. Quota mode: none. Oct 7 14:16:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.el39vv3_mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 7 14:16:50 storageqe-109 systemd[1]: tmp-libblockdev.el39vv3_mount_test.mount: Deactivated successfully. Oct 7 14:16:50 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 480b584b-caad-4f0f-b8cf-47426a4cd58a. Oct 7 14:16:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext4 in remove_crypt Oct 7 14:16:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._klq7o0tmount_test with fs ext3 Oct 7 14:17:00 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext3 file system using the ext4 subsystem Oct 7 14:17:00 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 605a0092-d9d7-4f06-8f7f-e16f76c4eafa r/w with ordered data mode. Quota mode: none. Oct 7 14:17:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev._klq7o0tmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 7 14:17:06 storageqe-109 systemd[1]: tmp-libblockdev._klq7o0tmount_test.mount: Deactivated successfully. Oct 7 14:17:06 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 605a0092-d9d7-4f06-8f7f-e16f76c4eafa. Oct 7 14:17:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext3 in remove_crypt Oct 7 14:17:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uoa_7q5_mount_test with fs ext2 Oct 7 14:17:16 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext2 file system using the ext4 subsystem Oct 7 14:17:16 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 5e91b62d-d4f6-496a-834a-62cc6dd67908 r/w without journal. Quota mode: none. Oct 7 14:17:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uoa_7q5_mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt INFO: remove crypt device dummy INFO: finishe the remove crypt device dummy INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:17:21 storageqe-109 systemd[1]: tmp-libblockdev.uoa_7q5_mount_test.mount: Deactivated successfully. Oct 7 14:17:21 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 5e91b62d-d4f6-496a-834a-62cc6dd67908. Oct 7 14:17:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/dummy and fs ext2 in remove_crypt Oct 7 14:17:21 storageqe-109 INFO: remove crypt device dummy Oct 7 14:17:21 storageqe-109 INFO: finishe the remove crypt device dummy Oct 7 14:17:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.xej0n5jsmount_test with fs xfs Oct 7 14:17:32 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f72c94f4-9725-415a-b5c7-5aea96c0c5f2 Oct 7 14:17:32 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:17:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xej0n5jsmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:17:36 storageqe-109 systemd[1]: tmp-libblockdev.xej0n5jsmount_test.mount: Deactivated successfully. Oct 7 14:17:36 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f72c94f4-9725-415a-b5c7-5aea96c0c5f2 Oct 7 14:17:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:17:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jzfu20prmount_test with fs ext4 Oct 7 14:17:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f1788a51-15db-4995-9e65-ba9d06dd6e57 r/w with ordered data mode. Quota mode: none. Oct 7 14:17:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jzfu20prmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:17:51 storageqe-109 systemd[1]: tmp-libblockdev.jzfu20prmount_test.mount: Deactivated successfully. Oct 7 14:17:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f1788a51-15db-4995-9e65-ba9d06dd6e57. Oct 7 14:17:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:17:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.l6wtu6ggmount_test with fs ext3 Oct 7 14:18:01 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:18:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 40ab78fc-8e04-48ec-ac3b-4e5dd9ca812c r/w with ordered data mode. Quota mode: none. Oct 7 14:18:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l6wtu6ggmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:18:06 storageqe-109 systemd[1]: tmp-libblockdev.l6wtu6ggmount_test.mount: Deactivated successfully. Oct 7 14:18:06 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 40ab78fc-8e04-48ec-ac3b-4e5dd9ca812c. Oct 7 14:18:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:18:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nz6zqjq3mount_test with fs ext2 Oct 7 14:18:16 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:18:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 85a57a2a-0553-479f-9c2a-09d0f9cf784c r/w without journal. Quota mode: none. Oct 7 14:18:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nz6zqjq3mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:18:21 storageqe-109 systemd[1]: tmp-libblockdev.nz6zqjq3mount_test.mount: Deactivated successfully. Oct 7 14:18:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 85a57a2a-0553-479f-9c2a-09d0f9cf784c. Oct 7 14:18:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:18:21 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:18:21 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:18:21 storageqe-109 stratisd[4947]: [2025-10-07T18:18:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:18:21 storageqe-109 stratisd[4947]: [2025-10-07T18:18:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:18:21 storageqe-109 stratisd[4947]: [2025-10-07T18:18:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:18:21 storageqe-109 stratisd[4947]: [2025-10-07T18:18:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:18:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.hmdaiof8mount_test with fs xfs Oct 7 14:18:32 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem e7baec97-4636-40b3-addb-1e1a0822ce7c Oct 7 14:18:32 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:18:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hmdaiof8mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:18:36 storageqe-109 systemd[1]: tmp-libblockdev.hmdaiof8mount_test.mount: Deactivated successfully. Oct 7 14:18:36 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem e7baec97-4636-40b3-addb-1e1a0822ce7c Oct 7 14:18:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:18:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.137zxfm0mount_test with fs ext4 Oct 7 14:18:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0430856b-3552-4c9a-9ae8-a090b7de0228 r/w with ordered data mode. Quota mode: none. Oct 7 14:18:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.137zxfm0mount_test with fs ext4 Oct 7 14:18:51 storageqe-109 systemd[1]: tmp-libblockdev.137zxfm0mount_test.mount: Deactivated successfully. Oct 7 14:18:51 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0430856b-3552-4c9a-9ae8-a090b7de0228. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:18:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:18:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:19:01 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:19:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1c24a77c-f9d1-4ebb-919c-2bf4c8fc83cf r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev._0g09i0_mount_test with fs ext3 Oct 7 14:19:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev._0g09i0_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:19:06 storageqe-109 systemd[1]: tmp-libblockdev._0g09i0_mount_test.mount: Deactivated successfully. Oct 7 14:19:06 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1c24a77c-f9d1-4ebb-919c-2bf4c8fc83cf. Oct 7 14:19:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:19:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bqu9gsjqmount_test with fs ext2 Oct 7 14:19:16 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:19:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 16e69998-0422-4840-ac7c-a593b0f4b0f0 r/w without journal. Quota mode: none. Oct 7 14:19:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bqu9gsjqmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:19:21 storageqe-109 systemd[1]: tmp-libblockdev.bqu9gsjqmount_test.mount: Deactivated successfully. Oct 7 14:19:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 16e69998-0422-4840-ac7c-a593b0f4b0f0. Oct 7 14:19:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:19:21 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:19:21 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:19:21 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:19:21 storageqe-109 stratisd[4947]: [2025-10-07T18:19:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:19:21 storageqe-109 stratisd[4947]: [2025-10-07T18:19:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:19:31 storageqe-109 stratisd[4947]: [2025-10-07T18:19:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:19:31 storageqe-109 stratisd[4947]: [2025-10-07T18:19:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:19:31 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --key-file '-' open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:19:42 storageqe-109 journal: cryptsetup --key-file '-' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --pbkdf 'pbkdf2' --key-file '-' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileNGT -q Oct 7 14:19:52 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '-' --pbkdf-force-iterations '1000' luksAddKey /dev/mapper/npo2linear /tmp/testfileNGT -q Oct 7 14:19:52 storageqe-109 stratisd[4947]: [2025-10-07T18:19:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:19:52 storageqe-109 stratisd[4947]: [2025-10-07T18:19:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileNGT' open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:20:02 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileNGT' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:20:12 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear /tmp/testfileOax -q Oct 7 14:20:12 storageqe-109 stratisd[4947]: [2025-10-07T18:20:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:20:12 storageqe-109 stratisd[4947]: [2025-10-07T18:20:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:20:22 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear /tmp/testfileNGT -q Oct 7 14:20:32 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear /tmp/testfileNGT -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '4' --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear /tmp/testfileNGT -q Oct 7 14:20:42 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '4' --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear /tmp/testfileNGT -q Oct 7 14:20:42 storageqe-109 stratisd[4947]: [2025-10-07T18:20:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:20:42 storageqe-109 stratisd[4947]: [2025-10-07T18:20:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileNGT' --key-slot '4' open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:20:52 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileNGT' --key-slot '4' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:21:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear -q Oct 7 14:21:12 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear -q Oct 7 14:21:12 storageqe-109 stratisd[4947]: [2025-10-07T18:21:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:21:12 storageqe-109 stratisd[4947]: [2025-10-07T18:21:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:21:22 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-slot '0' open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:21:32 storageqe-109 journal: cryptsetup --key-slot '0' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --key-slot '1' open /dev/mapper/npo2linear --test-passphrase -q Oct 7 14:21:42 storageqe-109 stratisd[4947]: [2025-10-07T18:21:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:21:42 storageqe-109 stratisd[4947]: [2025-10-07T18:21:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:21:42 storageqe-109 journal: cryptsetup --key-slot '1' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:21:52 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:22:02 storageqe-109 stratisd[4947]: [2025-10-07T18:22:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:22:02 storageqe-109 stratisd[4947]: [2025-10-07T18:22:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:22:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:22:12 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:22:22 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:22:32 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:22:32 storageqe-109 stratisd[4947]: [2025-10-07T18:22:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:22:32 storageqe-109 stratisd[4947]: [2025-10-07T18:22:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:22:42 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:22:52 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:23:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:23:12 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileOax cryptsetup --keyfile-size '1' luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:23:22 storageqe-109 journal: cryptsetup --keyfile-size '1' luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileNGT cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:23:32 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:23:42 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear /tmp/testfileNGT -q Oct 7 14:23:52 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear /tmp/testfileNGT -q Oct 7 14:23:52 storageqe-109 stratisd[4947]: [2025-10-07T18:23:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:23:52 storageqe-109 stratisd[4947]: [2025-10-07T18:23:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:24:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 Oct 7 14:24:13 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 Oct 7 14:24:23 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 2 cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q Oct 7 14:24:33 storageqe-109 journal: cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q Oct 7 14:24:43 storageqe-109 journal: cryptsetup --key-file '-' luksKillSlot /dev/mapper/npo2linear 2 -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:24:53 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear 2 -q Oct 7 14:25:03 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 2 -q Oct 7 14:25:03 storageqe-109 stratisd[4947]: [2025-10-07T18:25:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:25:03 storageqe-109 stratisd[4947]: [2025-10-07T18:25:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:25:13 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksRemoveKey /dev/mapper/npo2linear -q Oct 7 14:25:23 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q Oct 7 14:25:23 storageqe-109 stratisd[4947]: [2025-10-07T18:25:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:25:23 storageqe-109 stratisd[4947]: [2025-10-07T18:25:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:25:33 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 7 14:25:43 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear 1 -q Oct 7 14:25:43 storageqe-109 stratisd[4947]: [2025-10-07T18:25:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:25:43 storageqe-109 stratisd[4947]: [2025-10-07T18:25:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:25:53 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear -q Oct 7 14:26:03 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '3' luksFormat /dev/mapper/npo2linear -q Oct 7 14:26:03 storageqe-109 stratisd[4947]: [2025-10-07T18:26:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:26:03 storageqe-109 stratisd[4947]: [2025-10-07T18:26:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:26:13 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:26:13 storageqe-109 stratisd[4947]: [2025-10-07T18:26:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:26:13 storageqe-109 stratisd[4947]: [2025-10-07T18:26:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '16000' resize CcNRVLSvHQ -q Oct 7 14:26:23 storageqe-109 journal: cryptsetup --size '16000' resize CcNRVLSvHQ -q cryptsetup --key-description 'keydesc2' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 14:26:33 storageqe-109 journal: cryptsetup --key-description 'keydesc2' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 14:26:33 storageqe-109 stratisd[4947]: [2025-10-07T18:26:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:26:33 storageqe-109 stratisd[4947]: [2025-10-07T18:26:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '80' resize CcNRVLSvHQ -q Oct 7 14:26:43 storageqe-109 journal: cryptsetup --size '80' resize CcNRVLSvHQ -q Oct 7 14:26:43 storageqe-109 stratisd[4947]: [2025-10-07T18:26:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:26:43 storageqe-109 stratisd[4947]: [2025-10-07T18:26:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:26:43 storageqe-109 stratisd[4947]: [2025-10-07T18:26:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:26:43 storageqe-109 stratisd[4947]: [2025-10-07T18:26:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:26:53 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q Oct 7 14:26:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 14:26:53 storageqe-109 dnf[1467642]: Updating Subscription Management repositories. Oct 7 14:26:53 storageqe-109 dnf[1467642]: Unable to read consumer identity Oct 7 14:26:53 storageqe-109 dnf[1467642]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 14:26:53 storageqe-109 dnf[1467642]: Metadata cache refreshed recently. Oct 7 14:26:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 14:26:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. cryptsetup --size '1600000' resize CcNRVLSvHQ -q --token-only Oct 7 14:27:03 storageqe-109 journal: cryptsetup --size '1600000' resize CcNRVLSvHQ -q --token-only cryptsetup status CcNRVLSvHQ -q Oct 7 14:27:13 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup --size '1600000' resize CcNRVLSvHQ -q Oct 7 14:27:23 storageqe-109 journal: cryptsetup --size '1600000' resize CcNRVLSvHQ -q Oct 7 14:27:23 storageqe-109 stratisd[4947]: [2025-10-07T18:27:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:27:23 storageqe-109 stratisd[4947]: [2025-10-07T18:27:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:27:33 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup --device-size '81920' resize CcNRVLSvHQ -q Oct 7 14:27:43 storageqe-109 journal: cryptsetup --device-size '81920' resize CcNRVLSvHQ -q Oct 7 14:27:43 storageqe-109 stratisd[4947]: [2025-10-07T18:27:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:27:43 storageqe-109 stratisd[4947]: [2025-10-07T18:27:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:27:43 storageqe-109 stratisd[4947]: [2025-10-07T18:27:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:27:43 storageqe-109 stratisd[4947]: [2025-10-07T18:27:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:27:53 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup --device-size '800M' resize CcNRVLSvHQ -q Oct 7 14:28:03 storageqe-109 journal: cryptsetup --device-size '800M' resize CcNRVLSvHQ -q Oct 7 14:28:03 storageqe-109 stratisd[4947]: [2025-10-07T18:28:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:28:03 storageqe-109 stratisd[4947]: [2025-10-07T18:28:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:28:03 storageqe-109 stratisd[4947]: [2025-10-07T18:28:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:28:03 storageqe-109 stratisd[4947]: [2025-10-07T18:28:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:28:13 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup --device-size '512k' --size '1024' resize CcNRVLSvHQ -q Oct 7 14:28:23 storageqe-109 journal: cryptsetup --device-size '512k' --size '1024' resize CcNRVLSvHQ -q cryptsetup --device-size '4097' resize CcNRVLSvHQ -q Oct 7 14:28:33 storageqe-109 journal: cryptsetup --device-size '4097' resize CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 14:28:43 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:28:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.hqkmnffqmount_test with fs xfs Oct 7 14:29:04 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 16ac78d7-e7a7-4314-913d-5c68ecf1b901 Oct 7 14:29:04 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:29:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hqkmnffqmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:29:08 storageqe-109 systemd[1]: tmp-libblockdev.hqkmnffqmount_test.mount: Deactivated successfully. Oct 7 14:29:08 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 16ac78d7-e7a7-4314-913d-5c68ecf1b901 Oct 7 14:29:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:29:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.u5mjn8ihmount_test with fs ext4 Oct 7 14:29:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 47cc5006-bf10-4ea6-b995-74eb0b89a752 r/w with ordered data mode. Quota mode: none. Oct 7 14:29:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u5mjn8ihmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:29:23 storageqe-109 systemd[1]: tmp-libblockdev.u5mjn8ihmount_test.mount: Deactivated successfully. Oct 7 14:29:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 47cc5006-bf10-4ea6-b995-74eb0b89a752. Oct 7 14:29:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:29:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vtyuvswpmount_test with fs ext3 Oct 7 14:29:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:29:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2dd0afe2-7bb8-43ad-ba18-382a9c4794b1 r/w with ordered data mode. Quota mode: none. Oct 7 14:29:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vtyuvswpmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:29:38 storageqe-109 systemd[1]: tmp-libblockdev.vtyuvswpmount_test.mount: Deactivated successfully. Oct 7 14:29:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2dd0afe2-7bb8-43ad-ba18-382a9c4794b1. Oct 7 14:29:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:29:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cp67y54kmount_test with fs ext2 Oct 7 14:29:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:29:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a8bf9682-64b2-45cd-8c0c-26cd0fd2cfd8 r/w without journal. Quota mode: none. Oct 7 14:29:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cp67y54kmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q --disable-keyring Oct 7 14:29:53 storageqe-109 systemd[1]: tmp-libblockdev.cp67y54kmount_test.mount: Deactivated successfully. Oct 7 14:29:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a8bf9682-64b2-45cd-8c0c-26cd0fd2cfd8. Oct 7 14:29:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:29:53 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:29:53 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:29:53 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q --disable-keyring Oct 7 14:29:53 storageqe-109 stratisd[4947]: [2025-10-07T18:29:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:29:53 storageqe-109 stratisd[4947]: [2025-10-07T18:29:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '1600000' resize CcNRVLSvHQ -q Oct 7 14:30:03 storageqe-109 journal: cryptsetup --size '1600000' resize CcNRVLSvHQ -q Oct 7 14:30:03 storageqe-109 stratisd[4947]: [2025-10-07T18:30:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:30:03 storageqe-109 stratisd[4947]: [2025-10-07T18:30:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:30:03 storageqe-109 stratisd[4947]: [2025-10-07T18:30:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:30:03 storageqe-109 stratisd[4947]: [2025-10-07T18:30:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:30:13 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:30:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.7v2upt18mount_test with fs xfs Oct 7 14:30:33 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 91c4cef0-18df-43e9-8c3e-be1181c9cc81 Oct 7 14:30:33 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:30:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7v2upt18mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:30:38 storageqe-109 systemd[1]: tmp-libblockdev.7v2upt18mount_test.mount: Deactivated successfully. Oct 7 14:30:38 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 91c4cef0-18df-43e9-8c3e-be1181c9cc81 Oct 7 14:30:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:30:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dst2j4bkmount_test with fs ext4 Oct 7 14:30:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem be1d6d3c-6181-46fc-85f7-fecc2369cf43 r/w with ordered data mode. Quota mode: none. Oct 7 14:30:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dst2j4bkmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:30:53 storageqe-109 systemd[1]: tmp-libblockdev.dst2j4bkmount_test.mount: Deactivated successfully. Oct 7 14:30:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem be1d6d3c-6181-46fc-85f7-fecc2369cf43. Oct 7 14:30:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:30:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1ahm0ewimount_test with fs ext3 Oct 7 14:31:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:31:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5902800b-cbae-4251-942c-56139c8d6b5c r/w with ordered data mode. Quota mode: none. Oct 7 14:31:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1ahm0ewimount_test with fs ext3 Oct 7 14:31:08 storageqe-109 systemd[1]: tmp-libblockdev.1ahm0ewimount_test.mount: Deactivated successfully. Oct 7 14:31:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5902800b-cbae-4251-942c-56139c8d6b5c. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:31:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:31:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.efzvmzotmount_test with fs ext2 Oct 7 14:31:18 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:31:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3dd75dcc-9b29-493e-8e9b-a93e110c1c63 r/w without journal. Quota mode: none. Oct 7 14:31:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.efzvmzotmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ Oct 7 14:31:23 storageqe-109 systemd[1]: tmp-libblockdev.efzvmzotmount_test.mount: Deactivated successfully. Oct 7 14:31:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3dd75dcc-9b29-493e-8e9b-a93e110c1c63. Oct 7 14:31:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:31:23 storageqe-109 INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:31:23 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:31:23 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:31:23 storageqe-109 stratisd[4947]: [2025-10-07T18:31:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:31:23 storageqe-109 stratisd[4947]: [2025-10-07T18:31:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '1600000' resize CcNRVLSvHQ -q --disable-keyring Oct 7 14:31:33 storageqe-109 journal: cryptsetup --size '1600000' resize CcNRVLSvHQ -q --disable-keyring INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:31:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.ba4uexowmount_test with fs xfs Oct 7 14:31:53 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem c6ec80e1-2f89-4c29-8d03-6e853d5e9534 Oct 7 14:31:53 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:31:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ba4uexowmount_test with fs xfs Oct 7 14:31:58 storageqe-109 systemd[1]: tmp-libblockdev.ba4uexowmount_test.mount: Deactivated successfully. Oct 7 14:31:58 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem c6ec80e1-2f89-4c29-8d03-6e853d5e9534 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:31:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:31:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4tqxnwj8mount_test with fs ext4 Oct 7 14:32:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 309a3d49-717e-4777-b967-ce6cb293be60 r/w with ordered data mode. Quota mode: none. Oct 7 14:32:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4tqxnwj8mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:32:13 storageqe-109 systemd[1]: tmp-libblockdev.4tqxnwj8mount_test.mount: Deactivated successfully. Oct 7 14:32:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 309a3d49-717e-4777-b967-ce6cb293be60. Oct 7 14:32:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:32:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dbdsj3e3mount_test with fs ext3 Oct 7 14:32:23 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:32:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6a0d0a31-174d-4dac-9c44-602e388c6424 r/w with ordered data mode. Quota mode: none. Oct 7 14:32:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dbdsj3e3mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:32:28 storageqe-109 systemd[1]: tmp-libblockdev.dbdsj3e3mount_test.mount: Deactivated successfully. Oct 7 14:32:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6a0d0a31-174d-4dac-9c44-602e388c6424. Oct 7 14:32:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:32:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nyo2_py6mount_test with fs ext2 Oct 7 14:32:38 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:32:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1f01b77c-c148-441c-b1a9-5d7239bd5ecc r/w without journal. Quota mode: none. Oct 7 14:32:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nyo2_py6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:32:43 storageqe-109 systemd[1]: tmp-libblockdev.nyo2_py6mount_test.mount: Deactivated successfully. Oct 7 14:32:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1f01b77c-c148-441c-b1a9-5d7239bd5ecc. Oct 7 14:32:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:32:43 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:32:43 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 14:32:43 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --sector-size '4096' luksFormat /dev/mapper/npo2linear -q Oct 7 14:32:43 storageqe-109 stratisd[4947]: [2025-10-07T18:32:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:32:43 storageqe-109 stratisd[4947]: [2025-10-07T18:32:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:32:53 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:32:53 storageqe-109 stratisd[4947]: [2025-10-07T18:32:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:32:53 storageqe-109 stratisd[4947]: [2025-10-07T18:32:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --device-size '800M' resize CcNRVLSvHQ -q Oct 7 14:33:03 storageqe-109 journal: cryptsetup --device-size '800M' resize CcNRVLSvHQ -q Oct 7 14:33:03 storageqe-109 stratisd[4947]: [2025-10-07T18:33:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:33:03 storageqe-109 stratisd[4947]: [2025-10-07T18:33:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:33:03 storageqe-109 stratisd[4947]: [2025-10-07T18:33:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:33:03 storageqe-109 stratisd[4947]: [2025-10-07T18:33:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:33:13 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup --device-size '2049s' resize CcNRVLSvHQ -q Oct 7 14:33:23 storageqe-109 journal: cryptsetup --device-size '2049s' resize CcNRVLSvHQ -q Oct 7 14:33:23 storageqe-109 stratisd[4947]: [2025-10-07T18:33:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:33:23 storageqe-109 stratisd[4947]: [2025-10-07T18:33:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '2049' resize CcNRVLSvHQ -q Oct 7 14:33:33 storageqe-109 journal: cryptsetup --size '2049' resize CcNRVLSvHQ -q Oct 7 14:33:33 storageqe-109 stratisd[4947]: [2025-10-07T18:33:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:33:33 storageqe-109 stratisd[4947]: [2025-10-07T18:33:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:33:43 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup open /dev/mapper/npo2linear dummy2 -q Oct 7 14:33:53 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear dummy2 -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:34:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.zbmbqfi_mount_test with fs xfs Oct 7 14:34:13 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 906af806-23ab-40c3-9ee0-546e417d89b5 Oct 7 14:34:13 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:34:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zbmbqfi_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:34:18 storageqe-109 systemd[1]: tmp-libblockdev.zbmbqfi_mount_test.mount: Deactivated successfully. Oct 7 14:34:18 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 906af806-23ab-40c3-9ee0-546e417d89b5 Oct 7 14:34:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:34:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5uci9kifmount_test with fs ext4 Oct 7 14:34:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b7157e3e-98a6-45ad-9abe-895879f53f61 r/w with ordered data mode. Quota mode: none. Oct 7 14:34:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5uci9kifmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:34:33 storageqe-109 systemd[1]: tmp-libblockdev.5uci9kifmount_test.mount: Deactivated successfully. Oct 7 14:34:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b7157e3e-98a6-45ad-9abe-895879f53f61. Oct 7 14:34:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:34:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._j7xwdvrmount_test with fs ext3 Oct 7 14:34:43 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:34:43 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b361811c-a82b-461f-8aec-e861498acf43 r/w with ordered data mode. Quota mode: none. Oct 7 14:34:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev._j7xwdvrmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:34:48 storageqe-109 systemd[1]: tmp-libblockdev._j7xwdvrmount_test.mount: Deactivated successfully. Oct 7 14:34:48 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b361811c-a82b-461f-8aec-e861498acf43. Oct 7 14:34:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:34:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.msld2o7smount_test with fs ext2 Oct 7 14:34:58 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:34:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 069e460b-6b74-4e97-9d18-0209b530d92f r/w without journal. Quota mode: none. Oct 7 14:34:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.msld2o7smount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ Oct 7 14:35:03 storageqe-109 systemd[1]: tmp-libblockdev.msld2o7smount_test.mount: Deactivated successfully. Oct 7 14:35:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 069e460b-6b74-4e97-9d18-0209b530d92f. Oct 7 14:35:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:35:03 storageqe-109 INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:35:03 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:35:03 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 14:35:03 storageqe-109 stratisd[4947]: [2025-10-07T18:35:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:35:03 storageqe-109 stratisd[4947]: [2025-10-07T18:35:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:35:13 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:35:13 storageqe-109 stratisd[4947]: [2025-10-07T18:35:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:35:13 storageqe-109 stratisd[4947]: [2025-10-07T18:35:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:35:23 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:35:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.nnr1fw6umount_test with fs xfs Oct 7 14:35:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem aa0633f5-a6ff-4478-8509-775a3b82e134 Oct 7 14:35:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:35:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nnr1fw6umount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:35:48 storageqe-109 systemd[1]: tmp-libblockdev.nnr1fw6umount_test.mount: Deactivated successfully. Oct 7 14:35:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem aa0633f5-a6ff-4478-8509-775a3b82e134 Oct 7 14:35:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:35:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lqwn27qqmount_test with fs ext4 Oct 7 14:35:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 28d0707c-f0e2-4452-aa30-a46cc1c37dfe r/w with ordered data mode. Quota mode: none. Oct 7 14:35:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lqwn27qqmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:36:03 storageqe-109 systemd[1]: tmp-libblockdev.lqwn27qqmount_test.mount: Deactivated successfully. Oct 7 14:36:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 28d0707c-f0e2-4452-aa30-a46cc1c37dfe. Oct 7 14:36:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:36:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4_te7ujpmount_test with fs ext3 Oct 7 14:36:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:36:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 90b280d0-57e0-4b90-9279-afe4f1d5a950 r/w with ordered data mode. Quota mode: none. Oct 7 14:36:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4_te7ujpmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:36:18 storageqe-109 systemd[1]: tmp-libblockdev.4_te7ujpmount_test.mount: Deactivated successfully. Oct 7 14:36:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 90b280d0-57e0-4b90-9279-afe4f1d5a950. Oct 7 14:36:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:36:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tclqkdr8mount_test with fs ext2 Oct 7 14:36:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:36:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 54aafab7-3225-4c28-aceb-2956a0b8d8b2 r/w without journal. Quota mode: none. Oct 7 14:36:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tclqkdr8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ Oct 7 14:36:33 storageqe-109 systemd[1]: tmp-libblockdev.tclqkdr8mount_test.mount: Deactivated successfully. Oct 7 14:36:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 54aafab7-3225-4c28-aceb-2956a0b8d8b2. Oct 7 14:36:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:36:33 storageqe-109 INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:36:33 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:36:33 storageqe-109 kernel: device-mapper: table: 253:4: adding target device dm-3 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=4096, alignment_offset=0, start=1024 Oct 7 14:36:33 storageqe-109 kernel: device-mapper: table: 253:4: start=2 not aligned to h/w logical block size 4096 of dm-3 Oct 7 14:36:33 storageqe-109 kernel: device-mapper: core: Cannot calculate initial queue limits Oct 7 14:36:33 storageqe-109 kernel: device-mapper: ioctl: unable to set up device queue for new table. Oct 7 14:36:33 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:36:33 storageqe-109 stratisd[4947]: [2025-10-07T18:36:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:36:33 storageqe-109 stratisd[4947]: [2025-10-07T18:36:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:36:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '0' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:36:53 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '0' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '-1' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:37:03 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '-1' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '14' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:37:13 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '14' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '1' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:37:23 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '1' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '-1' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:37:33 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '-1' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:37:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:37:43 storageqe-109 stratisd[4947]: [2025-10-07T18:37:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:37:43 storageqe-109 stratisd[4947]: [2025-10-07T18:37:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:37:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.6450iqhgmount_test with fs xfs Oct 7 14:38:04 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 4b220f82-e634-4d7f-bf7e-31a34d64a51b Oct 7 14:38:04 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:38:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6450iqhgmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:38:08 storageqe-109 systemd[1]: tmp-libblockdev.6450iqhgmount_test.mount: Deactivated successfully. Oct 7 14:38:08 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 4b220f82-e634-4d7f-bf7e-31a34d64a51b Oct 7 14:38:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:38:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ilzyr50omount_test with fs ext4 Oct 7 14:38:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3bd8a043-4fa7-40f7-a0a8-fbd4a668c2cb r/w with ordered data mode. Quota mode: none. Oct 7 14:38:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ilzyr50omount_test with fs ext4 Oct 7 14:38:23 storageqe-109 systemd[1]: tmp-libblockdev.ilzyr50omount_test.mount: Deactivated successfully. Oct 7 14:38:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3bd8a043-4fa7-40f7-a0a8-fbd4a668c2cb. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:38:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:38:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:38:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:38:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8b69e0a1-f0a4-4bc4-bcbe-cf05c693cb39 r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.lo778ckfmount_test with fs ext3 Oct 7 14:38:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lo778ckfmount_test with fs ext3 Oct 7 14:38:38 storageqe-109 systemd[1]: tmp-libblockdev.lo778ckfmount_test.mount: Deactivated successfully. Oct 7 14:38:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8b69e0a1-f0a4-4bc4-bcbe-cf05c693cb39. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:38:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:38:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j1ady7eqmount_test with fs ext2 Oct 7 14:38:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:38:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9306c47b-e83d-4c65-bc52-e3533af92775 r/w without journal. Quota mode: none. Oct 7 14:38:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j1ady7eqmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:38:53 storageqe-109 systemd[1]: tmp-libblockdev.j1ady7eqmount_test.mount: Deactivated successfully. Oct 7 14:38:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9306c47b-e83d-4c65-bc52-e3533af92775. Oct 7 14:38:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:38:53 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:38:53 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:38:53 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '14' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:39:03 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '14' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '-1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:39:13 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '-1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:39:23 storageqe-109 journal: cryptsetup luksRemoveKey /dev/mapper/npo2linear -q /tmp/testfileNGT cryptsetup --key-file '/tmp/testfileOax' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:39:33 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '14' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:39:44 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '14' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:39:54 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:39:54 storageqe-109 stratisd[4947]: [2025-10-07T18:39:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:39:54 storageqe-109 stratisd[4947]: [2025-10-07T18:39:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileNGT' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q Oct 7 14:40:04 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileNGT' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksChangeKey /dev/mapper/npo2linear -q Oct 7 14:40:04 storageqe-109 stratisd[4947]: [2025-10-07T18:40:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:40:04 storageqe-109 stratisd[4947]: [2025-10-07T18:40:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --keyfile-size '11' luksRemoveKey /dev/mapper/npo2linear -q Oct 7 14:40:14 storageqe-109 journal: cryptsetup --keyfile-size '11' luksRemoveKey /dev/mapper/npo2linear -q cryptsetup --keyfile-size '12' luksRemoveKey /dev/mapper/npo2linear -q Oct 7 14:40:24 storageqe-109 journal: cryptsetup --keyfile-size '12' luksRemoveKey /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' --keyfile-offset '16' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:40:34 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyfile-size '13' --keyfile-offset '16' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:40:34 storageqe-109 stratisd[4947]: [2025-10-07T18:40:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:40:34 storageqe-109 stratisd[4947]: [2025-10-07T18:40:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '15' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:40:44 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '15' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '16' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:40:54 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --keyfile-size '13' --keyfile-offset '16' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:40:54 storageqe-109 stratisd[4947]: [2025-10-07T18:40:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:40:54 storageqe-109 stratisd[4947]: [2025-10-07T18:40:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:41:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev._dyj44gamount_test with fs xfs Oct 7 14:41:14 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem aafd324c-aa83-4dbb-8812-fa1ed9faaf4d Oct 7 14:41:14 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:41:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev._dyj44gamount_test with fs xfs Oct 7 14:41:19 storageqe-109 systemd[1]: tmp-libblockdev._dyj44gamount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:41:19 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem aafd324c-aa83-4dbb-8812-fa1ed9faaf4d Oct 7 14:41:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:41:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.856gz684mount_test with fs ext4 Oct 7 14:41:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 45babe85-c2e3-4b48-a1d6-2a855b5352dd r/w with ordered data mode. Quota mode: none. Oct 7 14:41:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.856gz684mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:41:34 storageqe-109 systemd[1]: tmp-libblockdev.856gz684mount_test.mount: Deactivated successfully. Oct 7 14:41:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 45babe85-c2e3-4b48-a1d6-2a855b5352dd. Oct 7 14:41:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:41:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fwp39vy7mount_test with fs ext3 Oct 7 14:41:44 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:41:44 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 12895e23-9fe7-4bda-92d7-75d5efdaee7c r/w with ordered data mode. Quota mode: none. Oct 7 14:41:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fwp39vy7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:41:49 storageqe-109 systemd[1]: tmp-libblockdev.fwp39vy7mount_test.mount: Deactivated successfully. Oct 7 14:41:49 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 12895e23-9fe7-4bda-92d7-75d5efdaee7c. Oct 7 14:41:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:41:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0nkxpoe2mount_test with fs ext2 Oct 7 14:41:59 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:41:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4b41e14c-4f10-4ca0-ae82-01e7e46c61e9 r/w without journal. Quota mode: none. Oct 7 14:41:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0nkxpoe2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:42:04 storageqe-109 systemd[1]: tmp-libblockdev.0nkxpoe2mount_test.mount: Deactivated successfully. Oct 7 14:42:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4b41e14c-4f10-4ca0-ae82-01e7e46c61e9. Oct 7 14:42:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:42:04 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:42:04 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileOax' --pbkdf-force-iterations '1000' --keyfile-size '13' --keyfile-offset '16' --new-keyfile-offset '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:42:04 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileOax' --pbkdf-force-iterations '1000' --keyfile-size '13' --keyfile-offset '16' --new-keyfile-offset '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:42:04 storageqe-109 stratisd[4947]: [2025-10-07T18:42:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:42:04 storageqe-109 stratisd[4947]: [2025-10-07T18:42:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileNGT' --keyfile-offset '11' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:42:14 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileNGT' --keyfile-offset '11' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-file '/tmp/testfileNGT' --keyfile-offset '1' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:42:24 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileNGT' --keyfile-offset '1' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:42:24 storageqe-109 stratisd[4947]: [2025-10-07T18:42:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:42:24 storageqe-109 stratisd[4947]: [2025-10-07T18:42:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:42:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.y_bfafy5mount_test with fs xfs Oct 7 14:42:44 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 1ba710ae-5412-4752-8af5-40ca8a8513a5 Oct 7 14:42:44 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:42:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y_bfafy5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:42:49 storageqe-109 systemd[1]: tmp-libblockdev.y_bfafy5mount_test.mount: Deactivated successfully. Oct 7 14:42:49 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 1ba710ae-5412-4752-8af5-40ca8a8513a5 Oct 7 14:42:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:42:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jiyi4hbkmount_test with fs ext4 Oct 7 14:42:59 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5f7b2710-aa5a-4094-a998-bd3153f2ed04 r/w with ordered data mode. Quota mode: none. Oct 7 14:42:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jiyi4hbkmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:43:04 storageqe-109 systemd[1]: tmp-libblockdev.jiyi4hbkmount_test.mount: Deactivated successfully. Oct 7 14:43:04 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5f7b2710-aa5a-4094-a998-bd3153f2ed04. Oct 7 14:43:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:43:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q2kc39f7mount_test with fs ext3 Oct 7 14:43:14 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:43:14 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4d4cb14b-320c-49d0-a076-e81a639c9140 r/w with ordered data mode. Quota mode: none. Oct 7 14:43:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q2kc39f7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:43:19 storageqe-109 systemd[1]: tmp-libblockdev.q2kc39f7mount_test.mount: Deactivated successfully. Oct 7 14:43:19 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4d4cb14b-320c-49d0-a076-e81a639c9140. Oct 7 14:43:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:43:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bnl8ix9cmount_test with fs ext2 Oct 7 14:43:29 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:43:29 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9d0babbd-0711-48d6-a3f2-b25982d0680f r/w without journal. Quota mode: none. Oct 7 14:43:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bnl8ix9cmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileNGT' --pbkdf-force-iterations '1000' --keyfile-offset '1' --new-keyfile-offset '0' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:43:34 storageqe-109 systemd[1]: tmp-libblockdev.bnl8ix9cmount_test.mount: Deactivated successfully. Oct 7 14:43:34 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9d0babbd-0711-48d6-a3f2-b25982d0680f. Oct 7 14:43:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:43:34 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:43:34 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:43:34 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfileNGT' --pbkdf-force-iterations '1000' --keyfile-offset '1' --new-keyfile-offset '0' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 14:43:34 storageqe-109 stratisd[4947]: [2025-10-07T18:43:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:43:34 storageqe-109 stratisd[4947]: [2025-10-07T18:43:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileNGT' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:43:44 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileNGT' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:43:44 storageqe-109 stratisd[4947]: [2025-10-07T18:43:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:43:44 storageqe-109 stratisd[4947]: [2025-10-07T18:43:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:43:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.fzhka9pdmount_test with fs xfs Oct 7 14:44:04 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 39911853-8f41-4432-ae03-a1b6c9029936 Oct 7 14:44:04 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:44:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fzhka9pdmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:44:09 storageqe-109 systemd[1]: tmp-libblockdev.fzhka9pdmount_test.mount: Deactivated successfully. Oct 7 14:44:09 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 39911853-8f41-4432-ae03-a1b6c9029936 Oct 7 14:44:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:44:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ii76n9svmount_test with fs ext4 Oct 7 14:44:19 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 75220a3f-f59a-4a1e-88aa-bc846db1fd02 r/w with ordered data mode. Quota mode: none. Oct 7 14:44:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ii76n9svmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:44:24 storageqe-109 systemd[1]: tmp-libblockdev.ii76n9svmount_test.mount: Deactivated successfully. Oct 7 14:44:24 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 75220a3f-f59a-4a1e-88aa-bc846db1fd02. Oct 7 14:44:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:44:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:44:34 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.37_5n1mtmount_test with fs ext3 Oct 7 14:44:34 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8f807714-3b84-4dae-bb56-378989661176 r/w with ordered data mode. Quota mode: none. Oct 7 14:44:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.37_5n1mtmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:44:39 storageqe-109 systemd[1]: tmp-libblockdev.37_5n1mtmount_test.mount: Deactivated successfully. Oct 7 14:44:39 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8f807714-3b84-4dae-bb56-378989661176. Oct 7 14:44:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:44:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jp3cme_pmount_test with fs ext2 Oct 7 14:44:49 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:44:49 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1994ce0e-4953-4a42-8094-a035d05ce172 r/w without journal. Quota mode: none. Oct 7 14:44:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jp3cme_pmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q Oct 7 14:44:54 storageqe-109 systemd[1]: tmp-libblockdev.jp3cme_pmount_test.mount: Deactivated successfully. Oct 7 14:44:54 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1994ce0e-4953-4a42-8094-a035d05ce172. Oct 7 14:44:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:44:54 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:44:54 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:44:54 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '1' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q Oct 7 14:45:04 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '1' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q Oct 7 14:45:14 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear /tmp/testheaderktf -q Oct 7 14:45:24 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear /tmp/testheaderktf -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' --sector-size '512' luksFormat /dev/mapper/npo2linear -q Oct 7 14:45:34 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' --sector-size '512' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderktf' open wrong_device CcNRVLSvHQ -q Oct 7 14:45:44 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' open wrong_device CcNRVLSvHQ -q cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:45:54 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:45:54 storageqe-109 stratisd[4947]: [2025-10-07T18:45:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:45:54 storageqe-109 stratisd[4947]: [2025-10-07T18:45:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --size '1600000' --header '/tmp/testheaderktf' resize CcNRVLSvHQ -q Oct 7 14:46:05 storageqe-109 journal: cryptsetup --size '1600000' --header '/tmp/testheaderktf' resize CcNRVLSvHQ -q Oct 7 14:46:05 storageqe-109 stratisd[4947]: [2025-10-07T18:46:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:46:05 storageqe-109 stratisd[4947]: [2025-10-07T18:46:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:46:05 storageqe-109 stratisd[4947]: [2025-10-07T18:46:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:46:05 storageqe-109 stratisd[4947]: [2025-10-07T18:46:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --header '/tmp/testheaderktf' status CcNRVLSvHQ -q Oct 7 14:46:15 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' status CcNRVLSvHQ -q cryptsetup --header '/tmp/testheaderktf' luksSuspend CcNRVLSvHQ -q Oct 7 14:46:25 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksSuspend CcNRVLSvHQ -q cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q Oct 7 14:46:35 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q cryptsetup --header '/tmp/testheaderktf' luksSuspend CcNRVLSvHQ -q Oct 7 14:46:45 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksSuspend CcNRVLSvHQ -q cryptsetup luksResume CcNRVLSvHQ -q Oct 7 14:46:55 storageqe-109 journal: cryptsetup luksResume CcNRVLSvHQ -q cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q Oct 7 14:47:05 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:47:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.a_s8gallmount_test with fs xfs Oct 7 14:47:25 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 830c6b88-6ee6-4a6f-bb7b-71debe5cdd94 Oct 7 14:47:25 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:47:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a_s8gallmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:47:30 storageqe-109 systemd[1]: tmp-libblockdev.a_s8gallmount_test.mount: Deactivated successfully. Oct 7 14:47:30 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 830c6b88-6ee6-4a6f-bb7b-71debe5cdd94 Oct 7 14:47:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:47:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._8yo7xzxmount_test with fs ext4 Oct 7 14:47:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d837ce97-4628-4810-99d8-58c9f651591f r/w with ordered data mode. Quota mode: none. Oct 7 14:47:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev._8yo7xzxmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:47:45 storageqe-109 systemd[1]: tmp-libblockdev._8yo7xzxmount_test.mount: Deactivated successfully. Oct 7 14:47:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d837ce97-4628-4810-99d8-58c9f651591f. Oct 7 14:47:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:47:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r4x5ola4mount_test with fs ext3 Oct 7 14:47:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:47:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6a6d22bb-c86e-4a62-a61e-45ce84a981bf r/w with ordered data mode. Quota mode: none. Oct 7 14:47:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r4x5ola4mount_test with fs ext3 Oct 7 14:47:59 storageqe-109 systemd[1]: tmp-libblockdev.r4x5ola4mount_test.mount: Deactivated successfully. Oct 7 14:47:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6a6d22bb-c86e-4a62-a61e-45ce84a981bf. INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:48:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:48:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._hj9liupmount_test with fs ext2 Oct 7 14:48:10 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:48:10 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a2f2378b-6076-4e6b-a6ec-d4c0d08a1198 r/w without journal. Quota mode: none. Oct 7 14:48:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev._hj9liupmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ Oct 7 14:48:14 storageqe-109 systemd[1]: tmp-libblockdev._hj9liupmount_test.mount: Deactivated successfully. Oct 7 14:48:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a2f2378b-6076-4e6b-a6ec-d4c0d08a1198. Oct 7 14:48:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:48:14 storageqe-109 INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' --header '/tmp/testheaderktf' luksAddKey _fakedev -q /tmp/testfilerVC Oct 7 14:48:15 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:48:15 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' --header '/tmp/testheaderktf' luksAddKey _fakedev -q /tmp/testfilerVC cryptsetup --header '/tmp/testheaderktf' luksDump _fakedev -q Oct 7 14:48:25 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksDump _fakedev -q cryptsetup --header '/tmp/testheaderktf' luksKillSlot _fakedev -q 5 Oct 7 14:48:35 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksKillSlot _fakedev -q 5 cryptsetup --header '/tmp/testheaderktf' luksDump _fakedev -q Oct 7 14:48:45 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksDump _fakedev -q cryptsetup open --test-passphrase /tmp/testheaderktf -q Oct 7 14:48:55 storageqe-109 journal: cryptsetup open --test-passphrase /tmp/testheaderktf -q cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --type 'luks2' --header '/tmp/testheaderktf' --luks2-keyslots-size '16352k' --luks2-metadata-size '16k' --offset '131072' luksFormat /dev/mapper/npo2linear -q Oct 7 14:49:05 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --type 'luks2' --header '/tmp/testheaderktf' --luks2-keyslots-size '16352k' --luks2-metadata-size '16k' --offset '131072' luksFormat /dev/mapper/npo2linear -q cryptsetup luksDump /tmp/testheaderktf -q Oct 7 14:49:15 storageqe-109 journal: cryptsetup luksDump /tmp/testheaderktf -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 14:49:25 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfilerVC' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:49:35 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfilerVC' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileOax cryptsetup luksDump /dev/mapper/npo2linear -q --dump-json-metadata Oct 7 14:49:45 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q --dump-json-metadata cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 7 14:49:55 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:50:05 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:50:15 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 14:50:25 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 14:50:25 storageqe-109 stratisd[4947]: [2025-10-07T18:50:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:50:25 storageqe-109 stratisd[4947]: [2025-10-07T18:50:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:50:35 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:50:45 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 7 14:50:55 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '512' --pbkdf-force-iterations '1000' --key-slot '0' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 14:51:05 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '512' --pbkdf-force-iterations '1000' --key-slot '0' --hash 'sha512' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 14:51:05 storageqe-109 stratisd[4947]: [2025-10-07T18:51:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:51:05 storageqe-109 stratisd[4947]: [2025-10-07T18:51:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfilerVC' --hash 'sha512' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:51:15 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-file '/tmp/testfilerVC' --hash 'sha512' --pbkdf-force-iterations '1000' --key-slot '1' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 14:51:15 storageqe-109 stratisd[4947]: [2025-10-07T18:51:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:51:15 storageqe-109 stratisd[4947]: [2025-10-07T18:51:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 7 14:51:25 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear -q 1 Oct 7 14:51:35 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 1 cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 7 14:51:45 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 14:51:55 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-slot '0' --key-file '/tmp/testfilerVC' open /dev/mapper/npo2linear -q --test-passphrase Oct 7 14:52:05 storageqe-109 journal: cryptsetup --key-slot '0' --key-file '/tmp/testfilerVC' open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '1024' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 14:52:15 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --sector-size '1024' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 14:52:16 storageqe-109 stratisd[4947]: [2025-10-07T18:52:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:52:16 storageqe-109 stratisd[4947]: [2025-10-07T18:52:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q Oct 7 14:52:26 storageqe-109 journal: cryptsetup --type 'luks1' convert /dev/mapper/npo2linear -q cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --align-payload '4097' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 14:52:36 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --align-payload '4097' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 14:52:46 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 14:52:46 storageqe-109 stratisd[4947]: [2025-10-07T18:52:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:52:46 storageqe-109 stratisd[4947]: [2025-10-07T18:52:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' isLuks /dev/mapper/npo2linear -q Oct 7 14:52:56 storageqe-109 journal: cryptsetup --type 'luks2' isLuks /dev/mapper/npo2linear -q cryptsetup --key-slot '0' --key-file '/tmp/testfilerVC' open /dev/mapper/npo2linear -q --test-passphrase Oct 7 14:53:06 storageqe-109 journal: cryptsetup --key-slot '0' --key-file '/tmp/testfilerVC' open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q Oct 7 14:53:16 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --header '/tmp/testheaderktf' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:53:26 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:53:26 storageqe-109 stratisd[4947]: [2025-10-07T18:53:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 14:53:26 storageqe-109 stratisd[4947]: [2025-10-07T18:53:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 14:53:36 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 14:53:46 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:53:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.qqo0ggvymount_test with fs xfs Oct 7 14:54:06 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3362df4e-c86b-4bcd-9c15-85cf031936dd Oct 7 14:54:06 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:54:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qqo0ggvymount_test with fs xfs Oct 7 14:54:11 storageqe-109 systemd[1]: tmp-libblockdev.qqo0ggvymount_test.mount: Deactivated successfully. Oct 7 14:54:11 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3362df4e-c86b-4bcd-9c15-85cf031936dd INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:54:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:54:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bdzximidmount_test with fs ext4 Oct 7 14:54:21 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9c6bc459-f7b4-42c5-b90b-9bb47be78f74 r/w with ordered data mode. Quota mode: none. Oct 7 14:54:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bdzximidmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:54:26 storageqe-109 systemd[1]: tmp-libblockdev.bdzximidmount_test.mount: Deactivated successfully. Oct 7 14:54:26 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9c6bc459-f7b4-42c5-b90b-9bb47be78f74. Oct 7 14:54:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:54:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cu0e43jhmount_test with fs ext3 Oct 7 14:54:36 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:54:36 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 237d622e-0947-44c5-b19a-3bde484a8d64 r/w with ordered data mode. Quota mode: none. Oct 7 14:54:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cu0e43jhmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:54:41 storageqe-109 systemd[1]: tmp-libblockdev.cu0e43jhmount_test.mount: Deactivated successfully. Oct 7 14:54:41 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 237d622e-0947-44c5-b19a-3bde484a8d64. Oct 7 14:54:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:54:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i0z881npmount_test with fs ext2 Oct 7 14:54:51 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:54:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c5cbba46-8b5f-4079-82a6-59ef83b2ee7b r/w without journal. Quota mode: none. Oct 7 14:54:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i0z881npmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:54:56 storageqe-109 systemd[1]: tmp-libblockdev.i0z881npmount_test.mount: Deactivated successfully. Oct 7 14:54:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c5cbba46-8b5f-4079-82a6-59ef83b2ee7b. Oct 7 14:54:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:54:56 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:54:56 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:54:56 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 14:55:06 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:55:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.92bu0zgtmount_test with fs xfs Oct 7 14:55:26 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 61194307-d9c4-4316-8624-31e38337c237 Oct 7 14:55:26 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:55:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.92bu0zgtmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:55:31 storageqe-109 systemd[1]: tmp-libblockdev.92bu0zgtmount_test.mount: Deactivated successfully. Oct 7 14:55:31 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 61194307-d9c4-4316-8624-31e38337c237 Oct 7 14:55:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:55:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gir9fb4cmount_test with fs ext4 Oct 7 14:55:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8d29a402-c615-4b42-be2e-f5838922c1de r/w with ordered data mode. Quota mode: none. Oct 7 14:55:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gir9fb4cmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:55:46 storageqe-109 systemd[1]: tmp-libblockdev.gir9fb4cmount_test.mount: Deactivated successfully. Oct 7 14:55:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8d29a402-c615-4b42-be2e-f5838922c1de. Oct 7 14:55:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:55:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6or0f0rnmount_test with fs ext3 Oct 7 14:55:56 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:55:56 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 2067724a-77b4-4195-bc66-291b24829b65 r/w with ordered data mode. Quota mode: none. Oct 7 14:55:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6or0f0rnmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:56:01 storageqe-109 systemd[1]: tmp-libblockdev.6or0f0rnmount_test.mount: Deactivated successfully. Oct 7 14:56:01 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 2067724a-77b4-4195-bc66-291b24829b65. Oct 7 14:56:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:56:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kwac_dvnmount_test with fs ext2 Oct 7 14:56:11 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:56:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e4c7d1e6-56cb-4171-84c6-aa01ce76cc77 r/w without journal. Quota mode: none. Oct 7 14:56:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kwac_dvnmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q --disable-keyring Oct 7 14:56:16 storageqe-109 systemd[1]: tmp-libblockdev.kwac_dvnmount_test.mount: Deactivated successfully. Oct 7 14:56:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e4c7d1e6-56cb-4171-84c6-aa01ce76cc77. Oct 7 14:56:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:56:16 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:56:16 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:56:16 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q --disable-keyring cryptsetup status CcNRVLSvHQ -q Oct 7 14:56:26 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 14:56:36 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:56:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8j6j9pwamount_test with fs xfs Oct 7 14:56:56 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3746379b-a7d2-4356-8565-4bdafe549037 Oct 7 14:56:56 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:56:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8j6j9pwamount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:57:01 storageqe-109 systemd[1]: tmp-libblockdev.8j6j9pwamount_test.mount: Deactivated successfully. Oct 7 14:57:01 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3746379b-a7d2-4356-8565-4bdafe549037 Oct 7 14:57:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:57:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e9e4dpyjmount_test with fs ext4 Oct 7 14:57:11 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d0b3f8ac-ba7f-424d-b876-4296c62c289b r/w with ordered data mode. Quota mode: none. Oct 7 14:57:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e9e4dpyjmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:57:16 storageqe-109 systemd[1]: tmp-libblockdev.e9e4dpyjmount_test.mount: Deactivated successfully. Oct 7 14:57:16 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d0b3f8ac-ba7f-424d-b876-4296c62c289b. Oct 7 14:57:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:57:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5r2qwwefmount_test with fs ext3 Oct 7 14:57:26 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:57:26 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 80a8b47d-c694-4b6b-8ec1-852a782e2864 r/w with ordered data mode. Quota mode: none. Oct 7 14:57:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5r2qwwefmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:57:31 storageqe-109 systemd[1]: tmp-libblockdev.5r2qwwefmount_test.mount: Deactivated successfully. Oct 7 14:57:31 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 80a8b47d-c694-4b6b-8ec1-852a782e2864. Oct 7 14:57:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:57:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wp1_ctp5mount_test with fs ext2 Oct 7 14:57:41 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:57:41 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 658b9977-4b07-4c4b-b565-f40074939aa8 r/w without journal. Quota mode: none. Oct 7 14:57:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wp1_ctp5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q --disable-keyring Oct 7 14:57:46 storageqe-109 systemd[1]: tmp-libblockdev.wp1_ctp5mount_test.mount: Deactivated successfully. Oct 7 14:57:46 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 658b9977-4b07-4c4b-b565-f40074939aa8. Oct 7 14:57:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:57:46 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:57:46 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:57:46 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q --disable-keyring cryptsetup luksSuspend CcNRVLSvHQ -q Oct 7 14:57:56 storageqe-109 journal: cryptsetup luksSuspend CcNRVLSvHQ -q cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q Oct 7 14:58:06 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 14:58:16 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 14:58:26 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q Oct 7 14:58:35 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 14:58:35 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 14:58:35 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:58:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.n3_irh86mount_test with fs xfs Oct 7 14:58:46 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f75475d0-d94f-4231-b6ad-4084dfe82386 Oct 7 14:58:46 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 14:58:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n3_irh86mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:58:51 storageqe-109 systemd[1]: tmp-libblockdev.n3_irh86mount_test.mount: Deactivated successfully. Oct 7 14:58:51 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f75475d0-d94f-4231-b6ad-4084dfe82386 Oct 7 14:58:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 14:58:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2v9ybz2qmount_test with fs ext4 Oct 7 14:59:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 26d2c2ec-aca3-4ae0-9cdf-99fcba15ac5c r/w with ordered data mode. Quota mode: none. Oct 7 14:59:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2v9ybz2qmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:59:06 storageqe-109 systemd[1]: tmp-libblockdev.2v9ybz2qmount_test.mount: Deactivated successfully. Oct 7 14:59:06 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 26d2c2ec-aca3-4ae0-9cdf-99fcba15ac5c. Oct 7 14:59:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 14:59:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.69b4sg7ymount_test with fs ext3 Oct 7 14:59:16 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 14:59:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1e66c2f8-2094-4be6-b127-e7711dba7808 r/w with ordered data mode. Quota mode: none. Oct 7 14:59:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.69b4sg7ymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:59:21 storageqe-109 systemd[1]: tmp-libblockdev.69b4sg7ymount_test.mount: Deactivated successfully. Oct 7 14:59:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1e66c2f8-2094-4be6-b127-e7711dba7808. Oct 7 14:59:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 14:59:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ez4x92rqmount_test with fs ext2 Oct 7 14:59:31 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 14:59:31 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 19ffc8e8-8a07-4b11-a763-622d3c8c0b58 r/w without journal. Quota mode: none. Oct 7 14:59:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ez4x92rqmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 14:59:36 storageqe-109 systemd[1]: tmp-libblockdev.ez4x92rqmount_test.mount: Deactivated successfully. Oct 7 14:59:36 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 19ffc8e8-8a07-4b11-a763-622d3c8c0b58. Oct 7 14:59:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 14:59:36 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 14:59:36 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 14:59:36 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup luksSuspend CcNRVLSvHQ -q Oct 7 14:59:46 storageqe-109 journal: cryptsetup luksSuspend CcNRVLSvHQ -q cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q --disable-keyring Oct 7 14:59:56 storageqe-109 journal: cryptsetup --header '/tmp/testheaderktf' luksResume CcNRVLSvHQ -q --disable-keyring cryptsetup status CcNRVLSvHQ -q Oct 7 15:00:06 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 15:00:16 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 15:00:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8_kfkljamount_test with fs xfs Oct 7 15:00:36 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 059c7ffc-e1e8-47b8-bc4a-6057fefb718e Oct 7 15:00:36 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 15:00:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8_kfkljamount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 15:00:41 storageqe-109 systemd[1]: tmp-libblockdev.8_kfkljamount_test.mount: Deactivated successfully. Oct 7 15:00:41 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 059c7ffc-e1e8-47b8-bc4a-6057fefb718e Oct 7 15:00:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 15:00:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3wladjvzmount_test with fs ext4 Oct 7 15:00:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem d6f1199a-fbfe-43ae-940f-b88d5575adde r/w with ordered data mode. Quota mode: none. Oct 7 15:00:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3wladjvzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 15:00:56 storageqe-109 systemd[1]: tmp-libblockdev.3wladjvzmount_test.mount: Deactivated successfully. Oct 7 15:00:56 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem d6f1199a-fbfe-43ae-940f-b88d5575adde. Oct 7 15:00:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 15:00:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1sn11zhqmount_test with fs ext3 Oct 7 15:01:06 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 15:01:06 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 91283093-e1d2-49a9-9a5a-111303aa1d27 r/w with ordered data mode. Quota mode: none. Oct 7 15:01:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1sn11zhqmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 15:01:11 storageqe-109 systemd[1]: tmp-libblockdev.1sn11zhqmount_test.mount: Deactivated successfully. Oct 7 15:01:11 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 91283093-e1d2-49a9-9a5a-111303aa1d27. Oct 7 15:01:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 15:01:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nvioarrlmount_test with fs ext2 Oct 7 15:01:21 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 15:01:21 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 33699529-586c-4ea3-b5c2-9c74371dbe57 r/w without journal. Quota mode: none. Oct 7 15:01:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nvioarrlmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ Oct 7 15:01:26 storageqe-109 systemd[1]: tmp-libblockdev.nvioarrlmount_test.mount: Deactivated successfully. Oct 7 15:01:26 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 33699529-586c-4ea3-b5c2-9c74371dbe57. Oct 7 15:01:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 15:01:26 storageqe-109 INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:01:26 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 15:01:26 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:01:26 storageqe-109 stratisd[4947]: [2025-10-07T19:01:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:01:26 storageqe-109 stratisd[4947]: [2025-10-07T19:01:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'keydesc0' --token-id '3' token add /dev/mapper/npo2linear -q Oct 7 15:01:36 storageqe-109 journal: cryptsetup --key-description 'keydesc0' --token-id '3' token add /dev/mapper/npo2linear -q Oct 7 15:01:36 storageqe-109 stratisd[4947]: [2025-10-07T19:01:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:01:36 storageqe-109 stratisd[4947]: [2025-10-07T19:01:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:01:46 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-description 'keydesc1' --key-slot '5' token add /dev/mapper/npo2linear -q Oct 7 15:01:56 storageqe-109 journal: cryptsetup --key-description 'keydesc1' --key-slot '5' token add /dev/mapper/npo2linear -q cryptsetup open /dev/mapper/npo2linear -q --token-only --test-passphrase Oct 7 15:02:06 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear -q --token-only --test-passphrase cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q --token-only --test-passphrase Oct 7 15:02:16 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q --token-only --test-passphrase cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q --token-only Oct 7 15:02:26 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q --token-only Oct 7 15:02:26 storageqe-109 stratisd[4947]: [2025-10-07T19:02:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:02:26 storageqe-109 stratisd[4947]: [2025-10-07T19:02:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status CcNRVLSvHQ -q Oct 7 15:02:36 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup luksSuspend CcNRVLSvHQ -q Oct 7 15:02:46 storageqe-109 journal: cryptsetup luksSuspend CcNRVLSvHQ -q cryptsetup luksResume CcNRVLSvHQ -q Oct 7 15:02:56 storageqe-109 journal: cryptsetup luksResume CcNRVLSvHQ -q cryptsetup status CcNRVLSvHQ -q Oct 7 15:03:06 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup luksSuspend CcNRVLSvHQ -q Oct 7 15:03:16 storageqe-109 journal: cryptsetup luksSuspend CcNRVLSvHQ -q cryptsetup --token-type 'luks2-keyring' luksResume CcNRVLSvHQ -q Oct 7 15:03:26 storageqe-109 journal: cryptsetup --token-type 'luks2-keyring' luksResume CcNRVLSvHQ -q INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 15:03:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.b1l6xxobmount_test with fs xfs Oct 7 15:03:46 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem bbf4e8d9-3ddf-43ee-bc3e-25da3083ccba Oct 7 15:03:46 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 15:03:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b1l6xxobmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 15:03:51 storageqe-109 systemd[1]: tmp-libblockdev.b1l6xxobmount_test.mount: Deactivated successfully. Oct 7 15:03:51 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem bbf4e8d9-3ddf-43ee-bc3e-25da3083ccba Oct 7 15:03:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs xfs in remove_crypt Oct 7 15:03:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gej5pt1fmount_test with fs ext4 Oct 7 15:04:01 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 965f511e-c70c-4a81-8fdd-b7ebcef29d0e r/w with ordered data mode. Quota mode: none. Oct 7 15:04:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gej5pt1fmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 15:04:06 storageqe-109 systemd[1]: tmp-libblockdev.gej5pt1fmount_test.mount: Deactivated successfully. Oct 7 15:04:06 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 965f511e-c70c-4a81-8fdd-b7ebcef29d0e. Oct 7 15:04:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext4 in remove_crypt Oct 7 15:04:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5h0a7adlmount_test with fs ext3 Oct 7 15:04:16 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 15:04:16 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 81ff02ca-deda-4acd-b257-b4c997dc1052 r/w with ordered data mode. Quota mode: none. Oct 7 15:04:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5h0a7adlmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 15:04:21 storageqe-109 systemd[1]: tmp-libblockdev.5h0a7adlmount_test.mount: Deactivated successfully. Oct 7 15:04:21 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 81ff02ca-deda-4acd-b257-b4c997dc1052. Oct 7 15:04:21 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext3 in remove_crypt Oct 7 15:04:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.k3zypz6lmount_test with fs ext2 Oct 7 15:04:31 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 15:04:31 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 60f02e4c-c381-471d-8441-763af1164275 r/w without journal. Quota mode: none. Oct 7 15:04:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k3zypz6lmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt INFO: remove crypt device CcNRVLSvHQ INFO: finishe the remove crypt device CcNRVLSvHQ cryptsetup --token-type 'some-type' open /dev/mapper/npo2linear --token-only --test-passphrase -q Oct 7 15:04:36 storageqe-109 systemd[1]: tmp-libblockdev.k3zypz6lmount_test.mount: Deactivated successfully. Oct 7 15:04:36 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 60f02e4c-c381-471d-8441-763af1164275. Oct 7 15:04:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/CcNRVLSvHQ and fs ext2 in remove_crypt Oct 7 15:04:36 storageqe-109 INFO: remove crypt device CcNRVLSvHQ Oct 7 15:04:36 storageqe-109 INFO: finishe the remove crypt device CcNRVLSvHQ Oct 7 15:04:36 storageqe-109 stratisd[4947]: [2025-10-07T19:04:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:04:36 storageqe-109 stratisd[4947]: [2025-10-07T19:04:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:04:36 storageqe-109 journal: cryptsetup --token-type 'some-type' open /dev/mapper/npo2linear --token-only --test-passphrase -q cryptsetup --token-type 'some-type' open /dev/mapper/npo2linear CcNRVLSvHQ --token-only -q Oct 7 15:04:46 storageqe-109 journal: cryptsetup --token-type 'some-type' open /dev/mapper/npo2linear CcNRVLSvHQ --token-only -q cryptsetup status CcNRVLSvHQ -q Oct 7 15:04:56 storageqe-109 journal: cryptsetup status CcNRVLSvHQ -q cryptsetup --token-id '3' token remove /dev/mapper/npo2linear -q Oct 7 15:05:06 storageqe-109 journal: cryptsetup --token-id '3' token remove /dev/mapper/npo2linear -q Oct 7 15:05:06 storageqe-109 stratisd[4947]: [2025-10-07T19:05:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:06 storageqe-109 stratisd[4947]: [2025-10-07T19:05:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:05:16 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-description 'keydesc1' --key-slot '4' token add /dev/mapper/npo2linear -q Oct 7 15:05:26 storageqe-109 stratisd[4947]: [2025-10-07T19:05:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:26 storageqe-109 stratisd[4947]: [2025-10-07T19:05:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:26 storageqe-109 journal: cryptsetup --key-description 'keydesc1' --key-slot '4' token add /dev/mapper/npo2linear -q Oct 7 15:05:26 storageqe-109 stratisd[4947]: [2025-10-07T19:05:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:26 storageqe-109 stratisd[4947]: [2025-10-07T19:05:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksKillSlot /dev/mapper/npo2linear -q 4 Oct 7 15:05:36 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 4 Oct 7 15:05:36 storageqe-109 stratisd[4947]: [2025-10-07T19:05:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:36 storageqe-109 stratisd[4947]: [2025-10-07T19:05:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --token-id '12' --json-file '/tmp/tokenfile0' token import /dev/mapper/npo2linear -q Oct 7 15:05:46 storageqe-109 stratisd[4947]: [2025-10-07T19:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:46 storageqe-109 stratisd[4947]: [2025-10-07T19:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:46 storageqe-109 stratisd[4947]: [2025-10-07T19:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:46 storageqe-109 stratisd[4947]: [2025-10-07T19:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:46 storageqe-109 journal: cryptsetup --token-id '12' --json-file '/tmp/tokenfile0' token import /dev/mapper/npo2linear -q Oct 7 15:05:46 storageqe-109 stratisd[4947]: [2025-10-07T19:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:05:46 storageqe-109 stratisd[4947]: [2025-10-07T19:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --token-id '12' --json-file '/tmp/tokenfile0' token import /dev/mapper/npo2linear -q Oct 7 15:05:56 storageqe-109 journal: cryptsetup --token-id '12' --json-file '/tmp/tokenfile0' token import /dev/mapper/npo2linear -q cryptsetup --token-id '10' token export /dev/mapper/npo2linear -q Oct 7 15:06:06 storageqe-109 journal: cryptsetup --token-id '10' token export /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' luksFormat /dev/mapper/npo2linear -q Oct 7 15:06:16 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' luksFormat /dev/mapper/npo2linear -q Oct 7 15:06:17 storageqe-109 stratisd[4947]: [2025-10-07T19:06:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:06:17 storageqe-109 stratisd[4947]: [2025-10-07T19:06:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-slot '0' --priority 'prefer' config /dev/mapper/npo2linear -q Oct 7 15:06:27 storageqe-109 stratisd[4947]: [2025-10-07T19:06:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:06:27 storageqe-109 stratisd[4947]: [2025-10-07T19:06:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:06:27 storageqe-109 journal: cryptsetup --key-slot '0' --priority 'prefer' config /dev/mapper/npo2linear -q cryptsetup --key-slot '1' --priority 'wrong' config /dev/mapper/npo2linear -q Oct 7 15:06:37 storageqe-109 journal: cryptsetup --key-slot '1' --priority 'wrong' config /dev/mapper/npo2linear -q cryptsetup --key-slot '1' --priority 'ignore' config /dev/mapper/npo2linear -q Oct 7 15:06:47 storageqe-109 journal: cryptsetup --key-slot '1' --priority 'ignore' config /dev/mapper/npo2linear -q Oct 7 15:06:47 storageqe-109 stratisd[4947]: [2025-10-07T19:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:06:47 storageqe-109 stratisd[4947]: [2025-10-07T19:06:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear -q --test-passphrase Oct 7 15:06:57 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --key-slot '1' open /dev/mapper/npo2linear -q --test-passphrase Oct 7 15:07:07 storageqe-109 journal: cryptsetup --key-slot '1' open /dev/mapper/npo2linear -q --test-passphrase cryptsetup open /dev/mapper/npo2linear -q --test-passphrase Oct 7 15:07:17 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --key-slot '1' --priority 'normal' config /dev/mapper/npo2linear -q Oct 7 15:07:27 storageqe-109 journal: cryptsetup --key-slot '1' --priority 'normal' config /dev/mapper/npo2linear -q Oct 7 15:07:27 storageqe-109 stratisd[4947]: [2025-10-07T19:07:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:07:27 storageqe-109 stratisd[4947]: [2025-10-07T19:07:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear -q --test-passphrase Oct 7 15:07:37 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --key-slot '1' --priority 'ignore' config /dev/mapper/npo2linear -q Oct 7 15:07:47 storageqe-109 journal: cryptsetup --key-slot '1' --priority 'ignore' config /dev/mapper/npo2linear -q Oct 7 15:07:47 storageqe-109 stratisd[4947]: [2025-10-07T19:07:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:07:47 storageqe-109 stratisd[4947]: [2025-10-07T19:07:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear -q --test-passphrase Oct 7 15:07:57 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear -q --test-passphrase cryptsetup --type 'luks2' --pbkdf 'pbkdfXX' luksFormat /dev/mapper/npo2linear -q Oct 7 15:08:07 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdfXX' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '999' luksFormat /dev/mapper/npo2linear -q Oct 7 15:08:17 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '999' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1234' luksFormat /dev/mapper/npo2linear -q Oct 7 15:08:27 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1234' luksFormat /dev/mapper/npo2linear -q Oct 7 15:08:27 storageqe-109 stratisd[4947]: [2025-10-07T19:08:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:08:27 storageqe-109 stratisd[4947]: [2025-10-07T19:08:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:08:37 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'argon2id' --pbkdf-force-iterations '3' luksFormat /dev/mapper/npo2linear -q Oct 7 15:08:47 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'argon2id' --pbkdf-force-iterations '3' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'argon2id' --pbkdf-force-iterations '1000' --pbkdf-memory '100000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:08:57 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'argon2id' --pbkdf-force-iterations '1000' --pbkdf-memory '100000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:09:11 storageqe-109 stratisd[4947]: [2025-10-07T19:09:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:09:11 storageqe-109 stratisd[4947]: [2025-10-07T19:09:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:09:21 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'argon2i' --pbkdf-force-iterations '1000' --pbkdf-memory '1234' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 15:09:31 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'argon2i' --pbkdf-force-iterations '1000' --pbkdf-memory '1234' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 15:09:32 storageqe-109 stratisd[4947]: [2025-10-07T19:09:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:09:32 storageqe-109 stratisd[4947]: [2025-10-07T19:09:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:09:42 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:09:52 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:10:02 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:10:12 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'argon2i' --pbkdf-force-iterations '1000' --pbkdf-memory '1234' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 15:10:22 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'argon2i' --pbkdf-force-iterations '1000' --pbkdf-memory '1234' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 15:10:22 storageqe-109 stratisd[4947]: [2025-10-07T19:10:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:10:22 storageqe-109 stratisd[4947]: [2025-10-07T19:10:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --iter-time '500' luksFormat /dev/mapper/npo2linear -q Oct 7 15:10:32 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --iter-time '500' luksFormat /dev/mapper/npo2linear -q Oct 7 15:10:35 storageqe-109 stratisd[4947]: [2025-10-07T19:10:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:10:35 storageqe-109 stratisd[4947]: [2025-10-07T19:10:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 15:10:45 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC cryptsetup --key-file '/tmp/testfilerVC' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:10:55 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilerVC' luksConvertKey /dev/mapper/npo2linear -q cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 15:11:05 storageqe-109 journal: cryptsetup --type 'luks2' convert /dev/mapper/npo2linear -q Oct 7 15:11:05 storageqe-109 stratisd[4947]: [2025-10-07T19:11:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:11:05 storageqe-109 stratisd[4947]: [2025-10-07T19:11:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:11:15 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:11:25 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilerVC' --key-slot '5' --pbkdf 'argon2i' --pbkdf-memory '32' --iter-time '1' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:11:35 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilerVC' --key-slot '5' --pbkdf 'argon2i' --pbkdf-memory '32' --iter-time '1' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:11:37 storageqe-109 stratisd[4947]: [2025-10-07T19:11:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:11:37 storageqe-109 stratisd[4947]: [2025-10-07T19:11:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:11:47 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --key-file '/tmp/testfilerVC' luksAddKey /dev/mapper/npo2linear -q Oct 7 15:11:57 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --key-file '/tmp/testfilerVC' luksAddKey /dev/mapper/npo2linear -q Oct 7 15:11:57 storageqe-109 stratisd[4947]: [2025-10-07T19:11:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:11:57 storageqe-109 stratisd[4947]: [2025-10-07T19:11:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:12:07 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksKillSlot /dev/mapper/npo2linear -q 5 Oct 7 15:12:17 storageqe-109 journal: cryptsetup luksKillSlot /dev/mapper/npo2linear -q 5 Oct 7 15:12:17 storageqe-109 stratisd[4947]: [2025-10-07T19:12:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:12:17 storageqe-109 stratisd[4947]: [2025-10-07T19:12:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:12:27 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:12:37 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-slot '1' --pbkdf 'argon2i' --pbkdf-memory '32' --iter-time '1' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:12:47 storageqe-109 journal: cryptsetup --key-slot '1' --pbkdf 'argon2i' --pbkdf-memory '32' --iter-time '1' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:12:49 storageqe-109 stratisd[4947]: [2025-10-07T19:12:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:12:49 storageqe-109 stratisd[4947]: [2025-10-07T19:12:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:12:59 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '21' --key-size '16' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:13:09 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '21' --key-size '16' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:13:09 storageqe-109 stratisd[4947]: [2025-10-07T19:13:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:13:09 storageqe-109 stratisd[4947]: [2025-10-07T19:13:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --key-slot '21' --pbkdf-force-iterations '1001' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:13:19 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --key-slot '21' --pbkdf-force-iterations '1001' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:13:19 storageqe-109 stratisd[4947]: [2025-10-07T19:13:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:13:19 storageqe-109 stratisd[4947]: [2025-10-07T19:13:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 15:13:29 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '5' luksFormat /dev/mapper/npo2linear -q /tmp/testfilerVC Oct 7 15:13:29 storageqe-109 stratisd[4947]: [2025-10-07T19:13:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:13:29 storageqe-109 stratisd[4947]: [2025-10-07T19:13:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:13:39 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:13:39 storageqe-109 stratisd[4947]: [2025-10-07T19:13:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:13:39 storageqe-109 stratisd[4947]: [2025-10-07T19:13:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '2' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:13:49 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '2' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:13:49 storageqe-109 stratisd[4947]: [2025-10-07T19:13:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:13:49 storageqe-109 stratisd[4947]: [2025-10-07T19:13:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksDump /dev/mapper/npo2linear -q Oct 7 15:13:59 storageqe-109 journal: cryptsetup luksDump /dev/mapper/npo2linear -q cryptsetup --key-slot '5' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:14:09 storageqe-109 journal: cryptsetup --key-slot '5' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 15:14:19 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --key-slot '2' open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 15:14:29 storageqe-109 journal: cryptsetup --key-slot '2' open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q Oct 7 15:14:39 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear CcNRVLSvHQ -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:14:49 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:14:49 storageqe-109 stratisd[4947]: [2025-10-07T19:14:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:14:49 storageqe-109 stratisd[4947]: [2025-10-07T19:14:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:14:59 storageqe-109 journal: cryptsetup --type 'luks1' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '127k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:09 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '127k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '127k' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:19 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '127k' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '128M' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:29 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '128M' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:30 storageqe-109 stratisd[4947]: [2025-10-07T19:15:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:15:30 storageqe-109 stratisd[4947]: [2025-10-07T19:15:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:40 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:40 storageqe-109 stratisd[4947]: [2025-10-07T19:15:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:15:40 storageqe-109 stratisd[4947]: [2025-10-07T19:15:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:15:40 storageqe-109 stratisd[4947]: [2025-10-07T19:15:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:15:40 storageqe-109 stratisd[4947]: [2025-10-07T19:15:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:15:40 storageqe-109 stratisd[4947]: [2025-10-07T19:15:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:15:40 storageqe-109 stratisd[4947]: [2025-10-07T19:15:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:50 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-metadata-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:15:50 storageqe-109 stratisd[4947]: [2025-10-07T19:15:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:15:50 storageqe-109 stratisd[4947]: [2025-10-07T19:15:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:00 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --luks2-keyslots-size '128k' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:00 storageqe-109 stratisd[4947]: [2025-10-07T19:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:16:00 storageqe-109 stratisd[4947]: [2025-10-07T19:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:16:00 storageqe-109 stratisd[4947]: [2025-10-07T19:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:16:00 storageqe-109 stratisd[4947]: [2025-10-07T19:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:16:00 storageqe-109 stratisd[4947]: [2025-10-07T19:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:16:00 storageqe-109 stratisd[4947]: [2025-10-07T19:16:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '16384' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:10 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '16384' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:10 storageqe-109 stratisd[4947]: [2025-10-07T19:16:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:16:10 storageqe-109 stratisd[4947]: [2025-10-07T19:16:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '64' --luks2-keyslots-size '8192' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:20 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '64' --luks2-keyslots-size '8192' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:20 storageqe-109 udisksd[1175313]: Error getting '/dev/dm-3' metadata_size: Unknown or unsupported LUKS version (g-bd-crypto-error-quark, 0) cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '120' --luks2-keyslots-size '8192' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:30 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '120' --luks2-keyslots-size '8192' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:30 storageqe-109 udisksd[1175313]: Error getting '/dev/dm-3' metadata_size: Unknown or unsupported LUKS version (g-bd-crypto-error-quark, 0) cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '128' --luks2-keyslots-size '8192' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:40 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --key-size '256' --offset '128' --luks2-keyslots-size '8192' --pbkdf-force-iterations '1000' luksFormat /dev/mapper/npo2linear -q Oct 7 15:16:40 storageqe-109 udisksd[1175313]: Error getting '/dev/dm-3' metadata_size: Unknown or unsupported LUKS version (g-bd-crypto-error-quark, 0) cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:16:50 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '0' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:16:50 storageqe-109 stratisd[4947]: [2025-10-07T19:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:16:50 storageqe-109 stratisd[4947]: [2025-10-07T19:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileOax' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 15:17:00 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '1' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 15:17:00 storageqe-109 stratisd[4947]: [2025-10-07T19:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:17:00 storageqe-109 stratisd[4947]: [2025-10-07T19:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileOax' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '2' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 15:17:10 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileOax' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '2' luksAddKey /dev/mapper/npo2linear -q /tmp/testfileNGT Oct 7 15:17:10 storageqe-109 stratisd[4947]: [2025-10-07T19:17:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:17:10 storageqe-109 stratisd[4947]: [2025-10-07T19:17:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfileNGT' --pbkdf 'pbkdf2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf-force-iterations '1000' --key-slot '2' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:17:20 storageqe-109 journal: cryptsetup --key-file '/tmp/testfileNGT' --pbkdf 'pbkdf2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf-force-iterations '1000' --key-slot '2' luksChangeKey /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:17:20 storageqe-109 stratisd[4947]: [2025-10-07T19:17:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:17:20 storageqe-109 stratisd[4947]: [2025-10-07T19:17:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf-force-iterations '1000' --key-slot '21' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:17:30 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --pbkdf-force-iterations '1000' --key-slot '21' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:17:30 storageqe-109 stratisd[4947]: [2025-10-07T19:17:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:17:30 storageqe-109 stratisd[4947]: [2025-10-07T19:17:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '22' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:17:40 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-slot '22' --key-size '72' luksAddKey /dev/mapper/npo2linear -q --unbound Oct 7 15:17:40 storageqe-109 stratisd[4947]: [2025-10-07T19:17:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:17:40 storageqe-109 stratisd[4947]: [2025-10-07T19:17:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --key-slot '22' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:17:50 storageqe-109 journal: cryptsetup --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --keyslot-cipher 'aes-cbc-plain64' --keyslot-key-size '128' --key-slot '22' luksConvertKey /dev/mapper/npo2linear -q Oct 7 15:17:50 storageqe-109 stratisd[4947]: [2025-10-07T19:17:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:17:50 storageqe-109 stratisd[4947]: [2025-10-07T19:17:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-ecb' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:01 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-ecb' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:01 storageqe-109 stratisd[4947]: [2025-10-07T19:18:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:01 storageqe-109 stratisd[4947]: [2025-10-07T19:18:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-null' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:11 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-null' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:11 storageqe-109 stratisd[4947]: [2025-10-07T19:18:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:11 storageqe-109 stratisd[4947]: [2025-10-07T19:18:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-plain64' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:21 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-plain64' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:21 storageqe-109 stratisd[4947]: [2025-10-07T19:18:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:21 storageqe-109 stratisd[4947]: [2025-10-07T19:18:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:31 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-cbc-essiv:sha256' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:31 storageqe-109 stratisd[4947]: [2025-10-07T19:18:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:31 storageqe-109 stratisd[4947]: [2025-10-07T19:18:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-xts-plain64' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:41 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --cipher 'aes-xts-plain64' --key-size '256' luksFormat /dev/mapper/npo2linear -q /tmp/testfileOax Oct 7 15:18:41 storageqe-109 stratisd[4947]: [2025-10-07T19:18:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:41 storageqe-109 stratisd[4947]: [2025-10-07T19:18:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_compat_test2[npo2_linear] #### Oct 7 15:18:56 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 15:18:56 storageqe-109 INFO: #### END test_compat_test2[npo2_linear] #### Oct 7 15:18:56 storageqe-109 stratisd[4947]: [2025-10-07T19:18:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:56 storageqe-109 stratisd[4947]: [2025-10-07T19:18:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:56 storageqe-109 stratisd[4947]: [2025-10-07T19:18:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:56 storageqe-109 stratisd[4947]: [2025-10-07T19:18:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:18:57 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:18:58 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:18:59 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 15:18:59 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:18:59 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:19:09 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_verify_lock_range ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:19:10 storageqe-109 INFO: #### will start test_verify_lock_range ##### Oct 7 15:19:10 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:19:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:19:27 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:19:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:19:38 storageqe-109 kernel: nvme0n1: Oct 7 15:19:38 storageqe-109 kernel: nvme0n1: p1 Oct 7 15:19:38 storageqe-109 kernel: nvme0n1: p1 p2 Oct 7 15:19:38 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal --debug cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal --debug Oct 7 15:19:48 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:48 storageqe-109 stratisd[4947]: [2025-10-07T19:19:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:19:48 storageqe-109 stratisd[4947]: [2025-10-07T19:19:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:19:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:58 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:19:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:19:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:19:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:19:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:19:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:20:08 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup erase /dev/nvme0n1p1 -q Oct 7 15:20:09 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p1 -q cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:20:19 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:20:29 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 15:20:29 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 15:20:29 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:20:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q INFO: finishe the remove crypt device None Oct 7 15:20:51 storageqe-109 INFO: finishe the remove crypt device None cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:20:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:21:05 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:21:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_verify_lock_range #### INFO: #### will start test_hw_opal ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:21:21 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:21:21 storageqe-109 INFO: #### END test_verify_lock_range #### Oct 7 15:21:21 storageqe-109 INFO: #### will start test_hw_opal ##### Oct 7 15:21:21 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:21:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:21:37 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:21:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:21:48 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:21:58 storageqe-109 kernel: nvme_log_error: 5 callbacks suppressed Oct 7 15:21:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:58 storageqe-109 kernel: blk_print_req_error: 5 callbacks suppressed Oct 7 15:21:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 15:21:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:21:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 15:21:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 15:21:59 storageqe-109 stratisd[4947]: [2025-10-07T19:21:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:21:59 storageqe-109 stratisd[4947]: [2025-10-07T19:21:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 nENe -q Oct 7 15:22:09 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 nENe -q Oct 7 15:22:11 storageqe-109 stratisd[4947]: [2025-10-07T19:22:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:22:11 storageqe-109 stratisd[4947]: [2025-10-07T19:22:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:22:18 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.es7lq5q3mount_test with fs xfs Oct 7 15:22:32 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem cc594ddc-9fa1-49b1-82e9-85fa8eb106e9 Oct 7 15:22:32 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:22:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.es7lq5q3mount_test with fs xfs Oct 7 15:22:37 storageqe-109 systemd[1]: tmp-libblockdev.es7lq5q3mount_test.mount: Deactivated successfully. Oct 7 15:22:37 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem cc594ddc-9fa1-49b1-82e9-85fa8eb106e9 INFO: will run io in dir /tmp/libblockdev.e1prsrmhmount_test with fs ext2 Oct 7 15:22:57 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 15:22:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 62fcc01f-4eb5-4e97-afd1-77ecd2972420 r/w without journal. Quota mode: none. Oct 7 15:22:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e1prsrmhmount_test with fs ext2 Oct 7 15:23:03 storageqe-109 systemd[1]: tmp-libblockdev.e1prsrmhmount_test.mount: Deactivated successfully. Oct 7 15:23:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 62fcc01f-4eb5-4e97-afd1-77ecd2972420. Oct 7 15:23:24 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.r4997vezmount_test with fs ext3 Oct 7 15:23:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem fa2c0a44-9d63-47cb-a796-164e107319ef r/w with ordered data mode. Quota mode: none. Oct 7 15:23:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r4997vezmount_test with fs ext3 Oct 7 15:23:29 storageqe-109 systemd[1]: tmp-libblockdev.r4997vezmount_test.mount: Deactivated successfully. Oct 7 15:23:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem fa2c0a44-9d63-47cb-a796-164e107319ef. INFO: will run io in dir /tmp/libblockdev.8yftfdckmount_test with fs ext4 Oct 7 15:23:39 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e15c7000-1d65-409a-b397-956838f3c242 r/w with ordered data mode. Quota mode: none. Oct 7 15:23:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8yftfdckmount_test with fs ext4 Oct 7 15:23:44 storageqe-109 systemd[1]: tmp-libblockdev.8yftfdckmount_test.mount: Deactivated successfully. Oct 7 15:23:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e15c7000-1d65-409a-b397-956838f3c242. INFO: will run io in dir /tmp/libblockdev.ffp2erx3mount_test with fs xfs Oct 7 15:23:55 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 75d41cf5-1d2d-4988-81fd-24092512939e Oct 7 15:23:55 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:23:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ffp2erx3mount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/nENe and fs xfs in remove_crypt Oct 7 15:23:59 storageqe-109 systemd[1]: tmp-libblockdev.ffp2erx3mount_test.mount: Deactivated successfully. Oct 7 15:23:59 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 75d41cf5-1d2d-4988-81fd-24092512939e Oct 7 15:23:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nENe and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8chvq4s1mount_test with fs xfs Oct 7 15:24:10 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem cccf9720-5797-42f8-96b0-d5a07b334d15 Oct 7 15:24:10 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:24:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8chvq4s1mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/nENe and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nENe and fs ext4 in remove_crypt Oct 7 15:24:15 storageqe-109 systemd[1]: tmp-libblockdev.8chvq4s1mount_test.mount: Deactivated successfully. Oct 7 15:24:15 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem cccf9720-5797-42f8-96b0-d5a07b334d15 Oct 7 15:24:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nENe and fs xfs in remove_crypt Oct 7 15:24:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nENe and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q0kt5s95mount_test with fs ext4 Oct 7 15:24:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5cc8e56a-bc9f-4918-a356-456108c61212 r/w with ordered data mode. Quota mode: none. Oct 7 15:24:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q0kt5s95mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/nENe and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nENe and fs ext3 in remove_crypt Oct 7 15:24:31 storageqe-109 systemd[1]: tmp-libblockdev.q0kt5s95mount_test.mount: Deactivated successfully. Oct 7 15:24:31 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5cc8e56a-bc9f-4918-a356-456108c61212. Oct 7 15:24:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nENe and fs ext4 in remove_crypt Oct 7 15:24:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nENe and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6130ps6hmount_test with fs ext3 Oct 7 15:24:52 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 15:24:52 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem eb27e563-c7b4-4f95-9bc2-b17b50f0d917 r/w with ordered data mode. Quota mode: none. Oct 7 15:24:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6130ps6hmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/nENe and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nENe and fs ext2 in remove_crypt Oct 7 15:24:57 storageqe-109 systemd[1]: tmp-libblockdev.6130ps6hmount_test.mount: Deactivated successfully. Oct 7 15:24:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem eb27e563-c7b4-4f95-9bc2-b17b50f0d917. Oct 7 15:24:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nENe and fs ext3 in remove_crypt Oct 7 15:24:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nENe and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.t_ljwvtamount_test with fs ext2 Oct 7 15:25:17 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 15:25:17 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 95186e47-f053-437e-93fb-89cd2350c79b r/w without journal. Quota mode: none. Oct 7 15:25:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t_ljwvtamount_test with fs ext2 Oct 7 15:25:22 storageqe-109 systemd[1]: tmp-libblockdev.t_ljwvtamount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/nENe and fs ext2 in remove_crypt INFO: remove crypt device nENe Oct 7 15:25:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 95186e47-f053-437e-93fb-89cd2350c79b. Oct 7 15:25:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nENe and fs ext2 in remove_crypt Oct 7 15:25:22 storageqe-109 INFO: remove crypt device nENe cryptsetup luksDump /dev/nvme0n1 -q Oct 7 15:25:23 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 15:25:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 15:25:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:25:54 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 15:25:54 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 15:25:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 15:26:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device nENe cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 15:26:16 storageqe-109 INFO: finishe the remove crypt device nENe Oct 7 15:26:16 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 15:26:28 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 15:26:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:26:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 15:26:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 15:26:28 storageqe-109 stratisd[4947]: [2025-10-07T19:26:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:26:28 storageqe-109 stratisd[4947]: [2025-10-07T19:26:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 HYZK -q Oct 7 15:26:38 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 HYZK -q Oct 7 15:26:41 storageqe-109 stratisd[4947]: [2025-10-07T19:26:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:26:41 storageqe-109 stratisd[4947]: [2025-10-07T19:26:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:26:46 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.lputif4ymount_test with fs xfs Oct 7 15:27:02 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 54cbd12f-d986-445e-8fed-7cce927c89a7 Oct 7 15:27:02 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:27:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lputif4ymount_test with fs xfs Oct 7 15:27:07 storageqe-109 systemd[1]: tmp-libblockdev.lputif4ymount_test.mount: Deactivated successfully. Oct 7 15:27:07 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 54cbd12f-d986-445e-8fed-7cce927c89a7 INFO: will run io in dir /tmp/libblockdev.it86hhq2mount_test with fs ext2 Oct 7 15:27:28 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 15:27:28 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8b54ca11-8b47-4ba3-bdf1-672c8519058b r/w without journal. Quota mode: none. Oct 7 15:27:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.it86hhq2mount_test with fs ext2 Oct 7 15:27:33 storageqe-109 systemd[1]: tmp-libblockdev.it86hhq2mount_test.mount: Deactivated successfully. Oct 7 15:27:33 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8b54ca11-8b47-4ba3-bdf1-672c8519058b. INFO: will run io in dir /tmp/libblockdev.g34oeknxmount_test with fs ext3 Oct 7 15:27:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 15:27:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem adf96963-cacb-46e0-a82a-21ebbaf0c195 r/w with ordered data mode. Quota mode: none. Oct 7 15:27:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g34oeknxmount_test with fs ext3 Oct 7 15:28:00 storageqe-109 systemd[1]: tmp-libblockdev.g34oeknxmount_test.mount: Deactivated successfully. Oct 7 15:28:00 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem adf96963-cacb-46e0-a82a-21ebbaf0c195. INFO: will run io in dir /tmp/libblockdev.4cxwtl6ymount_test with fs ext4 Oct 7 15:28:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 41f43a74-32d8-4815-9bc1-efd1c2f29802 r/w with ordered data mode. Quota mode: none. Oct 7 15:28:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4cxwtl6ymount_test with fs ext4 Oct 7 15:28:17 storageqe-109 systemd[1]: tmp-libblockdev.4cxwtl6ymount_test.mount: Deactivated successfully. Oct 7 15:28:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 41f43a74-32d8-4815-9bc1-efd1c2f29802. INFO: will run io in dir /tmp/libblockdev.2d9b7akvmount_test with fs xfs Oct 7 15:28:29 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 29ea6f65-cec7-4935-8daf-a923b0308815 Oct 7 15:28:29 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:28:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2d9b7akvmount_test with fs xfs INFO: start IO testing with the luks device /dev/mapper/HYZK and fs xfs in remove_crypt Oct 7 15:28:34 storageqe-109 systemd[1]: tmp-libblockdev.2d9b7akvmount_test.mount: Deactivated successfully. Oct 7 15:28:34 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 29ea6f65-cec7-4935-8daf-a923b0308815 Oct 7 15:28:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/HYZK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.b3_afwp8mount_test with fs xfs Oct 7 15:28:45 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 343b35d9-2ba6-40b3-bb9b-c382bbb99867 Oct 7 15:28:45 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:28:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b3_afwp8mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/HYZK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/HYZK and fs ext4 in remove_crypt Oct 7 15:28:50 storageqe-109 systemd[1]: tmp-libblockdev.b3_afwp8mount_test.mount: Deactivated successfully. Oct 7 15:28:50 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 343b35d9-2ba6-40b3-bb9b-c382bbb99867 Oct 7 15:28:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/HYZK and fs xfs in remove_crypt Oct 7 15:28:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/HYZK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ggtrko6cmount_test with fs ext4 Oct 7 15:29:01 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 168468ab-29fd-4662-84bc-a750eee735da r/w with ordered data mode. Quota mode: none. Oct 7 15:29:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ggtrko6cmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/HYZK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/HYZK and fs ext3 in remove_crypt Oct 7 15:29:06 storageqe-109 systemd[1]: tmp-libblockdev.ggtrko6cmount_test.mount: Deactivated successfully. Oct 7 15:29:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 168468ab-29fd-4662-84bc-a750eee735da. Oct 7 15:29:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/HYZK and fs ext4 in remove_crypt Oct 7 15:29:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/HYZK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3wi7grg7mount_test with fs ext3 Oct 7 15:29:28 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 15:29:28 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c3182939-91eb-4fdd-bfe3-78be2e9ec653 r/w with ordered data mode. Quota mode: none. Oct 7 15:29:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3wi7grg7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/HYZK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/HYZK and fs ext2 in remove_crypt Oct 7 15:29:33 storageqe-109 systemd[1]: tmp-libblockdev.3wi7grg7mount_test.mount: Deactivated successfully. Oct 7 15:29:33 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c3182939-91eb-4fdd-bfe3-78be2e9ec653. Oct 7 15:29:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/HYZK and fs ext3 in remove_crypt Oct 7 15:29:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/HYZK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.do9c1qedmount_test with fs ext2 Oct 7 15:29:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 15:29:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3f010674-5504-4ba4-b82a-6ac1e26c48d7 r/w without journal. Quota mode: none. Oct 7 15:29:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.do9c1qedmount_test with fs ext2 Oct 7 15:29:59 storageqe-109 systemd[1]: tmp-libblockdev.do9c1qedmount_test.mount: Deactivated successfully. Oct 7 15:30:00 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3f010674-5504-4ba4-b82a-6ac1e26c48d7. INFO: End IO testing with the luks device /dev/mapper/HYZK and fs ext2 in remove_crypt INFO: remove crypt device HYZK Oct 7 15:30:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/HYZK and fs ext2 in remove_crypt Oct 7 15:30:00 storageqe-109 INFO: remove crypt device HYZK cryptsetup luksDump /dev/nvme0n1 -q Oct 7 15:30:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 15:30:10 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 15:30:22 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:30:32 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 15:30:32 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 15:30:32 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 15:30:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device HYZK Oct 7 15:30:54 storageqe-109 INFO: finishe the remove crypt device HYZK cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:30:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:31:05 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:31:06 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_hw_opal #### INFO: #### will start test_hw_rw ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:31:21 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:31:21 storageqe-109 INFO: #### END test_hw_opal #### Oct 7 15:31:21 storageqe-109 INFO: #### will start test_hw_rw ##### Oct 7 15:31:21 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:31:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:31:38 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:31:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:31:49 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:31:59 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 15:31:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:31:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 15:31:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 15:31:59 storageqe-109 stratisd[4947]: [2025-10-07T19:31:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:31:59 storageqe-109 stratisd[4947]: [2025-10-07T19:31:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 Otmq -q --allow-discards Oct 7 15:32:09 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 Otmq -q --allow-discards Oct 7 15:32:12 storageqe-109 stratisd[4947]: [2025-10-07T19:32:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:32:12 storageqe-109 stratisd[4947]: [2025-10-07T19:32:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:32:19 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup luksSuspend Otmq -q Oct 7 15:32:22 storageqe-109 journal: cryptsetup luksSuspend Otmq -q cryptsetup close Otmq -q Oct 7 15:32:32 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32528, 256 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32528 op 0x0:(READ) flags 0x2080700 phys_seg 5 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32784, 256 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32784 op 0x0:(READ) flags 0x2080700 phys_seg 5 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32768, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32768 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32768, async page read Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32769, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32769 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32769, async page read Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32770, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32770 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32770, async page read Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32771, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32771 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32771, async page read Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32772, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32772 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32772, async page read Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32773, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32773 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32773, async page read Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32774, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32774 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32774, async page read Oct 7 15:32:32 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32775, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:32 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32775 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:32:32 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32775, async page read Oct 7 15:32:33 storageqe-109 journal: cryptsetup close Otmq -q Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32760, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32760 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32760, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32761, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32762, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32763, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32764, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32765, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32766, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32767, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32768, lost async page write Oct 7 15:32:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 32769, lost async page write Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32793, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32793 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32794, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32919, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32794 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32919 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32795, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32920, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32795 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32920 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32796, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32953, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32796 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32953 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32797, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 32954, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32797 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32954 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme_log_error: 3830 callbacks suppressed Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51960, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: blk_print_req_error: 3830 callbacks suppressed Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51960 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: buffer_io_error: 19190 callbacks suppressed Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51960, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51961, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51962, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51963, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51964, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51965, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51966, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51967, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51968, lost async page write Oct 7 15:32:48 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 51969, lost async page write Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51993, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51993 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51994, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51994 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51995, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51995 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51996, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51996 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51997, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51997 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51998, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51998 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 51999, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 51999 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 52000, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52000 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:32:48 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 52033, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:48 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52033 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: nvme_log_error: 4131 callbacks suppressed Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72677, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: blk_print_req_error: 4131 callbacks suppressed Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72677 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: buffer_io_error: 20707 callbacks suppressed Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72677, lost async page write Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72678, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72678 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72678, lost async page write Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72679, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72679 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72679, lost async page write Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72680, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72680 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72680, lost async page write Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72681, lost async page write Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72682, lost async page write Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72683, lost async page write Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72684, lost async page write Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72685, lost async page write Oct 7 15:32:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 72686, lost async page write Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72713, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72713 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72714, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72714 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72715, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72715 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72716, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72716 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72717, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72717 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 72718, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 72718 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme_log_error: 4129 callbacks suppressed Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93360, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: blk_print_req_error: 4129 callbacks suppressed Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93360 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: buffer_io_error: 20673 callbacks suppressed Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93360, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93361, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93362, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93363, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93364, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93365, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93366, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93367, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93368, lost async page write Oct 7 15:32:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 93369, lost async page write Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93393 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93394 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93395 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93396 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93397 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93398 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93399 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93400, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93400 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:32:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 93433, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:32:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 93433 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: nvme_log_error: 4132 callbacks suppressed Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114078, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: blk_print_req_error: 4132 callbacks suppressed Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114078 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: buffer_io_error: 20708 callbacks suppressed Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114078, lost async page write Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114079, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114079 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114079, lost async page write Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114080, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114080 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114080, lost async page write Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114081, lost async page write Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114082, lost async page write Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114083, lost async page write Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114084, lost async page write Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114085, lost async page write Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114086, lost async page write Oct 7 15:33:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 114087, lost async page write Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114113, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114113 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114114, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114114 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114115, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114115 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114116, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114116 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114117, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114117 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114118, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114118 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 114119, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 114119 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: nvme_log_error: 4131 callbacks suppressed Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134795, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: blk_print_req_error: 4131 callbacks suppressed Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134795 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: buffer_io_error: 20707 callbacks suppressed Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134795, lost async page write Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134796, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134796 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134796, lost async page write Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134797, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134797 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134797, lost async page write Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134798, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134798 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134798, lost async page write Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134799, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134799 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134799, lost async page write Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134800, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134800 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134800, lost async page write Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134801, lost async page write Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134802, lost async page write Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134803, lost async page write Oct 7 15:33:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 134804, lost async page write Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134833, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134833 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134834, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134834 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134835, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134835 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 134836, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 134836 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme_log_error: 4131 callbacks suppressed Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155480, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: blk_print_req_error: 4131 callbacks suppressed Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155480 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: buffer_io_error: 20675 callbacks suppressed Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155480, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155481, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155482, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155483, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155484, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155485, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155486, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155487, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155488, lost async page write Oct 7 15:33:14 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 155489, lost async page write Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155513, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155513 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155514, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155514 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155515, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155515 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155516, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155516 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155517, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155517 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155518, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155518 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155519, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155519 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155520, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155520 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:33:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 155553, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 155553 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: nvme_log_error: 4352 callbacks suppressed Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178576, 16 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: blk_print_req_error: 4352 callbacks suppressed Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178576 op 0x1:(WRITE) flags 0x2100000 phys_seg 16 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: buffer_io_error: 23086 callbacks suppressed Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178576, lost async page write Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178577, lost async page write Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178578, lost async page write Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178592, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178579, lost async page write Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178592 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178580, lost async page write Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178592, lost async page write Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178581, lost async page write Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178593, lost async page write Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178582, lost async page write Oct 7 15:33:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 178594, lost async page write Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178832, 16 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178625, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178832 op 0x1:(WRITE) flags 0x2100000 phys_seg 16 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178625 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 179088, 16 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 178626, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 179088 op 0x1:(WRITE) flags 0x2100000 phys_seg 16 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 178626 op 0x1:(WRITE) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 179344, 16 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 179600, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 179600 op 0x1:(WRITE) flags 0x2104000 phys_seg 33 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 179633, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 179633 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 179634, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 179634 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 179635 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: nvme_log_error: 4115 callbacks suppressed Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 200834, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 200835, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: blk_print_req_error: 4116 callbacks suppressed Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 200835 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 200968, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: buffer_io_error: 22249 callbacks suppressed Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 200835, lost async page write Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 200968 op 0x1:(WRITE) flags 0x2004800 phys_seg 33 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 200836, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 201884, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201884 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201884, lost async page write Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 201885, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201885 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201885, lost async page write Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 200968, lost async page write Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 201886, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201886 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201886, lost async page write Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 201887, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201887 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201887, lost async page write Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 201888, 33 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201888 op 0x1:(WRITE) flags 0x2104000 phys_seg 33 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201888, lost async page write Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201889, lost async page write Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201890, lost async page write Oct 7 15:33:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 201891, lost async page write Oct 7 15:33:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x1) @ LBA 201921, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201921 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201922 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 201923 op 0x1:(WRITE) flags 0x2100000 phys_seg 1 prio class 0 Oct 7 15:33:26 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:33:26 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 15:33:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:33:38 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:33:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_hw_rw #### INFO: #### will start test_hw_opal_header ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:33:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:33:54 storageqe-109 INFO: #### END test_hw_rw #### Oct 7 15:33:54 storageqe-109 INFO: #### will start test_hw_opal_header ##### Oct 7 15:33:54 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:34:01 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:34:11 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:34:12 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' --header '/tmp/testheaderUEA' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:34:22 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderUEA' luksFormat /dev/nvme0n1 -q --hw-opal cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q Oct 7 15:34:42 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q Oct 7 15:34:52 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderUEA' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:34:52 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '8192' --pbkdf-force-iterations '1000' --header '/tmp/testheaderUEA' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:34:52 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 15:34:53 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 15:34:53 storageqe-109 kernel: nvme_log_error: 1168 callbacks suppressed Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: blk_print_req_error: 1167 callbacks suppressed Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: buffer_io_error: 4353 callbacks suppressed Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 0, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 1, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 1 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 1, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 2, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 2 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 2, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 4, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 4 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 4, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 5, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 5 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 5, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 6, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 6 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 6, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 7, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 7 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 7, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 0, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 1, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:34:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 1 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:34:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 1, async page read Oct 7 15:34:53 storageqe-109 kernel: nvme0n1: unable to read partition table cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q Oct 7 15:35:06 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderUEA' --sector-size '512' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:35:17 storageqe-109 journal: cryptsetup --type 'luks2' --pbkdf 'pbkdf2' --align-payload '0' --pbkdf-force-iterations '1000' --header '/tmp/testheaderUEA' --sector-size '512' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 15:35:17 storageqe-109 kernel: nvme_log_error: 1420 callbacks suppressed Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: blk_print_req_error: 1420 callbacks suppressed Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: buffer_io_error: 1406 callbacks suppressed Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 15:35:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:35:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 15:35:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q Oct 7 15:35:30 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q cryptsetup --header '/tmp/testheaderUEA' open /dev/nvme0n1 jvzb -q Oct 7 15:35:40 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' open /dev/nvme0n1 jvzb -q Oct 7 15:35:47 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --header '/tmp/testheaderUEA' luksSuspend jvzb -q Oct 7 15:35:50 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksSuspend jvzb -q cryptsetup --header '/tmp/testheaderUEA' luksResume jvzb -q Oct 7 15:36:01 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksResume jvzb -q cryptsetup --header '/tmp/testheaderUEA' luksSuspend jvzb -q Oct 7 15:36:11 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksSuspend jvzb -q cryptsetup luksResume jvzb -q Oct 7 15:36:22 storageqe-109 journal: cryptsetup luksResume jvzb -q Oct 7 15:36:22 storageqe-109 kernel: nvme_log_error: 149 callbacks suppressed Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: blk_print_req_error: 149 callbacks suppressed Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 0, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 0 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 32, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 32 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 64, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 64 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 128, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 128 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 256, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 256 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 512, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 512 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 1024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 1024 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 2048, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 2048 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 Oct 7 15:36:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 4096, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:36:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 4096 op 0x0:(READ) flags 0x2000800 phys_seg 1 prio class 0 cryptsetup --header '/tmp/testheaderUEA' luksResume jvzb -q Oct 7 15:36:32 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksResume jvzb -q INFO: start IO testing with the luks device /dev/mapper/jvzb and fs xfs in remove_crypt Oct 7 15:36:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jvzb and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.5t4tn_3imount_test with fs xfs Oct 7 15:36:53 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f6b97864-9d3f-40e1-9aa1-91c5e4183c6d Oct 7 15:36:53 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:36:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5t4tn_3imount_test with fs xfs Oct 7 15:36:58 storageqe-109 systemd[1]: tmp-libblockdev.5t4tn_3imount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/jvzb and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/jvzb and fs ext4 in remove_crypt Oct 7 15:36:58 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f6b97864-9d3f-40e1-9aa1-91c5e4183c6d Oct 7 15:36:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jvzb and fs xfs in remove_crypt Oct 7 15:36:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jvzb and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i_2fjegymount_test with fs ext4 Oct 7 15:37:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem eb5a049a-7800-4c68-a501-02ddbdf0b7d7 r/w with ordered data mode. Quota mode: none. Oct 7 15:37:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i_2fjegymount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/jvzb and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/jvzb and fs ext3 in remove_crypt Oct 7 15:37:14 storageqe-109 systemd[1]: tmp-libblockdev.i_2fjegymount_test.mount: Deactivated successfully. Oct 7 15:37:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem eb5a049a-7800-4c68-a501-02ddbdf0b7d7. Oct 7 15:37:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jvzb and fs ext4 in remove_crypt Oct 7 15:37:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jvzb and fs ext3 in remove_crypt Oct 7 15:37:35 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 15:37:35 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e0a9bc0c-88f0-464e-9c50-da7a31a542a7 r/w with ordered data mode. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.bb4p1ptgmount_test with fs ext3 Oct 7 15:37:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bb4p1ptgmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/jvzb and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/jvzb and fs ext2 in remove_crypt Oct 7 15:37:40 storageqe-109 systemd[1]: tmp-libblockdev.bb4p1ptgmount_test.mount: Deactivated successfully. Oct 7 15:37:40 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e0a9bc0c-88f0-464e-9c50-da7a31a542a7. Oct 7 15:37:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jvzb and fs ext3 in remove_crypt Oct 7 15:37:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/jvzb and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6dgauozymount_test with fs ext2 Oct 7 15:38:01 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 15:38:01 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4883977e-1c2a-4b56-b9ce-dc6090e43e56 r/w without journal. Quota mode: none. Oct 7 15:38:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6dgauozymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/jvzb and fs ext2 in remove_crypt INFO: remove crypt device jvzb Oct 7 15:38:06 storageqe-109 systemd[1]: tmp-libblockdev.6dgauozymount_test.mount: Deactivated successfully. Oct 7 15:38:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4883977e-1c2a-4b56-b9ce-dc6090e43e56. Oct 7 15:38:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/jvzb and fs ext2 in remove_crypt Oct 7 15:38:06 storageqe-109 INFO: remove crypt device jvzb cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q Oct 7 15:38:06 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q cryptsetup --header '/tmp/testheaderUEA' erase /dev/nvme0n1 -q Oct 7 15:38:16 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' erase /dev/nvme0n1 -q cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q Oct 7 15:38:28 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:38:38 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 15:38:38 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 15:38:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q Oct 7 15:38:50 storageqe-109 journal: cryptsetup --header '/tmp/testheaderUEA' luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device jvzb Oct 7 15:39:00 storageqe-109 INFO: finishe the remove crypt device jvzb cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:39:01 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:39:12 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:39:12 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_hw_opal_header #### INFO: #### will start test_partitions_in_same_disk ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:39:27 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:39:27 storageqe-109 INFO: #### END test_hw_opal_header #### Oct 7 15:39:27 storageqe-109 INFO: #### will start test_partitions_in_same_disk ##### Oct 7 15:39:27 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:39:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:39:44 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:39:45 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:39:55 storageqe-109 kernel: nvme0n1: Oct 7 15:39:55 storageqe-109 kernel: nvme0n1: p1 Oct 7 15:39:55 storageqe-109 kernel: nvme0n1: p1 p2 Oct 7 15:39:55 storageqe-109 kernel: nvme0n1: p1 p2 p3 cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal Oct 7 15:39:55 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 Oct 7 15:39:55 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 p7 Oct 7 15:39:56 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8 Oct 7 15:39:56 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal Oct 7 15:40:05 storageqe-109 kernel: nvme_log_error: 1 callbacks suppressed Oct 7 15:40:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:05 storageqe-109 kernel: blk_print_req_error: 1 callbacks suppressed Oct 7 15:40:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:05 storageqe-109 kernel: buffer_io_error: 142 callbacks suppressed Oct 7 15:40:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:40:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:40:06 storageqe-109 stratisd[4947]: [2025-10-07T19:40:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:40:06 storageqe-109 stratisd[4947]: [2025-10-07T19:40:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:40:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 7 15:40:16 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 7 15:40:25 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310464, async page read Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:40:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:40:25 storageqe-109 stratisd[4947]: [2025-10-07T19:40:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:40:25 storageqe-109 stratisd[4947]: [2025-10-07T19:40:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 7 15:40:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 7 15:40:35 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 7 15:40:44 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:40:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:44 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:40:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310464, async page read Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:40:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:40:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:40:45 storageqe-109 stratisd[4947]: [2025-10-07T19:40:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:40:45 storageqe-109 stratisd[4947]: [2025-10-07T19:40:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 7 15:40:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 7 15:40:55 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 7 15:41:04 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310464, async page read Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:41:04 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:04 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:41:04 storageqe-109 stratisd[4947]: [2025-10-07T19:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:41:04 storageqe-109 stratisd[4947]: [2025-10-07T19:41:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 7 15:41:04 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 7 15:41:14 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 7 15:41:23 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:41:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:23 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:41:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310464, async page read Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:41:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:41:24 storageqe-109 stratisd[4947]: [2025-10-07T19:41:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:41:24 storageqe-109 stratisd[4947]: [2025-10-07T19:41:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 7 15:41:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 7 15:41:34 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 7 15:41:43 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310464, async page read Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:41:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:41:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:41:43 storageqe-109 stratisd[4947]: [2025-10-07T19:41:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:41:43 storageqe-109 stratisd[4947]: [2025-10-07T19:41:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 7 15:41:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 7 15:41:53 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 7 15:42:02 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:42:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:02 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:42:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:02 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:02 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:02 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:42:02 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310464, async page read Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:42:03 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:03 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:42:03 storageqe-109 stratisd[4947]: [2025-10-07T19:42:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:42:03 storageqe-109 stratisd[4947]: [2025-10-07T19:42:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 7 15:42:03 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 7 15:42:13 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 7 15:42:22 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310464, async page read Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:42:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:42:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:42:22 storageqe-109 stratisd[4947]: [2025-10-07T19:42:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:42:22 storageqe-109 stratisd[4947]: [2025-10-07T19:42:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 7 15:42:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:42:33 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q cryptsetup erase /dev/nvme0n1p1 -q Oct 7 15:42:43 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p1 -q Oct 7 15:42:43 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:42:53 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p2 -q Oct 7 15:43:03 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:43:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q cryptsetup erase /dev/nvme0n1p2 -q Oct 7 15:43:13 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p2 -q cryptsetup luksDump /dev/nvme0n1p2 -q Oct 7 15:43:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p3 -q Oct 7 15:43:34 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:43:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q cryptsetup erase /dev/nvme0n1p3 -q Oct 7 15:43:44 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p3 -q cryptsetup luksDump /dev/nvme0n1p3 -q Oct 7 15:43:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p4 -q Oct 7 15:44:05 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:44:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q cryptsetup erase /dev/nvme0n1p4 -q Oct 7 15:44:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p4 -q cryptsetup luksDump /dev/nvme0n1p4 -q Oct 7 15:44:26 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p5 -q Oct 7 15:44:36 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:44:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q cryptsetup erase /dev/nvme0n1p5 -q Oct 7 15:44:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p5 -q cryptsetup luksDump /dev/nvme0n1p5 -q Oct 7 15:44:57 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p6 -q Oct 7 15:45:07 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:45:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q cryptsetup erase /dev/nvme0n1p6 -q Oct 7 15:45:17 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p6 -q cryptsetup luksDump /dev/nvme0n1p6 -q Oct 7 15:45:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p7 -q Oct 7 15:45:38 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:45:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q cryptsetup erase /dev/nvme0n1p7 -q Oct 7 15:45:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p7 -q cryptsetup luksDump /dev/nvme0n1p7 -q Oct 7 15:45:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q INFO: finishe the remove crypt device None cryptsetup luksDump /dev/nvme0n1p8 -q Oct 7 15:46:08 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:46:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q cryptsetup erase /dev/nvme0n1p8 -q Oct 7 15:46:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p8 -q cryptsetup luksDump /dev/nvme0n1p8 -q Oct 7 15:46:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q INFO: finishe the remove crypt device None Oct 7 15:46:39 storageqe-109 INFO: finishe the remove crypt device None Oct 7 15:46:40 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 7 15:46:42 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 7 15:46:42 storageqe-109 kernel: nvme0n1: p3 p4 p5 p6 p7 p8 Oct 7 15:46:43 storageqe-109 kernel: nvme0n1: p3 p4 p5 p6 p7 p8 Oct 7 15:46:43 storageqe-109 kernel: nvme0n1: p4 p5 p6 p7 p8 Oct 7 15:46:44 storageqe-109 kernel: nvme0n1: p4 p5 p6 p7 p8 Oct 7 15:46:45 storageqe-109 kernel: nvme0n1: p4 p6 p7 p8 Oct 7 15:46:46 storageqe-109 kernel: nvme0n1: p4 p7 p8 Oct 7 15:46:47 storageqe-109 kernel: nvme0n1: p4 p8 cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:46:48 storageqe-109 kernel: nvme0n1: p4 Oct 7 15:46:48 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 15:46:48 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 15:46:48 storageqe-109 kernel: nvme0n1: p4 Oct 7 15:46:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:47:01 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:47:12 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:47:12 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_partitions_in_same_disk #### INFO: #### will start test_upstream_opal_test ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:47:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:47:28 storageqe-109 INFO: #### END test_partitions_in_same_disk #### Oct 7 15:47:28 storageqe-109 INFO: #### will start test_upstream_opal_test ##### Oct 7 15:47:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:47:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:47:44 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:47:45 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:47:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:48:07 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:48:07 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_upstream_opal_test #### INFO: #### will start test_hw_opal_tang ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:48:22 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 15:48:22 storageqe-109 INFO: #### END test_upstream_opal_test #### Oct 7 15:48:23 storageqe-109 INFO: #### will start test_hw_opal_tang ##### Oct 7 15:48:23 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:48:29 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:48:39 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:48:40 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 15:48:50 storageqe-109 systemd[1]: Reload requested from client PID 1915000 ('systemctl') (unit session-6.scope)... Oct 7 15:48:50 storageqe-109 systemd[1]: Reloading... Oct 7 15:48:50 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 7 15:48:50 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 7 15:48:50 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 7 15:48:50 storageqe-109 systemd[1]: Reloading finished in 146 ms. Oct 7 15:48:50 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 15:48:50 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 15:48:50 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 15:48:50 storageqe-109 kernel: nvme0n1: Oct 7 15:48:50 storageqe-109 kernel: nvme0n1: p1 Oct 7 15:48:51 storageqe-109 kernel: nvme0n1: p1 p2 Oct 7 15:48:51 storageqe-109 kernel: nvme0n1: p1 p2 p3 Oct 7 15:48:51 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 Oct 7 15:48:51 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 Oct 7 15:48:51 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 Oct 7 15:48:51 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 p7 Oct 7 15:48:51 storageqe-109 kernel: nvme0n1: p1 p2 p3 p4 p5 p6 p7 p8 cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal Oct 7 15:48:51 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p1 -q --hw-opal Oct 7 15:49:01 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:01 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:01 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:01 storageqe-109 stratisd[4947]: [2025-10-07T19:49:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:01 storageqe-109 stratisd[4947]: [2025-10-07T19:49:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:49:01 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:13 storageqe-109 systemd[1]: Started tangd@17-10.73.194.89:80-10.73.194.89:38026.service - Tang Server (10.73.194.89:38026). Oct 7 15:49:13 storageqe-109 tangd[1916134]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:49:13 storageqe-109 systemd[1]: tangd@17-10.73.194.89:80-10.73.194.89:38026.service: Deactivated successfully. Oct 7 15:49:17 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:49:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:17 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:49:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487680, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487680 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:17 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:49:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:49:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487792, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487792 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:49:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10485760, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10485760 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310464, async page read Oct 7 15:49:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 10487800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 10487800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:18 storageqe-109 stratisd[4947]: [2025-10-07T19:49:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:18 storageqe-109 stratisd[4947]: [2025-10-07T19:49:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310704, async page read Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310718, async page read Oct 7 15:49:18 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p1, logical block 1310719, async page read Oct 7 15:49:18 storageqe-109 systemd[1]: Started tangd@18-10.73.194.89:80-10.73.194.89:41870.service - Tang Server (10.73.194.89:41870). Oct 7 15:49:18 storageqe-109 tangd[1916630]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:49:18 storageqe-109 systemd[1]: tangd@18-10.73.194.89:80-10.73.194.89:41870.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 7 15:49:20 storageqe-109 stratisd[4947]: [2025-10-07T19:49:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:20 storageqe-109 stratisd[4947]: [2025-10-07T19:49:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:20 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p2 -q --hw-opal Oct 7 15:49:29 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:49:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:29 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:49:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310464, async page read Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:30 storageqe-109 stratisd[4947]: [2025-10-07T19:49:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:30 storageqe-109 stratisd[4947]: [2025-10-07T19:49:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 7 15:49:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:42 storageqe-109 systemd[1]: Started tangd@19-10.73.194.89:80-10.73.194.89:59122.service - Tang Server (10.73.194.89:59122). Oct 7 15:49:42 storageqe-109 tangd[1917877]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:49:42 storageqe-109 systemd[1]: tangd@19-10.73.194.89:80-10.73.194.89:59122.service: Deactivated successfully. Oct 7 15:49:46 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975488, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975488 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975600, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975600 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20973568, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20973568 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310464, async page read Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 20975608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 20975608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:46 storageqe-109 stratisd[4947]: [2025-10-07T19:49:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:46 storageqe-109 stratisd[4947]: [2025-10-07T19:49:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310704, async page read Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310718, async page read Oct 7 15:49:46 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p2, logical block 1310719, async page read Oct 7 15:49:46 storageqe-109 systemd[1]: Started tangd@20-10.73.194.89:80-10.73.194.89:46636.service - Tang Server (10.73.194.89:46636). Oct 7 15:49:46 storageqe-109 tangd[1918375]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:49:46 storageqe-109 systemd[1]: tangd@20-10.73.194.89:80-10.73.194.89:46636.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 7 15:49:49 storageqe-109 stratisd[4947]: [2025-10-07T19:49:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:49 storageqe-109 stratisd[4947]: [2025-10-07T19:49:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:49 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p3 -q --hw-opal Oct 7 15:49:58 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:49:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:58 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:49:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:58 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:49:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 7 15:49:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 7 15:49:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:49:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:49:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310464, async page read Oct 7 15:49:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:49:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:49:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:49:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:49:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:49:59 storageqe-109 stratisd[4947]: [2025-10-07T19:49:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:59 storageqe-109 stratisd[4947]: [2025-10-07T19:49:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:49:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 7 15:49:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 7 15:49:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:50:11 storageqe-109 systemd[1]: Started tangd@21-10.73.194.89:80-10.73.194.89:54380.service - Tang Server (10.73.194.89:54380). Oct 7 15:50:11 storageqe-109 tangd[1919638]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:50:11 storageqe-109 systemd[1]: tangd@21-10.73.194.89:80-10.73.194.89:54380.service: Deactivated successfully. Oct 7 15:50:15 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463296, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463296 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463408, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463408 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31461376, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31461376 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310464, async page read Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:50:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 31463416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 31463416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:50:15 storageqe-109 stratisd[4947]: [2025-10-07T19:50:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:15 storageqe-109 stratisd[4947]: [2025-10-07T19:50:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310704, async page read Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310718, async page read Oct 7 15:50:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p3, logical block 1310719, async page read Oct 7 15:50:15 storageqe-109 systemd[1]: Started tangd@22-10.73.194.89:80-10.73.194.89:54386.service - Tang Server (10.73.194.89:54386). Oct 7 15:50:15 storageqe-109 tangd[1920134]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:50:15 storageqe-109 systemd[1]: tangd@22-10.73.194.89:80-10.73.194.89:54386.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 7 15:50:18 storageqe-109 stratisd[4947]: [2025-10-07T19:50:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:18 storageqe-109 stratisd[4947]: [2025-10-07T19:50:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:18 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p4 -q --hw-opal Oct 7 15:50:27 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310464, async page read Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:27 storageqe-109 stratisd[4947]: [2025-10-07T19:50:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:27 storageqe-109 stratisd[4947]: [2025-10-07T19:50:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 7 15:50:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:39 storageqe-109 systemd[1]: Started tangd@23-10.73.194.89:80-10.73.194.89:34086.service - Tang Server (10.73.194.89:34086). Oct 7 15:50:39 storageqe-109 tangd[1921397]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:50:39 storageqe-109 systemd[1]: tangd@23-10.73.194.89:80-10.73.194.89:34086.service: Deactivated successfully. Oct 7 15:50:44 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951104, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951104 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951216, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951216 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41949184, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41949184 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310464, async page read Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:44 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 41951224, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:44 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 41951224 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:44 storageqe-109 stratisd[4947]: [2025-10-07T19:50:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:44 storageqe-109 stratisd[4947]: [2025-10-07T19:50:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310704, async page read Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310718, async page read Oct 7 15:50:44 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p4, logical block 1310719, async page read Oct 7 15:50:44 storageqe-109 systemd[1]: Started tangd@24-10.73.194.89:80-10.73.194.89:34102.service - Tang Server (10.73.194.89:34102). Oct 7 15:50:44 storageqe-109 tangd[1921895]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:50:44 storageqe-109 systemd[1]: tangd@24-10.73.194.89:80-10.73.194.89:34102.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 7 15:50:46 storageqe-109 stratisd[4947]: [2025-10-07T19:50:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:46 storageqe-109 stratisd[4947]: [2025-10-07T19:50:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:47 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p5 -q --hw-opal Oct 7 15:50:56 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310464, async page read Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:50:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:50:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:50:56 storageqe-109 stratisd[4947]: [2025-10-07T19:50:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:56 storageqe-109 stratisd[4947]: [2025-10-07T19:50:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 7 15:50:56 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:51:08 storageqe-109 systemd[1]: Started tangd@25-10.73.194.89:80-10.73.194.89:45524.service - Tang Server (10.73.194.89:45524). Oct 7 15:51:08 storageqe-109 tangd[1923140]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:51:08 storageqe-109 systemd[1]: tangd@25-10.73.194.89:80-10.73.194.89:45524.service: Deactivated successfully. Oct 7 15:51:12 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:51:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:12 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:51:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52438912, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52438912 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:12 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:51:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 7 15:51:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439024, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439024 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 7 15:51:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:51:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52436992, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52436992 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310464, async page read Oct 7 15:51:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:51:13 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 52439032, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:13 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 52439032 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:51:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:51:13 storageqe-109 stratisd[4947]: [2025-10-07T19:51:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:13 storageqe-109 stratisd[4947]: [2025-10-07T19:51:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310704, async page read Oct 7 15:51:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310718, async page read Oct 7 15:51:13 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p5, logical block 1310719, async page read Oct 7 15:51:13 storageqe-109 systemd[1]: Started tangd@26-10.73.194.89:80-10.73.194.89:45536.service - Tang Server (10.73.194.89:45536). Oct 7 15:51:13 storageqe-109 tangd[1923636]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:51:13 storageqe-109 systemd[1]: tangd@26-10.73.194.89:80-10.73.194.89:45536.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 7 15:51:15 storageqe-109 stratisd[4947]: [2025-10-07T19:51:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:15 storageqe-109 stratisd[4947]: [2025-10-07T19:51:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:15 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p6 -q --hw-opal Oct 7 15:51:24 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:51:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:24 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:51:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310464, async page read Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:25 storageqe-109 stratisd[4947]: [2025-10-07T19:51:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:25 storageqe-109 stratisd[4947]: [2025-10-07T19:51:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 7 15:51:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:37 storageqe-109 systemd[1]: Started tangd@27-10.73.194.89:80-10.73.194.89:56426.service - Tang Server (10.73.194.89:56426). Oct 7 15:51:37 storageqe-109 tangd[1924883]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:51:37 storageqe-109 systemd[1]: tangd@27-10.73.194.89:80-10.73.194.89:56426.service: Deactivated successfully. Oct 7 15:51:41 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926720, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926720 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926832, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926832 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62924800, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62924800 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310464, async page read Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:41 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 62926840, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:41 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 62926840 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:41 storageqe-109 stratisd[4947]: [2025-10-07T19:51:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:41 storageqe-109 stratisd[4947]: [2025-10-07T19:51:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310704, async page read Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310718, async page read Oct 7 15:51:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p6, logical block 1310719, async page read Oct 7 15:51:41 storageqe-109 systemd[1]: Started tangd@28-10.73.194.89:80-10.73.194.89:56432.service - Tang Server (10.73.194.89:56432). Oct 7 15:51:41 storageqe-109 tangd[1925380]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:51:41 storageqe-109 systemd[1]: tangd@28-10.73.194.89:80-10.73.194.89:56432.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 7 15:51:44 storageqe-109 stratisd[4947]: [2025-10-07T19:51:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:44 storageqe-109 stratisd[4947]: [2025-10-07T19:51:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:44 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p7 -q --hw-opal Oct 7 15:51:53 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:51:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:53 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:51:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:53 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:51:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 7 15:51:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 7 15:51:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:53 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:51:53 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:53 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:51:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310464, async page read Oct 7 15:51:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:51:54 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:51:54 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:51:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:51:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:51:54 storageqe-109 stratisd[4947]: [2025-10-07T19:51:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:54 storageqe-109 stratisd[4947]: [2025-10-07T19:51:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:51:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 7 15:51:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 7 15:51:54 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:52:06 storageqe-109 systemd[1]: Started tangd@29-10.73.194.89:80-10.73.194.89:58984.service - Tang Server (10.73.194.89:58984). Oct 7 15:52:06 storageqe-109 tangd[1926627]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:52:06 storageqe-109 systemd[1]: tangd@29-10.73.194.89:80-10.73.194.89:58984.service: Deactivated successfully. Oct 7 15:52:10 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414528, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414528 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414640, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414640 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73412608, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73412608 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310464, async page read Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:52:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 73414648, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 73414648 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:52:10 storageqe-109 stratisd[4947]: [2025-10-07T19:52:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:10 storageqe-109 stratisd[4947]: [2025-10-07T19:52:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310704, async page read Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310718, async page read Oct 7 15:52:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p7, logical block 1310719, async page read Oct 7 15:52:10 storageqe-109 systemd[1]: Started tangd@30-10.73.194.89:80-10.73.194.89:58988.service - Tang Server (10.73.194.89:58988). Oct 7 15:52:10 storageqe-109 tangd[1927123]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:52:10 storageqe-109 systemd[1]: tangd@30-10.73.194.89:80-10.73.194.89:58988.service: Deactivated successfully. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 7 15:52:13 storageqe-109 stratisd[4947]: [2025-10-07T19:52:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:13 storageqe-109 stratisd[4947]: [2025-10-07T19:52:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:13 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1p8 -q --hw-opal Oct 7 15:52:22 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310464, async page read Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:22 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:22 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:22 storageqe-109 stratisd[4947]: [2025-10-07T19:52:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:22 storageqe-109 stratisd[4947]: [2025-10-07T19:52:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 7 15:52:22 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:34 storageqe-109 systemd[1]: Started tangd@31-10.73.194.89:80-10.73.194.89:40270.service - Tang Server (10.73.194.89:40270). Oct 7 15:52:34 storageqe-109 tangd[1928370]: 10.73.194.89 GET /adv/ => 200 (../src/tangd.c:97) Oct 7 15:52:34 storageqe-109 systemd[1]: tangd@31-10.73.194.89:80-10.73.194.89:40270.service: Deactivated successfully. Oct 7 15:52:38 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 15:52:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:38 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 15:52:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902336, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902336 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902448, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902448 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83900416, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83900416 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310464, async page read Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:39 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 83902456, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 15:52:39 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 83902456 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:39 storageqe-109 stratisd[4947]: [2025-10-07T19:52:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:39 storageqe-109 stratisd[4947]: [2025-10-07T19:52:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310704, async page read Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310718, async page read Oct 7 15:52:39 storageqe-109 kernel: Buffer I/O error on dev nvme0n1p8, logical block 1310719, async page read Oct 7 15:52:39 storageqe-109 systemd[1]: Started tangd@32-10.73.194.89:80-10.73.194.89:35670.service - Tang Server (10.73.194.89:35670). Oct 7 15:52:39 storageqe-109 tangd[1928866]: 10.73.194.89 POST /rec/l88sybXh7BHiOUXdjpiA2zUpnfNmYWEvntA5BeRRdjc => 200 (../src/tangd.c:181) Oct 7 15:52:39 storageqe-109 systemd[1]: tangd@32-10.73.194.89:80-10.73.194.89:35670.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/GpTj and fs xfs in remove_crypt Oct 7 15:52:41 storageqe-109 stratisd[4947]: [2025-10-07T19:52:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:41 storageqe-109 stratisd[4947]: [2025-10-07T19:52:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 15:52:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GpTj and fs xfs in remove_crypt Oct 7 15:52:43 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.de0g_r5cmount_test with fs xfs Oct 7 15:52:52 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 7585f823-a063-47fc-8e3b-47b16dae9e04 Oct 7 15:52:52 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 15:52:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.de0g_r5cmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/GpTj and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/GpTj and fs ext4 in remove_crypt Oct 7 15:52:57 storageqe-109 systemd[1]: tmp-libblockdev.de0g_r5cmount_test.mount: Deactivated successfully. Oct 7 15:52:57 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 7585f823-a063-47fc-8e3b-47b16dae9e04 Oct 7 15:52:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GpTj and fs xfs in remove_crypt Oct 7 15:52:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GpTj and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._g4h1gi0mount_test with fs ext4 Oct 7 15:53:07 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem cf6f3688-eb05-4310-ba91-fb37a9029924 r/w with ordered data mode. Quota mode: none. Oct 7 15:53:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev._g4h1gi0mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/GpTj and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/GpTj and fs ext3 in remove_crypt Oct 7 15:53:12 storageqe-109 systemd[1]: tmp-libblockdev._g4h1gi0mount_test.mount: Deactivated successfully. Oct 7 15:53:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem cf6f3688-eb05-4310-ba91-fb37a9029924. Oct 7 15:53:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GpTj and fs ext4 in remove_crypt Oct 7 15:53:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GpTj and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6ovxrlp2mount_test with fs ext3 Oct 7 15:53:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 15:53:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0868372b-ff00-439b-8d5f-44148fcda016 r/w with ordered data mode. Quota mode: none. Oct 7 15:53:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6ovxrlp2mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/GpTj and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/GpTj and fs ext2 in remove_crypt Oct 7 15:53:27 storageqe-109 systemd[1]: tmp-libblockdev.6ovxrlp2mount_test.mount: Deactivated successfully. Oct 7 15:53:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0868372b-ff00-439b-8d5f-44148fcda016. Oct 7 15:53:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GpTj and fs ext3 in remove_crypt Oct 7 15:53:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/GpTj and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gly9taqgmount_test with fs ext2 Oct 7 15:53:37 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 15:53:37 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 03743b25-ae68-4750-a05c-dbb38afb1595 r/w without journal. Quota mode: none. Oct 7 15:53:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gly9taqgmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/GpTj and fs ext2 in remove_crypt INFO: remove crypt device GpTj Oct 7 15:53:42 storageqe-109 systemd[1]: tmp-libblockdev.gly9taqgmount_test.mount: Deactivated successfully. Oct 7 15:53:42 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 03743b25-ae68-4750-a05c-dbb38afb1595. Oct 7 15:53:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/GpTj and fs ext2 in remove_crypt Oct 7 15:53:42 storageqe-109 INFO: remove crypt device GpTj cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:53:42 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q cryptsetup erase /dev/nvme0n1p1 -q Oct 7 15:53:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p1 -q cryptsetup luksDump /dev/nvme0n1p1 -q Oct 7 15:54:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p1 -q INFO: finishe the remove crypt device GpTj INFO: start IO testing with the luks device /dev/mapper/lISM and fs xfs in remove_crypt Oct 7 15:54:13 storageqe-109 INFO: finishe the remove crypt device GpTj Oct 7 15:54:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/lISM and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2cixdvfnmount_test with fs xfs Oct 7 15:54:23 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 3c6777db-00d2-4475-9721-b76b58e84c0a Oct 7 15:54:23 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 15:54:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2cixdvfnmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/lISM and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/lISM and fs ext4 in remove_crypt Oct 7 15:54:28 storageqe-109 systemd[1]: tmp-libblockdev.2cixdvfnmount_test.mount: Deactivated successfully. Oct 7 15:54:28 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 3c6777db-00d2-4475-9721-b76b58e84c0a Oct 7 15:54:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/lISM and fs xfs in remove_crypt Oct 7 15:54:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/lISM and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2drwnycxmount_test with fs ext4 Oct 7 15:54:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 844ed825-19ee-4f9b-82fe-6f0c7c71d580 r/w with ordered data mode. Quota mode: none. Oct 7 15:54:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2drwnycxmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/lISM and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/lISM and fs ext3 in remove_crypt Oct 7 15:54:43 storageqe-109 systemd[1]: tmp-libblockdev.2drwnycxmount_test.mount: Deactivated successfully. Oct 7 15:54:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 844ed825-19ee-4f9b-82fe-6f0c7c71d580. Oct 7 15:54:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/lISM and fs ext4 in remove_crypt Oct 7 15:54:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/lISM and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1gb4rkc0mount_test with fs ext3 Oct 7 15:54:53 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 15:54:53 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5b25d869-b370-4fcf-805a-f254315791a0 r/w with ordered data mode. Quota mode: none. Oct 7 15:54:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1gb4rkc0mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/lISM and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/lISM and fs ext2 in remove_crypt Oct 7 15:54:58 storageqe-109 systemd[1]: tmp-libblockdev.1gb4rkc0mount_test.mount: Deactivated successfully. Oct 7 15:54:58 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5b25d869-b370-4fcf-805a-f254315791a0. Oct 7 15:54:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/lISM and fs ext3 in remove_crypt Oct 7 15:54:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/lISM and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2sa7e51amount_test with fs ext2 Oct 7 15:55:08 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 15:55:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 61bd8c15-499b-4c41-9a23-4132ae0027e7 r/w without journal. Quota mode: none. Oct 7 15:55:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2sa7e51amount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/lISM and fs ext2 in remove_crypt INFO: remove crypt device lISM Oct 7 15:55:13 storageqe-109 systemd[1]: tmp-libblockdev.2sa7e51amount_test.mount: Deactivated successfully. Oct 7 15:55:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 61bd8c15-499b-4c41-9a23-4132ae0027e7. Oct 7 15:55:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/lISM and fs ext2 in remove_crypt Oct 7 15:55:13 storageqe-109 INFO: remove crypt device lISM cryptsetup luksDump /dev/nvme0n1p2 -q Oct 7 15:55:14 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q cryptsetup erase /dev/nvme0n1p2 -q Oct 7 15:55:24 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p2 -q cryptsetup luksDump /dev/nvme0n1p2 -q Oct 7 15:55:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p2 -q INFO: finishe the remove crypt device lISM INFO: start IO testing with the luks device /dev/mapper/oCpT and fs xfs in remove_crypt Oct 7 15:55:44 storageqe-109 INFO: finishe the remove crypt device lISM Oct 7 15:55:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oCpT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.35j0ltybmount_test with fs xfs Oct 7 15:55:55 storageqe-109 kernel: XFS (dm-5): Mounting V5 Filesystem 1334920b-00f1-40e2-8b2d-2075c369ed07 Oct 7 15:55:55 storageqe-109 kernel: XFS (dm-5): Ending clean mount Oct 7 15:55:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.35j0ltybmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/oCpT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oCpT and fs ext4 in remove_crypt Oct 7 15:55:59 storageqe-109 systemd[1]: tmp-libblockdev.35j0ltybmount_test.mount: Deactivated successfully. Oct 7 15:55:59 storageqe-109 kernel: XFS (dm-5): Unmounting Filesystem 1334920b-00f1-40e2-8b2d-2075c369ed07 Oct 7 15:55:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oCpT and fs xfs in remove_crypt Oct 7 15:55:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oCpT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dip_e961mount_test with fs ext4 Oct 7 15:56:10 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem b675f822-8f02-4dee-a7c4-b7217e4ee206 r/w with ordered data mode. Quota mode: none. Oct 7 15:56:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dip_e961mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/oCpT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oCpT and fs ext3 in remove_crypt Oct 7 15:56:14 storageqe-109 systemd[1]: tmp-libblockdev.dip_e961mount_test.mount: Deactivated successfully. Oct 7 15:56:14 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem b675f822-8f02-4dee-a7c4-b7217e4ee206. Oct 7 15:56:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oCpT and fs ext4 in remove_crypt Oct 7 15:56:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oCpT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.50smmsy6mount_test with fs ext3 Oct 7 15:56:24 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext3 file system using the ext4 subsystem Oct 7 15:56:24 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 941ae221-259f-4765-b483-c8a4cd807bfc r/w with ordered data mode. Quota mode: none. Oct 7 15:56:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.50smmsy6mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/oCpT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/oCpT and fs ext2 in remove_crypt Oct 7 15:56:29 storageqe-109 systemd[1]: tmp-libblockdev.50smmsy6mount_test.mount: Deactivated successfully. Oct 7 15:56:29 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 941ae221-259f-4765-b483-c8a4cd807bfc. Oct 7 15:56:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oCpT and fs ext3 in remove_crypt Oct 7 15:56:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/oCpT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hnu9yipbmount_test with fs ext2 Oct 7 15:56:39 storageqe-109 kernel: EXT4-fs (dm-5): mounting ext2 file system using the ext4 subsystem Oct 7 15:56:39 storageqe-109 kernel: EXT4-fs (dm-5): mounted filesystem 96355f66-8533-4c72-96cd-56b16b9e0901 r/w without journal. Quota mode: none. Oct 7 15:56:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hnu9yipbmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/oCpT and fs ext2 in remove_crypt INFO: remove crypt device oCpT Oct 7 15:56:44 storageqe-109 systemd[1]: tmp-libblockdev.hnu9yipbmount_test.mount: Deactivated successfully. Oct 7 15:56:44 storageqe-109 kernel: EXT4-fs (dm-5): unmounting filesystem 96355f66-8533-4c72-96cd-56b16b9e0901. Oct 7 15:56:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/oCpT and fs ext2 in remove_crypt Oct 7 15:56:44 storageqe-109 INFO: remove crypt device oCpT cryptsetup luksDump /dev/nvme0n1p3 -q Oct 7 15:56:45 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q cryptsetup erase /dev/nvme0n1p3 -q Oct 7 15:56:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p3 -q cryptsetup luksDump /dev/nvme0n1p3 -q Oct 7 15:57:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p3 -q INFO: finishe the remove crypt device oCpT INFO: start IO testing with the luks device /dev/mapper/hjmu and fs xfs in remove_crypt Oct 7 15:57:16 storageqe-109 INFO: finishe the remove crypt device oCpT Oct 7 15:57:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hjmu and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.tqzavw12mount_test with fs xfs Oct 7 15:57:26 storageqe-109 kernel: XFS (dm-6): Mounting V5 Filesystem f7a41d15-d78d-4a6b-8027-6ab6333a422d Oct 7 15:57:26 storageqe-109 kernel: XFS (dm-6): Ending clean mount Oct 7 15:57:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tqzavw12mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/hjmu and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hjmu and fs ext4 in remove_crypt Oct 7 15:57:31 storageqe-109 systemd[1]: tmp-libblockdev.tqzavw12mount_test.mount: Deactivated successfully. Oct 7 15:57:31 storageqe-109 kernel: XFS (dm-6): Unmounting Filesystem f7a41d15-d78d-4a6b-8027-6ab6333a422d Oct 7 15:57:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hjmu and fs xfs in remove_crypt Oct 7 15:57:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hjmu and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2_i0qcu3mount_test with fs ext4 Oct 7 15:57:41 storageqe-109 kernel: EXT4-fs (dm-6): mounted filesystem 8d15df64-e7cd-496b-bb50-42ca4505fe3d r/w with ordered data mode. Quota mode: none. Oct 7 15:57:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2_i0qcu3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/hjmu and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hjmu and fs ext3 in remove_crypt Oct 7 15:57:46 storageqe-109 systemd[1]: tmp-libblockdev.2_i0qcu3mount_test.mount: Deactivated successfully. Oct 7 15:57:46 storageqe-109 kernel: EXT4-fs (dm-6): unmounting filesystem 8d15df64-e7cd-496b-bb50-42ca4505fe3d. Oct 7 15:57:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hjmu and fs ext4 in remove_crypt Oct 7 15:57:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hjmu and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.adhrrv4kmount_test with fs ext3 Oct 7 15:57:56 storageqe-109 kernel: EXT4-fs (dm-6): mounting ext3 file system using the ext4 subsystem Oct 7 15:57:56 storageqe-109 kernel: EXT4-fs (dm-6): mounted filesystem a514abf8-0b58-4e25-acb8-3f309315d925 r/w with ordered data mode. Quota mode: none. Oct 7 15:57:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.adhrrv4kmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/hjmu and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hjmu and fs ext2 in remove_crypt Oct 7 15:58:01 storageqe-109 systemd[1]: tmp-libblockdev.adhrrv4kmount_test.mount: Deactivated successfully. Oct 7 15:58:01 storageqe-109 kernel: EXT4-fs (dm-6): unmounting filesystem a514abf8-0b58-4e25-acb8-3f309315d925. Oct 7 15:58:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hjmu and fs ext3 in remove_crypt Oct 7 15:58:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hjmu and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9if5k0_wmount_test with fs ext2 Oct 7 15:58:11 storageqe-109 kernel: EXT4-fs (dm-6): mounting ext2 file system using the ext4 subsystem Oct 7 15:58:11 storageqe-109 kernel: EXT4-fs (dm-6): mounted filesystem c66849bc-9f42-4fa4-b3c7-88b761a0e090 r/w without journal. Quota mode: none. Oct 7 15:58:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9if5k0_wmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/hjmu and fs ext2 in remove_crypt INFO: remove crypt device hjmu Oct 7 15:58:16 storageqe-109 systemd[1]: tmp-libblockdev.9if5k0_wmount_test.mount: Deactivated successfully. Oct 7 15:58:16 storageqe-109 kernel: EXT4-fs (dm-6): unmounting filesystem c66849bc-9f42-4fa4-b3c7-88b761a0e090. Oct 7 15:58:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hjmu and fs ext2 in remove_crypt Oct 7 15:58:16 storageqe-109 INFO: remove crypt device hjmu cryptsetup luksDump /dev/nvme0n1p4 -q Oct 7 15:58:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q cryptsetup erase /dev/nvme0n1p4 -q Oct 7 15:58:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p4 -q cryptsetup luksDump /dev/nvme0n1p4 -q Oct 7 15:58:37 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p4 -q INFO: finishe the remove crypt device hjmu Oct 7 15:58:47 storageqe-109 INFO: finishe the remove crypt device hjmu INFO: start IO testing with the luks device /dev/mapper/nlER and fs xfs in remove_crypt Oct 7 15:58:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nlER and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.5h0kmjlrmount_test with fs xfs Oct 7 15:58:57 storageqe-109 kernel: XFS (dm-7): Mounting V5 Filesystem a46387ee-e08b-408b-be2d-db23baa5713f Oct 7 15:58:57 storageqe-109 kernel: XFS (dm-7): Ending clean mount Oct 7 15:58:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5h0kmjlrmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/nlER and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nlER and fs ext4 in remove_crypt Oct 7 15:59:02 storageqe-109 systemd[1]: tmp-libblockdev.5h0kmjlrmount_test.mount: Deactivated successfully. Oct 7 15:59:02 storageqe-109 kernel: XFS (dm-7): Unmounting Filesystem a46387ee-e08b-408b-be2d-db23baa5713f Oct 7 15:59:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nlER and fs xfs in remove_crypt Oct 7 15:59:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nlER and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8rq9s8vrmount_test with fs ext4 Oct 7 15:59:12 storageqe-109 kernel: EXT4-fs (dm-7): mounted filesystem 8eb846e6-2bc9-4f85-8ceb-1d558613afbb r/w with ordered data mode. Quota mode: none. Oct 7 15:59:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8rq9s8vrmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/nlER and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nlER and fs ext3 in remove_crypt Oct 7 15:59:17 storageqe-109 systemd[1]: tmp-libblockdev.8rq9s8vrmount_test.mount: Deactivated successfully. Oct 7 15:59:17 storageqe-109 kernel: EXT4-fs (dm-7): unmounting filesystem 8eb846e6-2bc9-4f85-8ceb-1d558613afbb. Oct 7 15:59:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nlER and fs ext4 in remove_crypt Oct 7 15:59:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nlER and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.76snjfkfmount_test with fs ext3 Oct 7 15:59:27 storageqe-109 kernel: EXT4-fs (dm-7): mounting ext3 file system using the ext4 subsystem Oct 7 15:59:27 storageqe-109 kernel: EXT4-fs (dm-7): mounted filesystem 016af5c7-b3f3-464b-a283-d335e0c41506 r/w with ordered data mode. Quota mode: none. Oct 7 15:59:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.76snjfkfmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/nlER and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/nlER and fs ext2 in remove_crypt Oct 7 15:59:32 storageqe-109 systemd[1]: tmp-libblockdev.76snjfkfmount_test.mount: Deactivated successfully. Oct 7 15:59:32 storageqe-109 kernel: EXT4-fs (dm-7): unmounting filesystem 016af5c7-b3f3-464b-a283-d335e0c41506. Oct 7 15:59:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nlER and fs ext3 in remove_crypt Oct 7 15:59:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/nlER and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tuhhyrr8mount_test with fs ext2 Oct 7 15:59:42 storageqe-109 kernel: EXT4-fs (dm-7): mounting ext2 file system using the ext4 subsystem Oct 7 15:59:42 storageqe-109 kernel: EXT4-fs (dm-7): mounted filesystem 0f6e240a-91ca-45c8-b401-4fdc7e512d77 r/w without journal. Quota mode: none. Oct 7 15:59:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tuhhyrr8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/nlER and fs ext2 in remove_crypt INFO: remove crypt device nlER Oct 7 15:59:47 storageqe-109 systemd[1]: tmp-libblockdev.tuhhyrr8mount_test.mount: Deactivated successfully. Oct 7 15:59:47 storageqe-109 kernel: EXT4-fs (dm-7): unmounting filesystem 0f6e240a-91ca-45c8-b401-4fdc7e512d77. Oct 7 15:59:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/nlER and fs ext2 in remove_crypt Oct 7 15:59:47 storageqe-109 INFO: remove crypt device nlER cryptsetup luksDump /dev/nvme0n1p5 -q Oct 7 15:59:47 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q cryptsetup erase /dev/nvme0n1p5 -q Oct 7 15:59:57 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p5 -q cryptsetup luksDump /dev/nvme0n1p5 -q Oct 7 16:00:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p5 -q INFO: finishe the remove crypt device nlER Oct 7 16:00:18 storageqe-109 INFO: finishe the remove crypt device nlER INFO: start IO testing with the luks device /dev/mapper/ODiR and fs xfs in remove_crypt Oct 7 16:00:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ODiR and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.gch878b7mount_test with fs xfs Oct 7 16:00:28 storageqe-109 kernel: XFS (dm-8): Mounting V5 Filesystem 055f24dc-dfc6-424a-9fed-357f03a3f110 Oct 7 16:00:28 storageqe-109 kernel: XFS (dm-8): Ending clean mount Oct 7 16:00:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gch878b7mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ODiR and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ODiR and fs ext4 in remove_crypt Oct 7 16:00:33 storageqe-109 systemd[1]: tmp-libblockdev.gch878b7mount_test.mount: Deactivated successfully. Oct 7 16:00:33 storageqe-109 kernel: XFS (dm-8): Unmounting Filesystem 055f24dc-dfc6-424a-9fed-357f03a3f110 Oct 7 16:00:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ODiR and fs xfs in remove_crypt Oct 7 16:00:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ODiR and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vzp75yl5mount_test with fs ext4 Oct 7 16:00:43 storageqe-109 kernel: EXT4-fs (dm-8): mounted filesystem 707e560d-467d-4515-845b-81b934787ed5 r/w with ordered data mode. Quota mode: none. Oct 7 16:00:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vzp75yl5mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ODiR and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ODiR and fs ext3 in remove_crypt Oct 7 16:00:48 storageqe-109 systemd[1]: tmp-libblockdev.vzp75yl5mount_test.mount: Deactivated successfully. Oct 7 16:00:48 storageqe-109 kernel: EXT4-fs (dm-8): unmounting filesystem 707e560d-467d-4515-845b-81b934787ed5. Oct 7 16:00:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ODiR and fs ext4 in remove_crypt Oct 7 16:00:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ODiR and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.77w_405omount_test with fs ext3 Oct 7 16:00:58 storageqe-109 kernel: EXT4-fs (dm-8): mounting ext3 file system using the ext4 subsystem Oct 7 16:00:58 storageqe-109 kernel: EXT4-fs (dm-8): mounted filesystem f9a77d40-2775-48d7-a4e2-d6b8ae74561a r/w with ordered data mode. Quota mode: none. Oct 7 16:00:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.77w_405omount_test with fs ext3 Oct 7 16:01:03 storageqe-109 systemd[1]: tmp-libblockdev.77w_405omount_test.mount: Deactivated successfully. Oct 7 16:01:03 storageqe-109 kernel: EXT4-fs (dm-8): unmounting filesystem f9a77d40-2775-48d7-a4e2-d6b8ae74561a. INFO: End IO testing with the luks device /dev/mapper/ODiR and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ODiR and fs ext2 in remove_crypt Oct 7 16:01:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ODiR and fs ext3 in remove_crypt Oct 7 16:01:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ODiR and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7fn6xln8mount_test with fs ext2 Oct 7 16:01:13 storageqe-109 kernel: EXT4-fs (dm-8): mounting ext2 file system using the ext4 subsystem Oct 7 16:01:13 storageqe-109 kernel: EXT4-fs (dm-8): mounted filesystem b18690df-07e1-4715-87ed-8bbbba664c8f r/w without journal. Quota mode: none. Oct 7 16:01:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7fn6xln8mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ODiR and fs ext2 in remove_crypt INFO: remove crypt device ODiR Oct 7 16:01:18 storageqe-109 systemd[1]: tmp-libblockdev.7fn6xln8mount_test.mount: Deactivated successfully. Oct 7 16:01:18 storageqe-109 kernel: EXT4-fs (dm-8): unmounting filesystem b18690df-07e1-4715-87ed-8bbbba664c8f. Oct 7 16:01:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ODiR and fs ext2 in remove_crypt Oct 7 16:01:18 storageqe-109 INFO: remove crypt device ODiR cryptsetup luksDump /dev/nvme0n1p6 -q Oct 7 16:01:18 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q cryptsetup erase /dev/nvme0n1p6 -q Oct 7 16:01:28 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p6 -q cryptsetup luksDump /dev/nvme0n1p6 -q Oct 7 16:01:39 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p6 -q INFO: finishe the remove crypt device ODiR INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs xfs in remove_crypt Oct 7 16:01:49 storageqe-109 INFO: finishe the remove crypt device ODiR Oct 7 16:01:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.fmm59k3ymount_test with fs xfs Oct 7 16:01:59 storageqe-109 kernel: XFS (dm-9): Mounting V5 Filesystem 0591446e-aba9-4a1d-a365-25f0c7e8486c Oct 7 16:01:59 storageqe-109 kernel: XFS (dm-9): Ending clean mount Oct 7 16:01:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fmm59k3ymount_test with fs xfs Oct 7 16:02:04 storageqe-109 systemd[1]: tmp-libblockdev.fmm59k3ymount_test.mount: Deactivated successfully. Oct 7 16:02:04 storageqe-109 kernel: XFS (dm-9): Unmounting Filesystem 0591446e-aba9-4a1d-a365-25f0c7e8486c INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs ext4 in remove_crypt Oct 7 16:02:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs xfs in remove_crypt Oct 7 16:02:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.t1bmq853mount_test with fs ext4 Oct 7 16:02:14 storageqe-109 kernel: EXT4-fs (dm-9): mounted filesystem f1fcbe4b-2a16-4505-8019-cfeb6a4d5c12 r/w with ordered data mode. Quota mode: none. Oct 7 16:02:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t1bmq853mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs ext3 in remove_crypt Oct 7 16:02:19 storageqe-109 systemd[1]: tmp-libblockdev.t1bmq853mount_test.mount: Deactivated successfully. Oct 7 16:02:19 storageqe-109 kernel: EXT4-fs (dm-9): unmounting filesystem f1fcbe4b-2a16-4505-8019-cfeb6a4d5c12. Oct 7 16:02:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs ext4 in remove_crypt Oct 7 16:02:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5ze0pyagmount_test with fs ext3 Oct 7 16:02:29 storageqe-109 kernel: EXT4-fs (dm-9): mounting ext3 file system using the ext4 subsystem Oct 7 16:02:29 storageqe-109 kernel: EXT4-fs (dm-9): mounted filesystem 74c24d5e-6f96-49cf-a3f1-078c0ba93db6 r/w with ordered data mode. Quota mode: none. Oct 7 16:02:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5ze0pyagmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs ext2 in remove_crypt Oct 7 16:02:34 storageqe-109 systemd[1]: tmp-libblockdev.5ze0pyagmount_test.mount: Deactivated successfully. Oct 7 16:02:34 storageqe-109 kernel: EXT4-fs (dm-9): unmounting filesystem 74c24d5e-6f96-49cf-a3f1-078c0ba93db6. Oct 7 16:02:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs ext3 in remove_crypt Oct 7 16:02:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/Wgtb and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uujz_1u9mount_test with fs ext2 Oct 7 16:02:44 storageqe-109 kernel: EXT4-fs (dm-9): mounting ext2 file system using the ext4 subsystem Oct 7 16:02:44 storageqe-109 kernel: EXT4-fs (dm-9): mounted filesystem b29762f2-283c-408e-b181-0ba386a30a02 r/w without journal. Quota mode: none. Oct 7 16:02:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uujz_1u9mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs ext2 in remove_crypt INFO: remove crypt device Wgtb Oct 7 16:02:49 storageqe-109 systemd[1]: tmp-libblockdev.uujz_1u9mount_test.mount: Deactivated successfully. Oct 7 16:02:49 storageqe-109 kernel: EXT4-fs (dm-9): unmounting filesystem b29762f2-283c-408e-b181-0ba386a30a02. Oct 7 16:02:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/Wgtb and fs ext2 in remove_crypt Oct 7 16:02:49 storageqe-109 INFO: remove crypt device Wgtb cryptsetup luksDump /dev/nvme0n1p7 -q Oct 7 16:02:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q cryptsetup erase /dev/nvme0n1p7 -q Oct 7 16:03:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p7 -q cryptsetup luksDump /dev/nvme0n1p7 -q Oct 7 16:03:10 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p7 -q INFO: finishe the remove crypt device Wgtb INFO: start IO testing with the luks device /dev/mapper/TOBp and fs xfs in remove_crypt Oct 7 16:03:20 storageqe-109 INFO: finishe the remove crypt device Wgtb Oct 7 16:03:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TOBp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.11m4eyjrmount_test with fs xfs Oct 7 16:03:31 storageqe-109 kernel: XFS (dm-10): Mounting V5 Filesystem 2e9cf9b7-1509-4774-805d-55fda2259072 Oct 7 16:03:31 storageqe-109 kernel: XFS (dm-10): Ending clean mount Oct 7 16:03:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.11m4eyjrmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/TOBp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TOBp and fs ext4 in remove_crypt Oct 7 16:03:35 storageqe-109 systemd[1]: tmp-libblockdev.11m4eyjrmount_test.mount: Deactivated successfully. Oct 7 16:03:35 storageqe-109 kernel: XFS (dm-10): Unmounting Filesystem 2e9cf9b7-1509-4774-805d-55fda2259072 Oct 7 16:03:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TOBp and fs xfs in remove_crypt Oct 7 16:03:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TOBp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i96_k8d8mount_test with fs ext4 Oct 7 16:03:45 storageqe-109 kernel: EXT4-fs (dm-10): mounted filesystem a74167c0-0222-4060-b747-7fbd47b6f9cc r/w with ordered data mode. Quota mode: none. Oct 7 16:03:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i96_k8d8mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/TOBp and fs ext4 in remove_crypt Oct 7 16:03:50 storageqe-109 systemd[1]: tmp-libblockdev.i96_k8d8mount_test.mount: Deactivated successfully. Oct 7 16:03:50 storageqe-109 kernel: EXT4-fs (dm-10): unmounting filesystem a74167c0-0222-4060-b747-7fbd47b6f9cc. Oct 7 16:03:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TOBp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TOBp and fs ext3 in remove_crypt Oct 7 16:03:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TOBp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tuimvlf9mount_test with fs ext3 Oct 7 16:04:00 storageqe-109 kernel: EXT4-fs (dm-10): mounting ext3 file system using the ext4 subsystem Oct 7 16:04:00 storageqe-109 kernel: EXT4-fs (dm-10): mounted filesystem f4a56298-c6d5-4a69-b93c-167989280347 r/w with ordered data mode. Quota mode: none. Oct 7 16:04:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tuimvlf9mount_test with fs ext3 Oct 7 16:04:05 storageqe-109 systemd[1]: tmp-libblockdev.tuimvlf9mount_test.mount: Deactivated successfully. Oct 7 16:04:05 storageqe-109 kernel: EXT4-fs (dm-10): unmounting filesystem f4a56298-c6d5-4a69-b93c-167989280347. INFO: End IO testing with the luks device /dev/mapper/TOBp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/TOBp and fs ext2 in remove_crypt Oct 7 16:04:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TOBp and fs ext3 in remove_crypt Oct 7 16:04:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/TOBp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rz5bmpl2mount_test with fs ext2 Oct 7 16:04:15 storageqe-109 kernel: EXT4-fs (dm-10): mounting ext2 file system using the ext4 subsystem Oct 7 16:04:15 storageqe-109 kernel: EXT4-fs (dm-10): mounted filesystem 8f27cf14-e90b-4189-a5ef-b4e43efc7eba r/w without journal. Quota mode: none. Oct 7 16:04:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rz5bmpl2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/TOBp and fs ext2 in remove_crypt INFO: remove crypt device TOBp Oct 7 16:04:20 storageqe-109 systemd[1]: tmp-libblockdev.rz5bmpl2mount_test.mount: Deactivated successfully. Oct 7 16:04:20 storageqe-109 kernel: EXT4-fs (dm-10): unmounting filesystem 8f27cf14-e90b-4189-a5ef-b4e43efc7eba. Oct 7 16:04:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/TOBp and fs ext2 in remove_crypt Oct 7 16:04:20 storageqe-109 INFO: remove crypt device TOBp cryptsetup luksDump /dev/nvme0n1p8 -q Oct 7 16:04:21 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q cryptsetup erase /dev/nvme0n1p8 -q Oct 7 16:04:31 storageqe-109 journal: cryptsetup erase /dev/nvme0n1p8 -q cryptsetup luksDump /dev/nvme0n1p8 -q Oct 7 16:04:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1p8 -q INFO: finishe the remove crypt device TOBp Oct 7 16:04:51 storageqe-109 INFO: finishe the remove crypt device TOBp Oct 7 16:04:53 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 7 16:04:54 storageqe-109 kernel: nvme0n1: p2 p3 p4 p5 p6 p7 p8 Oct 7 16:04:54 storageqe-109 kernel: nvme0n1: p3 p4 p5 p6 p7 p8 Oct 7 16:04:55 storageqe-109 kernel: nvme0n1: p3 p4 p5 p6 p7 p8 Oct 7 16:04:55 storageqe-109 kernel: nvme0n1: p4 p5 p6 p7 p8 Oct 7 16:04:56 storageqe-109 kernel: nvme0n1: p4 p5 p6 p7 p8 Oct 7 16:04:57 storageqe-109 kernel: nvme0n1: p4 p6 p7 p8 Oct 7 16:04:58 storageqe-109 kernel: nvme0n1: p4 p6 p7 p8 Oct 7 16:04:59 storageqe-109 kernel: nvme0n1: p4 p6 p8 Oct 7 16:05:01 storageqe-109 kernel: nvme0n1: p4 p6 Oct 7 16:05:02 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:05:02 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:05:02 storageqe-109 kernel: nvme0n1: p4 p6 Oct 7 16:05:02 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_hw_opal_tang #### INFO: #### will start test_hw_luks_paramter ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 16:05:19 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 16:05:19 storageqe-109 INFO: #### END test_hw_opal_tang #### Oct 7 16:05:19 storageqe-109 INFO: #### will start test_hw_luks_paramter ##### Oct 7 16:05:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:05:25 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:05:35 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:05:36 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:05:46 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:05:51 storageqe-109 kernel: nvme_log_error: 12 callbacks suppressed Oct 7 16:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:51 storageqe-109 kernel: blk_print_req_error: 12 callbacks suppressed Oct 7 16:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: buffer_io_error: 4 callbacks suppressed Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:05:52 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:05:52 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:05:52 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:05:52 storageqe-109 stratisd[4947]: [2025-10-07T20:05:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:05:52 storageqe-109 stratisd[4947]: [2025-10-07T20:05:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:06:02 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:06:03 storageqe-109 stratisd[4947]: [2025-10-07T20:06:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:06:03 storageqe-109 stratisd[4947]: [2025-10-07T20:06:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:06:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:06:16 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.3x11ci0amount_test with fs xfs Oct 7 16:06:24 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 016abd68-cb02-4ded-8651-0c8c415aa419 Oct 7 16:06:24 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:06:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3x11ci0amount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:06:29 storageqe-109 systemd[1]: tmp-libblockdev.3x11ci0amount_test.mount: Deactivated successfully. Oct 7 16:06:29 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 016abd68-cb02-4ded-8651-0c8c415aa419 Oct 7 16:06:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:06:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i78r72n2mount_test with fs ext4 Oct 7 16:06:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem febc99bd-eeed-48a9-b3da-cc28257d7e36 r/w with ordered data mode. Quota mode: none. Oct 7 16:06:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i78r72n2mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:06:46 storageqe-109 systemd[1]: tmp-libblockdev.i78r72n2mount_test.mount: Deactivated successfully. Oct 7 16:06:46 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem febc99bd-eeed-48a9-b3da-cc28257d7e36. Oct 7 16:06:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:06:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._vd59lp_mount_test with fs ext3 Oct 7 16:07:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:07:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0d35de39-2afb-47cf-bad4-1edd47938370 r/w with ordered data mode. Quota mode: none. Oct 7 16:07:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev._vd59lp_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:07:14 storageqe-109 systemd[1]: tmp-libblockdev._vd59lp_mount_test.mount: Deactivated successfully. Oct 7 16:07:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0d35de39-2afb-47cf-bad4-1edd47938370. Oct 7 16:07:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:07:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8hpi7rx2mount_test with fs ext2 Oct 7 16:07:35 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:07:35 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 87827156-faf0-4536-b6d0-af9fa2ee1ac5 r/w without journal. Quota mode: none. Oct 7 16:07:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8hpi7rx2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:07:41 storageqe-109 systemd[1]: tmp-libblockdev.8hpi7rx2mount_test.mount: Deactivated successfully. Oct 7 16:07:41 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 87827156-faf0-4536-b6d0-af9fa2ee1ac5. Oct 7 16:07:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:07:41 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:07:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:07:51 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:08:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:08:13 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:08:13 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:08:13 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:08:25 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:08:35 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:08:35 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:08:40 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:08:40 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:08:40 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:08:40 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:08:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:08:41 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:08:41 storageqe-109 stratisd[4947]: [2025-10-07T20:08:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:08:41 storageqe-109 stratisd[4947]: [2025-10-07T20:08:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:08:50 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:08:51 storageqe-109 stratisd[4947]: [2025-10-07T20:08:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:08:51 storageqe-109 stratisd[4947]: [2025-10-07T20:08:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:09:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:09:05 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.xhglilcmmount_test with fs xfs Oct 7 16:09:12 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 020767b8-8e0d-475e-a4a8-bfb0e5ad98c7 Oct 7 16:09:12 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:09:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xhglilcmmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:09:17 storageqe-109 systemd[1]: tmp-libblockdev.xhglilcmmount_test.mount: Deactivated successfully. Oct 7 16:09:17 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 020767b8-8e0d-475e-a4a8-bfb0e5ad98c7 Oct 7 16:09:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:09:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.19lk4jujmount_test with fs ext4 Oct 7 16:09:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9aa7da1d-e733-4cd9-9084-9b420c09a425 r/w with ordered data mode. Quota mode: none. Oct 7 16:09:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.19lk4jujmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:09:34 storageqe-109 systemd[1]: tmp-libblockdev.19lk4jujmount_test.mount: Deactivated successfully. Oct 7 16:09:34 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9aa7da1d-e733-4cd9-9084-9b420c09a425. Oct 7 16:09:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:09:34 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:09:47 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 16:09:47 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 16:09:47 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: will run io in dir /tmp/libblockdev.oiwsq8aqmount_test with fs ext3 Oct 7 16:09:56 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:09:56 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 66db1126-af20-444b-bfa3-b4e67cfd37c4 r/w with ordered data mode. Quota mode: none. Oct 7 16:09:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.oiwsq8aqmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:10:01 storageqe-109 systemd[1]: tmp-libblockdev.oiwsq8aqmount_test.mount: Deactivated successfully. Oct 7 16:10:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 66db1126-af20-444b-bfa3-b4e67cfd37c4. Oct 7 16:10:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:10:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zhbupgqwmount_test with fs ext2 Oct 7 16:10:23 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:10:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 01ab0546-86af-40ee-bc3f-0a8906466a8c r/w without journal. Quota mode: none. Oct 7 16:10:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zhbupgqwmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:10:27 storageqe-109 systemd[1]: tmp-libblockdev.zhbupgqwmount_test.mount: Deactivated successfully. Oct 7 16:10:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 01ab0546-86af-40ee-bc3f-0a8906466a8c. Oct 7 16:10:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:10:27 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:10:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:10:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:10:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:11:00 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:11:00 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:11:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:11:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:11:22 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:11:22 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:11:27 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:11:27 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:11:27 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:11:27 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:11:27 storageqe-109 stratisd[4947]: [2025-10-07T20:11:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:11:27 storageqe-109 stratisd[4947]: [2025-10-07T20:11:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:11:37 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:11:38 storageqe-109 stratisd[4947]: [2025-10-07T20:11:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:11:38 storageqe-109 stratisd[4947]: [2025-10-07T20:11:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:11:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:11:52 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.d0luqhaimount_test with fs xfs Oct 7 16:11:59 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 7a5698aa-4cd6-487f-beee-e0f03ecdf9e5 Oct 7 16:11:59 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:11:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d0luqhaimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:12:05 storageqe-109 systemd[1]: tmp-libblockdev.d0luqhaimount_test.mount: Deactivated successfully. Oct 7 16:12:05 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 7a5698aa-4cd6-487f-beee-e0f03ecdf9e5 Oct 7 16:12:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:12:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zatbizokmount_test with fs ext4 Oct 7 16:12:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem cb21f68a-673a-4610-98b5-f16e6b0adc65 r/w with ordered data mode. Quota mode: none. Oct 7 16:12:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zatbizokmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:12:22 storageqe-109 systemd[1]: tmp-libblockdev.zatbizokmount_test.mount: Deactivated successfully. Oct 7 16:12:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem cb21f68a-673a-4610-98b5-f16e6b0adc65. Oct 7 16:12:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:12:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ujlyg1dpmount_test with fs ext3 Oct 7 16:12:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:12:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b59e1e62-4277-4e2b-8994-d153083693db r/w with ordered data mode. Quota mode: none. Oct 7 16:12:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ujlyg1dpmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:12:50 storageqe-109 systemd[1]: tmp-libblockdev.ujlyg1dpmount_test.mount: Deactivated successfully. Oct 7 16:12:50 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b59e1e62-4277-4e2b-8994-d153083693db. Oct 7 16:12:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:12:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._jswzwo5mount_test with fs ext2 Oct 7 16:13:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:13:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ccef76dc-9744-43a0-82bf-3ad4fa9b1fc0 r/w without journal. Quota mode: none. Oct 7 16:13:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev._jswzwo5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:13:16 storageqe-109 systemd[1]: tmp-libblockdev._jswzwo5mount_test.mount: Deactivated successfully. Oct 7 16:13:16 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ccef76dc-9744-43a0-82bf-3ad4fa9b1fc0. Oct 7 16:13:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:13:16 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:13:17 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:13:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:13:39 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:13:49 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:13:49 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:13:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:14:01 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:14:11 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:14:11 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:14:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:14:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:14:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:14:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:14:16 storageqe-109 stratisd[4947]: [2025-10-07T20:14:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:14:16 storageqe-109 stratisd[4947]: [2025-10-07T20:14:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:14:26 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:14:27 storageqe-109 stratisd[4947]: [2025-10-07T20:14:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:14:27 storageqe-109 stratisd[4947]: [2025-10-07T20:14:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:14:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:14:41 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.tmohh644mount_test with fs xfs Oct 7 16:14:49 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 6d490d05-6c0c-46df-97f6-ec147e0ca132 Oct 7 16:14:49 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:14:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tmohh644mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:14:53 storageqe-109 systemd[1]: tmp-libblockdev.tmohh644mount_test.mount: Deactivated successfully. Oct 7 16:14:53 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 6d490d05-6c0c-46df-97f6-ec147e0ca132 Oct 7 16:14:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:14:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zhlyxtxqmount_test with fs ext4 Oct 7 16:15:05 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c5ed7ab7-95ef-400e-9161-e67f02499955 r/w with ordered data mode. Quota mode: none. Oct 7 16:15:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zhlyxtxqmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:15:09 storageqe-109 systemd[1]: tmp-libblockdev.zhlyxtxqmount_test.mount: Deactivated successfully. Oct 7 16:15:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c5ed7ab7-95ef-400e-9161-e67f02499955. Oct 7 16:15:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:15:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:15:31 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.iivxib7hmount_test with fs ext3 Oct 7 16:15:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8065df5a-f2d1-4834-a399-577b12de4dab r/w with ordered data mode. Quota mode: none. Oct 7 16:15:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.iivxib7hmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:15:36 storageqe-109 systemd[1]: tmp-libblockdev.iivxib7hmount_test.mount: Deactivated successfully. Oct 7 16:15:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8065df5a-f2d1-4834-a399-577b12de4dab. Oct 7 16:15:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:15:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.7fs0p4kqmount_test with fs ext2 Oct 7 16:15:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:15:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d9f44995-86f3-40ef-a94e-bfa4bfc13e1e r/w without journal. Quota mode: none. Oct 7 16:15:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7fs0p4kqmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:16:03 storageqe-109 systemd[1]: tmp-libblockdev.7fs0p4kqmount_test.mount: Deactivated successfully. Oct 7 16:16:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d9f44995-86f3-40ef-a94e-bfa4bfc13e1e. Oct 7 16:16:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:16:03 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:16:03 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:16:13 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:16:25 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:16:35 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:16:35 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:16:35 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:16:47 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:16:57 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:16:57 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:17:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:18:25 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:18:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:18:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:18:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:18:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:18:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:18:26 storageqe-109 stratisd[4947]: [2025-10-07T20:18:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:18:26 storageqe-109 stratisd[4947]: [2025-10-07T20:18:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:18:35 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:19:06 storageqe-109 stratisd[4947]: [2025-10-07T20:19:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:19:06 storageqe-109 stratisd[4947]: [2025-10-07T20:19:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:19:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.m8a7ql_9mount_test with fs xfs Oct 7 16:19:27 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem c8aa3a72-89f3-4e8f-8a44-89412e67f83a Oct 7 16:19:27 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:19:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m8a7ql_9mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:19:32 storageqe-109 systemd[1]: tmp-libblockdev.m8a7ql_9mount_test.mount: Deactivated successfully. Oct 7 16:19:32 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem c8aa3a72-89f3-4e8f-8a44-89412e67f83a Oct 7 16:19:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:19:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9l5f9jl4mount_test with fs ext4 Oct 7 16:19:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a9c5ec04-b407-476e-950c-e1fbc61bb38d r/w with ordered data mode. Quota mode: none. Oct 7 16:19:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9l5f9jl4mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:19:49 storageqe-109 systemd[1]: tmp-libblockdev.9l5f9jl4mount_test.mount: Deactivated successfully. Oct 7 16:19:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a9c5ec04-b407-476e-950c-e1fbc61bb38d. Oct 7 16:19:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:19:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jeng0eyxmount_test with fs ext3 Oct 7 16:20:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:20:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 56a29a0a-11c2-4ea4-9c75-6de98a493763 r/w with ordered data mode. Quota mode: none. Oct 7 16:20:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jeng0eyxmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:20:17 storageqe-109 systemd[1]: tmp-libblockdev.jeng0eyxmount_test.mount: Deactivated successfully. Oct 7 16:20:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 56a29a0a-11c2-4ea4-9c75-6de98a493763. Oct 7 16:20:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:20:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._f6euzgqmount_test with fs ext2 Oct 7 16:20:38 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:20:38 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6954a10a-3a78-4e99-a939-5d43ba0d4eac r/w without journal. Quota mode: none. Oct 7 16:20:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev._f6euzgqmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:20:44 storageqe-109 systemd[1]: tmp-libblockdev._f6euzgqmount_test.mount: Deactivated successfully. Oct 7 16:20:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6954a10a-3a78-4e99-a939-5d43ba0d4eac. Oct 7 16:20:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:20:44 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:20:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:20:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:21:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:21:16 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:21:16 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:21:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:21:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:21:38 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:21:38 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:22:08 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:23:06 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:23:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:23:06 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:23:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:23:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:23:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:23:07 storageqe-109 stratisd[4947]: [2025-10-07T20:23:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:23:07 storageqe-109 stratisd[4947]: [2025-10-07T20:23:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:23:16 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:23:47 storageqe-109 stratisd[4947]: [2025-10-07T20:23:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:23:47 storageqe-109 stratisd[4947]: [2025-10-07T20:23:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:23:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.cuqblhh4mount_test with fs xfs Oct 7 16:24:08 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 084fbc47-679d-4040-890a-f44d725e6b05 Oct 7 16:24:08 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:24:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cuqblhh4mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:24:13 storageqe-109 systemd[1]: tmp-libblockdev.cuqblhh4mount_test.mount: Deactivated successfully. Oct 7 16:24:13 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 084fbc47-679d-4040-890a-f44d725e6b05 Oct 7 16:24:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:24:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3czkxdgbmount_test with fs ext4 Oct 7 16:24:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 663956c9-7af4-4642-8a00-958c23046b81 r/w with ordered data mode. Quota mode: none. Oct 7 16:24:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3czkxdgbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:24:30 storageqe-109 systemd[1]: tmp-libblockdev.3czkxdgbmount_test.mount: Deactivated successfully. Oct 7 16:24:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 663956c9-7af4-4642-8a00-958c23046b81. Oct 7 16:24:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:24:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.a8mxfk1jmount_test with fs ext3 Oct 7 16:24:52 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:24:52 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 06e63ed7-7077-4174-a0c5-2b7959f332b6 r/w with ordered data mode. Quota mode: none. Oct 7 16:24:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.a8mxfk1jmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:24:57 storageqe-109 systemd[1]: tmp-libblockdev.a8mxfk1jmount_test.mount: Deactivated successfully. Oct 7 16:24:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 06e63ed7-7077-4174-a0c5-2b7959f332b6. Oct 7 16:24:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:24:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g8r8jooumount_test with fs ext2 Oct 7 16:25:19 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:25:19 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 96a333a4-bcf7-4c73-8683-be8bddecce6f r/w without journal. Quota mode: none. Oct 7 16:25:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g8r8jooumount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:25:24 storageqe-109 systemd[1]: tmp-libblockdev.g8r8jooumount_test.mount: Deactivated successfully. Oct 7 16:25:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 96a333a4-bcf7-4c73-8683-be8bddecce6f. Oct 7 16:25:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:25:24 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:25:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:25:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:25:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:25:56 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:25:56 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:25:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:26:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:26:18 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:26:18 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:26:48 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 16:26:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:26:48 storageqe-109 dnf[1964391]: Updating Subscription Management repositories. Oct 7 16:26:48 storageqe-109 dnf[1964391]: Unable to read consumer identity Oct 7 16:26:48 storageqe-109 dnf[1964391]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 16:26:48 storageqe-109 dnf[1964391]: beaker-AppStream 64 kB/s | 2.8 kB 00:00 Oct 7 16:26:48 storageqe-109 dnf[1964391]: beaker-AppStream-debuginfo 57 kB/s | 1.5 kB 00:00 Oct 7 16:26:48 storageqe-109 dnf[1964391]: beaker-BaseOS 214 kB/s | 2.7 kB 00:00 Oct 7 16:26:48 storageqe-109 dnf[1964391]: beaker-BaseOS-debuginfo 58 kB/s | 1.5 kB 00:00 Oct 7 16:26:48 storageqe-109 dnf[1964391]: beaker-CRB 96 kB/s | 2.7 kB 00:00 Oct 7 16:26:48 storageqe-109 dnf[1964391]: beaker-CRB-debuginfo 74 kB/s | 1.5 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-HighAvailability 58 kB/s | 2.8 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-HighAvailability-debuginfo 516 kB/s | 1.5 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-NFV 48 kB/s | 2.7 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-NFV-debuginfo 61 kB/s | 1.5 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-RT 766 kB/s | 2.7 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-RT-debuginfo 114 kB/s | 1.5 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-SAP 228 kB/s | 2.7 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-SAP-debuginfo 424 kB/s | 1.5 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-SAPHANA 603 kB/s | 2.7 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: beaker-SAPHANA-debuginfo 211 kB/s | 1.5 kB 00:00 Oct 7 16:26:49 storageqe-109 dnf[1964391]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 7 16:26:50 storageqe-109 dnf[1964391]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 7 16:26:50 storageqe-109 dnf[1964391]: Google Cloud CLI 4.4 kB/s | 1.4 kB 00:00 Oct 7 16:26:51 storageqe-109 dnf[1964391]: Copr repo for python-ssh2-python312 owned by mh 2.0 kB/s | 1.5 kB 00:00 Oct 7 16:26:52 storageqe-109 dnf[1964391]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 7 16:26:52 storageqe-109 dnf[1964391]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 7 16:26:52 storageqe-109 dnf[1964391]: Metadata cache created. Oct 7 16:26:52 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 16:26:52 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 16:27:46 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:27:46 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:46 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:27:46 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:27:47 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:27:47 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:27:47 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:27:47 storageqe-109 stratisd[4947]: [2025-10-07T20:27:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:27:47 storageqe-109 stratisd[4947]: [2025-10-07T20:27:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:27:57 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:28:28 storageqe-109 stratisd[4947]: [2025-10-07T20:28:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:28:28 storageqe-109 stratisd[4947]: [2025-10-07T20:28:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:28:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.x4wbnj4xmount_test with fs xfs Oct 7 16:28:49 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 9f99219e-7c30-4376-a049-c0447a5c4277 Oct 7 16:28:49 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:28:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x4wbnj4xmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:28:54 storageqe-109 systemd[1]: tmp-libblockdev.x4wbnj4xmount_test.mount: Deactivated successfully. Oct 7 16:28:54 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 9f99219e-7c30-4376-a049-c0447a5c4277 Oct 7 16:28:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:28:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9giw0qwamount_test with fs ext4 Oct 7 16:29:06 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 871ac523-271f-434c-a900-2c744d5976f1 r/w with ordered data mode. Quota mode: none. Oct 7 16:29:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9giw0qwamount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:29:11 storageqe-109 systemd[1]: tmp-libblockdev.9giw0qwamount_test.mount: Deactivated successfully. Oct 7 16:29:11 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 871ac523-271f-434c-a900-2c744d5976f1. Oct 7 16:29:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:29:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dfgg2xqsmount_test with fs ext3 Oct 7 16:29:34 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:29:34 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 863f902e-2584-40ea-9717-e19d0034cdc1 r/w with ordered data mode. Quota mode: none. Oct 7 16:29:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dfgg2xqsmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:29:39 storageqe-109 systemd[1]: tmp-libblockdev.dfgg2xqsmount_test.mount: Deactivated successfully. Oct 7 16:29:39 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 863f902e-2584-40ea-9717-e19d0034cdc1. Oct 7 16:29:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:29:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.08yqthwymount_test with fs ext2 Oct 7 16:30:00 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:30:00 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 722b5127-154b-4e90-bdc1-23e1ef9e7c15 r/w without journal. Quota mode: none. Oct 7 16:30:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.08yqthwymount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:30:06 storageqe-109 systemd[1]: tmp-libblockdev.08yqthwymount_test.mount: Deactivated successfully. Oct 7 16:30:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 722b5127-154b-4e90-bdc1-23e1ef9e7c15. Oct 7 16:30:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:30:06 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:30:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:30:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:30:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:30:38 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:30:38 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:30:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:30:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:31:00 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:31:00 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:31:30 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:32:28 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:32:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:32:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:32:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:32:29 storageqe-109 stratisd[4947]: [2025-10-07T20:32:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:32:29 storageqe-109 stratisd[4947]: [2025-10-07T20:32:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:32:38 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:33:09 storageqe-109 stratisd[4947]: [2025-10-07T20:33:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:33:09 storageqe-109 stratisd[4947]: [2025-10-07T20:33:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:33:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.78y3sbyemount_test with fs xfs Oct 7 16:33:30 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem b1f37463-6da8-4518-a114-d581cad82932 Oct 7 16:33:30 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:33:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.78y3sbyemount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:33:35 storageqe-109 systemd[1]: tmp-libblockdev.78y3sbyemount_test.mount: Deactivated successfully. Oct 7 16:33:35 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem b1f37463-6da8-4518-a114-d581cad82932 Oct 7 16:33:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:33:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ghnsgsjjmount_test with fs ext4 Oct 7 16:33:47 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 36ab444f-e89b-4189-ad69-350306775526 r/w with ordered data mode. Quota mode: none. Oct 7 16:33:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ghnsgsjjmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:33:52 storageqe-109 systemd[1]: tmp-libblockdev.ghnsgsjjmount_test.mount: Deactivated successfully. Oct 7 16:33:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 36ab444f-e89b-4189-ad69-350306775526. Oct 7 16:33:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:33:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:34:14 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.ttf5zachmount_test with fs ext3 Oct 7 16:34:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5d027ab0-182a-4855-b413-55d3c93487de r/w with ordered data mode. Quota mode: none. Oct 7 16:34:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ttf5zachmount_test with fs ext3 Oct 7 16:34:19 storageqe-109 systemd[1]: tmp-libblockdev.ttf5zachmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:34:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5d027ab0-182a-4855-b413-55d3c93487de. Oct 7 16:34:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:34:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.m5m__zo0mount_test with fs ext2 Oct 7 16:34:40 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:34:40 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 074948b0-e3f4-4317-a9ec-8a1928dc311f r/w without journal. Quota mode: none. Oct 7 16:34:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.m5m__zo0mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:34:45 storageqe-109 systemd[1]: tmp-libblockdev.m5m__zo0mount_test.mount: Deactivated successfully. Oct 7 16:34:45 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 074948b0-e3f4-4317-a9ec-8a1928dc311f. Oct 7 16:34:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:34:45 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:34:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:34:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:35:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:35:17 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:35:17 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:35:17 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:35:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:35:39 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:35:39 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:35:45 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:35:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:35:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:35:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:35:45 storageqe-109 stratisd[4947]: [2025-10-07T20:35:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:35:45 storageqe-109 stratisd[4947]: [2025-10-07T20:35:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:35:55 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:35:56 storageqe-109 stratisd[4947]: [2025-10-07T20:35:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:35:56 storageqe-109 stratisd[4947]: [2025-10-07T20:35:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:36:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:36:09 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:36:17 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f65ee08c-4a7c-44ac-a6fb-2ca4f3a4f58e Oct 7 16:36:17 storageqe-109 kernel: XFS (dm-3): Ending clean mount INFO: will run io in dir /tmp/libblockdev.smv2cgtvmount_test with fs xfs Oct 7 16:36:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.smv2cgtvmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:36:22 storageqe-109 systemd[1]: tmp-libblockdev.smv2cgtvmount_test.mount: Deactivated successfully. Oct 7 16:36:22 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f65ee08c-4a7c-44ac-a6fb-2ca4f3a4f58e Oct 7 16:36:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:36:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9l54gqmbmount_test with fs ext4 Oct 7 16:36:34 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0c1d5a72-41d7-4634-922f-8133f07c2357 r/w with ordered data mode. Quota mode: none. Oct 7 16:36:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9l54gqmbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:36:39 storageqe-109 systemd[1]: tmp-libblockdev.9l54gqmbmount_test.mount: Deactivated successfully. Oct 7 16:36:39 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0c1d5a72-41d7-4634-922f-8133f07c2357. Oct 7 16:36:39 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:36:39 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hhfaal4qmount_test with fs ext3 Oct 7 16:37:01 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:37:01 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem fecb2657-7e1b-42d1-907c-69bf370ea6ce r/w with ordered data mode. Quota mode: none. Oct 7 16:37:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hhfaal4qmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:37:07 storageqe-109 systemd[1]: tmp-libblockdev.hhfaal4qmount_test.mount: Deactivated successfully. Oct 7 16:37:07 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem fecb2657-7e1b-42d1-907c-69bf370ea6ce. Oct 7 16:37:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:37:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pnl94nppmount_test with fs ext2 Oct 7 16:37:28 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:37:28 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0f0c69f7-1846-442b-9632-11d9fac01c92 r/w without journal. Quota mode: none. Oct 7 16:37:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pnl94nppmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:37:34 storageqe-109 systemd[1]: tmp-libblockdev.pnl94nppmount_test.mount: Deactivated successfully. Oct 7 16:37:34 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0f0c69f7-1846-442b-9632-11d9fac01c92. Oct 7 16:37:34 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:37:34 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:37:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:37:44 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:37:56 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:38:06 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:38:06 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:38:06 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:38:18 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:38:28 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:38:28 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:38:33 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:38:33 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:33 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:38:33 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:38:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:38:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:38:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:38:34 storageqe-109 stratisd[4947]: [2025-10-07T20:38:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:38:34 storageqe-109 stratisd[4947]: [2025-10-07T20:38:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:38:44 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:38:44 storageqe-109 stratisd[4947]: [2025-10-07T20:38:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:38:44 storageqe-109 stratisd[4947]: [2025-10-07T20:38:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:38:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:38:58 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.g6m17ojdmount_test with fs xfs Oct 7 16:39:06 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 25021ad4-a308-447f-8f2f-1a1fb9dd077e Oct 7 16:39:06 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:39:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g6m17ojdmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:39:10 storageqe-109 systemd[1]: tmp-libblockdev.g6m17ojdmount_test.mount: Deactivated successfully. Oct 7 16:39:10 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 25021ad4-a308-447f-8f2f-1a1fb9dd077e Oct 7 16:39:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:39:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.n2ukp0urmount_test with fs ext4 Oct 7 16:39:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4fa37800-5a83-4805-8513-ff7e427a88f1 r/w with ordered data mode. Quota mode: none. Oct 7 16:39:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n2ukp0urmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:39:27 storageqe-109 systemd[1]: tmp-libblockdev.n2ukp0urmount_test.mount: Deactivated successfully. Oct 7 16:39:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4fa37800-5a83-4805-8513-ff7e427a88f1. Oct 7 16:39:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:39:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wr4vzah2mount_test with fs ext3 Oct 7 16:39:49 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:39:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ef1c7f73-5f9f-431e-94ec-4dfe724e53ad r/w with ordered data mode. Quota mode: none. Oct 7 16:39:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wr4vzah2mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:39:54 storageqe-109 systemd[1]: tmp-libblockdev.wr4vzah2mount_test.mount: Deactivated successfully. Oct 7 16:39:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ef1c7f73-5f9f-431e-94ec-4dfe724e53ad. Oct 7 16:39:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:39:54 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.10gkhzg1mount_test with fs ext2 Oct 7 16:40:15 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:40:15 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1fcc123a-dee8-478d-b0b0-af045c6a1524 r/w without journal. Quota mode: none. Oct 7 16:40:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.10gkhzg1mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:40:20 storageqe-109 systemd[1]: tmp-libblockdev.10gkhzg1mount_test.mount: Deactivated successfully. Oct 7 16:40:20 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1fcc123a-dee8-478d-b0b0-af045c6a1524. Oct 7 16:40:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:40:20 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:40:20 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:40:30 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:40:42 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:40:52 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:40:52 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:40:52 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:41:04 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:41:14 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:41:14 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:41:19 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:41:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:19 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:41:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:41:20 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:41:20 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:41:20 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:41:20 storageqe-109 stratisd[4947]: [2025-10-07T20:41:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:41:20 storageqe-109 stratisd[4947]: [2025-10-07T20:41:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:41:30 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:41:30 storageqe-109 stratisd[4947]: [2025-10-07T20:41:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:41:30 storageqe-109 stratisd[4947]: [2025-10-07T20:41:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:41:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:41:44 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:41:52 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 220c9125-bab0-48f6-940a-e4fe65a23d89 INFO: will run io in dir /tmp/libblockdev.74reg26gmount_test with fs xfs Oct 7 16:41:52 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:41:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.74reg26gmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:41:57 storageqe-109 systemd[1]: tmp-libblockdev.74reg26gmount_test.mount: Deactivated successfully. Oct 7 16:41:57 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 220c9125-bab0-48f6-940a-e4fe65a23d89 Oct 7 16:41:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:41:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q_fszi7vmount_test with fs ext4 Oct 7 16:42:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 658c1cf9-6cb5-4e17-9833-f61a1fd60965 r/w with ordered data mode. Quota mode: none. Oct 7 16:42:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q_fszi7vmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:42:14 storageqe-109 systemd[1]: tmp-libblockdev.q_fszi7vmount_test.mount: Deactivated successfully. Oct 7 16:42:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 658c1cf9-6cb5-4e17-9833-f61a1fd60965. Oct 7 16:42:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:42:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:42:36 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev._kgm7ijdmount_test with fs ext3 Oct 7 16:42:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 49fe70d6-d154-4e22-922b-1f33872db1cc r/w with ordered data mode. Quota mode: none. Oct 7 16:42:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev._kgm7ijdmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:42:42 storageqe-109 systemd[1]: tmp-libblockdev._kgm7ijdmount_test.mount: Deactivated successfully. Oct 7 16:42:42 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 49fe70d6-d154-4e22-922b-1f33872db1cc. Oct 7 16:42:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:42:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.scf18_cjmount_test with fs ext2 Oct 7 16:43:03 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:43:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a924fe05-baff-476e-a5c1-08a162996997 r/w without journal. Quota mode: none. Oct 7 16:43:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.scf18_cjmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:43:09 storageqe-109 systemd[1]: tmp-libblockdev.scf18_cjmount_test.mount: Deactivated successfully. Oct 7 16:43:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a924fe05-baff-476e-a5c1-08a162996997. Oct 7 16:43:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:43:09 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:43:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:43:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:43:31 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:43:41 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:43:41 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:43:41 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:43:53 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:44:03 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:44:03 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:44:08 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:44:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:08 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:44:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:44:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:44:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:44:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:44:09 storageqe-109 stratisd[4947]: [2025-10-07T20:44:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:44:09 storageqe-109 stratisd[4947]: [2025-10-07T20:44:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:44:18 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:44:19 storageqe-109 stratisd[4947]: [2025-10-07T20:44:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:44:19 storageqe-109 stratisd[4947]: [2025-10-07T20:44:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:44:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:44:33 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.r7rh9k13mount_test with fs xfs Oct 7 16:44:40 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem c905fed8-470d-40f5-826b-6c1d3adbb29d Oct 7 16:44:40 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:44:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r7rh9k13mount_test with fs xfs Oct 7 16:44:45 storageqe-109 systemd[1]: tmp-libblockdev.r7rh9k13mount_test.mount: Deactivated successfully. Oct 7 16:44:45 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem c905fed8-470d-40f5-826b-6c1d3adbb29d Oct 7 16:44:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:44:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dq5tjvejmount_test with fs ext4 Oct 7 16:44:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e851746b-ffe5-4624-b162-dbc2fb92ad0b r/w with ordered data mode. Quota mode: none. Oct 7 16:44:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dq5tjvejmount_test with fs ext4 Oct 7 16:45:01 storageqe-109 systemd[1]: tmp-libblockdev.dq5tjvejmount_test.mount: Deactivated successfully. Oct 7 16:45:02 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e851746b-ffe5-4624-b162-dbc2fb92ad0b. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:45:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:45:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tdmc3r9imount_test with fs ext3 Oct 7 16:45:24 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:45:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 787aba41-9e5b-465a-85e0-4691da6b274e r/w with ordered data mode. Quota mode: none. Oct 7 16:45:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tdmc3r9imount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:45:28 storageqe-109 systemd[1]: tmp-libblockdev.tdmc3r9imount_test.mount: Deactivated successfully. Oct 7 16:45:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 787aba41-9e5b-465a-85e0-4691da6b274e. Oct 7 16:45:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:45:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3h9_093nmount_test with fs ext2 Oct 7 16:45:50 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:45:50 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b6bdb6f5-4dd2-483d-a198-8ca2b9393620 r/w without journal. Quota mode: none. Oct 7 16:45:50 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3h9_093nmount_test with fs ext2 Oct 7 16:45:55 storageqe-109 systemd[1]: tmp-libblockdev.3h9_093nmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:45:55 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b6bdb6f5-4dd2-483d-a198-8ca2b9393620. Oct 7 16:45:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:45:55 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:45:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:46:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:46:17 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:46:27 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:46:27 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:46:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:46:39 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:46:49 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:46:49 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:47:19 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:48:17 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:48:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:48:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:48:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:48:17 storageqe-109 stratisd[4947]: [2025-10-07T20:48:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:48:17 storageqe-109 stratisd[4947]: [2025-10-07T20:48:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:48:27 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:48:58 storageqe-109 stratisd[4947]: [2025-10-07T20:48:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:48:58 storageqe-109 stratisd[4947]: [2025-10-07T20:48:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:49:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.igfagxd9mount_test with fs xfs Oct 7 16:49:19 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 3f29f71e-cb44-46d6-bacf-d2721e066823 Oct 7 16:49:19 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:49:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.igfagxd9mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:49:24 storageqe-109 systemd[1]: tmp-libblockdev.igfagxd9mount_test.mount: Deactivated successfully. Oct 7 16:49:24 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 3f29f71e-cb44-46d6-bacf-d2721e066823 Oct 7 16:49:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:49:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.twg4bfksmount_test with fs ext4 Oct 7 16:49:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 482e496c-ebdf-4df5-98be-44a5c96103a6 r/w with ordered data mode. Quota mode: none. Oct 7 16:49:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.twg4bfksmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:49:41 storageqe-109 systemd[1]: tmp-libblockdev.twg4bfksmount_test.mount: Deactivated successfully. Oct 7 16:49:41 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 482e496c-ebdf-4df5-98be-44a5c96103a6. Oct 7 16:49:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:49:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2nme0u33mount_test with fs ext3 Oct 7 16:50:04 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:50:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 88e390b0-ac5f-4fb9-ae58-9d8274e66d42 r/w with ordered data mode. Quota mode: none. Oct 7 16:50:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2nme0u33mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:50:09 storageqe-109 systemd[1]: tmp-libblockdev.2nme0u33mount_test.mount: Deactivated successfully. Oct 7 16:50:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 88e390b0-ac5f-4fb9-ae58-9d8274e66d42. Oct 7 16:50:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:50:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.e_c0loszmount_test with fs ext2 Oct 7 16:50:30 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:50:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d3c497cc-bd36-4415-b09b-4172cea364e9 r/w without journal. Quota mode: none. Oct 7 16:50:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.e_c0loszmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:50:36 storageqe-109 systemd[1]: tmp-libblockdev.e_c0loszmount_test.mount: Deactivated successfully. Oct 7 16:50:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d3c497cc-bd36-4415-b09b-4172cea364e9. Oct 7 16:50:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:50:36 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:50:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:50:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:50:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:51:08 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:51:08 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:51:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:51:20 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:51:30 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:51:30 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 16:52:00 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:52:58 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:52:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:52:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:52:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:52:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:52:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:52:59 storageqe-109 stratisd[4947]: [2025-10-07T20:52:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:52:59 storageqe-109 stratisd[4947]: [2025-10-07T20:52:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:53:09 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:53:39 storageqe-109 stratisd[4947]: [2025-10-07T20:53:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:53:39 storageqe-109 stratisd[4947]: [2025-10-07T20:53:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:53:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.skhtuf50mount_test with fs xfs Oct 7 16:54:00 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 237f0f2a-ccf4-4096-98ba-ec3d3858f029 Oct 7 16:54:00 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:54:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.skhtuf50mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:54:05 storageqe-109 systemd[1]: tmp-libblockdev.skhtuf50mount_test.mount: Deactivated successfully. Oct 7 16:54:05 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 237f0f2a-ccf4-4096-98ba-ec3d3858f029 Oct 7 16:54:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:54:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ks7ho5dpmount_test with fs ext4 Oct 7 16:54:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 38e7bfc4-7d2d-4dcf-ad4c-f5a2418eb33a r/w with ordered data mode. Quota mode: none. Oct 7 16:54:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ks7ho5dpmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:54:22 storageqe-109 systemd[1]: tmp-libblockdev.ks7ho5dpmount_test.mount: Deactivated successfully. Oct 7 16:54:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 38e7bfc4-7d2d-4dcf-ad4c-f5a2418eb33a. Oct 7 16:54:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:54:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i4ttqm_amount_test with fs ext3 Oct 7 16:54:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:54:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1c1bcb2c-cdeb-4708-af00-19ac199d030b r/w with ordered data mode. Quota mode: none. Oct 7 16:54:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i4ttqm_amount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:54:49 storageqe-109 systemd[1]: tmp-libblockdev.i4ttqm_amount_test.mount: Deactivated successfully. Oct 7 16:54:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1c1bcb2c-cdeb-4708-af00-19ac199d030b. Oct 7 16:54:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:54:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.23uvvw17mount_test with fs ext2 Oct 7 16:55:10 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:55:10 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9812cc02-436a-4fd5-bc49-4b7b5420182b r/w without journal. Quota mode: none. Oct 7 16:55:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.23uvvw17mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:55:15 storageqe-109 systemd[1]: tmp-libblockdev.23uvvw17mount_test.mount: Deactivated successfully. Oct 7 16:55:15 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9812cc02-436a-4fd5-bc49-4b7b5420182b. Oct 7 16:55:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:55:15 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:55:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 16:55:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:55:37 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 16:55:47 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 16:55:47 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 16:55:47 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:55:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:56:09 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 16:56:09 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 16:56:39 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 16:57:37 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 16:57:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:37 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 16:57:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 16:57:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 16:57:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 16:57:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 16:57:38 storageqe-109 stratisd[4947]: [2025-10-07T20:57:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:57:38 storageqe-109 stratisd[4947]: [2025-10-07T20:57:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:57:48 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 16:58:18 storageqe-109 stratisd[4947]: [2025-10-07T20:58:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 16:58:18 storageqe-109 stratisd[4947]: [2025-10-07T20:58:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:58:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.266r_w7umount_test with fs xfs Oct 7 16:58:39 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 17c009a5-adbf-4c72-9a92-3057f2413d85 Oct 7 16:58:39 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 16:58:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.266r_w7umount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:58:45 storageqe-109 systemd[1]: tmp-libblockdev.266r_w7umount_test.mount: Deactivated successfully. Oct 7 16:58:45 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 17c009a5-adbf-4c72-9a92-3057f2413d85 Oct 7 16:58:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 16:58:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jex_lutnmount_test with fs ext4 Oct 7 16:58:56 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9320456b-414a-4a95-824a-e1a0cc59e745 r/w with ordered data mode. Quota mode: none. Oct 7 16:58:56 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jex_lutnmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:59:02 storageqe-109 systemd[1]: tmp-libblockdev.jex_lutnmount_test.mount: Deactivated successfully. Oct 7 16:59:02 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9320456b-414a-4a95-824a-e1a0cc59e745. Oct 7 16:59:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 16:59:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kdtyxd09mount_test with fs ext3 Oct 7 16:59:24 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 16:59:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 74a5fd21-c225-4544-ac7c-c3ecec991e0a r/w with ordered data mode. Quota mode: none. Oct 7 16:59:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kdtyxd09mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:59:29 storageqe-109 systemd[1]: tmp-libblockdev.kdtyxd09mount_test.mount: Deactivated successfully. Oct 7 16:59:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 74a5fd21-c225-4544-ac7c-c3ecec991e0a. Oct 7 16:59:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 16:59:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0d5resa5mount_test with fs ext2 Oct 7 16:59:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 16:59:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b68d8faa-0b0d-4566-9a91-8a091ac459dd r/w without journal. Quota mode: none. Oct 7 16:59:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0d5resa5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 16:59:56 storageqe-109 systemd[1]: tmp-libblockdev.0d5resa5mount_test.mount: Deactivated successfully. Oct 7 16:59:56 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b68d8faa-0b0d-4566-9a91-8a091ac459dd. Oct 7 16:59:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 16:59:56 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 16:59:57 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:00:07 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:00:18 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:00:28 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:00:28 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:00:28 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:00:40 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:00:50 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:00:50 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:01:20 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:02:18 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:02:18 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:18 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:02:18 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:02:19 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:02:19 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:02:19 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:02:19 storageqe-109 stratisd[4947]: [2025-10-07T21:02:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:02:19 storageqe-109 stratisd[4947]: [2025-10-07T21:02:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:02:28 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:02:59 storageqe-109 stratisd[4947]: [2025-10-07T21:02:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:02:59 storageqe-109 stratisd[4947]: [2025-10-07T21:02:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:03:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:03:20 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 1e8cd4e8-0c0b-4a0c-9320-5bda677b2235 Oct 7 17:03:20 storageqe-109 kernel: XFS (dm-3): Ending clean mount INFO: will run io in dir /tmp/libblockdev.9e6galysmount_test with fs xfs Oct 7 17:03:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9e6galysmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:03:25 storageqe-109 systemd[1]: tmp-libblockdev.9e6galysmount_test.mount: Deactivated successfully. Oct 7 17:03:25 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 1e8cd4e8-0c0b-4a0c-9320-5bda677b2235 Oct 7 17:03:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:03:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.elv20nmzmount_test with fs ext4 Oct 7 17:03:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9069f28a-21cc-451d-8622-c91070b92c44 r/w with ordered data mode. Quota mode: none. Oct 7 17:03:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.elv20nmzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:03:42 storageqe-109 systemd[1]: tmp-libblockdev.elv20nmzmount_test.mount: Deactivated successfully. Oct 7 17:03:42 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9069f28a-21cc-451d-8622-c91070b92c44. Oct 7 17:03:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:03:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.yvgc3xsvmount_test with fs ext3 Oct 7 17:04:04 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:04:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c12e019e-00db-40e1-9a2a-5083db3f6456 r/w with ordered data mode. Quota mode: none. Oct 7 17:04:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yvgc3xsvmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:04:09 storageqe-109 systemd[1]: tmp-libblockdev.yvgc3xsvmount_test.mount: Deactivated successfully. Oct 7 17:04:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c12e019e-00db-40e1-9a2a-5083db3f6456. Oct 7 17:04:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:04:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gn7enjjmmount_test with fs ext2 Oct 7 17:04:30 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:04:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d93974d1-11e1-410a-bcff-fd4b52cbb9e3 r/w without journal. Quota mode: none. Oct 7 17:04:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gn7enjjmmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:04:35 storageqe-109 systemd[1]: tmp-libblockdev.gn7enjjmmount_test.mount: Deactivated successfully. Oct 7 17:04:35 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d93974d1-11e1-410a-bcff-fd4b52cbb9e3. Oct 7 17:04:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:04:35 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:04:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:04:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:04:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:05:08 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:05:08 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:05:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:05:19 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:05:29 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:05:29 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:05:35 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:05:35 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:05:35 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:05:35 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:05:35 storageqe-109 stratisd[4947]: [2025-10-07T21:05:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:05:35 storageqe-109 stratisd[4947]: [2025-10-07T21:05:35Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:05:45 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:05:46 storageqe-109 stratisd[4947]: [2025-10-07T21:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:05:46 storageqe-109 stratisd[4947]: [2025-10-07T21:05:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:05:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:05:59 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.g31pk1thmount_test with fs xfs Oct 7 17:06:07 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f3b2b0b6-59b2-4d05-b149-0b251d52b526 Oct 7 17:06:07 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:06:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g31pk1thmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:06:12 storageqe-109 systemd[1]: tmp-libblockdev.g31pk1thmount_test.mount: Deactivated successfully. Oct 7 17:06:12 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f3b2b0b6-59b2-4d05-b149-0b251d52b526 Oct 7 17:06:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:06:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zdaqrb6vmount_test with fs ext4 Oct 7 17:06:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3b4ae5a4-8744-4f99-8b83-9c58805376c5 r/w with ordered data mode. Quota mode: none. Oct 7 17:06:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zdaqrb6vmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:06:29 storageqe-109 systemd[1]: tmp-libblockdev.zdaqrb6vmount_test.mount: Deactivated successfully. Oct 7 17:06:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3b4ae5a4-8744-4f99-8b83-9c58805376c5. Oct 7 17:06:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:06:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:06:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.uelxjj1mmount_test with fs ext3 Oct 7 17:06:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4adae2d0-1c99-460d-a325-62b2630bfe6f r/w with ordered data mode. Quota mode: none. Oct 7 17:06:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uelxjj1mmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:06:57 storageqe-109 systemd[1]: tmp-libblockdev.uelxjj1mmount_test.mount: Deactivated successfully. Oct 7 17:06:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4adae2d0-1c99-460d-a325-62b2630bfe6f. Oct 7 17:06:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:06:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dbs1rxt3mount_test with fs ext2 Oct 7 17:07:18 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:07:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 70794ee1-cb7c-496b-92b8-7eaab5cd13ec r/w without journal. Quota mode: none. Oct 7 17:07:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dbs1rxt3mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:07:24 storageqe-109 systemd[1]: tmp-libblockdev.dbs1rxt3mount_test.mount: Deactivated successfully. Oct 7 17:07:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 70794ee1-cb7c-496b-92b8-7eaab5cd13ec. Oct 7 17:07:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:07:24 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:07:24 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:07:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:07:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:07:56 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:07:56 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:07:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:08:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:08:18 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:08:18 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:08:23 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:08:23 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:23 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:08:23 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:08:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:08:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:08:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:08:24 storageqe-109 stratisd[4947]: [2025-10-07T21:08:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:08:24 storageqe-109 stratisd[4947]: [2025-10-07T21:08:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:08:33 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:08:34 storageqe-109 stratisd[4947]: [2025-10-07T21:08:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:08:34 storageqe-109 stratisd[4947]: [2025-10-07T21:08:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:08:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:08:48 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.wn16saf9mount_test with fs xfs Oct 7 17:08:55 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem a5783995-33be-441e-bdca-f7332630639e Oct 7 17:08:55 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:08:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wn16saf9mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:09:00 storageqe-109 systemd[1]: tmp-libblockdev.wn16saf9mount_test.mount: Deactivated successfully. Oct 7 17:09:00 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem a5783995-33be-441e-bdca-f7332630639e Oct 7 17:09:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:09:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.s0xxe2_9mount_test with fs ext4 Oct 7 17:09:12 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 836464b4-cc4b-4106-9949-9799807b2c5f r/w with ordered data mode. Quota mode: none. Oct 7 17:09:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s0xxe2_9mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:09:17 storageqe-109 systemd[1]: tmp-libblockdev.s0xxe2_9mount_test.mount: Deactivated successfully. Oct 7 17:09:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 836464b4-cc4b-4106-9949-9799807b2c5f. Oct 7 17:09:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:09:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nlgapbrhmount_test with fs ext3 Oct 7 17:09:39 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:09:39 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9d80351e-e2bc-46e2-a2a4-fb9d99bef18b r/w with ordered data mode. Quota mode: none. Oct 7 17:09:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nlgapbrhmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:09:44 storageqe-109 systemd[1]: tmp-libblockdev.nlgapbrhmount_test.mount: Deactivated successfully. Oct 7 17:09:44 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9d80351e-e2bc-46e2-a2a4-fb9d99bef18b. Oct 7 17:09:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:09:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.xg0xsz3rmount_test with fs ext2 Oct 7 17:10:06 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:10:06 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem bf01567d-20b1-44c7-aefc-c1213b767b22 r/w without journal. Quota mode: none. Oct 7 17:10:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xg0xsz3rmount_test with fs ext2 Oct 7 17:10:11 storageqe-109 systemd[1]: tmp-libblockdev.xg0xsz3rmount_test.mount: Deactivated successfully. Oct 7 17:10:11 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem bf01567d-20b1-44c7-aefc-c1213b767b22. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:10:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:10:11 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:10:11 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:10:21 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:10:33 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:10:43 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:10:43 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:10:43 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:10:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:11:05 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:11:05 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:11:10 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:11:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:10 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:11:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:11:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:11:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:11:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:11:11 storageqe-109 stratisd[4947]: [2025-10-07T21:11:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:11:11 storageqe-109 stratisd[4947]: [2025-10-07T21:11:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:11:20 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:11:21 storageqe-109 stratisd[4947]: [2025-10-07T21:11:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:11:21 storageqe-109 stratisd[4947]: [2025-10-07T21:11:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:11:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:11:35 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.xp5ihrjsmount_test with fs xfs Oct 7 17:11:42 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 28327f93-c31d-4033-b1cd-0c64c9ad8986 Oct 7 17:11:42 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:11:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xp5ihrjsmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:11:48 storageqe-109 systemd[1]: tmp-libblockdev.xp5ihrjsmount_test.mount: Deactivated successfully. Oct 7 17:11:48 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 28327f93-c31d-4033-b1cd-0c64c9ad8986 Oct 7 17:11:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:11:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1hbo6saumount_test with fs ext4 Oct 7 17:11:59 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 50f3dc97-7460-4b40-918d-3619d18bdb15 r/w with ordered data mode. Quota mode: none. Oct 7 17:11:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1hbo6saumount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:12:05 storageqe-109 systemd[1]: tmp-libblockdev.1hbo6saumount_test.mount: Deactivated successfully. Oct 7 17:12:05 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 50f3dc97-7460-4b40-918d-3619d18bdb15. Oct 7 17:12:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:12:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.17sh1q6_mount_test with fs ext3 Oct 7 17:12:27 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:12:27 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5a89ee67-00b7-4a9a-a559-3908ac10d2f0 r/w with ordered data mode. Quota mode: none. Oct 7 17:12:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.17sh1q6_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:12:32 storageqe-109 systemd[1]: tmp-libblockdev.17sh1q6_mount_test.mount: Deactivated successfully. Oct 7 17:12:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5a89ee67-00b7-4a9a-a559-3908ac10d2f0. Oct 7 17:12:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:12:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.c89j8il4mount_test with fs ext2 Oct 7 17:12:54 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:12:54 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 376ba180-8236-47e8-b84c-02a062978299 r/w without journal. Quota mode: none. Oct 7 17:12:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c89j8il4mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:12:59 storageqe-109 systemd[1]: tmp-libblockdev.c89j8il4mount_test.mount: Deactivated successfully. Oct 7 17:12:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 376ba180-8236-47e8-b84c-02a062978299. Oct 7 17:12:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:12:59 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:13:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:13:10 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:13:21 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:13:31 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:13:31 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:13:32 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:13:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:13:53 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:13:53 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:13:59 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:13:59 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:13:59 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:13:59 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:13:59 storageqe-109 stratisd[4947]: [2025-10-07T21:13:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:13:59 storageqe-109 stratisd[4947]: [2025-10-07T21:13:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:14:09 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:14:10 storageqe-109 stratisd[4947]: [2025-10-07T21:14:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:14:10 storageqe-109 stratisd[4947]: [2025-10-07T21:14:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:14:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:14:23 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.tjmsgeqjmount_test with fs xfs Oct 7 17:14:31 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem ec7ac636-46d2-45c2-83d7-c26f5ac413d6 Oct 7 17:14:31 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:14:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tjmsgeqjmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:14:36 storageqe-109 systemd[1]: tmp-libblockdev.tjmsgeqjmount_test.mount: Deactivated successfully. Oct 7 17:14:36 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem ec7ac636-46d2-45c2-83d7-c26f5ac413d6 Oct 7 17:14:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:14:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ja8k4dlmmount_test with fs ext4 Oct 7 17:14:47 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 36310abc-0c15-4585-afe7-1a58e40d1f50 r/w with ordered data mode. Quota mode: none. Oct 7 17:14:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ja8k4dlmmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:14:53 storageqe-109 systemd[1]: tmp-libblockdev.ja8k4dlmmount_test.mount: Deactivated successfully. Oct 7 17:14:53 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 36310abc-0c15-4585-afe7-1a58e40d1f50. Oct 7 17:14:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:14:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:15:15 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.8w6y5ww1mount_test with fs ext3 Oct 7 17:15:15 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b3b55719-6df1-4c0e-9283-47b551153174 r/w with ordered data mode. Quota mode: none. Oct 7 17:15:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8w6y5ww1mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:15:20 storageqe-109 systemd[1]: tmp-libblockdev.8w6y5ww1mount_test.mount: Deactivated successfully. Oct 7 17:15:20 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b3b55719-6df1-4c0e-9283-47b551153174. Oct 7 17:15:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:15:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3szp5as9mount_test with fs ext2 Oct 7 17:15:42 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:15:42 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6517d15b-41c6-4e03-80f7-1fb6409e099a r/w without journal. Quota mode: none. Oct 7 17:15:42 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3szp5as9mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:15:46 storageqe-109 systemd[1]: tmp-libblockdev.3szp5as9mount_test.mount: Deactivated successfully. Oct 7 17:15:46 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6517d15b-41c6-4e03-80f7-1fb6409e099a. Oct 7 17:15:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:15:46 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:15:47 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:15:57 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:16:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:16:14 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 17:16:14 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 17:16:14 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 17:16:19 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:16:19 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:16:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:16:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:16:41 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:16:41 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:17:11 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:18:09 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:18:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:18:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:18:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:18:09 storageqe-109 stratisd[4947]: [2025-10-07T21:18:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:18:09 storageqe-109 stratisd[4947]: [2025-10-07T21:18:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:18:19 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:18:49 storageqe-109 stratisd[4947]: [2025-10-07T21:18:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:18:49 storageqe-109 stratisd[4947]: [2025-10-07T21:18:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:18:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.z_8sf_4zmount_test with fs xfs Oct 7 17:19:11 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 27b65673-b949-4028-beb5-f1fb574b30f8 Oct 7 17:19:11 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:19:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z_8sf_4zmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:19:16 storageqe-109 systemd[1]: tmp-libblockdev.z_8sf_4zmount_test.mount: Deactivated successfully. Oct 7 17:19:16 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 27b65673-b949-4028-beb5-f1fb574b30f8 Oct 7 17:19:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:19:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.lahsnpckmount_test with fs ext4 Oct 7 17:19:27 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem dad7a4a9-7012-4185-929d-d75ee7007675 r/w with ordered data mode. Quota mode: none. Oct 7 17:19:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lahsnpckmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:19:33 storageqe-109 systemd[1]: tmp-libblockdev.lahsnpckmount_test.mount: Deactivated successfully. Oct 7 17:19:33 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem dad7a4a9-7012-4185-929d-d75ee7007675. Oct 7 17:19:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:19:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g1nom73wmount_test with fs ext3 Oct 7 17:19:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:19:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6853b31f-ac4a-41f2-a28a-b21b74a0a781 r/w with ordered data mode. Quota mode: none. Oct 7 17:19:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g1nom73wmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:20:01 storageqe-109 systemd[1]: tmp-libblockdev.g1nom73wmount_test.mount: Deactivated successfully. Oct 7 17:20:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6853b31f-ac4a-41f2-a28a-b21b74a0a781. Oct 7 17:20:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:20:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.n1qg_9rwmount_test with fs ext2 Oct 7 17:20:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:20:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 68fad17e-29b7-4343-9455-e70593e27a7f r/w without journal. Quota mode: none. Oct 7 17:20:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.n1qg_9rwmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:20:27 storageqe-109 systemd[1]: tmp-libblockdev.n1qg_9rwmount_test.mount: Deactivated successfully. Oct 7 17:20:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 68fad17e-29b7-4343-9455-e70593e27a7f. Oct 7 17:20:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:20:28 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:20:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:20:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:20:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:21:00 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:21:00 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:21:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:21:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:21:22 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:21:22 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:21:52 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:22:50 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:22:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:22:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:22:50 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627558, async page read Oct 7 17:22:50 storageqe-109 stratisd[4947]: [2025-10-07T21:22:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:22:50 storageqe-109 stratisd[4947]: [2025-10-07T21:22:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:23:00 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:23:31 storageqe-109 stratisd[4947]: [2025-10-07T21:23:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:23:31 storageqe-109 stratisd[4947]: [2025-10-07T21:23:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:23:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.s5vk5gk5mount_test with fs xfs Oct 7 17:23:52 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 63037191-ccc3-47d0-af7d-62d97a883c69 Oct 7 17:23:52 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:23:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s5vk5gk5mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:23:57 storageqe-109 systemd[1]: tmp-libblockdev.s5vk5gk5mount_test.mount: Deactivated successfully. Oct 7 17:23:57 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 63037191-ccc3-47d0-af7d-62d97a883c69 Oct 7 17:23:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:23:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cc2fwohhmount_test with fs ext4 Oct 7 17:24:09 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 787f20b6-d5bc-4015-b690-1da9430c440f r/w with ordered data mode. Quota mode: none. Oct 7 17:24:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cc2fwohhmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:24:14 storageqe-109 systemd[1]: tmp-libblockdev.cc2fwohhmount_test.mount: Deactivated successfully. Oct 7 17:24:14 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 787f20b6-d5bc-4015-b690-1da9430c440f. Oct 7 17:24:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:24:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uatx1zolmount_test with fs ext3 Oct 7 17:24:36 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:24:36 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 39cf8d51-b572-4d0a-b1ab-71f0757a301a r/w with ordered data mode. Quota mode: none. Oct 7 17:24:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uatx1zolmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:24:41 storageqe-109 systemd[1]: tmp-libblockdev.uatx1zolmount_test.mount: Deactivated successfully. Oct 7 17:24:41 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 39cf8d51-b572-4d0a-b1ab-71f0757a301a. Oct 7 17:24:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:24:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.824mdhf9mount_test with fs ext2 Oct 7 17:25:03 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:25:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 128f99a5-71f9-45e2-b416-a61e62ac0f45 r/w without journal. Quota mode: none. Oct 7 17:25:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.824mdhf9mount_test with fs ext2 Oct 7 17:25:07 storageqe-109 systemd[1]: tmp-libblockdev.824mdhf9mount_test.mount: Deactivated successfully. Oct 7 17:25:07 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 128f99a5-71f9-45e2-b416-a61e62ac0f45. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:25:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:25:08 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:25:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:25:18 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:25:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:25:40 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:25:40 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:25:40 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:25:52 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:26:02 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:26:02 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:26:32 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:27:30 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:27:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:27:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:27:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:27:30 storageqe-109 stratisd[4947]: [2025-10-07T21:27:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:27:30 storageqe-109 stratisd[4947]: [2025-10-07T21:27:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:27:40 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:28:11 storageqe-109 stratisd[4947]: [2025-10-07T21:28:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:28:11 storageqe-109 stratisd[4947]: [2025-10-07T21:28:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:28:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.fkl7x98emount_test with fs xfs Oct 7 17:28:32 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 380ae87a-b307-45d1-b390-671ace133cfd Oct 7 17:28:32 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:28:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fkl7x98emount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:28:38 storageqe-109 systemd[1]: tmp-libblockdev.fkl7x98emount_test.mount: Deactivated successfully. Oct 7 17:28:38 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 380ae87a-b307-45d1-b390-671ace133cfd Oct 7 17:28:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:28:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2iawcmivmount_test with fs ext4 Oct 7 17:28:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d0bab1df-d343-4dce-8dd8-c23022558262 r/w with ordered data mode. Quota mode: none. Oct 7 17:28:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2iawcmivmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:28:55 storageqe-109 systemd[1]: tmp-libblockdev.2iawcmivmount_test.mount: Deactivated successfully. Oct 7 17:28:55 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d0bab1df-d343-4dce-8dd8-c23022558262. Oct 7 17:28:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:28:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wyi8x8zrmount_test with fs ext3 Oct 7 17:29:17 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:29:17 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1a983b52-8e83-40fd-8527-3e4fe90f34c3 r/w with ordered data mode. Quota mode: none. Oct 7 17:29:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wyi8x8zrmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:29:22 storageqe-109 systemd[1]: tmp-libblockdev.wyi8x8zrmount_test.mount: Deactivated successfully. Oct 7 17:29:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1a983b52-8e83-40fd-8527-3e4fe90f34c3. Oct 7 17:29:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:29:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nmx906sqmount_test with fs ext2 Oct 7 17:29:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:29:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem afcc7908-7c59-4dcd-9dcd-ec5dde797766 r/w without journal. Quota mode: none. Oct 7 17:29:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nmx906sqmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:29:49 storageqe-109 systemd[1]: tmp-libblockdev.nmx906sqmount_test.mount: Deactivated successfully. Oct 7 17:29:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem afcc7908-7c59-4dcd-9dcd-ec5dde797766. Oct 7 17:29:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:29:49 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:29:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:30:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:30:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:30:22 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:30:22 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:30:22 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:30:33 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:30:43 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:30:43 storageqe-109 journal: cryptsetup --cipher 'capi:cbc(aes)-essiv:sha3-256' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:31:13 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:32:12 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:32:12 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:32:12 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:32:12 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:32:12 storageqe-109 stratisd[4947]: [2025-10-07T21:32:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:32:12 storageqe-109 stratisd[4947]: [2025-10-07T21:32:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:32:22 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:32:53 storageqe-109 stratisd[4947]: [2025-10-07T21:32:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:32:53 storageqe-109 stratisd[4947]: [2025-10-07T21:32:53Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:33:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.tg4iw456mount_test with fs xfs Oct 7 17:33:14 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 50530c24-4fb6-445a-bf42-ab8f96227fb1 Oct 7 17:33:14 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:33:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tg4iw456mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:33:19 storageqe-109 systemd[1]: tmp-libblockdev.tg4iw456mount_test.mount: Deactivated successfully. Oct 7 17:33:19 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 50530c24-4fb6-445a-bf42-ab8f96227fb1 Oct 7 17:33:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:33:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.sel5tp45mount_test with fs ext4 Oct 7 17:33:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 42b17f7a-0125-4cc5-a0e0-c97795da526a r/w with ordered data mode. Quota mode: none. Oct 7 17:33:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sel5tp45mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:33:36 storageqe-109 systemd[1]: tmp-libblockdev.sel5tp45mount_test.mount: Deactivated successfully. Oct 7 17:33:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 42b17f7a-0125-4cc5-a0e0-c97795da526a. Oct 7 17:33:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:33:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kh2xfhxymount_test with fs ext3 Oct 7 17:33:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:33:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 622681ee-a956-4a31-b373-c9945df9002d r/w with ordered data mode. Quota mode: none. Oct 7 17:33:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kh2xfhxymount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:34:03 storageqe-109 systemd[1]: tmp-libblockdev.kh2xfhxymount_test.mount: Deactivated successfully. Oct 7 17:34:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 622681ee-a956-4a31-b373-c9945df9002d. Oct 7 17:34:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:34:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f25pgy4nmount_test with fs ext2 Oct 7 17:34:24 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:34:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 60d3e08d-a85d-490a-8d07-c2c78eb3e552 r/w without journal. Quota mode: none. Oct 7 17:34:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f25pgy4nmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:34:29 storageqe-109 systemd[1]: tmp-libblockdev.f25pgy4nmount_test.mount: Deactivated successfully. Oct 7 17:34:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 60d3e08d-a85d-490a-8d07-c2c78eb3e552. Oct 7 17:34:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:34:29 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:34:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:34:40 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:34:51 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:35:01 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:35:02 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:35:02 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:35:13 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:35:23 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:35:23 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:35:29 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:35:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:35:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:35:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:35:29 storageqe-109 stratisd[4947]: [2025-10-07T21:35:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:35:29 storageqe-109 stratisd[4947]: [2025-10-07T21:35:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:35:39 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:35:39 storageqe-109 stratisd[4947]: [2025-10-07T21:35:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:35:39 storageqe-109 stratisd[4947]: [2025-10-07T21:35:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:35:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:35:53 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.ieish3g_mount_test with fs xfs Oct 7 17:36:01 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 1ce0d143-df23-4d07-8c2d-d44870526636 Oct 7 17:36:01 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:36:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ieish3g_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:36:07 storageqe-109 systemd[1]: tmp-libblockdev.ieish3g_mount_test.mount: Deactivated successfully. Oct 7 17:36:07 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 1ce0d143-df23-4d07-8c2d-d44870526636 Oct 7 17:36:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:36:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tkhaw7slmount_test with fs ext4 Oct 7 17:36:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 87128d3c-ed84-47cc-958a-bac686402224 r/w with ordered data mode. Quota mode: none. Oct 7 17:36:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tkhaw7slmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:36:24 storageqe-109 systemd[1]: tmp-libblockdev.tkhaw7slmount_test.mount: Deactivated successfully. Oct 7 17:36:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 87128d3c-ed84-47cc-958a-bac686402224. Oct 7 17:36:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:36:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.cez89d0tmount_test with fs ext3 Oct 7 17:36:49 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:36:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2286d576-6d55-4481-a571-ee9f214f066f r/w with ordered data mode. Quota mode: none. Oct 7 17:36:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.cez89d0tmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:36:55 storageqe-109 systemd[1]: tmp-libblockdev.cez89d0tmount_test.mount: Deactivated successfully. Oct 7 17:36:55 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2286d576-6d55-4481-a571-ee9f214f066f. Oct 7 17:36:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:36:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jl0siqecmount_test with fs ext2 Oct 7 17:37:19 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:37:19 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b5d9994e-9ba1-4fa4-8174-1d381af9290f r/w without journal. Quota mode: none. Oct 7 17:37:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jl0siqecmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:37:25 storageqe-109 systemd[1]: tmp-libblockdev.jl0siqecmount_test.mount: Deactivated successfully. Oct 7 17:37:25 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b5d9994e-9ba1-4fa4-8174-1d381af9290f. Oct 7 17:37:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:37:25 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:37:26 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:37:36 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:37:47 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:37:58 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:37:58 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:37:58 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:38:09 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:38:19 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:38:19 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:38:25 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:38:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:38:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:38:25 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:38:25 storageqe-109 stratisd[4947]: [2025-10-07T21:38:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:38:25 storageqe-109 stratisd[4947]: [2025-10-07T21:38:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:38:35 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:38:36 storageqe-109 stratisd[4947]: [2025-10-07T21:38:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:38:36 storageqe-109 stratisd[4947]: [2025-10-07T21:38:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:38:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:38:49 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:38:57 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 5572c7f9-dd0d-4a26-bab0-2950729593b7 Oct 7 17:38:57 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:38:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2xvxmoqomount_test with fs xfs INFO: will run io in dir /tmp/libblockdev.2xvxmoqomount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:39:02 storageqe-109 systemd[1]: tmp-libblockdev.2xvxmoqomount_test.mount: Deactivated successfully. Oct 7 17:39:02 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 5572c7f9-dd0d-4a26-bab0-2950729593b7 Oct 7 17:39:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:39:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f9bpgqkjmount_test with fs ext4 Oct 7 17:39:13 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem bc7a14aa-df9b-4805-ac09-ddd91cc50d6f r/w with ordered data mode. Quota mode: none. Oct 7 17:39:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f9bpgqkjmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:39:18 storageqe-109 systemd[1]: tmp-libblockdev.f9bpgqkjmount_test.mount: Deactivated successfully. Oct 7 17:39:18 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem bc7a14aa-df9b-4805-ac09-ddd91cc50d6f. Oct 7 17:39:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:39:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.x47si6lfmount_test with fs ext3 Oct 7 17:39:40 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:39:40 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8a5d6a91-fb1d-4681-986c-06d2a854b144 r/w with ordered data mode. Quota mode: none. Oct 7 17:39:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x47si6lfmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:39:45 storageqe-109 systemd[1]: tmp-libblockdev.x47si6lfmount_test.mount: Deactivated successfully. Oct 7 17:39:45 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8a5d6a91-fb1d-4681-986c-06d2a854b144. Oct 7 17:39:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:39:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9dxmavjlmount_test with fs ext2 Oct 7 17:40:06 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:40:06 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a4bd2571-82b4-462e-8965-b379d42d4ad5 r/w without journal. Quota mode: none. Oct 7 17:40:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9dxmavjlmount_test with fs ext2 Oct 7 17:40:11 storageqe-109 systemd[1]: tmp-libblockdev.9dxmavjlmount_test.mount: Deactivated successfully. Oct 7 17:40:11 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a4bd2571-82b4-462e-8965-b379d42d4ad5. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:40:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:40:11 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:40:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:40:22 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:40:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:40:44 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:40:44 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:40:44 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:40:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:41:05 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:41:05 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:41:11 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:41:11 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:41:11 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:41:11 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:41:11 storageqe-109 stratisd[4947]: [2025-10-07T21:41:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:41:11 storageqe-109 stratisd[4947]: [2025-10-07T21:41:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:41:21 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:41:22 storageqe-109 stratisd[4947]: [2025-10-07T21:41:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:41:22 storageqe-109 stratisd[4947]: [2025-10-07T21:41:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:41:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:41:35 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.8ofzwdjgmount_test with fs xfs Oct 7 17:41:43 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem dbd69141-d986-43ac-87b1-416dc56cd897 Oct 7 17:41:43 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:41:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8ofzwdjgmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:41:49 storageqe-109 systemd[1]: tmp-libblockdev.8ofzwdjgmount_test.mount: Deactivated successfully. Oct 7 17:41:49 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem dbd69141-d986-43ac-87b1-416dc56cd897 Oct 7 17:41:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:41:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ratuw4gzmount_test with fs ext4 Oct 7 17:42:00 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2c1f0138-7c49-486b-8b6e-45b85e85535b r/w with ordered data mode. Quota mode: none. Oct 7 17:42:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ratuw4gzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:42:06 storageqe-109 systemd[1]: tmp-libblockdev.ratuw4gzmount_test.mount: Deactivated successfully. Oct 7 17:42:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2c1f0138-7c49-486b-8b6e-45b85e85535b. Oct 7 17:42:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:42:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev._my95a3amount_test with fs ext3 Oct 7 17:42:31 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:42:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ca95aa75-1558-4b26-b4df-4902db8d3e84 r/w with ordered data mode. Quota mode: none. Oct 7 17:42:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev._my95a3amount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:42:37 storageqe-109 systemd[1]: tmp-libblockdev._my95a3amount_test.mount: Deactivated successfully. Oct 7 17:42:37 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ca95aa75-1558-4b26-b4df-4902db8d3e84. Oct 7 17:42:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:42:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hjqmfs27mount_test with fs ext2 Oct 7 17:43:01 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:43:01 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5ccaa68a-af15-4a34-ab97-c85655faf60d r/w without journal. Quota mode: none. Oct 7 17:43:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hjqmfs27mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:43:07 storageqe-109 systemd[1]: tmp-libblockdev.hjqmfs27mount_test.mount: Deactivated successfully. Oct 7 17:43:07 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5ccaa68a-af15-4a34-ab97-c85655faf60d. Oct 7 17:43:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:43:07 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:43:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:43:18 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:43:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:43:39 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:43:39 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:43:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:43:51 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:44:01 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:44:01 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:44:07 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:44:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:44:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:44:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:44:07 storageqe-109 stratisd[4947]: [2025-10-07T21:44:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:44:07 storageqe-109 stratisd[4947]: [2025-10-07T21:44:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:44:17 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:44:18 storageqe-109 stratisd[4947]: [2025-10-07T21:44:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:44:18 storageqe-109 stratisd[4947]: [2025-10-07T21:44:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:44:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:44:31 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.5tr5fzdbmount_test with fs xfs Oct 7 17:44:39 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem b7a3b2a3-28fd-4473-855f-5b3ea91eb966 Oct 7 17:44:39 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:44:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5tr5fzdbmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:44:44 storageqe-109 systemd[1]: tmp-libblockdev.5tr5fzdbmount_test.mount: Deactivated successfully. Oct 7 17:44:44 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem b7a3b2a3-28fd-4473-855f-5b3ea91eb966 Oct 7 17:44:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:44:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.wxazi0f3mount_test with fs ext4 Oct 7 17:44:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7df948af-97df-4673-bab4-63fdc55cb1ed r/w with ordered data mode. Quota mode: none. Oct 7 17:44:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wxazi0f3mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:45:01 storageqe-109 systemd[1]: tmp-libblockdev.wxazi0f3mount_test.mount: Deactivated successfully. Oct 7 17:45:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7df948af-97df-4673-bab4-63fdc55cb1ed. Oct 7 17:45:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:45:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:45:23 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.1a7i8dtjmount_test with fs ext3 Oct 7 17:45:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1e95dc46-cb18-401c-9aa6-d137fd094ce2 r/w with ordered data mode. Quota mode: none. Oct 7 17:45:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1a7i8dtjmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:45:28 storageqe-109 systemd[1]: tmp-libblockdev.1a7i8dtjmount_test.mount: Deactivated successfully. Oct 7 17:45:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1e95dc46-cb18-401c-9aa6-d137fd094ce2. Oct 7 17:45:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:45:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.woq6tronmount_test with fs ext2 Oct 7 17:45:49 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:45:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 977308f7-cf6d-474a-9c96-d9b5c8b9afe2 r/w without journal. Quota mode: none. Oct 7 17:45:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.woq6tronmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:45:54 storageqe-109 systemd[1]: tmp-libblockdev.woq6tronmount_test.mount: Deactivated successfully. Oct 7 17:45:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 977308f7-cf6d-474a-9c96-d9b5c8b9afe2. Oct 7 17:45:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:45:54 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:45:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:46:04 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:46:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:46:26 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:46:26 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:46:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:46:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:46:48 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:46:48 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:47:18 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:48:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:48:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:48:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:48:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:48:17 storageqe-109 stratisd[4947]: [2025-10-07T21:48:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:48:17 storageqe-109 stratisd[4947]: [2025-10-07T21:48:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:48:26 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:48:57 storageqe-109 stratisd[4947]: [2025-10-07T21:48:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:48:57 storageqe-109 stratisd[4947]: [2025-10-07T21:48:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:49:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.c324_cswmount_test with fs xfs Oct 7 17:49:18 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 943b2741-d1cf-492c-97e1-bc761d9321b5 Oct 7 17:49:18 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:49:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c324_cswmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:49:24 storageqe-109 systemd[1]: tmp-libblockdev.c324_cswmount_test.mount: Deactivated successfully. Oct 7 17:49:24 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 943b2741-d1cf-492c-97e1-bc761d9321b5 Oct 7 17:49:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:49:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ugnzn4asmount_test with fs ext4 Oct 7 17:49:35 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6136613f-e02a-4e3b-9733-fda3b762731a r/w with ordered data mode. Quota mode: none. Oct 7 17:49:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ugnzn4asmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:49:42 storageqe-109 systemd[1]: tmp-libblockdev.ugnzn4asmount_test.mount: Deactivated successfully. Oct 7 17:49:42 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6136613f-e02a-4e3b-9733-fda3b762731a. Oct 7 17:49:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:49:42 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.er4yrfeumount_test with fs ext3 Oct 7 17:50:06 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:50:07 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 53fc52ff-286d-44fd-abc0-2846fc1a5102 r/w with ordered data mode. Quota mode: none. Oct 7 17:50:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.er4yrfeumount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:50:12 storageqe-109 systemd[1]: tmp-libblockdev.er4yrfeumount_test.mount: Deactivated successfully. Oct 7 17:50:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 53fc52ff-286d-44fd-abc0-2846fc1a5102. Oct 7 17:50:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:50:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:50:36 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 17:50:36 storageqe-109 dnf[2110089]: Updating Subscription Management repositories. Oct 7 17:50:36 storageqe-109 dnf[2110089]: Unable to read consumer identity Oct 7 17:50:36 storageqe-109 dnf[2110089]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 17:50:36 storageqe-109 dnf[2110089]: Metadata cache refreshed recently. Oct 7 17:50:36 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 17:50:36 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. INFO: will run io in dir /tmp/libblockdev.7a_wwl88mount_test with fs ext2 Oct 7 17:50:37 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:50:37 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem cc1824ae-23ab-4728-830b-fb5ce982612a r/w without journal. Quota mode: none. Oct 7 17:50:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7a_wwl88mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:50:43 storageqe-109 systemd[1]: tmp-libblockdev.7a_wwl88mount_test.mount: Deactivated successfully. Oct 7 17:50:43 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem cc1824ae-23ab-4728-830b-fb5ce982612a. Oct 7 17:50:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:50:43 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:50:43 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:50:53 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:51:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:51:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:51:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:51:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:51:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:51:37 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:51:37 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 17:52:07 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:53:05 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:05 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:53:05 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:53:05 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:53:06 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:53:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:53:06 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:53:06 storageqe-109 stratisd[4947]: [2025-10-07T21:53:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:53:06 storageqe-109 stratisd[4947]: [2025-10-07T21:53:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:53:16 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:53:46 storageqe-109 stratisd[4947]: [2025-10-07T21:53:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:53:46 storageqe-109 stratisd[4947]: [2025-10-07T21:53:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:53:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.j3dmh0i_mount_test with fs xfs Oct 7 17:54:07 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 473d10e6-1a10-49a3-9cb2-a51d27729955 Oct 7 17:54:07 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:54:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j3dmh0i_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:54:12 storageqe-109 systemd[1]: tmp-libblockdev.j3dmh0i_mount_test.mount: Deactivated successfully. Oct 7 17:54:12 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 473d10e6-1a10-49a3-9cb2-a51d27729955 Oct 7 17:54:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:54:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.k04fcketmount_test with fs ext4 Oct 7 17:54:24 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8c508009-7056-4fed-9238-adcce256dc3b r/w with ordered data mode. Quota mode: none. Oct 7 17:54:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k04fcketmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:54:29 storageqe-109 systemd[1]: tmp-libblockdev.k04fcketmount_test.mount: Deactivated successfully. Oct 7 17:54:29 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8c508009-7056-4fed-9238-adcce256dc3b. Oct 7 17:54:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:54:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y6mphnofmount_test with fs ext3 Oct 7 17:54:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:54:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f834f94e-3d54-4e2d-ae2d-42e2f2a909c0 r/w with ordered data mode. Quota mode: none. Oct 7 17:54:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y6mphnofmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:54:56 storageqe-109 systemd[1]: tmp-libblockdev.y6mphnofmount_test.mount: Deactivated successfully. Oct 7 17:54:56 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f834f94e-3d54-4e2d-ae2d-42e2f2a909c0. Oct 7 17:54:56 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:54:56 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.gn7xab22mount_test with fs ext2 Oct 7 17:55:17 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 17:55:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b5faf12c-06b6-4bac-ae75-f61c267b29d7 r/w without journal. Quota mode: none. Oct 7 17:55:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.gn7xab22mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 17:55:22 storageqe-109 systemd[1]: tmp-libblockdev.gn7xab22mount_test.mount: Deactivated successfully. Oct 7 17:55:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b5faf12c-06b6-4bac-ae75-f61c267b29d7. Oct 7 17:55:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:55:22 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:55:23 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 17:55:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:55:45 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 17:55:55 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 17:55:55 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 17:55:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 17:56:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:56:16 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 17:56:17 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 17:56:47 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 17:57:45 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 17:57:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 17:57:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 17:57:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 17:57:45 storageqe-109 stratisd[4947]: [2025-10-07T21:57:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:57:45 storageqe-109 stratisd[4947]: [2025-10-07T21:57:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:57:55 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 17:58:26 storageqe-109 stratisd[4947]: [2025-10-07T21:58:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 17:58:26 storageqe-109 stratisd[4947]: [2025-10-07T21:58:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:58:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:58:47 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 7b3930c3-091d-43ce-80ff-ddc2d1834d2d INFO: will run io in dir /tmp/libblockdev.yjxss9osmount_test with fs xfs Oct 7 17:58:47 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 17:58:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.yjxss9osmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:58:53 storageqe-109 systemd[1]: tmp-libblockdev.yjxss9osmount_test.mount: Deactivated successfully. Oct 7 17:58:53 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 7b3930c3-091d-43ce-80ff-ddc2d1834d2d Oct 7 17:58:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 17:58:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qfhzyp91mount_test with fs ext4 Oct 7 17:59:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ebe49356-8f82-4cc3-be5f-58bfc500a24b r/w with ordered data mode. Quota mode: none. Oct 7 17:59:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qfhzyp91mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:59:10 storageqe-109 systemd[1]: tmp-libblockdev.qfhzyp91mount_test.mount: Deactivated successfully. Oct 7 17:59:10 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ebe49356-8f82-4cc3-be5f-58bfc500a24b. Oct 7 17:59:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 17:59:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jnz8fp2qmount_test with fs ext3 Oct 7 17:59:35 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 17:59:35 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d744a38b-a59f-4d2f-81f8-a6cbabd6ac80 r/w with ordered data mode. Quota mode: none. Oct 7 17:59:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jnz8fp2qmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 17:59:41 storageqe-109 systemd[1]: tmp-libblockdev.jnz8fp2qmount_test.mount: Deactivated successfully. Oct 7 17:59:41 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d744a38b-a59f-4d2f-81f8-a6cbabd6ac80. Oct 7 17:59:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 17:59:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bl13ouk6mount_test with fs ext2 Oct 7 18:00:05 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:00:05 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 08e93018-b7ee-4e46-9757-dd5f1f74e239 r/w without journal. Quota mode: none. Oct 7 18:00:05 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bl13ouk6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:00:11 storageqe-109 systemd[1]: tmp-libblockdev.bl13ouk6mount_test.mount: Deactivated successfully. Oct 7 18:00:11 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 08e93018-b7ee-4e46-9757-dd5f1f74e239. Oct 7 18:00:11 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:00:11 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:00:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:00:22 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:00:34 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:00:44 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:00:44 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:00:44 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:00:56 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:01:06 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:01:06 storageqe-109 journal: cryptsetup --cipher 'twofish-ecb' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:01:36 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:02:34 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:02:34 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:02:34 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:02:34 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:02:34 storageqe-109 stratisd[4947]: [2025-10-07T22:02:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:02:34 storageqe-109 stratisd[4947]: [2025-10-07T22:02:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:02:44 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:03:15 storageqe-109 stratisd[4947]: [2025-10-07T22:03:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:03:15 storageqe-109 stratisd[4947]: [2025-10-07T22:03:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:03:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.254wnrijmount_test with fs xfs Oct 7 18:03:36 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 4a341c16-6e53-4abd-be66-c928cc8794c1 Oct 7 18:03:36 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:03:36 storageqe-109 INFO: will run io in dir /tmp/libblockdev.254wnrijmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:03:41 storageqe-109 systemd[1]: tmp-libblockdev.254wnrijmount_test.mount: Deactivated successfully. Oct 7 18:03:41 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 4a341c16-6e53-4abd-be66-c928cc8794c1 Oct 7 18:03:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:03:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.awse0elomount_test with fs ext4 Oct 7 18:03:52 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem aae7d944-1426-4577-8a70-dec5624a43ef r/w with ordered data mode. Quota mode: none. Oct 7 18:03:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.awse0elomount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:03:57 storageqe-109 systemd[1]: tmp-libblockdev.awse0elomount_test.mount: Deactivated successfully. Oct 7 18:03:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem aae7d944-1426-4577-8a70-dec5624a43ef. Oct 7 18:03:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:03:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kn4fjux7mount_test with fs ext3 Oct 7 18:04:19 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:04:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ef1c9740-a985-4c73-b4d1-359256482884 r/w with ordered data mode. Quota mode: none. Oct 7 18:04:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kn4fjux7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:04:24 storageqe-109 systemd[1]: tmp-libblockdev.kn4fjux7mount_test.mount: Deactivated successfully. Oct 7 18:04:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ef1c9740-a985-4c73-b4d1-359256482884. Oct 7 18:04:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:04:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mlrdd1_0mount_test with fs ext2 Oct 7 18:04:46 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:04:46 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 90536c15-47de-4bca-b3f4-881ab15668cb r/w without journal. Quota mode: none. Oct 7 18:04:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mlrdd1_0mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:04:51 storageqe-109 systemd[1]: tmp-libblockdev.mlrdd1_0mount_test.mount: Deactivated successfully. Oct 7 18:04:51 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 90536c15-47de-4bca-b3f4-881ab15668cb. Oct 7 18:04:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:04:51 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:04:51 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:05:01 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:05:13 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:05:23 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:05:23 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:05:23 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:05:35 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:05:45 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:05:45 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:05:50 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:05:50 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:50 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:05:50 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:05:51 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:05:51 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:05:51 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:05:51 storageqe-109 stratisd[4947]: [2025-10-07T22:05:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:05:51 storageqe-109 stratisd[4947]: [2025-10-07T22:05:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:06:00 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:06:01 storageqe-109 stratisd[4947]: [2025-10-07T22:06:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:06:01 storageqe-109 stratisd[4947]: [2025-10-07T22:06:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:06:11 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:06:15 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:06:24 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem c9edf6d1-aa37-4e25-a396-2478bd862639 Oct 7 18:06:24 storageqe-109 kernel: XFS (dm-3): Ending clean mount INFO: will run io in dir /tmp/libblockdev.bthtomr2mount_test with fs xfs Oct 7 18:06:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bthtomr2mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:06:30 storageqe-109 systemd[1]: tmp-libblockdev.bthtomr2mount_test.mount: Deactivated successfully. Oct 7 18:06:30 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem c9edf6d1-aa37-4e25-a396-2478bd862639 Oct 7 18:06:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:06:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._kk_erprmount_test with fs ext4 Oct 7 18:06:43 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6ff254c2-8b07-4c0f-97c9-19cbf5c3f0f6 r/w with ordered data mode. Quota mode: none. Oct 7 18:06:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev._kk_erprmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:06:50 storageqe-109 systemd[1]: tmp-libblockdev._kk_erprmount_test.mount: Deactivated successfully. Oct 7 18:06:50 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6ff254c2-8b07-4c0f-97c9-19cbf5c3f0f6. Oct 7 18:06:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:06:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rncb3l6mmount_test with fs ext3 Oct 7 18:07:54 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:07:54 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem e250905a-e575-46ed-856e-ad08032dd759 r/w with ordered data mode. Quota mode: none. Oct 7 18:07:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rncb3l6mmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:08:01 storageqe-109 systemd[1]: tmp-libblockdev.rncb3l6mmount_test.mount: Deactivated successfully. Oct 7 18:08:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem e250905a-e575-46ed-856e-ad08032dd759. Oct 7 18:08:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:08:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qyhcfgbdmount_test with fs ext2 Oct 7 18:09:03 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:09:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 476aec68-1359-48bc-8076-6a2b604c7564 r/w without journal. Quota mode: none. Oct 7 18:09:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qyhcfgbdmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:09:09 storageqe-109 systemd[1]: tmp-libblockdev.qyhcfgbdmount_test.mount: Deactivated successfully. Oct 7 18:09:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 476aec68-1359-48bc-8076-6a2b604c7564. Oct 7 18:09:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:09:10 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:09:10 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:09:20 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:09:32 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:09:42 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:09:42 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:09:42 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:09:54 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:10:04 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:10:04 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:10:09 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:10:09 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:10:09 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:10:09 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:10:10 storageqe-109 stratisd[4947]: [2025-10-07T22:10:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:10:10 storageqe-109 stratisd[4947]: [2025-10-07T22:10:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:10:19 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:10:20 storageqe-109 stratisd[4947]: [2025-10-07T22:10:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:10:20 storageqe-109 stratisd[4947]: [2025-10-07T22:10:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:10:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:10:34 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.p4joyu_0mount_test with fs xfs Oct 7 18:10:41 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f37ca535-d045-449c-9767-1bf5a56d437f Oct 7 18:10:41 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:10:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p4joyu_0mount_test with fs xfs Oct 7 18:10:46 storageqe-109 systemd[1]: tmp-libblockdev.p4joyu_0mount_test.mount: Deactivated successfully. Oct 7 18:10:46 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f37ca535-d045-449c-9767-1bf5a56d437f INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:10:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:10:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r83r0tgrmount_test with fs ext4 Oct 7 18:10:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d3de5677-233a-44f0-b784-6eefe39c0bf6 r/w with ordered data mode. Quota mode: none. Oct 7 18:10:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r83r0tgrmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:11:03 storageqe-109 systemd[1]: tmp-libblockdev.r83r0tgrmount_test.mount: Deactivated successfully. Oct 7 18:11:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d3de5677-233a-44f0-b784-6eefe39c0bf6. Oct 7 18:11:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:11:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qwaxbkcmmount_test with fs ext3 Oct 7 18:11:25 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:11:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7f6b625d-3602-4ff5-aba3-ff02cc319929 r/w with ordered data mode. Quota mode: none. Oct 7 18:11:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qwaxbkcmmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:11:30 storageqe-109 systemd[1]: tmp-libblockdev.qwaxbkcmmount_test.mount: Deactivated successfully. Oct 7 18:11:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7f6b625d-3602-4ff5-aba3-ff02cc319929. Oct 7 18:11:31 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:11:31 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y8tx2goamount_test with fs ext2 Oct 7 18:11:52 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:11:52 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a64e17db-608a-4f89-b4be-2ae3fea99075 r/w without journal. Quota mode: none. Oct 7 18:11:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y8tx2goamount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:11:57 storageqe-109 systemd[1]: tmp-libblockdev.y8tx2goamount_test.mount: Deactivated successfully. Oct 7 18:11:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a64e17db-608a-4f89-b4be-2ae3fea99075. Oct 7 18:11:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:11:57 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:11:57 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:12:07 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:12:19 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:12:29 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:12:29 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:12:29 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:12:41 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:12:51 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:12:51 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:12:56 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:12:56 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:56 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:12:56 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:12:57 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:12:57 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:12:57 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:12:57 storageqe-109 stratisd[4947]: [2025-10-07T22:12:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:12:57 storageqe-109 stratisd[4947]: [2025-10-07T22:12:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:13:06 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:13:07 storageqe-109 stratisd[4947]: [2025-10-07T22:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:13:07 storageqe-109 stratisd[4947]: [2025-10-07T22:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:13:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:13:21 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.t66jel0_mount_test with fs xfs Oct 7 18:13:30 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 46396e54-2618-4867-a5fd-45f4144db1d5 Oct 7 18:13:30 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:13:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t66jel0_mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:13:36 storageqe-109 systemd[1]: tmp-libblockdev.t66jel0_mount_test.mount: Deactivated successfully. Oct 7 18:13:36 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 46396e54-2618-4867-a5fd-45f4144db1d5 Oct 7 18:13:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:13:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.p3wtcg3bmount_test with fs ext4 Oct 7 18:13:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 4f5f8694-c6b8-4cce-b599-0c39deaf5d01 r/w with ordered data mode. Quota mode: none. Oct 7 18:13:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p3wtcg3bmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:13:56 storageqe-109 systemd[1]: tmp-libblockdev.p3wtcg3bmount_test.mount: Deactivated successfully. Oct 7 18:13:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 4f5f8694-c6b8-4cce-b599-0c39deaf5d01. Oct 7 18:13:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:13:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.aqo1k0avmount_test with fs ext3 Oct 7 18:15:01 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:15:01 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ce9160d3-4939-4ce2-bfc5-098b9e224fbd r/w with ordered data mode. Quota mode: none. Oct 7 18:15:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.aqo1k0avmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:15:08 storageqe-109 systemd[1]: tmp-libblockdev.aqo1k0avmount_test.mount: Deactivated successfully. Oct 7 18:15:08 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ce9160d3-4939-4ce2-bfc5-098b9e224fbd. Oct 7 18:15:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:15:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kwbxx18bmount_test with fs ext2 Oct 7 18:16:10 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:16:10 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 462c96a3-4e7f-4297-bb5a-dfe08b85040d r/w without journal. Quota mode: none. Oct 7 18:16:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kwbxx18bmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:16:16 storageqe-109 systemd[1]: tmp-libblockdev.kwbxx18bmount_test.mount: Deactivated successfully. Oct 7 18:16:16 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 462c96a3-4e7f-4297-bb5a-dfe08b85040d. Oct 7 18:16:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:16:16 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:16:17 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:16:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:16:39 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:16:49 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:16:49 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:16:49 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:17:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:17:10 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:17:10 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:17:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:17:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:17:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:17:16 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:17:16 storageqe-109 stratisd[4947]: [2025-10-07T22:17:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:17:16 storageqe-109 stratisd[4947]: [2025-10-07T22:17:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:17:26 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:17:27 storageqe-109 stratisd[4947]: [2025-10-07T22:17:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:17:27 storageqe-109 stratisd[4947]: [2025-10-07T22:17:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:17:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:17:41 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.x2qsrt0zmount_test with fs xfs Oct 7 18:17:48 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 000d3ee0-474d-4466-890d-c7b1b98669de Oct 7 18:17:48 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:17:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x2qsrt0zmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:17:53 storageqe-109 systemd[1]: tmp-libblockdev.x2qsrt0zmount_test.mount: Deactivated successfully. Oct 7 18:17:53 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 000d3ee0-474d-4466-890d-c7b1b98669de Oct 7 18:17:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:17:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.th_7bazfmount_test with fs ext4 Oct 7 18:18:04 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 44095551-f86f-41c7-b9a8-d861809a3863 r/w with ordered data mode. Quota mode: none. Oct 7 18:18:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.th_7bazfmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:18:10 storageqe-109 systemd[1]: tmp-libblockdev.th_7bazfmount_test.mount: Deactivated successfully. Oct 7 18:18:10 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 44095551-f86f-41c7-b9a8-d861809a3863. Oct 7 18:18:10 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:18:10 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.09dlajncmount_test with fs ext3 Oct 7 18:18:32 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:18:32 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 62783fcb-d5c5-49c4-b8d9-ae089d9250e7 r/w with ordered data mode. Quota mode: none. Oct 7 18:18:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.09dlajncmount_test with fs ext3 Oct 7 18:18:37 storageqe-109 systemd[1]: tmp-libblockdev.09dlajncmount_test.mount: Deactivated successfully. Oct 7 18:18:37 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 62783fcb-d5c5-49c4-b8d9-ae089d9250e7. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:18:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:18:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h6uwd_immount_test with fs ext2 Oct 7 18:18:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:18:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0cfe9ac5-d780-47c1-ade0-7bf2b5fa74e0 r/w without journal. Quota mode: none. Oct 7 18:18:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h6uwd_immount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:19:03 storageqe-109 systemd[1]: tmp-libblockdev.h6uwd_immount_test.mount: Deactivated successfully. Oct 7 18:19:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0cfe9ac5-d780-47c1-ade0-7bf2b5fa74e0. Oct 7 18:19:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:19:03 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:19:04 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:19:14 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:19:25 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:19:35 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:19:35 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:19:36 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:19:47 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:19:57 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:19:57 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:20:27 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:21:25 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:21:25 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:25 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:21:25 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:21:26 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:21:26 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:21:26 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:21:26 storageqe-109 stratisd[4947]: [2025-10-07T22:21:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:21:26 storageqe-109 stratisd[4947]: [2025-10-07T22:21:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:21:36 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:22:06 storageqe-109 stratisd[4947]: [2025-10-07T22:22:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:22:06 storageqe-109 stratisd[4947]: [2025-10-07T22:22:06Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:22:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.lpesptt9mount_test with fs xfs Oct 7 18:22:29 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 195736d5-f28f-4f76-a9d5-4d230f95cf0f Oct 7 18:22:29 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:22:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.lpesptt9mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:22:35 storageqe-109 systemd[1]: tmp-libblockdev.lpesptt9mount_test.mount: Deactivated successfully. Oct 7 18:22:35 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 195736d5-f28f-4f76-a9d5-4d230f95cf0f Oct 7 18:22:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:22:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._f91eyj3mount_test with fs ext4 Oct 7 18:22:48 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7d05dbb3-0cc5-4bf0-927e-9345e0585f2b r/w with ordered data mode. Quota mode: none. Oct 7 18:22:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev._f91eyj3mount_test with fs ext4 Oct 7 18:22:55 storageqe-109 systemd[1]: tmp-libblockdev._f91eyj3mount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:22:55 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7d05dbb3-0cc5-4bf0-927e-9345e0585f2b. Oct 7 18:22:55 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:22:55 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j8q0q1kpmount_test with fs ext3 Oct 7 18:23:59 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:23:59 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0f1080af-b835-48be-a3f2-8eea48de4a5f r/w with ordered data mode. Quota mode: none. Oct 7 18:23:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j8q0q1kpmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:24:06 storageqe-109 systemd[1]: tmp-libblockdev.j8q0q1kpmount_test.mount: Deactivated successfully. Oct 7 18:24:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0f1080af-b835-48be-a3f2-8eea48de4a5f. Oct 7 18:24:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:24:06 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.tpi7tgyjmount_test with fs ext2 Oct 7 18:25:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:25:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5f18bfb5-ddfa-4f8b-90bf-9aee131defe8 r/w without journal. Quota mode: none. Oct 7 18:25:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.tpi7tgyjmount_test with fs ext2 Oct 7 18:25:15 storageqe-109 systemd[1]: tmp-libblockdev.tpi7tgyjmount_test.mount: Deactivated successfully. Oct 7 18:25:15 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5f18bfb5-ddfa-4f8b-90bf-9aee131defe8. INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:25:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:25:15 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:25:15 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:25:25 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:25:37 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:25:47 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:25:47 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:25:47 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:25:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:26:09 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:26:09 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:26:39 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:27:37 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:27:37 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:27:37 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:27:37 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:27:37 storageqe-109 stratisd[4947]: [2025-10-07T22:27:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:27:37 storageqe-109 stratisd[4947]: [2025-10-07T22:27:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:27:47 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:28:17 storageqe-109 stratisd[4947]: [2025-10-07T22:28:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:28:17 storageqe-109 stratisd[4947]: [2025-10-07T22:28:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:28:27 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:28:39 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 4b511b82-840b-4b9f-8af3-d7a4d2b27984 INFO: will run io in dir /tmp/libblockdev.irbq6r0vmount_test with fs xfs Oct 7 18:28:39 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:28:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.irbq6r0vmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:28:43 storageqe-109 systemd[1]: tmp-libblockdev.irbq6r0vmount_test.mount: Deactivated successfully. Oct 7 18:28:43 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 4b511b82-840b-4b9f-8af3-d7a4d2b27984 Oct 7 18:28:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:28:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0_12_p3gmount_test with fs ext4 Oct 7 18:28:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2697e67b-f058-4f61-aab5-8fd42564a949 r/w with ordered data mode. Quota mode: none. Oct 7 18:28:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0_12_p3gmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:29:01 storageqe-109 systemd[1]: tmp-libblockdev.0_12_p3gmount_test.mount: Deactivated successfully. Oct 7 18:29:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2697e67b-f058-4f61-aab5-8fd42564a949. Oct 7 18:29:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:29:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z8590ucbmount_test with fs ext3 Oct 7 18:29:23 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:29:23 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 87607874-33be-4377-a759-a748d034bda9 r/w with ordered data mode. Quota mode: none. Oct 7 18:29:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z8590ucbmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:29:28 storageqe-109 systemd[1]: tmp-libblockdev.z8590ucbmount_test.mount: Deactivated successfully. Oct 7 18:29:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 87607874-33be-4377-a759-a748d034bda9. Oct 7 18:29:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:29:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.j6cy66dhmount_test with fs ext2 Oct 7 18:29:49 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:29:49 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 958c0ef5-a21f-4dad-9718-1cb66b4564ea r/w without journal. Quota mode: none. Oct 7 18:29:49 storageqe-109 INFO: will run io in dir /tmp/libblockdev.j6cy66dhmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:29:54 storageqe-109 systemd[1]: tmp-libblockdev.j6cy66dhmount_test.mount: Deactivated successfully. Oct 7 18:29:54 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 958c0ef5-a21f-4dad-9718-1cb66b4564ea. Oct 7 18:29:54 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:29:54 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:29:55 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:30:05 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:30:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:30:26 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:30:26 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:30:27 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:30:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:30:48 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:30:48 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:31:18 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:32:16 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:32:16 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:16 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:32:16 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:32:17 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:32:17 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:32:17 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:32:17 storageqe-109 stratisd[4947]: [2025-10-07T22:32:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:32:17 storageqe-109 stratisd[4947]: [2025-10-07T22:32:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:32:27 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:32:57 storageqe-109 stratisd[4947]: [2025-10-07T22:32:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:32:57 storageqe-109 stratisd[4947]: [2025-10-07T22:32:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:33:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.fzf_n5mxmount_test with fs xfs Oct 7 18:33:20 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 48b909b2-1487-4614-9a41-586ae12034f2 Oct 7 18:33:20 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:33:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fzf_n5mxmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:33:26 storageqe-109 systemd[1]: tmp-libblockdev.fzf_n5mxmount_test.mount: Deactivated successfully. Oct 7 18:33:26 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 48b909b2-1487-4614-9a41-586ae12034f2 Oct 7 18:33:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:33:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z9nfoqxzmount_test with fs ext4 Oct 7 18:33:39 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 97af078d-c761-4951-a5eb-b30b4df9149b r/w with ordered data mode. Quota mode: none. Oct 7 18:33:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z9nfoqxzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:33:47 storageqe-109 systemd[1]: tmp-libblockdev.z9nfoqxzmount_test.mount: Deactivated successfully. Oct 7 18:33:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 97af078d-c761-4951-a5eb-b30b4df9149b. Oct 7 18:33:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:33:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ep49ajatmount_test with fs ext3 Oct 7 18:34:51 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:34:51 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem aa7b9574-8385-451c-b9ea-93633485b0a9 r/w with ordered data mode. Quota mode: none. Oct 7 18:34:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ep49ajatmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:34:58 storageqe-109 systemd[1]: tmp-libblockdev.ep49ajatmount_test.mount: Deactivated successfully. Oct 7 18:34:58 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem aa7b9574-8385-451c-b9ea-93633485b0a9. Oct 7 18:34:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:34:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3gvbi_22mount_test with fs ext2 Oct 7 18:36:00 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:36:00 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d1ec5fc3-2099-4f68-8c94-9dfca730059f r/w without journal. Quota mode: none. Oct 7 18:36:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3gvbi_22mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:36:06 storageqe-109 systemd[1]: tmp-libblockdev.3gvbi_22mount_test.mount: Deactivated successfully. Oct 7 18:36:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d1ec5fc3-2099-4f68-8c94-9dfca730059f. Oct 7 18:36:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:36:06 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:36:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:36:17 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:36:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:36:39 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:36:39 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:36:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:36:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:37:00 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:37:00 storageqe-109 journal: cryptsetup --cipher 'serpent-cbc-plain' --type 'luks2' --key-size '256' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:37:31 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:38:28 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:38:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:28 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:38:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:38:29 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:38:29 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:38:29 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:38:29 storageqe-109 stratisd[4947]: [2025-10-07T22:38:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:38:29 storageqe-109 stratisd[4947]: [2025-10-07T22:38:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:38:39 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:39:09 storageqe-109 stratisd[4947]: [2025-10-07T22:39:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:39:09 storageqe-109 stratisd[4947]: [2025-10-07T22:39:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:39:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2et6gok6mount_test with fs xfs Oct 7 18:39:30 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 3c795b46-8a24-4dbb-b61e-d8cdaee477c7 Oct 7 18:39:30 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:39:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2et6gok6mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:39:35 storageqe-109 systemd[1]: tmp-libblockdev.2et6gok6mount_test.mount: Deactivated successfully. Oct 7 18:39:35 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 3c795b46-8a24-4dbb-b61e-d8cdaee477c7 Oct 7 18:39:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:39:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ggfc4ztkmount_test with fs ext4 Oct 7 18:39:47 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a3f3abd2-e37a-4725-92eb-2ed5c50ad75f r/w with ordered data mode. Quota mode: none. Oct 7 18:39:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ggfc4ztkmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:39:52 storageqe-109 systemd[1]: tmp-libblockdev.ggfc4ztkmount_test.mount: Deactivated successfully. Oct 7 18:39:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a3f3abd2-e37a-4725-92eb-2ed5c50ad75f. Oct 7 18:39:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:39:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:40:14 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.i869yd7_mount_test with fs ext3 Oct 7 18:40:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 85a526e1-9647-4ecf-a4f4-36eed10b4c9a r/w with ordered data mode. Quota mode: none. Oct 7 18:40:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i869yd7_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:40:19 storageqe-109 systemd[1]: tmp-libblockdev.i869yd7_mount_test.mount: Deactivated successfully. Oct 7 18:40:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 85a526e1-9647-4ecf-a4f4-36eed10b4c9a. Oct 7 18:40:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:40:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vccddf7jmount_test with fs ext2 Oct 7 18:40:41 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:40:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 3fc4b0ad-75c9-45ce-b7db-d1305dd482c2 r/w without journal. Quota mode: none. Oct 7 18:40:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vccddf7jmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:40:45 storageqe-109 systemd[1]: tmp-libblockdev.vccddf7jmount_test.mount: Deactivated successfully. Oct 7 18:40:45 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 3fc4b0ad-75c9-45ce-b7db-d1305dd482c2. Oct 7 18:40:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:40:45 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:40:46 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:40:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:41:08 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:41:18 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:41:18 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:41:18 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:41:30 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:41:40 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:41:40 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:41:45 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:41:45 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:41:45 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:41:45 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:41:45 storageqe-109 stratisd[4947]: [2025-10-07T22:41:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:41:45 storageqe-109 stratisd[4947]: [2025-10-07T22:41:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:41:55 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:41:55 storageqe-109 stratisd[4947]: [2025-10-07T22:41:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:41:55 storageqe-109 stratisd[4947]: [2025-10-07T22:41:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:42:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:42:10 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.vlbflh4bmount_test with fs xfs Oct 7 18:42:17 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 928ede5d-0dcf-4a75-b8f7-536480187fce Oct 7 18:42:17 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:42:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vlbflh4bmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:42:23 storageqe-109 systemd[1]: tmp-libblockdev.vlbflh4bmount_test.mount: Deactivated successfully. Oct 7 18:42:23 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 928ede5d-0dcf-4a75-b8f7-536480187fce Oct 7 18:42:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:42:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pkm1abzfmount_test with fs ext4 Oct 7 18:42:34 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 6b53def2-6b14-40eb-9f9d-03fd5919cfeb r/w with ordered data mode. Quota mode: none. Oct 7 18:42:34 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pkm1abzfmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:42:40 storageqe-109 systemd[1]: tmp-libblockdev.pkm1abzfmount_test.mount: Deactivated successfully. Oct 7 18:42:40 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 6b53def2-6b14-40eb-9f9d-03fd5919cfeb. Oct 7 18:42:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:42:40 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4nzxy217mount_test with fs ext3 Oct 7 18:43:06 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:43:06 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem ca4528ed-7ab4-4bc8-8188-ec3d1c6358b6 r/w with ordered data mode. Quota mode: none. Oct 7 18:43:06 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4nzxy217mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:43:12 storageqe-109 systemd[1]: tmp-libblockdev.4nzxy217mount_test.mount: Deactivated successfully. Oct 7 18:43:12 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem ca4528ed-7ab4-4bc8-8188-ec3d1c6358b6. Oct 7 18:43:12 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:43:12 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.i8fak3jhmount_test with fs ext2 Oct 7 18:43:37 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:43:37 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f502f128-2cf5-4c5c-8e55-c31675387e2f r/w without journal. Quota mode: none. Oct 7 18:43:37 storageqe-109 INFO: will run io in dir /tmp/libblockdev.i8fak3jhmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:43:43 storageqe-109 systemd[1]: tmp-libblockdev.i8fak3jhmount_test.mount: Deactivated successfully. Oct 7 18:43:43 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f502f128-2cf5-4c5c-8e55-c31675387e2f. Oct 7 18:43:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:43:43 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:43:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:43:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:44:05 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:44:15 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:44:15 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:44:15 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:44:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:44:37 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:44:37 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:44:43 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:44:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:44:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:44:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:44:43 storageqe-109 stratisd[4947]: [2025-10-07T22:44:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:44:43 storageqe-109 stratisd[4947]: [2025-10-07T22:44:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:44:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:44:54 storageqe-109 stratisd[4947]: [2025-10-07T22:44:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:44:54 storageqe-109 stratisd[4947]: [2025-10-07T22:44:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:45:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:45:07 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.mbwei65pmount_test with fs xfs Oct 7 18:45:15 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem d5308ba4-551d-4d5b-a9ef-6681a37331ce Oct 7 18:45:15 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:45:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mbwei65pmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:45:20 storageqe-109 systemd[1]: tmp-libblockdev.mbwei65pmount_test.mount: Deactivated successfully. Oct 7 18:45:20 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem d5308ba4-551d-4d5b-a9ef-6681a37331ce Oct 7 18:45:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:45:20 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qa65g_zmmount_test with fs ext4 Oct 7 18:45:31 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f42e67aa-ba0d-412a-959a-1bf25dce9e37 r/w with ordered data mode. Quota mode: none. Oct 7 18:45:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qa65g_zmmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:45:37 storageqe-109 systemd[1]: tmp-libblockdev.qa65g_zmmount_test.mount: Deactivated successfully. Oct 7 18:45:37 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f42e67aa-ba0d-412a-959a-1bf25dce9e37. Oct 7 18:45:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:45:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8ymnd3almount_test with fs ext3 Oct 7 18:45:59 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:45:59 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 32ec5e65-1e21-48f2-8579-f0136683483b r/w with ordered data mode. Quota mode: none. Oct 7 18:45:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8ymnd3almount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:46:04 storageqe-109 systemd[1]: tmp-libblockdev.8ymnd3almount_test.mount: Deactivated successfully. Oct 7 18:46:04 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 32ec5e65-1e21-48f2-8579-f0136683483b. Oct 7 18:46:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:46:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.sq4guupemount_test with fs ext2 Oct 7 18:46:25 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:46:25 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d3906c84-d991-457d-bb33-c435a6a2b92a r/w without journal. Quota mode: none. Oct 7 18:46:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sq4guupemount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:46:30 storageqe-109 systemd[1]: tmp-libblockdev.sq4guupemount_test.mount: Deactivated successfully. Oct 7 18:46:30 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d3906c84-d991-457d-bb33-c435a6a2b92a. Oct 7 18:46:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:46:30 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:46:31 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:46:41 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:46:53 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:47:03 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:47:03 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:47:03 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:47:14 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:47:24 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:47:24 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:47:24 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 18:47:25 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 18:47:25 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 18:47:30 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:47:30 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:47:30 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:47:30 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:47:30 storageqe-109 stratisd[4947]: [2025-10-07T22:47:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:47:30 storageqe-109 stratisd[4947]: [2025-10-07T22:47:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:47:40 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:47:41 storageqe-109 stratisd[4947]: [2025-10-07T22:47:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:47:41 storageqe-109 stratisd[4947]: [2025-10-07T22:47:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:47:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:47:54 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.nmoa8kscmount_test with fs xfs Oct 7 18:48:02 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 6de213a8-1261-496e-8e62-cdd24fea7f11 Oct 7 18:48:02 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:48:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nmoa8kscmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:48:08 storageqe-109 systemd[1]: tmp-libblockdev.nmoa8kscmount_test.mount: Deactivated successfully. Oct 7 18:48:08 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 6de213a8-1261-496e-8e62-cdd24fea7f11 Oct 7 18:48:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:48:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8k68wl4dmount_test with fs ext4 Oct 7 18:48:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d4aca9c9-c502-49c5-87d1-8545e1eec957 r/w with ordered data mode. Quota mode: none. Oct 7 18:48:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8k68wl4dmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:48:26 storageqe-109 systemd[1]: tmp-libblockdev.8k68wl4dmount_test.mount: Deactivated successfully. Oct 7 18:48:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d4aca9c9-c502-49c5-87d1-8545e1eec957. Oct 7 18:48:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:48:26 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.k_frxgjgmount_test with fs ext3 Oct 7 18:48:52 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:48:52 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1a248487-24d5-4c8f-8099-595e08c3fe5c r/w with ordered data mode. Quota mode: none. Oct 7 18:48:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k_frxgjgmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:48:57 storageqe-109 systemd[1]: tmp-libblockdev.k_frxgjgmount_test.mount: Deactivated successfully. Oct 7 18:48:57 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1a248487-24d5-4c8f-8099-595e08c3fe5c. Oct 7 18:48:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:48:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rzclipolmount_test with fs ext2 Oct 7 18:49:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:49:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 486448c2-c75a-465b-b96e-497d5620081d r/w without journal. Quota mode: none. Oct 7 18:49:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rzclipolmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:49:28 storageqe-109 systemd[1]: tmp-libblockdev.rzclipolmount_test.mount: Deactivated successfully. Oct 7 18:49:28 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 486448c2-c75a-465b-b96e-497d5620081d. Oct 7 18:49:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:49:28 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:49:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:49:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:49:51 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:50:01 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:50:01 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:50:01 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:50:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:50:22 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:50:23 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '20' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:50:28 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:50:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:50:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:50:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:50:28 storageqe-109 stratisd[4947]: [2025-10-07T22:50:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:50:28 storageqe-109 stratisd[4947]: [2025-10-07T22:50:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:50:38 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:50:39 storageqe-109 stratisd[4947]: [2025-10-07T22:50:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:50:39 storageqe-109 stratisd[4947]: [2025-10-07T22:50:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:50:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:50:53 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.ojychg2kmount_test with fs xfs Oct 7 18:51:00 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem a9c31bf6-a539-45f3-85cc-dc7bbdf6dff1 Oct 7 18:51:00 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:51:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ojychg2kmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:51:05 storageqe-109 systemd[1]: tmp-libblockdev.ojychg2kmount_test.mount: Deactivated successfully. Oct 7 18:51:05 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem a9c31bf6-a539-45f3-85cc-dc7bbdf6dff1 Oct 7 18:51:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:51:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bz_eomxgmount_test with fs ext4 Oct 7 18:51:16 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1835ea75-961c-4c92-9660-c32cb6cbbf39 r/w with ordered data mode. Quota mode: none. Oct 7 18:51:16 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bz_eomxgmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:51:22 storageqe-109 systemd[1]: tmp-libblockdev.bz_eomxgmount_test.mount: Deactivated successfully. Oct 7 18:51:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1835ea75-961c-4c92-9660-c32cb6cbbf39. Oct 7 18:51:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:51:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.qbkomonimount_test with fs ext3 Oct 7 18:51:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:51:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 19d1fdcb-8bd3-4ee0-afd7-959ae0e1af5c r/w with ordered data mode. Quota mode: none. Oct 7 18:51:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qbkomonimount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:51:49 storageqe-109 systemd[1]: tmp-libblockdev.qbkomonimount_test.mount: Deactivated successfully. Oct 7 18:51:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 19d1fdcb-8bd3-4ee0-afd7-959ae0e1af5c. Oct 7 18:51:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:51:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1euih3a3mount_test with fs ext2 Oct 7 18:52:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:52:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2ba165d4-1681-473d-8207-ce26947df913 r/w without journal. Quota mode: none. Oct 7 18:52:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1euih3a3mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:52:15 storageqe-109 systemd[1]: tmp-libblockdev.1euih3a3mount_test.mount: Deactivated successfully. Oct 7 18:52:15 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2ba165d4-1681-473d-8207-ce26947df913. Oct 7 18:52:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:52:15 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:52:16 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:52:26 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:52:38 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:52:48 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:52:48 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:52:48 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:53:00 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:53:10 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:53:10 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 18:53:40 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:54:38 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:54:38 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:54:38 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:54:38 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:54:38 storageqe-109 stratisd[4947]: [2025-10-07T22:54:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:54:38 storageqe-109 stratisd[4947]: [2025-10-07T22:54:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:54:48 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:55:19 storageqe-109 stratisd[4947]: [2025-10-07T22:55:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:55:19 storageqe-109 stratisd[4947]: [2025-10-07T22:55:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:55:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.xbxzefv0mount_test with fs xfs Oct 7 18:55:40 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem adfd99d0-2567-477c-af2c-69aa447ba85c Oct 7 18:55:40 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 18:55:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.xbxzefv0mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:55:46 storageqe-109 systemd[1]: tmp-libblockdev.xbxzefv0mount_test.mount: Deactivated successfully. Oct 7 18:55:46 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem adfd99d0-2567-477c-af2c-69aa447ba85c Oct 7 18:55:46 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 18:55:46 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hpwhk_ykmount_test with fs ext4 Oct 7 18:55:57 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 0a6fcd70-9ac1-46b6-92f4-675bd56d216d r/w with ordered data mode. Quota mode: none. Oct 7 18:55:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hpwhk_ykmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:56:03 storageqe-109 systemd[1]: tmp-libblockdev.hpwhk_ykmount_test.mount: Deactivated successfully. Oct 7 18:56:03 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 0a6fcd70-9ac1-46b6-92f4-675bd56d216d. Oct 7 18:56:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 18:56:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8v8dn7apmount_test with fs ext3 Oct 7 18:56:29 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 18:56:29 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 80253865-975e-41d7-a332-8553db666ec6 r/w with ordered data mode. Quota mode: none. Oct 7 18:56:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8v8dn7apmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:56:35 storageqe-109 systemd[1]: tmp-libblockdev.8v8dn7apmount_test.mount: Deactivated successfully. Oct 7 18:56:35 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 80253865-975e-41d7-a332-8553db666ec6. Oct 7 18:56:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 18:56:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ru_wdqo5mount_test with fs ext2 Oct 7 18:57:00 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 18:57:00 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem efc70400-e5df-4d81-bd99-cf9a9f7550bd r/w without journal. Quota mode: none. Oct 7 18:57:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ru_wdqo5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 18:57:06 storageqe-109 systemd[1]: tmp-libblockdev.ru_wdqo5mount_test.mount: Deactivated successfully. Oct 7 18:57:06 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem efc70400-e5df-4d81-bd99-cf9a9f7550bd. Oct 7 18:57:06 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 18:57:06 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:57:06 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 18:57:16 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:57:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 18:57:38 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 18:57:38 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 18:57:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 18:57:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:58:00 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 18:58:00 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha256' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 18:58:30 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 18:59:28 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 18:59:28 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 18:59:28 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 18:59:28 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 18:59:29 storageqe-109 stratisd[4947]: [2025-10-07T22:59:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 18:59:29 storageqe-109 stratisd[4947]: [2025-10-07T22:59:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 18:59:38 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 19:00:09 storageqe-109 stratisd[4947]: [2025-10-07T23:00:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:00:09 storageqe-109 stratisd[4947]: [2025-10-07T23:00:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 19:00:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.k5c8j1t6mount_test with fs xfs Oct 7 19:00:30 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem ed5b9b20-b170-465e-99d3-e29ffc98df4e Oct 7 19:00:30 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:00:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.k5c8j1t6mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 19:00:35 storageqe-109 systemd[1]: tmp-libblockdev.k5c8j1t6mount_test.mount: Deactivated successfully. Oct 7 19:00:35 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem ed5b9b20-b170-465e-99d3-e29ffc98df4e Oct 7 19:00:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 19:00:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3j72bbpnmount_test with fs ext4 Oct 7 19:00:47 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c7e70137-ff61-45b4-af8f-d67333510fae r/w with ordered data mode. Quota mode: none. Oct 7 19:00:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3j72bbpnmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 19:00:52 storageqe-109 systemd[1]: tmp-libblockdev.3j72bbpnmount_test.mount: Deactivated successfully. Oct 7 19:00:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c7e70137-ff61-45b4-af8f-d67333510fae. Oct 7 19:00:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 19:00:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nplbqymqmount_test with fs ext3 Oct 7 19:01:14 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:01:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem cd486f80-bffa-42e7-8636-4aa3bd973499 r/w with ordered data mode. Quota mode: none. Oct 7 19:01:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nplbqymqmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 19:01:19 storageqe-109 systemd[1]: tmp-libblockdev.nplbqymqmount_test.mount: Deactivated successfully. Oct 7 19:01:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem cd486f80-bffa-42e7-8636-4aa3bd973499. Oct 7 19:01:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 19:01:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6jeifkc5mount_test with fs ext2 Oct 7 19:01:40 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:01:40 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem cc2bb3e6-ba8c-4254-a09d-ef9ba8594010 r/w without journal. Quota mode: none. Oct 7 19:01:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6jeifkc5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 19:01:45 storageqe-109 systemd[1]: tmp-libblockdev.6jeifkc5mount_test.mount: Deactivated successfully. Oct 7 19:01:45 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem cc2bb3e6-ba8c-4254-a09d-ef9ba8594010. Oct 7 19:01:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 19:01:45 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:01:45 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 19:01:55 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:02:07 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:02:17 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 19:02:17 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 19:02:17 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:02:29 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:02:39 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 19:02:39 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:03:09 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 19:04:07 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 19:04:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:07 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 19:04:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:04:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:07 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 19:04:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 19:04:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:07 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:07 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 19:04:07 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 19:04:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 19:04:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 19:04:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 19:04:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 19:04:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 19:04:08 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:04:08 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 19:04:08 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 19:04:08 storageqe-109 stratisd[4947]: [2025-10-07T23:04:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:04:08 storageqe-109 stratisd[4947]: [2025-10-07T23:04:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 19:04:17 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 19:04:48 storageqe-109 stratisd[4947]: [2025-10-07T23:04:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:04:48 storageqe-109 stratisd[4947]: [2025-10-07T23:04:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 19:04:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 19:05:09 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem f179a015-3634-43b8-946c-aec680ce89cf INFO: will run io in dir /tmp/libblockdev.sdw790hrmount_test with fs xfs Oct 7 19:05:09 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:05:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.sdw790hrmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 19:05:15 storageqe-109 systemd[1]: tmp-libblockdev.sdw790hrmount_test.mount: Deactivated successfully. Oct 7 19:05:15 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem f179a015-3634-43b8-946c-aec680ce89cf Oct 7 19:05:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 19:05:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h209glvzmount_test with fs ext4 Oct 7 19:05:26 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem a2accc1e-f75a-4ea8-b1dc-aa676b570f2c r/w with ordered data mode. Quota mode: none. Oct 7 19:05:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h209glvzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 19:05:32 storageqe-109 systemd[1]: tmp-libblockdev.h209glvzmount_test.mount: Deactivated successfully. Oct 7 19:05:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem a2accc1e-f75a-4ea8-b1dc-aa676b570f2c. Oct 7 19:05:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 19:05:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.3tkpvi51mount_test with fs ext3 Oct 7 19:05:58 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:05:58 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f18333de-4ae1-436c-8fdc-61f7cefef081 r/w with ordered data mode. Quota mode: none. Oct 7 19:05:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3tkpvi51mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 19:06:04 storageqe-109 systemd[1]: tmp-libblockdev.3tkpvi51mount_test.mount: Deactivated successfully. Oct 7 19:06:04 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f18333de-4ae1-436c-8fdc-61f7cefef081. Oct 7 19:06:04 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 19:06:04 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6ymrgd_jmount_test with fs ext2 Oct 7 19:06:30 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:06:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d7481165-81d6-4f08-851b-a16c1fbabed5 r/w without journal. Quota mode: none. Oct 7 19:06:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6ymrgd_jmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 19:06:36 storageqe-109 systemd[1]: tmp-libblockdev.6ymrgd_jmount_test.mount: Deactivated successfully. Oct 7 19:06:36 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d7481165-81d6-4f08-851b-a16c1fbabed5. Oct 7 19:06:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 19:06:36 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:06:36 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 19:06:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:06:58 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:07:08 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 19:07:08 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 19:07:08 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:07:20 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 19:07:30 storageqe-109 INFO: finishe the remove crypt device IjxF Oct 7 19:07:30 storageqe-109 journal: cryptsetup --cipher 'twofish-xts-plain64' --type 'luks2' --key-size '512' --hash 'sha512' --iter-time '30000' --sector-size '4096' luksFormat /dev/nvme0n1 -q --hw-opal-only Oct 7 19:08:00 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 19:08:58 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 19:08:58 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:08:58 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 19:08:58 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 19:08:58 storageqe-109 stratisd[4947]: [2025-10-07T23:08:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:08:58 storageqe-109 stratisd[4947]: [2025-10-07T23:08:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 19:09:08 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 IjxF -q --allow-discards Oct 7 19:09:39 storageqe-109 stratisd[4947]: [2025-10-07T23:09:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:09:39 storageqe-109 stratisd[4947]: [2025-10-07T23:09:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 19:09:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.l4ez8yflmount_test with fs xfs Oct 7 19:10:01 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem a4a78699-4411-4ede-8764-6e9d39f1e6a6 Oct 7 19:10:01 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:10:01 storageqe-109 INFO: will run io in dir /tmp/libblockdev.l4ez8yflmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 19:10:05 storageqe-109 systemd[1]: tmp-libblockdev.l4ez8yflmount_test.mount: Deactivated successfully. Oct 7 19:10:05 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem a4a78699-4411-4ede-8764-6e9d39f1e6a6 Oct 7 19:10:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs xfs in remove_crypt Oct 7 19:10:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.74qtonotmount_test with fs ext4 Oct 7 19:10:17 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8c82e1a0-41dd-4477-ac3e-ae3e0a334f18 r/w with ordered data mode. Quota mode: none. Oct 7 19:10:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.74qtonotmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt Oct 7 19:10:22 storageqe-109 systemd[1]: tmp-libblockdev.74qtonotmount_test.mount: Deactivated successfully. Oct 7 19:10:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8c82e1a0-41dd-4477-ac3e-ae3e0a334f18. Oct 7 19:10:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 19:10:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.17qrxt8omount_test with fs ext3 Oct 7 19:10:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:10:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem fcd34c31-5ab0-4781-bad7-83704ce9de60 r/w with ordered data mode. Quota mode: none. Oct 7 19:10:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev.17qrxt8omount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 19:10:49 storageqe-109 systemd[1]: tmp-libblockdev.17qrxt8omount_test.mount: Deactivated successfully. Oct 7 19:10:49 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem fcd34c31-5ab0-4781-bad7-83704ce9de60. Oct 7 19:10:49 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext3 in remove_crypt Oct 7 19:10:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.phh3lddgmount_test with fs ext2 Oct 7 19:11:10 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:11:10 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 9081a375-57d9-4c9c-9833-be0cc49a2fbf r/w without journal. Quota mode: none. Oct 7 19:11:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.phh3lddgmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt INFO: remove crypt device IjxF Oct 7 19:11:15 storageqe-109 systemd[1]: tmp-libblockdev.phh3lddgmount_test.mount: Deactivated successfully. Oct 7 19:11:15 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 9081a375-57d9-4c9c-9833-be0cc49a2fbf. Oct 7 19:11:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IjxF and fs ext2 in remove_crypt Oct 7 19:11:15 storageqe-109 INFO: remove crypt device IjxF cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:11:15 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 19:11:25 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:11:37 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:11:47 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 19:11:47 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 19:11:47 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:11:59 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device IjxF Oct 7 19:12:09 storageqe-109 INFO: finishe the remove crypt device IjxF cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:12:10 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:12:21 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:12:21 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_hw_luks_paramter #### INFO: #### will start test_hw_luks_bz1750680 ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:12:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:12:36 storageqe-109 INFO: #### END test_hw_luks_paramter #### Oct 7 19:12:36 storageqe-109 INFO: #### will start test_hw_luks_bz1750680 ##### Oct 7 19:12:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:12:43 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:12:53 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:12:54 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:13:04 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:13:14 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 19:13:14 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:14 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 19:13:14 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 19:13:15 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:13:15 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 19:13:15 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 19:13:15 storageqe-109 stratisd[4947]: [2025-10-07T23:13:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:13:15 storageqe-109 stratisd[4947]: [2025-10-07T23:13:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 FOxH -q --disable-keyring Oct 7 19:13:24 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 FOxH -q --disable-keyring Oct 7 19:13:27 storageqe-109 stratisd[4947]: [2025-10-07T23:13:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:13:27 storageqe-109 stratisd[4947]: [2025-10-07T23:13:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:13:34 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/FOxH and fs xfs in remove_crypt Oct 7 19:13:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FOxH and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.u8bjbwsmmount_test with fs xfs Oct 7 19:13:47 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 3b83b122-837d-4e37-8ca7-aa2ee4d44c2a Oct 7 19:13:47 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:13:47 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u8bjbwsmmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/FOxH and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FOxH and fs ext4 in remove_crypt Oct 7 19:13:53 storageqe-109 systemd[1]: tmp-libblockdev.u8bjbwsmmount_test.mount: Deactivated successfully. Oct 7 19:13:53 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 3b83b122-837d-4e37-8ca7-aa2ee4d44c2a Oct 7 19:13:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FOxH and fs xfs in remove_crypt Oct 7 19:13:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FOxH and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z98r_tmcmount_test with fs ext4 Oct 7 19:14:03 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 477c0e64-500a-4f10-b52e-c2797af3d4e4 r/w with ordered data mode. Quota mode: none. Oct 7 19:14:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z98r_tmcmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/FOxH and fs ext4 in remove_crypt Oct 7 19:14:09 storageqe-109 systemd[1]: tmp-libblockdev.z98r_tmcmount_test.mount: Deactivated successfully. Oct 7 19:14:09 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 477c0e64-500a-4f10-b52e-c2797af3d4e4. Oct 7 19:14:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FOxH and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FOxH and fs ext3 in remove_crypt Oct 7 19:14:09 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FOxH and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ywopk_m8mount_test with fs ext3 Oct 7 19:14:30 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:14:30 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 2ca11d11-0ca1-4d72-b4c3-71ab128548c7 r/w with ordered data mode. Quota mode: none. Oct 7 19:14:30 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ywopk_m8mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/FOxH and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/FOxH and fs ext2 in remove_crypt Oct 7 19:14:35 storageqe-109 systemd[1]: tmp-libblockdev.ywopk_m8mount_test.mount: Deactivated successfully. Oct 7 19:14:35 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 2ca11d11-0ca1-4d72-b4c3-71ab128548c7. Oct 7 19:14:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FOxH and fs ext3 in remove_crypt Oct 7 19:14:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/FOxH and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f39ypj8fmount_test with fs ext2 Oct 7 19:14:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:14:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 18ee3136-cb16-4d6f-8815-f89ae9812389 r/w without journal. Quota mode: none. Oct 7 19:14:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f39ypj8fmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/FOxH and fs ext2 in remove_crypt INFO: remove crypt device FOxH Oct 7 19:15:00 storageqe-109 systemd[1]: tmp-libblockdev.f39ypj8fmount_test.mount: Deactivated successfully. Oct 7 19:15:00 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 18ee3136-cb16-4d6f-8815-f89ae9812389. Oct 7 19:15:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/FOxH and fs ext2 in remove_crypt Oct 7 19:15:00 storageqe-109 INFO: remove crypt device FOxH cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:15:01 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 19:15:11 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:15:22 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:15:32 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 19:15:33 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 19:15:33 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:15:44 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device FOxH Oct 7 19:15:54 storageqe-109 INFO: finishe the remove crypt device FOxH cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:15:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:16:06 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:16:07 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_hw_luks_bz1750680 #### INFO: #### will start test_hw_luks_bz1862173 ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:16:22 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:16:22 storageqe-109 INFO: #### END test_hw_luks_bz1750680 #### Oct 7 19:16:22 storageqe-109 INFO: #### will start test_hw_luks_bz1862173 ##### Oct 7 19:16:22 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:16:28 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:16:38 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:16:39 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:16:49 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:17:00 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 19:17:00 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:00 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 19:17:00 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 19:17:00 storageqe-109 stratisd[4947]: [2025-10-07T23:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:17:00 storageqe-109 stratisd[4947]: [2025-10-07T23:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' token add /dev/nvme0n1 -q Oct 7 19:17:10 storageqe-109 journal: cryptsetup --key-description 'mykey' token add /dev/nvme0n1 -q Oct 7 19:17:10 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 19:17:10 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:10 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 19:17:10 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 19:17:10 storageqe-109 stratisd[4947]: [2025-10-07T23:17:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:17:10 storageqe-109 stratisd[4947]: [2025-10-07T23:17:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:17:19 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --type 'luks2' open /dev/nvme0n1 SskC -q --allow-discards --token-only Oct 7 19:17:20 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 SskC -q --allow-discards --token-only Oct 7 19:17:22 storageqe-109 stratisd[4947]: [2025-10-07T23:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:17:22 storageqe-109 stratisd[4947]: [2025-10-07T23:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey1' --key-slot '1' --token-id '1' token add /dev/nvme0n1 -q Oct 7 19:17:43 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 journal: cryptsetup --key-description 'mykey1' --key-slot '1' --token-id '1' token add /dev/nvme0n1 -q Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 19:17:43 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:17:43 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 19:17:43 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 19:17:43 storageqe-109 stratisd[4947]: [2025-10-07T23:17:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:17:43 storageqe-109 stratisd[4947]: [2025-10-07T23:17:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:17:43 storageqe-109 stratisd[4947]: [2025-10-07T23:17:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 19:17:43 storageqe-109 stratisd[4947]: [2025-10-07T23:17:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:17:43 storageqe-109 stratisd[4947]: [2025-10-07T23:17:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:17:43 storageqe-109 stratisd[4947]: [2025-10-07T23:17:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/nvme0n1 SskC -q --allow-discards --token-only Oct 7 19:17:53 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/nvme0n1 SskC -q --allow-discards --token-only Oct 7 19:17:55 storageqe-109 stratisd[4947]: [2025-10-07T23:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:17:55 storageqe-109 stratisd[4947]: [2025-10-07T23:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:17:55 storageqe-109 stratisd[4947]: [2025-10-07T23:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 19:17:55 storageqe-109 stratisd[4947]: [2025-10-07T23:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:17:55 storageqe-109 stratisd[4947]: [2025-10-07T23:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:17:55 storageqe-109 stratisd[4947]: [2025-10-07T23:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup luksAddKey /dev/nvme0n1 -q --token-only Oct 7 19:18:05 storageqe-109 journal: cryptsetup luksAddKey /dev/nvme0n1 -q --token-only Oct 7 19:18:14 storageqe-109 stratisd[4947]: [2025-10-07T23:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:18:14 storageqe-109 stratisd[4947]: [2025-10-07T23:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:18:14 storageqe-109 stratisd[4947]: [2025-10-07T23:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 19:18:14 storageqe-109 stratisd[4947]: [2025-10-07T23:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:18:14 storageqe-109 stratisd[4947]: [2025-10-07T23:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:18:14 storageqe-109 stratisd[4947]: [2025-10-07T23:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup luksAddKey /dev/nvme0n1 -q --token-only /tmp/testfilezYn Oct 7 19:18:24 storageqe-109 journal: cryptsetup luksAddKey /dev/nvme0n1 -q --token-only /tmp/testfilezYn Oct 7 19:18:32 storageqe-109 stratisd[4947]: [2025-10-07T23:18:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:18:32 storageqe-109 stratisd[4947]: [2025-10-07T23:18:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:18:32 storageqe-109 stratisd[4947]: [2025-10-07T23:18:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 19:18:32 storageqe-109 stratisd[4947]: [2025-10-07T23:18:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:18:32 storageqe-109 stratisd[4947]: [2025-10-07T23:18:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:18:32 storageqe-109 stratisd[4947]: [2025-10-07T23:18:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. cryptsetup luksRemoveKey /dev/nvme0n1 -q --token-only /tmp/testfilezYn Oct 7 19:18:42 storageqe-109 journal: cryptsetup luksRemoveKey /dev/nvme0n1 -q --token-only /tmp/testfilezYn Oct 7 19:18:50 storageqe-109 stratisd[4947]: [2025-10-07T23:18:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:18:50 storageqe-109 stratisd[4947]: [2025-10-07T23:18:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:18:50 storageqe-109 stratisd[4947]: [2025-10-07T23:18:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 19:18:50 storageqe-109 stratisd[4947]: [2025-10-07T23:18:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"key_description":"mykey","keyslots":["0"],"type":"luks2-keyring"} Oct 7 19:18:50 storageqe-109 stratisd[4947]: [2025-10-07T23:18:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key key_description. Oct 7 19:18:50 storageqe-109 stratisd[4947]: [2025-10-07T23:18:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/SskC and fs xfs in remove_crypt Oct 7 19:19:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SskC and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.qrlpcsxxmount_test with fs xfs Oct 7 19:19:11 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem d6795fa3-8e5e-4c54-b3a8-c7a9533f9fe0 Oct 7 19:19:11 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:19:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.qrlpcsxxmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/SskC and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SskC and fs ext4 in remove_crypt Oct 7 19:19:16 storageqe-109 systemd[1]: tmp-libblockdev.qrlpcsxxmount_test.mount: Deactivated successfully. Oct 7 19:19:16 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem d6795fa3-8e5e-4c54-b3a8-c7a9533f9fe0 Oct 7 19:19:16 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SskC and fs xfs in remove_crypt Oct 7 19:19:16 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SskC and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._x9wjncumount_test with fs ext4 Oct 7 19:19:28 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 57c81270-b9fc-48cd-9c3f-d1c2f240c650 r/w with ordered data mode. Quota mode: none. Oct 7 19:19:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev._x9wjncumount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/SskC and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SskC and fs ext3 in remove_crypt Oct 7 19:19:33 storageqe-109 systemd[1]: tmp-libblockdev._x9wjncumount_test.mount: Deactivated successfully. Oct 7 19:19:33 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 57c81270-b9fc-48cd-9c3f-d1c2f240c650. Oct 7 19:19:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SskC and fs ext4 in remove_crypt Oct 7 19:19:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SskC and fs ext3 in remove_crypt Oct 7 19:19:55 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev.h0w63b6omount_test with fs ext3 Oct 7 19:19:55 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 10bffa71-991f-4148-a07f-0b5f9c38ebcd r/w with ordered data mode. Quota mode: none. Oct 7 19:19:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h0w63b6omount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/SskC and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/SskC and fs ext2 in remove_crypt Oct 7 19:20:01 storageqe-109 systemd[1]: tmp-libblockdev.h0w63b6omount_test.mount: Deactivated successfully. Oct 7 19:20:01 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 10bffa71-991f-4148-a07f-0b5f9c38ebcd. Oct 7 19:20:01 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SskC and fs ext3 in remove_crypt Oct 7 19:20:01 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/SskC and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ixcvzqdfmount_test with fs ext2 Oct 7 19:20:22 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:20:22 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 7f346e3e-6c84-491a-bef8-2230fbda4e13 r/w without journal. Quota mode: none. Oct 7 19:20:22 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ixcvzqdfmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/SskC and fs ext2 in remove_crypt INFO: remove crypt device SskC Oct 7 19:20:27 storageqe-109 systemd[1]: tmp-libblockdev.ixcvzqdfmount_test.mount: Deactivated successfully. Oct 7 19:20:27 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 7f346e3e-6c84-491a-bef8-2230fbda4e13. Oct 7 19:20:27 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/SskC and fs ext2 in remove_crypt Oct 7 19:20:27 storageqe-109 INFO: remove crypt device SskC cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:20:28 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 19:20:38 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:20:50 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:21:00 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 19:21:00 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 19:21:00 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:21:12 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device SskC Oct 7 19:21:22 storageqe-109 INFO: finishe the remove crypt device SskC cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:21:23 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:21:33 storageqe-109 kernel: nvme nvme0: rescanning namespaces. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:21:34 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_hw_luks_bz1862173 #### INFO: #### will start test_libaio_vs_io_uring_comparison ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:21:49 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:21:49 storageqe-109 INFO: #### END test_hw_luks_bz1862173 #### Oct 7 19:21:49 storageqe-109 INFO: #### will start test_libaio_vs_io_uring_comparison ##### Oct 7 19:21:49 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:21:55 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:22:03 storageqe-109 stratisd[4947]: [2025-10-07T23:22:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:22:03 storageqe-109 stratisd[4947]: [2025-10-07T23:22:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:22:04 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup open /dev/nvme0n1 JMUksl -q --allow-discards Oct 7 19:22:13 storageqe-109 journal: cryptsetup open /dev/nvme0n1 JMUksl -q --allow-discards Oct 7 19:22:15 storageqe-109 stratisd[4947]: [2025-10-07T23:22:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:22:15 storageqe-109 stratisd[4947]: [2025-10-07T23:22:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:38:23 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 19:38:23 storageqe-109 dnf[2266061]: Updating Subscription Management repositories. Oct 7 19:38:23 storageqe-109 dnf[2266061]: Unable to read consumer identity Oct 7 19:38:23 storageqe-109 dnf[2266061]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-AppStream 398 kB/s | 2.8 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-AppStream-debuginfo 313 kB/s | 1.5 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-BaseOS 567 kB/s | 2.7 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-BaseOS-debuginfo 308 kB/s | 1.5 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-CRB 575 kB/s | 2.7 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-CRB-debuginfo 384 kB/s | 1.5 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-HighAvailability 677 kB/s | 2.8 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-HighAvailability-debuginfo 532 kB/s | 1.5 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-NFV 552 kB/s | 2.7 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-NFV-debuginfo 378 kB/s | 1.5 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-RT 777 kB/s | 2.7 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-RT-debuginfo 414 kB/s | 1.5 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-SAP 184 kB/s | 2.7 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-SAP-debuginfo 364 kB/s | 1.5 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-SAPHANA 603 kB/s | 2.7 kB 00:00 Oct 7 19:38:23 storageqe-109 dnf[2266061]: beaker-SAPHANA-debuginfo 327 kB/s | 1.5 kB 00:00 Oct 7 19:38:24 storageqe-109 dnf[2266061]: Beaker Client - RedHatEnterpriseLinux10 1.2 kB/s | 1.3 kB 00:01 Oct 7 19:38:24 storageqe-109 dnf[2266061]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 7 19:38:25 storageqe-109 dnf[2266061]: Google Cloud CLI 3.7 kB/s | 1.4 kB 00:00 Oct 7 19:38:26 storageqe-109 dnf[2266061]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 7 19:38:27 storageqe-109 dnf[2266061]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 7 19:38:27 storageqe-109 dnf[2266061]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 7 19:38:27 storageqe-109 dnf[2266061]: Metadata cache created. Oct 7 19:38:27 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 19:38:27 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs xfs in remove_crypt Oct 7 19:39:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.fnnu0y1imount_test with fs xfs Oct 7 19:39:33 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 04ce0bff-c2f7-4004-b884-03d3c0d70560 Oct 7 19:39:33 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:39:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fnnu0y1imount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs ext4 in remove_crypt Oct 7 19:39:41 storageqe-109 systemd[1]: tmp-libblockdev.fnnu0y1imount_test.mount: Deactivated successfully. Oct 7 19:39:41 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 04ce0bff-c2f7-4004-b884-03d3c0d70560 Oct 7 19:39:41 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs xfs in remove_crypt Oct 7 19:39:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fkxuv_zzmount_test with fs ext4 Oct 7 19:39:52 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 87a21ca4-419d-41b9-bbbc-1d48d4dc8d74 r/w with ordered data mode. Quota mode: none. Oct 7 19:39:52 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fkxuv_zzmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs ext3 in remove_crypt Oct 7 19:39:58 storageqe-109 systemd[1]: tmp-libblockdev.fkxuv_zzmount_test.mount: Deactivated successfully. Oct 7 19:39:58 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 87a21ca4-419d-41b9-bbbc-1d48d4dc8d74. Oct 7 19:39:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs ext4 in remove_crypt Oct 7 19:39:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.v4cckjowmount_test with fs ext3 Oct 7 19:40:20 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:40:20 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5a16ba8e-f89f-4ad1-8a90-2adb1fd392e6 r/w with ordered data mode. Quota mode: none. Oct 7 19:40:20 storageqe-109 INFO: will run io in dir /tmp/libblockdev.v4cckjowmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs ext2 in remove_crypt Oct 7 19:40:25 storageqe-109 systemd[1]: tmp-libblockdev.v4cckjowmount_test.mount: Deactivated successfully. Oct 7 19:40:25 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5a16ba8e-f89f-4ad1-8a90-2adb1fd392e6. Oct 7 19:40:25 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs ext3 in remove_crypt Oct 7 19:40:25 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/JMUksl and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.c7wsfcm5mount_test with fs ext2 Oct 7 19:40:46 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:40:46 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d3765375-fa0f-4b2c-a748-6f01e1ddf558 r/w without journal. Quota mode: none. Oct 7 19:40:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c7wsfcm5mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs ext2 in remove_crypt INFO: remove crypt device JMUksl INFO: finishe the remove crypt device JMUksl Oct 7 19:40:52 storageqe-109 systemd[1]: tmp-libblockdev.c7wsfcm5mount_test.mount: Deactivated successfully. Oct 7 19:40:52 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d3765375-fa0f-4b2c-a748-6f01e1ddf558. Oct 7 19:40:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/JMUksl and fs ext2 in remove_crypt Oct 7 19:40:52 storageqe-109 INFO: remove crypt device JMUksl Oct 7 19:40:52 storageqe-109 INFO: finishe the remove crypt device JMUksl Oct 7 19:40:52 storageqe-109 stratisd[4947]: [2025-10-07T23:40:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:40:52 storageqe-109 stratisd[4947]: [2025-10-07T23:40:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_libaio_vs_io_uring_comparison #### INFO: #### will start test_luks_hardware_vs_software_performance ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:40:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:40:58 storageqe-109 INFO: #### END test_libaio_vs_io_uring_comparison #### Oct 7 19:40:58 storageqe-109 INFO: #### will start test_luks_hardware_vs_software_performance ##### Oct 7 19:40:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:41:03 storageqe-109 stratisd[4947]: [2025-10-07T23:41:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:41:03 storageqe-109 stratisd[4947]: [2025-10-07T23:41:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:41:04 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:41:12 storageqe-109 stratisd[4947]: [2025-10-07T23:41:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:41:12 storageqe-109 stratisd[4947]: [2025-10-07T23:41:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 cMDrOu -q --allow-discards Oct 7 19:41:22 storageqe-109 journal: cryptsetup open /dev/nvme0n1 cMDrOu -q --allow-discards Oct 7 19:41:24 storageqe-109 stratisd[4947]: [2025-10-07T23:41:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:41:24 storageqe-109 stratisd[4947]: [2025-10-07T23:41:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:41:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 19:41:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 19:41:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs xfs in remove_crypt Oct 7 19:42:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs xfs in remove_crypt Oct 7 19:42:55 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 5d6c87ce-c91a-45d6-be02-ba3a1450dbe7 INFO: will run io in dir /tmp/libblockdev.u9cfq6xhmount_test with fs xfs Oct 7 19:42:55 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:42:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.u9cfq6xhmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs ext4 in remove_crypt Oct 7 19:43:03 storageqe-109 systemd[1]: tmp-libblockdev.u9cfq6xhmount_test.mount: Deactivated successfully. Oct 7 19:43:03 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 5d6c87ce-c91a-45d6-be02-ba3a1450dbe7 Oct 7 19:43:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs xfs in remove_crypt Oct 7 19:43:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.0yrpfgermount_test with fs ext4 Oct 7 19:43:14 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d554c594-4f4b-48f0-867a-92bfe46087ce r/w with ordered data mode. Quota mode: none. Oct 7 19:43:14 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0yrpfgermount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs ext3 in remove_crypt Oct 7 19:43:19 storageqe-109 systemd[1]: tmp-libblockdev.0yrpfgermount_test.mount: Deactivated successfully. Oct 7 19:43:19 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d554c594-4f4b-48f0-867a-92bfe46087ce. Oct 7 19:43:19 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs ext4 in remove_crypt Oct 7 19:43:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6s2i1gt8mount_test with fs ext3 Oct 7 19:43:41 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:43:41 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem f3cefa27-5337-4f5f-9d35-27244da069fd r/w with ordered data mode. Quota mode: none. Oct 7 19:43:41 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6s2i1gt8mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs ext2 in remove_crypt Oct 7 19:43:47 storageqe-109 systemd[1]: tmp-libblockdev.6s2i1gt8mount_test.mount: Deactivated successfully. Oct 7 19:43:47 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem f3cefa27-5337-4f5f-9d35-27244da069fd. Oct 7 19:43:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs ext3 in remove_crypt Oct 7 19:43:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/cMDrOu and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dxetcivtmount_test with fs ext2 Oct 7 19:44:08 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:44:08 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 8791b418-8d56-4380-987f-b3a9397723fd r/w without journal. Quota mode: none. Oct 7 19:44:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dxetcivtmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs ext2 in remove_crypt INFO: remove crypt device cMDrOu INFO: finishe the remove crypt device cMDrOu cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:44:13 storageqe-109 systemd[1]: tmp-libblockdev.dxetcivtmount_test.mount: Deactivated successfully. Oct 7 19:44:13 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 8791b418-8d56-4380-987f-b3a9397723fd. Oct 7 19:44:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/cMDrOu and fs ext2 in remove_crypt Oct 7 19:44:13 storageqe-109 INFO: remove crypt device cMDrOu Oct 7 19:44:13 storageqe-109 INFO: finishe the remove crypt device cMDrOu Oct 7 19:44:13 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q --hw-opal Oct 7 19:44:13 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 19:44:14 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 19:44:14 storageqe-109 stratisd[4947]: [2025-10-07T23:44:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:44:14 storageqe-109 stratisd[4947]: [2025-10-07T23:44:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:44:24 storageqe-109 kernel: nvme_log_error: 251 callbacks suppressed Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627392, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627392 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627392, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627393, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627393 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627393, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627394, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627394 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627394, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627395, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627395 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627395, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627396, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627396 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627396, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627397, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627397 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627397, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627398, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627398 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627398, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627399, 1 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627399 op 0x0:(READ) flags 0x2000000 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627399, async page read Oct 7 19:44:24 storageqe-109 kernel: nvme0c0n1: I/O Cmd(0x2) @ LBA 3125627552, 8 blocks, I/O Error (sct 0x2 / sc 0x86) Oct 7 19:44:24 storageqe-109 kernel: critical medium error, dev nvme0c0n1, sector 3125627552 op 0x0:(READ) flags 0x2080700 phys_seg 1 prio class 0 Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627552, async page read Oct 7 19:44:24 storageqe-109 kernel: Buffer I/O error on dev nvme0n1, logical block 3125627553, async page read Oct 7 19:44:24 storageqe-109 stratisd[4947]: [2025-10-07T23:44:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:44:24 storageqe-109 stratisd[4947]: [2025-10-07T23:44:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 hBlwob -q --allow-discards Oct 7 19:44:34 storageqe-109 journal: cryptsetup open /dev/nvme0n1 hBlwob -q --allow-discards Oct 7 19:44:36 storageqe-109 stratisd[4947]: [2025-10-07T23:44:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:44:36 storageqe-109 stratisd[4947]: [2025-10-07T23:44:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:44:44 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs xfs in remove_crypt Oct 7 19:45:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.s18_4a6amount_test with fs xfs Oct 7 19:46:08 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem 0fb614bb-b260-411d-985a-a86b03655e23 Oct 7 19:46:08 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:46:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.s18_4a6amount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs ext4 in remove_crypt Oct 7 19:46:15 storageqe-109 systemd[1]: tmp-libblockdev.s18_4a6amount_test.mount: Deactivated successfully. Oct 7 19:46:15 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem 0fb614bb-b260-411d-985a-a86b03655e23 Oct 7 19:46:15 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs xfs in remove_crypt Oct 7 19:46:15 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.mouu79l2mount_test with fs ext4 Oct 7 19:46:26 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem b42e2339-f255-48d1-99a8-649ea5fb4ee8 r/w with ordered data mode. Quota mode: none. Oct 7 19:46:26 storageqe-109 INFO: will run io in dir /tmp/libblockdev.mouu79l2mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs ext3 in remove_crypt Oct 7 19:46:32 storageqe-109 systemd[1]: tmp-libblockdev.mouu79l2mount_test.mount: Deactivated successfully. Oct 7 19:46:32 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem b42e2339-f255-48d1-99a8-649ea5fb4ee8. Oct 7 19:46:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs ext4 in remove_crypt Oct 7 19:46:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.dl4jjhh7mount_test with fs ext3 Oct 7 19:46:54 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:46:54 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 32cf902a-ffca-455d-98c9-0101527999d2 r/w with ordered data mode. Quota mode: none. Oct 7 19:46:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.dl4jjhh7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs ext2 in remove_crypt Oct 7 19:46:59 storageqe-109 systemd[1]: tmp-libblockdev.dl4jjhh7mount_test.mount: Deactivated successfully. Oct 7 19:46:59 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 32cf902a-ffca-455d-98c9-0101527999d2. Oct 7 19:46:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs ext3 in remove_crypt Oct 7 19:46:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/hBlwob and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2tsmglo6mount_test with fs ext2 Oct 7 19:47:21 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:47:21 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 5b3eaedf-7bba-4c38-a39b-9827bfdd3490 r/w without journal. Quota mode: none. Oct 7 19:47:21 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2tsmglo6mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs ext2 in remove_crypt INFO: remove crypt device hBlwob Oct 7 19:47:26 storageqe-109 systemd[1]: tmp-libblockdev.2tsmglo6mount_test.mount: Deactivated successfully. Oct 7 19:47:26 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 5b3eaedf-7bba-4c38-a39b-9827bfdd3490. Oct 7 19:47:26 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/hBlwob and fs ext2 in remove_crypt Oct 7 19:47:26 storageqe-109 INFO: remove crypt device hBlwob cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:47:27 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q Oct 7 19:47:37 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:47:49 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 19:47:59 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 19:47:59 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 19:47:59 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup luksDump /dev/nvme0n1 -q Oct 7 19:48:10 storageqe-109 journal: cryptsetup luksDump /dev/nvme0n1 -q INFO: finishe the remove crypt device hBlwob Oct 7 19:48:20 storageqe-109 INFO: finishe the remove crypt device hBlwob Oct 7 19:48:29 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_hardware_vs_software_performance #### INFO: #### will start test_luks_block_size_optimization ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:49:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:49:37 storageqe-109 INFO: #### END test_luks_hardware_vs_software_performance #### Oct 7 19:49:37 storageqe-109 INFO: #### will start test_luks_block_size_optimization ##### Oct 7 19:49:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:49:43 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:49:50 storageqe-109 stratisd[4947]: [2025-10-07T23:49:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:49:50 storageqe-109 stratisd[4947]: [2025-10-07T23:49:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 mhvOAp -q --allow-discards Oct 7 19:50:00 storageqe-109 journal: cryptsetup open /dev/nvme0n1 mhvOAp -q --allow-discards Oct 7 19:50:02 storageqe-109 stratisd[4947]: [2025-10-07T23:50:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:50:02 storageqe-109 stratisd[4947]: [2025-10-07T23:50:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs xfs in remove_crypt Oct 7 19:57:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.2m6ohfphmount_test with fs xfs Oct 7 19:57:59 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem d151bedc-122c-4189-bce1-3aa3fa351bfb Oct 7 19:57:59 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 19:57:59 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2m6ohfphmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs ext4 in remove_crypt Oct 7 19:58:07 storageqe-109 systemd[1]: tmp-libblockdev.2m6ohfphmount_test.mount: Deactivated successfully. Oct 7 19:58:07 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem d151bedc-122c-4189-bce1-3aa3fa351bfb Oct 7 19:58:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs xfs in remove_crypt Oct 7 19:58:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.y54z2ywhmount_test with fs ext4 Oct 7 19:58:18 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 949faf8c-69af-4633-acf2-5328f4e57db4 r/w with ordered data mode. Quota mode: none. Oct 7 19:58:19 storageqe-109 INFO: will run io in dir /tmp/libblockdev.y54z2ywhmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs ext3 in remove_crypt Oct 7 19:58:24 storageqe-109 systemd[1]: tmp-libblockdev.y54z2ywhmount_test.mount: Deactivated successfully. Oct 7 19:58:24 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 949faf8c-69af-4633-acf2-5328f4e57db4. Oct 7 19:58:24 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs ext4 in remove_crypt Oct 7 19:58:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.nstn5_zwmount_test with fs ext3 Oct 7 19:58:46 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem Oct 7 19:58:46 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem d71fc575-b8f1-4c7a-b27f-151180c1d7e1 r/w with ordered data mode. Quota mode: none. Oct 7 19:58:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.nstn5_zwmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs ext2 in remove_crypt Oct 7 19:58:51 storageqe-109 systemd[1]: tmp-libblockdev.nstn5_zwmount_test.mount: Deactivated successfully. Oct 7 19:58:51 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem d71fc575-b8f1-4c7a-b27f-151180c1d7e1. Oct 7 19:58:51 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs ext3 in remove_crypt Oct 7 19:58:51 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/mhvOAp and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._4i9uigtmount_test with fs ext2 Oct 7 19:59:13 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 19:59:13 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 1792e6c0-fe8b-4b1c-918a-d4d3e235d2c3 r/w without journal. Quota mode: none. Oct 7 19:59:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev._4i9uigtmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs ext2 in remove_crypt INFO: remove crypt device mhvOAp INFO: finishe the remove crypt device mhvOAp Oct 7 19:59:18 storageqe-109 systemd[1]: tmp-libblockdev._4i9uigtmount_test.mount: Deactivated successfully. Oct 7 19:59:18 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 1792e6c0-fe8b-4b1c-918a-d4d3e235d2c3. Oct 7 19:59:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/mhvOAp and fs ext2 in remove_crypt Oct 7 19:59:18 storageqe-109 INFO: remove crypt device mhvOAp Oct 7 19:59:18 storageqe-109 INFO: finishe the remove crypt device mhvOAp Oct 7 19:59:18 storageqe-109 stratisd[4947]: [2025-10-07T23:59:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:59:18 storageqe-109 stratisd[4947]: [2025-10-07T23:59:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_block_size_optimization #### INFO: #### will start test_luks_cpu_utilization_analysis ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:59:24 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:59:24 storageqe-109 INFO: #### END test_luks_block_size_optimization #### Oct 7 19:59:24 storageqe-109 INFO: #### will start test_luks_cpu_utilization_analysis ##### Oct 7 19:59:24 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 19:59:29 storageqe-109 stratisd[4947]: [2025-10-07T23:59:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:59:29 storageqe-109 stratisd[4947]: [2025-10-07T23:59:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:59:30 storageqe-109 journal: cryptsetup --type 'luks2' luksFormat /dev/nvme0n1 -q Oct 7 19:59:38 storageqe-109 stratisd[4947]: [2025-10-07T23:59:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:59:38 storageqe-109 stratisd[4947]: [2025-10-07T23:59:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/nvme0n1 IqeZrf -q --allow-discards Oct 7 19:59:48 storageqe-109 journal: cryptsetup open /dev/nvme0n1 IqeZrf -q --allow-discards Oct 7 19:59:50 storageqe-109 stratisd[4947]: [2025-10-07T23:59:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 19:59:50 storageqe-109 stratisd[4947]: [2025-10-07T23:59:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs xfs in remove_crypt Oct 7 20:01:49 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.651fq6vdmount_test with fs xfs Oct 7 20:02:00 storageqe-109 kernel: XFS (dm-3): Mounting V5 Filesystem ebfb67bd-b1e6-45f7-bbd2-09c8240782ac Oct 7 20:02:00 storageqe-109 kernel: XFS (dm-3): Ending clean mount Oct 7 20:02:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.651fq6vdmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs ext4 in remove_crypt Oct 7 20:02:05 storageqe-109 systemd[1]: tmp-libblockdev.651fq6vdmount_test.mount: Deactivated successfully. Oct 7 20:02:05 storageqe-109 kernel: XFS (dm-3): Unmounting Filesystem ebfb67bd-b1e6-45f7-bbd2-09c8240782ac Oct 7 20:02:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs xfs in remove_crypt Oct 7 20:02:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zodjni4wmount_test with fs ext4 Oct 7 20:02:17 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem c5c601d9-a3e9-4dc7-8886-64c3034bc007 r/w with ordered data mode. Quota mode: none. Oct 7 20:02:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zodjni4wmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs ext3 in remove_crypt Oct 7 20:02:22 storageqe-109 systemd[1]: tmp-libblockdev.zodjni4wmount_test.mount: Deactivated successfully. Oct 7 20:02:22 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem c5c601d9-a3e9-4dc7-8886-64c3034bc007. Oct 7 20:02:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs ext4 in remove_crypt Oct 7 20:02:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs ext3 in remove_crypt Oct 7 20:02:44 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext3 file system using the ext4 subsystem INFO: will run io in dir /tmp/libblockdev._xw45vvumount_test with fs ext3 Oct 7 20:02:44 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem fdd21d03-8538-4f71-a5af-bf37d1b73215 r/w with ordered data mode. Quota mode: none. Oct 7 20:02:44 storageqe-109 INFO: will run io in dir /tmp/libblockdev._xw45vvumount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs ext2 in remove_crypt Oct 7 20:02:50 storageqe-109 systemd[1]: tmp-libblockdev._xw45vvumount_test.mount: Deactivated successfully. Oct 7 20:02:50 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem fdd21d03-8538-4f71-a5af-bf37d1b73215. Oct 7 20:02:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs ext3 in remove_crypt Oct 7 20:02:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/IqeZrf and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ylu0sec4mount_test with fs ext2 Oct 7 20:03:11 storageqe-109 kernel: EXT4-fs (dm-3): mounting ext2 file system using the ext4 subsystem Oct 7 20:03:11 storageqe-109 kernel: EXT4-fs (dm-3): mounted filesystem 85c17f2f-37ba-4f09-b2b2-6c2284434e4c r/w without journal. Quota mode: none. Oct 7 20:03:11 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ylu0sec4mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs ext2 in remove_crypt INFO: remove crypt device IqeZrf INFO: finishe the remove crypt device IqeZrf Oct 7 20:03:17 storageqe-109 systemd[1]: tmp-libblockdev.ylu0sec4mount_test.mount: Deactivated successfully. Oct 7 20:03:17 storageqe-109 kernel: EXT4-fs (dm-3): unmounting filesystem 85c17f2f-37ba-4f09-b2b2-6c2284434e4c. Oct 7 20:03:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/IqeZrf and fs ext2 in remove_crypt Oct 7 20:03:17 storageqe-109 INFO: remove crypt device IqeZrf Oct 7 20:03:17 storageqe-109 INFO: finishe the remove crypt device IqeZrf Oct 7 20:03:17 storageqe-109 stratisd[4947]: [2025-10-08T00:03:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:03:17 storageqe-109 stratisd[4947]: [2025-10-08T00:03:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_cpu_utilization_analysis #### Oct 7 20:03:23 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 20:03:23 storageqe-109 INFO: #### END test_luks_cpu_utilization_analysis #### Oct 7 20:03:23 storageqe-109 stratisd[4947]: [2025-10-08T00:03:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:03:23 storageqe-109 stratisd[4947]: [2025-10-08T00:03:23Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 20:03:24 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 20:03:24 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 20:03:24 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 20:03:34 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_reencrypt_token_tpm2_import[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:03:40 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:03:40 storageqe-109 INFO: #### will start test_reencrypt_token_tpm2_import[npo2_linear] ##### Oct 7 20:03:40 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:03:54 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 7 20:03:54 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:03:54 storageqe-109 stratisd[4947]: [2025-10-08T00:03:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:03:54 storageqe-109 stratisd[4947]: [2025-10-08T00:03:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:04:04 storageqe-109 stratisd[4947]: [2025-10-08T00:04:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:04:04 storageqe-109 stratisd[4947]: [2025-10-08T00:04:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --token-id '1' --token-type 'systemd-tpm2' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q Oct 7 20:04:05 storageqe-109 stratisd[4947]: [2025-10-08T00:04:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:05 storageqe-109 stratisd[4947]: [2025-10-08T00:04:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:05 storageqe-109 journal: cryptsetup --token-id '1' --token-type 'systemd-tpm2' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q Oct 7 20:04:08 storageqe-109 stratisd[4947]: [2025-10-08T00:04:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:08 storageqe-109 stratisd[4947]: [2025-10-08T00:04:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:08 storageqe-109 stratisd[4947]: [2025-10-08T00:04:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:08 storageqe-109 stratisd[4947]: [2025-10-08T00:04:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:20 storageqe-109 stratisd[4947]: [2025-10-08T00:04:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:20 storageqe-109 stratisd[4947]: [2025-10-08T00:04:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 7 20:04:30 storageqe-109 journal: cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 7 20:04:37 storageqe-109 stratisd[4947]: [2025-10-08T00:04:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. Oct 7 20:04:37 storageqe-109 stratisd[4947]: [2025-10-08T00:04:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: LUKS2 token is invalid; reporting as not a Stratis device. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_tpm2_import[npo2_linear] #### INFO: #### will start test_reencrypt_token_tpm2_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:04:52 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:04:52 storageqe-109 INFO: #### END test_reencrypt_token_tpm2_import[npo2_linear] #### Oct 7 20:04:52 storageqe-109 INFO: #### will start test_reencrypt_token_tpm2_header[npo2_linear] ##### Oct 7 20:04:52 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderrAe' luksFormat /dev/mapper/npo2linear -q Oct 7 20:05:05 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderrAe' luksFormat /dev/mapper/npo2linear -q cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderrAe' reencrypt /dev/mapper/npo2linear -q Oct 7 20:05:15 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderrAe' reencrypt /dev/mapper/npo2linear -q cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' --header '/tmp/testheaderrAe' reencrypt /dev/mapper/npo2linear -q --token-only Oct 7 20:05:37 storageqe-109 journal: cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' --header '/tmp/testheaderrAe' reencrypt /dev/mapper/npo2linear -q --token-only cryptsetup --header '/tmp/testheaderrAe' luksAddKey /dev/mapper/npo2linear -q --token-only Oct 7 20:06:00 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrAe' luksAddKey /dev/mapper/npo2linear -q --token-only cryptsetup --key-description 'mykey' --token-id '1' --header '/tmp/testheaderrAe' token add /dev/mapper/npo2linear -q Oct 7 20:06:17 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '1' --header '/tmp/testheaderrAe' token add /dev/mapper/npo2linear -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_tpm2_header[npo2_linear] #### INFO: #### will start test_reencrypt_token_tpm2[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:06:32 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:06:32 storageqe-109 INFO: #### END test_reencrypt_token_tpm2_header[npo2_linear] #### Oct 7 20:06:32 storageqe-109 INFO: #### will start test_reencrypt_token_tpm2[npo2_linear] ##### Oct 7 20:06:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:06:41 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:06:41 storageqe-109 stratisd[4947]: [2025-10-08T00:06:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:06:41 storageqe-109 stratisd[4947]: [2025-10-08T00:06:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:06:51 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:06:51 storageqe-109 stratisd[4947]: [2025-10-08T00:06:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:06:51 storageqe-109 stratisd[4947]: [2025-10-08T00:06:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:06:51 storageqe-109 stratisd[4947]: [2025-10-08T00:06:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:06:51 storageqe-109 stratisd[4947]: [2025-10-08T00:06:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:02 storageqe-109 stratisd[4947]: [2025-10-08T00:07:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:02 storageqe-109 stratisd[4947]: [2025-10-08T00:07:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' reencrypt /dev/mapper/npo2linear -q --token-only Oct 7 20:07:13 storageqe-109 stratisd[4947]: [2025-10-08T00:07:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:13 storageqe-109 stratisd[4947]: [2025-10-08T00:07:13Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:13 storageqe-109 journal: cryptsetup --token-id '0' --token-type 'systemd-tpm2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '4' reencrypt /dev/mapper/npo2linear -q --token-only Oct 7 20:07:16 storageqe-109 stratisd[4947]: [2025-10-08T00:07:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:16 storageqe-109 stratisd[4947]: [2025-10-08T00:07:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:16 storageqe-109 stratisd[4947]: [2025-10-08T00:07:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:16 storageqe-109 stratisd[4947]: [2025-10-08T00:07:16Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:27 storageqe-109 stratisd[4947]: [2025-10-08T00:07:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:27 storageqe-109 stratisd[4947]: [2025-10-08T00:07:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 7 20:07:37 storageqe-109 journal: cryptsetup luksAddKey /dev/mapper/npo2linear -q --token-only Oct 7 20:07:44 storageqe-109 stratisd[4947]: [2025-10-08T00:07:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:44 storageqe-109 stratisd[4947]: [2025-10-08T00:07:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear yLJbMkRoup -q --allow-discards --token-only Oct 7 20:07:54 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear yLJbMkRoup -q --allow-discards --token-only Oct 7 20:07:55 storageqe-109 stratisd[4947]: [2025-10-08T00:07:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:07:55 storageqe-109 stratisd[4947]: [2025-10-08T00:07:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 20:08:09 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 20:08:09 storageqe-109 stratisd[4947]: [2025-10-08T00:08:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"keyslots":["2"],"tpm2-blob":"AJ4AIH57XUOKJZOF3IKfhuAFnZae+pDNtLWNl4xd/LQPb8X3ABCRgMnNUGvEUdBEVwlOredDJv6kZL/rerOvhBaXW0hz+zTCv5Ou0hSWS13HGRxXG1/PeVfgDDtEqE5gCMd/XXWBCmnMiyo+BZzXren6KLIlk1br48ZhkTiUBXCe7xrPp+sg/4Yg6bsToAK6hXbTK2WfWwYpKV0DWWSyqgBOAAgACwAABBIAIDxT1KyvQs/XyV+t0nEVczfsRr/qjkdbjx+nkJrT42X8ABAAIPn+Yd5QMAGHLT383mh9+7Cjkr6SGF1Ip86KMSGgqHPE","tpm2-pcr-bank":"sha256","tpm2-pcrs":[7],"tpm2-policy-hash":"3c53d4acaf42cfd7c95fadd271157337ec46bfea8e475b8f1fa7909ad3e365fc","tpm2_srk":"gQAAAQAiAAuPHHGDVxNxkDpz+QWecJQnnMk0LH5AVDbx6K3cCUubVQAAAAEAWgAjAAsAAwRyAAAABgCAAEMAEAADABAAIPGcvI794Hz7eIk4pYZKSrnQnj3zdfXN2VAHBhcQoGThACA7KAmia7zzlX9anD6t5Lw05klF/djswexkcEQhCEEqxw==","type":"systemd-tpm2"} Oct 7 20:08:09 storageqe-109 stratisd[4947]: [2025-10-08T00:08:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key tpm2-blob. Oct 7 20:08:09 storageqe-109 stratisd[4947]: [2025-10-08T00:08:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. Oct 7 20:08:09 storageqe-109 stratisd[4947]: [2025-10-08T00:08:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Stratis LUKS2 token: {"keyslots":["2"],"tpm2-blob":"AJ4AIH57XUOKJZOF3IKfhuAFnZae+pDNtLWNl4xd/LQPb8X3ABCRgMnNUGvEUdBEVwlOredDJv6kZL/rerOvhBaXW0hz+zTCv5Ou0hSWS13HGRxXG1/PeVfgDDtEqE5gCMd/XXWBCmnMiyo+BZzXren6KLIlk1br48ZhkTiUBXCe7xrPp+sg/4Yg6bsToAK6hXbTK2WfWwYpKV0DWWSyqgBOAAgACwAABBIAIDxT1KyvQs/XyV+t0nEVczfsRr/qjkdbjx+nkJrT42X8ABAAIPn+Yd5QMAGHLT383mh9+7Cjkr6SGF1Ip86KMSGgqHPE","tpm2-pcr-bank":"sha256","tpm2-pcrs":[7],"tpm2-policy-hash":"3c53d4acaf42cfd7c95fadd271157337ec46bfea8e475b8f1fa7909ad3e365fc","tpm2_srk":"gQAAAQAiAAuPHHGDVxNxkDpz+QWecJQnnMk0LH5AVDbx6K3cCUubVQAAAAEAWgAjAAsAAwRyAAAABgCAAEMAEAADABAAIPGcvI794Hz7eIk4pYZKSrnQnj3zdfXN2VAHBhcQoGThACA7KAmia7zzlX9anD6t5Lw05klF/djswexkcEQhCEEqxw==","type":"systemd-tpm2"} Oct 7 20:08:09 storageqe-109 stratisd[4947]: [2025-10-08T00:08:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] LUKS2 token in the Stratis token slot does not appear to be a Stratis token: Found unrecognized key tpm2-blob. Oct 7 20:08:09 storageqe-109 stratisd[4947]: [2025-10-08T00:08:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Stratis token is invalid; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs xfs in remove_crypt Oct 7 20:08:19 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.prc3odkgmount_test with fs xfs Oct 7 20:08:29 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b18faa7f-4b82-4d1d-a522-e45cac62850c Oct 7 20:08:29 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:08:29 storageqe-109 INFO: will run io in dir /tmp/libblockdev.prc3odkgmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext4 in remove_crypt Oct 7 20:08:35 storageqe-109 systemd[1]: tmp-libblockdev.prc3odkgmount_test.mount: Deactivated successfully. Oct 7 20:08:35 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b18faa7f-4b82-4d1d-a522-e45cac62850c Oct 7 20:08:35 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs xfs in remove_crypt Oct 7 20:08:35 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.o1gh_azbmount_test with fs ext4 Oct 7 20:08:45 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 42171559-da4c-4d61-a9ef-d8a82160f3a7 r/w with ordered data mode. Quota mode: none. Oct 7 20:08:45 storageqe-109 INFO: will run io in dir /tmp/libblockdev.o1gh_azbmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext3 in remove_crypt Oct 7 20:08:50 storageqe-109 systemd[1]: tmp-libblockdev.o1gh_azbmount_test.mount: Deactivated successfully. Oct 7 20:08:50 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 42171559-da4c-4d61-a9ef-d8a82160f3a7. Oct 7 20:08:50 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext4 in remove_crypt Oct 7 20:08:50 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.9b10z2yqmount_test with fs ext3 Oct 7 20:09:00 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:09:00 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0e81d0f9-43e3-4604-83ed-69428c0cc7d6 r/w with ordered data mode. Quota mode: none. Oct 7 20:09:00 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9b10z2yqmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext2 in remove_crypt Oct 7 20:09:05 storageqe-109 systemd[1]: tmp-libblockdev.9b10z2yqmount_test.mount: Deactivated successfully. Oct 7 20:09:05 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0e81d0f9-43e3-4604-83ed-69428c0cc7d6. Oct 7 20:09:05 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext3 in remove_crypt Oct 7 20:09:05 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.znv8m4_0mount_test with fs ext2 Oct 7 20:09:15 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:09:15 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 1c93e771-9eaa-4528-9773-d563079a31df r/w without journal. Quota mode: none. Oct 7 20:09:15 storageqe-109 INFO: will run io in dir /tmp/libblockdev.znv8m4_0mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext2 in remove_crypt INFO: remove crypt device yLJbMkRoup INFO: finishe the remove crypt device yLJbMkRoup Oct 7 20:09:20 storageqe-109 systemd[1]: tmp-libblockdev.znv8m4_0mount_test.mount: Deactivated successfully. Oct 7 20:09:20 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 1c93e771-9eaa-4528-9773-d563079a31df. Oct 7 20:09:20 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/yLJbMkRoup and fs ext2 in remove_crypt Oct 7 20:09:20 storageqe-109 INFO: remove crypt device yLJbMkRoup Oct 7 20:09:20 storageqe-109 INFO: finishe the remove crypt device yLJbMkRoup INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_tpm2[npo2_linear] #### INFO: #### will start test_reencrypt_token_keyring_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:09:25 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:09:25 storageqe-109 INFO: #### END test_reencrypt_token_tpm2[npo2_linear] #### Oct 7 20:09:25 storageqe-109 INFO: #### will start test_reencrypt_token_keyring_header[npo2_linear] ##### Oct 7 20:09:25 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderCdI' luksFormat /dev/mapper/npo2linear -q Oct 7 20:09:30 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderCdI' luksFormat /dev/mapper/npo2linear -q cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderCdI' reencrypt /dev/mapper/npo2linear -q Oct 7 20:09:40 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderCdI' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --header '/tmp/testheaderCdI' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:10:03 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --header '/tmp/testheaderCdI' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderCdI' token add /dev/mapper/npo2linear -q Oct 7 20:10:23 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderCdI' token add /dev/mapper/npo2linear -q cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '10' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderCdI' reencrypt /dev/mapper/npo2linear -q --token-only Oct 7 20:10:33 storageqe-109 journal: cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '10' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' --header '/tmp/testheaderCdI' reencrypt /dev/mapper/npo2linear -q --token-only cryptsetup --type 'luks2' --header '/tmp/testheaderCdI' open /dev/mapper/npo2linear KWoELcRgjv -q --allow-discards --token-only Oct 7 20:10:53 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderCdI' open /dev/mapper/npo2linear KWoELcRgjv -q --allow-discards --token-only cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderCdI' token remove /dev/mapper/npo2linear -q Oct 7 20:11:03 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '10' --header '/tmp/testheaderCdI' token remove /dev/mapper/npo2linear -q INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs xfs in remove_crypt Oct 7 20:11:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.0rrxu4rymount_test with fs xfs Oct 7 20:11:23 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 9d716da8-57b2-4ebb-9dcf-f395769cbb03 Oct 7 20:11:23 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:11:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.0rrxu4rymount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext4 in remove_crypt Oct 7 20:11:28 storageqe-109 systemd[1]: tmp-libblockdev.0rrxu4rymount_test.mount: Deactivated successfully. Oct 7 20:11:28 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 9d716da8-57b2-4ebb-9dcf-f395769cbb03 Oct 7 20:11:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs xfs in remove_crypt Oct 7 20:11:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ghtg1uadmount_test with fs ext4 Oct 7 20:11:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 594e9075-b67b-47fe-ba7b-e5f7fcc1ee2e r/w with ordered data mode. Quota mode: none. Oct 7 20:11:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ghtg1uadmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext3 in remove_crypt Oct 7 20:11:43 storageqe-109 systemd[1]: tmp-libblockdev.ghtg1uadmount_test.mount: Deactivated successfully. Oct 7 20:11:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 594e9075-b67b-47fe-ba7b-e5f7fcc1ee2e. Oct 7 20:11:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext4 in remove_crypt Oct 7 20:11:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.z4m_v8u7mount_test with fs ext3 Oct 7 20:11:54 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:11:54 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 117e23d2-5748-4c21-beb0-3448f1ce68b3 r/w with ordered data mode. Quota mode: none. Oct 7 20:11:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.z4m_v8u7mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext2 in remove_crypt Oct 7 20:11:59 storageqe-109 systemd[1]: tmp-libblockdev.z4m_v8u7mount_test.mount: Deactivated successfully. Oct 7 20:11:59 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 117e23d2-5748-4c21-beb0-3448f1ce68b3. Oct 7 20:11:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext3 in remove_crypt Oct 7 20:11:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5kyuu1tsmount_test with fs ext2 Oct 7 20:12:09 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:12:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ae8a8a00-c036-4231-8657-c099e47210eb r/w without journal. Quota mode: none. Oct 7 20:12:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5kyuu1tsmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext2 in remove_crypt INFO: remove crypt device KWoELcRgjv INFO: finishe the remove crypt device KWoELcRgjv Oct 7 20:12:14 storageqe-109 systemd[1]: tmp-libblockdev.5kyuu1tsmount_test.mount: Deactivated successfully. Oct 7 20:12:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ae8a8a00-c036-4231-8657-c099e47210eb. Oct 7 20:12:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/KWoELcRgjv and fs ext2 in remove_crypt Oct 7 20:12:14 storageqe-109 INFO: remove crypt device KWoELcRgjv Oct 7 20:12:14 storageqe-109 INFO: finishe the remove crypt device KWoELcRgjv INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_keyring_header[npo2_linear] #### INFO: #### will start test_reencrypt_token_keyring[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:12:19 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:12:19 storageqe-109 INFO: #### END test_reencrypt_token_keyring_header[npo2_linear] #### Oct 7 20:12:19 storageqe-109 INFO: #### will start test_reencrypt_token_keyring[npo2_linear] ##### Oct 7 20:12:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:12:24 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:12:24 storageqe-109 stratisd[4947]: [2025-10-08T00:12:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:24 storageqe-109 stratisd[4947]: [2025-10-08T00:12:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:12:34 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:12:34 storageqe-109 stratisd[4947]: [2025-10-08T00:12:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:34 storageqe-109 stratisd[4947]: [2025-10-08T00:12:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:34 storageqe-109 stratisd[4947]: [2025-10-08T00:12:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:34 storageqe-109 stratisd[4947]: [2025-10-08T00:12:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:46 storageqe-109 stratisd[4947]: [2025-10-08T00:12:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:46 storageqe-109 stratisd[4947]: [2025-10-08T00:12:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:12:56 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:12:56 storageqe-109 stratisd[4947]: [2025-10-08T00:12:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:56 storageqe-109 stratisd[4947]: [2025-10-08T00:12:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:56 storageqe-109 stratisd[4947]: [2025-10-08T00:12:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:12:56 storageqe-109 stratisd[4947]: [2025-10-08T00:12:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:07 storageqe-109 stratisd[4947]: [2025-10-08T00:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:07 storageqe-109 stratisd[4947]: [2025-10-08T00:13:07Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 20:13:17 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '1' token add /dev/mapper/npo2linear -q Oct 7 20:13:17 storageqe-109 stratisd[4947]: [2025-10-08T00:13:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:17 storageqe-109 stratisd[4947]: [2025-10-08T00:13:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '1' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --token-only Oct 7 20:13:27 storageqe-109 journal: cryptsetup --resilience 'journal' --token-type 'luks2-keyring' --token-id '1' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --token-only Oct 7 20:13:27 storageqe-109 stratisd[4947]: [2025-10-08T00:13:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:27 storageqe-109 stratisd[4947]: [2025-10-08T00:13:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:27 storageqe-109 stratisd[4947]: [2025-10-08T00:13:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:27 storageqe-109 stratisd[4947]: [2025-10-08T00:13:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:37 storageqe-109 stratisd[4947]: [2025-10-08T00:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:37 storageqe-109 stratisd[4947]: [2025-10-08T00:13:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --type 'luks2' open /dev/mapper/npo2linear RBATiIjzFD -q --allow-discards --token-only Oct 7 20:13:47 storageqe-109 journal: cryptsetup --type 'luks2' open /dev/mapper/npo2linear RBATiIjzFD -q --allow-discards --token-only Oct 7 20:13:47 storageqe-109 stratisd[4947]: [2025-10-08T00:13:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:47 storageqe-109 stratisd[4947]: [2025-10-08T00:13:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-description 'mykey' --token-id '1' token remove /dev/mapper/npo2linear -q Oct 7 20:13:57 storageqe-109 journal: cryptsetup --key-description 'mykey' --token-id '1' token remove /dev/mapper/npo2linear -q Oct 7 20:13:57 storageqe-109 stratisd[4947]: [2025-10-08T00:13:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:13:57 storageqe-109 stratisd[4947]: [2025-10-08T00:13:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs xfs in remove_crypt Oct 7 20:14:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.9swwaxc6mount_test with fs xfs Oct 7 20:14:17 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem a79cfc12-7883-4f46-96f9-a3b63f5a8feb Oct 7 20:14:17 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:14:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.9swwaxc6mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext4 in remove_crypt Oct 7 20:14:22 storageqe-109 systemd[1]: tmp-libblockdev.9swwaxc6mount_test.mount: Deactivated successfully. Oct 7 20:14:22 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem a79cfc12-7883-4f46-96f9-a3b63f5a8feb Oct 7 20:14:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs xfs in remove_crypt Oct 7 20:14:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2tof_ws8mount_test with fs ext4 Oct 7 20:14:32 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem dc20c6b3-3f6c-4d4c-bafd-edddf95f27cd r/w with ordered data mode. Quota mode: none. Oct 7 20:14:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2tof_ws8mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext3 in remove_crypt Oct 7 20:14:37 storageqe-109 systemd[1]: tmp-libblockdev.2tof_ws8mount_test.mount: Deactivated successfully. Oct 7 20:14:37 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem dc20c6b3-3f6c-4d4c-bafd-edddf95f27cd. Oct 7 20:14:37 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext4 in remove_crypt Oct 7 20:14:37 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.6zhht9w9mount_test with fs ext3 Oct 7 20:14:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:14:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c18b1813-582d-452a-a7f6-92a3d162aa37 r/w with ordered data mode. Quota mode: none. Oct 7 20:14:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.6zhht9w9mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext2 in remove_crypt Oct 7 20:14:52 storageqe-109 systemd[1]: tmp-libblockdev.6zhht9w9mount_test.mount: Deactivated successfully. Oct 7 20:14:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c18b1813-582d-452a-a7f6-92a3d162aa37. Oct 7 20:14:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext3 in remove_crypt Oct 7 20:14:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.5fpefmgxmount_test with fs ext2 Oct 7 20:15:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:15:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 896a3251-6ef2-48bf-b03a-07fea2dab28f r/w without journal. Quota mode: none. Oct 7 20:15:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.5fpefmgxmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext2 in remove_crypt INFO: remove crypt device RBATiIjzFD Oct 7 20:15:07 storageqe-109 systemd[1]: tmp-libblockdev.5fpefmgxmount_test.mount: Deactivated successfully. Oct 7 20:15:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 896a3251-6ef2-48bf-b03a-07fea2dab28f. Oct 7 20:15:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/RBATiIjzFD and fs ext2 in remove_crypt Oct 7 20:15:07 storageqe-109 INFO: remove crypt device RBATiIjzFD INFO: finishe the remove crypt device RBATiIjzFD Oct 7 20:15:08 storageqe-109 INFO: finishe the remove crypt device RBATiIjzFD INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_token_keyring[npo2_linear] #### INFO: #### will start test_reencrypt[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:15:13 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:15:13 storageqe-109 INFO: #### END test_reencrypt_token_keyring[npo2_linear] #### Oct 7 20:15:13 storageqe-109 INFO: #### will start test_reencrypt[npo2_linear] ##### Oct 7 20:15:13 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:15:18 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:15:18 storageqe-109 stratisd[4947]: [2025-10-08T00:15:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:15:18 storageqe-109 stratisd[4947]: [2025-10-08T00:15:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksOpen /dev/mapper/npo2linear ewNTlSxyoK -q Oct 7 20:15:28 storageqe-109 journal: cryptsetup luksOpen /dev/mapper/npo2linear ewNTlSxyoK -q Oct 7 20:15:28 storageqe-109 stratisd[4947]: [2025-10-08T00:15:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:15:28 storageqe-109 stratisd[4947]: [2025-10-08T00:15:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt Oct 7 20:15:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.pckp_xlimount_test with fs xfs Oct 7 20:15:48 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 85468cf6-c144-4dbc-bc3a-b3f401585b5c Oct 7 20:15:48 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:15:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pckp_xlimount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt Oct 7 20:15:53 storageqe-109 systemd[1]: tmp-libblockdev.pckp_xlimount_test.mount: Deactivated successfully. Oct 7 20:15:53 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 85468cf6-c144-4dbc-bc3a-b3f401585b5c Oct 7 20:15:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt Oct 7 20:15:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vr39_wyamount_test with fs ext4 Oct 7 20:16:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 343bbc67-8372-49f4-a747-567226aeded6 r/w with ordered data mode. Quota mode: none. Oct 7 20:16:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vr39_wyamount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt Oct 7 20:16:08 storageqe-109 systemd[1]: tmp-libblockdev.vr39_wyamount_test.mount: Deactivated successfully. Oct 7 20:16:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 343bbc67-8372-49f4-a747-567226aeded6. Oct 7 20:16:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt Oct 7 20:16:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.trgu_dlkmount_test with fs ext3 Oct 7 20:16:18 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:16:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem e6d6ff6b-9e2e-41ad-84e0-86407fd5c5c2 r/w with ordered data mode. Quota mode: none. Oct 7 20:16:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.trgu_dlkmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt Oct 7 20:16:23 storageqe-109 systemd[1]: tmp-libblockdev.trgu_dlkmount_test.mount: Deactivated successfully. Oct 7 20:16:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem e6d6ff6b-9e2e-41ad-84e0-86407fd5c5c2. Oct 7 20:16:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt Oct 7 20:16:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.vvrz6_vvmount_test with fs ext2 Oct 7 20:16:33 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:16:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c5b6b503-b146-4b57-a6ef-389a810c7815 r/w without journal. Quota mode: none. Oct 7 20:16:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vvrz6_vvmount_test with fs ext2 Oct 7 20:16:38 storageqe-109 systemd[1]: tmp-libblockdev.vvrz6_vvmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt INFO: remove crypt device ewNTlSxyoK INFO: finishe the remove crypt device ewNTlSxyoK cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:16:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c5b6b503-b146-4b57-a6ef-389a810c7815. Oct 7 20:16:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt Oct 7 20:16:38 storageqe-109 INFO: remove crypt device ewNTlSxyoK Oct 7 20:16:38 storageqe-109 INFO: finishe the remove crypt device ewNTlSxyoK Oct 7 20:16:38 storageqe-109 journal: cryptsetup --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:16:38 storageqe-109 stratisd[4947]: [2025-10-08T00:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:16:38 storageqe-109 stratisd[4947]: [2025-10-08T00:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:16:38 storageqe-109 stratisd[4947]: [2025-10-08T00:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:16:38 storageqe-109 stratisd[4947]: [2025-10-08T00:16:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:16:50 storageqe-109 stratisd[4947]: [2025-10-08T00:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:16:50 storageqe-109 stratisd[4947]: [2025-10-08T00:16:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '256' --cipher 'twofish-cbc-essiv:sha256' --resilience 'journal' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:17:00 storageqe-109 journal: cryptsetup --key-size '256' --cipher 'twofish-cbc-essiv:sha256' --resilience 'journal' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:17:00 storageqe-109 stratisd[4947]: [2025-10-08T00:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:00 storageqe-109 stratisd[4947]: [2025-10-08T00:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:00 storageqe-109 stratisd[4947]: [2025-10-08T00:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:00 storageqe-109 stratisd[4947]: [2025-10-08T00:17:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:12 storageqe-109 stratisd[4947]: [2025-10-08T00:17:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:12 storageqe-109 stratisd[4947]: [2025-10-08T00:17:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:17:22 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:17:22 storageqe-109 stratisd[4947]: [2025-10-08T00:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:22 storageqe-109 stratisd[4947]: [2025-10-08T00:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:22 storageqe-109 stratisd[4947]: [2025-10-08T00:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:22 storageqe-109 stratisd[4947]: [2025-10-08T00:17:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:36 storageqe-109 stratisd[4947]: [2025-10-08T00:17:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:36 storageqe-109 stratisd[4947]: [2025-10-08T00:17:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --cipher 'aes-xts-plain64' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --init-only Oct 7 20:17:46 storageqe-109 journal: cryptsetup --cipher 'aes-xts-plain64' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --init-only Oct 7 20:17:46 storageqe-109 stratisd[4947]: [2025-10-08T00:17:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:46 storageqe-109 stratisd[4947]: [2025-10-08T00:17:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:46 storageqe-109 stratisd[4947]: [2025-10-08T00:17:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:46 storageqe-109 stratisd[4947]: [2025-10-08T00:17:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:17:56 storageqe-109 journal: cryptsetup --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:17:56 storageqe-109 stratisd[4947]: [2025-10-08T00:17:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:17:56 storageqe-109 stratisd[4947]: [2025-10-08T00:17:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:04 storageqe-109 stratisd[4947]: [2025-10-08T00:18:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:04 storageqe-109 stratisd[4947]: [2025-10-08T00:18:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --sector-size '512' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:18:14 storageqe-109 journal: cryptsetup --sector-size '512' --key-size '128' --cipher 'aes-cbc-essiv:sha256' --resilience 'checksum' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:18:14 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 20:18:14 storageqe-109 stratisd[4947]: [2025-10-08T00:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:14 storageqe-109 stratisd[4947]: [2025-10-08T00:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:14 storageqe-109 stratisd[4947]: [2025-10-08T00:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:14 storageqe-109 stratisd[4947]: [2025-10-08T00:18:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:14 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 20:18:14 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 7 20:18:27 storageqe-109 stratisd[4947]: [2025-10-08T00:18:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:27 storageqe-109 stratisd[4947]: [2025-10-08T00:18:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup open /dev/mapper/npo2linear ewNTlSxyoK -q Oct 7 20:18:37 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear ewNTlSxyoK -q Oct 7 20:18:37 storageqe-109 stratisd[4947]: [2025-10-08T00:18:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:37 storageqe-109 stratisd[4947]: [2025-10-08T00:18:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --active-name '/dev/mapper/ewNTlSxyoK' --resilience 'none' reencrypt -q Oct 7 20:18:47 storageqe-109 journal: cryptsetup --active-name '/dev/mapper/ewNTlSxyoK' --resilience 'none' reencrypt -q Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:18:47 storageqe-109 stratisd[4947]: [2025-10-08T00:18:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:19:01 storageqe-109 stratisd[4947]: [2025-10-08T00:19:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:19:01 storageqe-109 stratisd[4947]: [2025-10-08T00:19:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:19:01 storageqe-109 stratisd[4947]: [2025-10-08T00:19:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:19:01 storageqe-109 stratisd[4947]: [2025-10-08T00:19:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status ewNTlSxyoK -q Oct 7 20:19:11 storageqe-109 journal: cryptsetup status ewNTlSxyoK -q INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt Oct 7 20:19:21 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.x153nstlmount_test with fs xfs Oct 7 20:19:31 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem b24d8723-19f5-442c-8631-f6e531384a92 Oct 7 20:19:31 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:19:31 storageqe-109 INFO: will run io in dir /tmp/libblockdev.x153nstlmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt Oct 7 20:19:36 storageqe-109 systemd[1]: tmp-libblockdev.x153nstlmount_test.mount: Deactivated successfully. Oct 7 20:19:36 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem b24d8723-19f5-442c-8631-f6e531384a92 Oct 7 20:19:36 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs xfs in remove_crypt Oct 7 20:19:36 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ozvnl_pamount_test with fs ext4 Oct 7 20:19:46 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7367ce47-8f74-41dc-bbba-94f9ad7cf2d8 r/w with ordered data mode. Quota mode: none. Oct 7 20:19:46 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ozvnl_pamount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt Oct 7 20:19:52 storageqe-109 systemd[1]: tmp-libblockdev.ozvnl_pamount_test.mount: Deactivated successfully. Oct 7 20:19:52 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7367ce47-8f74-41dc-bbba-94f9ad7cf2d8. Oct 7 20:19:52 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext4 in remove_crypt Oct 7 20:19:52 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.g4bo811kmount_test with fs ext3 Oct 7 20:20:02 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:20:02 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 40dedf1e-8888-4bd0-9947-ecd015168395 r/w with ordered data mode. Quota mode: none. Oct 7 20:20:02 storageqe-109 INFO: will run io in dir /tmp/libblockdev.g4bo811kmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt Oct 7 20:20:07 storageqe-109 systemd[1]: tmp-libblockdev.g4bo811kmount_test.mount: Deactivated successfully. Oct 7 20:20:07 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 40dedf1e-8888-4bd0-9947-ecd015168395. Oct 7 20:20:07 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext3 in remove_crypt Oct 7 20:20:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.jaxne36pmount_test with fs ext2 Oct 7 20:20:17 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:20:17 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 56cb507f-db1a-4d35-a9be-5e29ceb761fd r/w without journal. Quota mode: none. Oct 7 20:20:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jaxne36pmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt INFO: remove crypt device ewNTlSxyoK INFO: finishe the remove crypt device ewNTlSxyoK Oct 7 20:20:22 storageqe-109 systemd[1]: tmp-libblockdev.jaxne36pmount_test.mount: Deactivated successfully. Oct 7 20:20:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 56cb507f-db1a-4d35-a9be-5e29ceb761fd. Oct 7 20:20:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/ewNTlSxyoK and fs ext2 in remove_crypt Oct 7 20:20:23 storageqe-109 INFO: remove crypt device ewNTlSxyoK Oct 7 20:20:23 storageqe-109 INFO: finishe the remove crypt device ewNTlSxyoK INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt[npo2_linear] #### INFO: #### will start test_reencrypt_data_shift[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:20:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:20:28 storageqe-109 INFO: #### END test_reencrypt[npo2_linear] #### Oct 7 20:20:28 storageqe-109 INFO: #### will start test_reencrypt_data_shift[npo2_linear] ##### Oct 7 20:20:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --key-size '128' --reduce-device-size '8M' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:20:33 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:20:33 storageqe-109 stratisd[4947]: [2025-10-08T00:20:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:20:33 storageqe-109 stratisd[4947]: [2025-10-08T00:20:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:20:41 storageqe-109 stratisd[4947]: [2025-10-08T00:20:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:20:41 storageqe-109 stratisd[4947]: [2025-10-08T00:20:41Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '21M' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:20:51 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '21M' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:20:51 storageqe-109 stratisd[4947]: [2025-10-08T00:20:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:20:51 storageqe-109 stratisd[4947]: [2025-10-08T00:20:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:00 storageqe-109 stratisd[4947]: [2025-10-08T00:21:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:00 storageqe-109 stratisd[4947]: [2025-10-08T00:21:00Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '30M' --offset '21504' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:21:10 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '30M' --offset '21504' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:21:10 storageqe-109 stratisd[4947]: [2025-10-08T00:21:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:10 storageqe-109 stratisd[4947]: [2025-10-08T00:21:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:18 storageqe-109 stratisd[4947]: [2025-10-08T00:21:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:18 storageqe-109 stratisd[4947]: [2025-10-08T00:21:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '33M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:21:28 storageqe-109 journal: cryptsetup --reduce-device-size '33M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:21:29 storageqe-109 stratisd[4947]: [2025-10-08T00:21:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:29 storageqe-109 stratisd[4947]: [2025-10-08T00:21:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:33 storageqe-109 stratisd[4947]: [2025-10-08T00:21:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:33 storageqe-109 stratisd[4947]: [2025-10-08T00:21:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '64M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:21:43 storageqe-109 journal: cryptsetup --reduce-device-size '64M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:21:43 storageqe-109 stratisd[4947]: [2025-10-08T00:21:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:43 storageqe-109 stratisd[4947]: [2025-10-08T00:21:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:48 storageqe-109 stratisd[4947]: [2025-10-08T00:21:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:48 storageqe-109 stratisd[4947]: [2025-10-08T00:21:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --reduce-device-size '8M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 7 20:21:58 storageqe-109 journal: cryptsetup --reduce-device-size '8M' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 7 20:21:58 storageqe-109 stratisd[4947]: [2025-10-08T00:21:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:21:58 storageqe-109 stratisd[4947]: [2025-10-08T00:21:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '8M' --offset '32760' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only Oct 7 20:22:08 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --offset '32760' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only cryptsetup --reduce-device-size '21M' --offset '43008' --header '/tmp/testheaderOQB' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:22:18 storageqe-109 journal: cryptsetup --reduce-device-size '21M' --offset '43008' --header '/tmp/testheaderOQB' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only MEDuBNcsFm Oct 7 20:22:33 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only MEDuBNcsFm Oct 7 20:22:33 storageqe-109 stratisd[4947]: [2025-10-08T00:22:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:33 storageqe-109 stratisd[4947]: [2025-10-08T00:22:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:33 storageqe-109 stratisd[4947]: [2025-10-08T00:22:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:33 storageqe-109 stratisd[4947]: [2025-10-08T00:22:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:33 storageqe-109 stratisd[4947]: [2025-10-08T00:22:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:33 storageqe-109 stratisd[4947]: [2025-10-08T00:22:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup reencrypt /dev/mapper/npo2linear -q --resume-only Oct 7 20:22:43 storageqe-109 journal: cryptsetup reencrypt /dev/mapper/npo2linear -q --resume-only Oct 7 20:22:43 storageqe-109 stratisd[4947]: [2025-10-08T00:22:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:43 storageqe-109 stratisd[4947]: [2025-10-08T00:22:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:43 storageqe-109 stratisd[4947]: [2025-10-08T00:22:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:43 storageqe-109 stratisd[4947]: [2025-10-08T00:22:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:22:57 storageqe-109 auditd[957]: Audit daemon rotating log files Oct 7 20:23:12 storageqe-109 stratisd[4947]: [2025-10-08T00:23:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:23:12 storageqe-109 stratisd[4947]: [2025-10-08T00:23:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:23:12 storageqe-109 stratisd[4947]: [2025-10-08T00:23:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:23:12 storageqe-109 stratisd[4947]: [2025-10-08T00:23:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only MEDuBNcsFm Oct 7 20:23:23 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --key-slot '11' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only MEDuBNcsFm INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt Oct 7 20:23:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.h0fosl94mount_test with fs xfs Oct 7 20:23:43 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 29cc8191-e229-43af-828c-7bf70d9ea55e Oct 7 20:23:43 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:23:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h0fosl94mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt Oct 7 20:23:48 storageqe-109 systemd[1]: tmp-libblockdev.h0fosl94mount_test.mount: Deactivated successfully. Oct 7 20:23:48 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 29cc8191-e229-43af-828c-7bf70d9ea55e Oct 7 20:23:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt Oct 7 20:23:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.irdlimaumount_test with fs ext4 Oct 7 20:23:58 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0dfe2c29-0126-48c9-a74c-74493e29a478 r/w with ordered data mode. Quota mode: none. Oct 7 20:23:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.irdlimaumount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt Oct 7 20:24:03 storageqe-109 systemd[1]: tmp-libblockdev.irdlimaumount_test.mount: Deactivated successfully. Oct 7 20:24:03 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0dfe2c29-0126-48c9-a74c-74493e29a478. Oct 7 20:24:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt Oct 7 20:24:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.eodtw1mdmount_test with fs ext3 Oct 7 20:24:13 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:24:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a03d20fd-d68d-422e-adfe-e962654d94bf r/w with ordered data mode. Quota mode: none. Oct 7 20:24:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.eodtw1mdmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt Oct 7 20:24:18 storageqe-109 systemd[1]: tmp-libblockdev.eodtw1mdmount_test.mount: Deactivated successfully. Oct 7 20:24:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a03d20fd-d68d-422e-adfe-e962654d94bf. Oct 7 20:24:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt Oct 7 20:24:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.86clievomount_test with fs ext2 Oct 7 20:24:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:24:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 66bcb39a-a5c9-403f-83e7-436fd026ea68 r/w without journal. Quota mode: none. Oct 7 20:24:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.86clievomount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt INFO: remove crypt device MEDuBNcsFm INFO: finishe the remove crypt device MEDuBNcsFm cryptsetup --key-size '128' --reduce-device-size '8M' --key-file '/tmp/testfileWnD' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only MEDuBNcsFm Oct 7 20:24:33 storageqe-109 systemd[1]: tmp-libblockdev.86clievomount_test.mount: Deactivated successfully. Oct 7 20:24:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 66bcb39a-a5c9-403f-83e7-436fd026ea68. Oct 7 20:24:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt Oct 7 20:24:33 storageqe-109 INFO: remove crypt device MEDuBNcsFm Oct 7 20:24:33 storageqe-109 INFO: finishe the remove crypt device MEDuBNcsFm Oct 7 20:24:33 storageqe-109 journal: cryptsetup --key-size '128' --reduce-device-size '8M' --key-file '/tmp/testfileWnD' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only MEDuBNcsFm Oct 7 20:24:34 storageqe-109 stratisd[4947]: [2025-10-08T00:24:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:24:34 storageqe-109 stratisd[4947]: [2025-10-08T00:24:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:24:34 storageqe-109 stratisd[4947]: [2025-10-08T00:24:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:24:34 storageqe-109 stratisd[4947]: [2025-10-08T00:24:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:24:34 storageqe-109 stratisd[4947]: [2025-10-08T00:24:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:24:34 storageqe-109 stratisd[4947]: [2025-10-08T00:24:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt Oct 7 20:24:44 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.jmh2zju3mount_test with fs xfs Oct 7 20:24:54 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem ee1e9424-ea8c-4378-a94c-adcb8b32b5b1 Oct 7 20:24:54 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:24:54 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jmh2zju3mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt Oct 7 20:24:59 storageqe-109 systemd[1]: tmp-libblockdev.jmh2zju3mount_test.mount: Deactivated successfully. Oct 7 20:24:59 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem ee1e9424-ea8c-4378-a94c-adcb8b32b5b1 Oct 7 20:24:59 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs xfs in remove_crypt Oct 7 20:24:59 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.q3czq9pwmount_test with fs ext4 Oct 7 20:25:09 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 9ec95ab3-600b-4841-bca3-237fa104aeb8 r/w with ordered data mode. Quota mode: none. Oct 7 20:25:09 storageqe-109 INFO: will run io in dir /tmp/libblockdev.q3czq9pwmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt Oct 7 20:25:14 storageqe-109 systemd[1]: tmp-libblockdev.q3czq9pwmount_test.mount: Deactivated successfully. Oct 7 20:25:14 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 9ec95ab3-600b-4841-bca3-237fa104aeb8. Oct 7 20:25:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext4 in remove_crypt Oct 7 20:25:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.daheluhlmount_test with fs ext3 Oct 7 20:25:24 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:25:24 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 418e1341-b0cf-4d13-95bd-13a564b17d9f r/w with ordered data mode. Quota mode: none. Oct 7 20:25:24 storageqe-109 INFO: will run io in dir /tmp/libblockdev.daheluhlmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt Oct 7 20:25:29 storageqe-109 systemd[1]: tmp-libblockdev.daheluhlmount_test.mount: Deactivated successfully. Oct 7 20:25:29 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 418e1341-b0cf-4d13-95bd-13a564b17d9f. Oct 7 20:25:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext3 in remove_crypt Oct 7 20:25:29 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.2acuk4hdmount_test with fs ext2 Oct 7 20:25:39 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:25:39 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem b355bd2a-fcd7-456b-8d23-9e9bdd7b4fe1 r/w without journal. Quota mode: none. Oct 7 20:25:39 storageqe-109 INFO: will run io in dir /tmp/libblockdev.2acuk4hdmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt INFO: remove crypt device MEDuBNcsFm INFO: finishe the remove crypt device MEDuBNcsFm cryptsetup open /dev/mapper/npo2linear MEDuBNcsFm -q --test-passphrase Oct 7 20:25:44 storageqe-109 systemd[1]: tmp-libblockdev.2acuk4hdmount_test.mount: Deactivated successfully. Oct 7 20:25:44 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem b355bd2a-fcd7-456b-8d23-9e9bdd7b4fe1. Oct 7 20:25:44 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/MEDuBNcsFm and fs ext2 in remove_crypt Oct 7 20:25:44 storageqe-109 INFO: remove crypt device MEDuBNcsFm Oct 7 20:25:44 storageqe-109 INFO: finishe the remove crypt device MEDuBNcsFm Oct 7 20:25:44 storageqe-109 journal: cryptsetup open /dev/mapper/npo2linear MEDuBNcsFm -q --test-passphrase INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_data_shift[npo2_linear] #### INFO: #### will start test_reencrypt_with_header[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:25:59 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:25:59 storageqe-109 INFO: #### END test_reencrypt_data_shift[npo2_linear] #### Oct 7 20:25:59 storageqe-109 INFO: #### will start test_reencrypt_with_header[npo2_linear] ##### Oct 7 20:25:59 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### cryptsetup --key-size '128' --header '/tmp/testheaderiYv' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:26:04 storageqe-109 journal: cryptsetup --key-size '128' --header '/tmp/testheaderiYv' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --header '/tmp/testheaderlnR' --resilience 'none' --cipher 'twofish-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:26:27 storageqe-109 journal: cryptsetup --header '/tmp/testheaderlnR' --resilience 'none' --cipher 'twofish-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --header '/tmp/testheadereiF' --resilience 'checksum' --cipher 'serpent-xts-plain' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:26:45 storageqe-109 journal: cryptsetup --header '/tmp/testheadereiF' --resilience 'checksum' --cipher 'serpent-xts-plain' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --header '/tmp/testheadermwV' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt QwoMEfHaPT Oct 7 20:27:02 storageqe-109 journal: cryptsetup --header '/tmp/testheadermwV' --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt QwoMEfHaPT cryptsetup --header '/tmp/testheadermwV' status QwoMEfHaPT -q Oct 7 20:27:23 storageqe-109 journal: cryptsetup --header '/tmp/testheadermwV' status QwoMEfHaPT -q cryptsetup --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt QwoMEfHaPT Oct 7 20:27:33 storageqe-109 journal: cryptsetup --cipher 'aes-cbc-essiv:sha256' --key-size '128' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt QwoMEfHaPT INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:27:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.p2er1hbbmount_test with fs xfs Oct 7 20:27:53 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem bdecaa49-4aef-4773-baf7-f7069bc7c7c7 Oct 7 20:27:53 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:27:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.p2er1hbbmount_test with fs xfs Oct 7 20:27:58 storageqe-109 systemd[1]: tmp-libblockdev.p2er1hbbmount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:27:58 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem bdecaa49-4aef-4773-baf7-f7069bc7c7c7 Oct 7 20:27:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:27:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev._n1d9ji5mount_test with fs ext4 Oct 7 20:28:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 62d17aba-869b-4271-ab87-5968c6d79d54 r/w with ordered data mode. Quota mode: none. Oct 7 20:28:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev._n1d9ji5mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:28:13 storageqe-109 systemd[1]: tmp-libblockdev._n1d9ji5mount_test.mount: Deactivated successfully. Oct 7 20:28:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 62d17aba-869b-4271-ab87-5968c6d79d54. Oct 7 20:28:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:28:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.rbttpg3jmount_test with fs ext3 Oct 7 20:28:23 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:28:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ed87fcec-e9e6-4e27-b39b-28224d260ab6 r/w with ordered data mode. Quota mode: none. Oct 7 20:28:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.rbttpg3jmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:28:28 storageqe-109 systemd[1]: tmp-libblockdev.rbttpg3jmount_test.mount: Deactivated successfully. Oct 7 20:28:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ed87fcec-e9e6-4e27-b39b-28224d260ab6. Oct 7 20:28:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:28:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.ph77x64hmount_test with fs ext2 Oct 7 20:28:38 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:28:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 21ff3264-9a18-4657-b828-ce9696eed90a r/w without journal. Quota mode: none. Oct 7 20:28:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.ph77x64hmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:28:43 storageqe-109 systemd[1]: tmp-libblockdev.ph77x64hmount_test.mount: Deactivated successfully. Oct 7 20:28:43 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 21ff3264-9a18-4657-b828-ce9696eed90a. Oct 7 20:28:43 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:28:43 storageqe-109 INFO: remove crypt device QwoMEfHaPT Oct 7 20:28:43 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --offset '32768' --header '/tmp/testheadercKk' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt Oct 7 20:28:44 storageqe-109 journal: cryptsetup --offset '32768' --header '/tmp/testheadercKk' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt cryptsetup --key-size '128' --offset '32768' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --key-file '/tmp/testfileDAd' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only QwoMEfHaPT Oct 7 20:29:02 storageqe-109 journal: cryptsetup --key-size '128' --offset '32768' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --key-file '/tmp/testfileDAd' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q --encrypt --init-only QwoMEfHaPT cryptsetup --header '/tmp/testheaderrzA' status QwoMEfHaPT -q Oct 7 20:29:12 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' status QwoMEfHaPT -q INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:29:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.t74rerwrmount_test with fs xfs Oct 7 20:29:32 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 9b4b9975-3709-455d-a942-7d2d91a51707 Oct 7 20:29:32 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:29:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.t74rerwrmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:29:38 storageqe-109 systemd[1]: tmp-libblockdev.t74rerwrmount_test.mount: Deactivated successfully. Oct 7 20:29:38 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 9b4b9975-3709-455d-a942-7d2d91a51707 Oct 7 20:29:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:29:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1weoh8h_mount_test with fs ext4 Oct 7 20:29:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem f3f5dab8-74d1-41ad-b968-19d88114c64c r/w with ordered data mode. Quota mode: none. Oct 7 20:29:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1weoh8h_mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:29:53 storageqe-109 systemd[1]: tmp-libblockdev.1weoh8h_mount_test.mount: Deactivated successfully. Oct 7 20:29:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem f3f5dab8-74d1-41ad-b968-19d88114c64c. Oct 7 20:29:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:29:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fxht4lqvmount_test with fs ext3 Oct 7 20:30:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:30:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c4d0385e-fcbf-4f5c-8776-a3ff5b64480a r/w with ordered data mode. Quota mode: none. Oct 7 20:30:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fxht4lqvmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:30:08 storageqe-109 systemd[1]: tmp-libblockdev.fxht4lqvmount_test.mount: Deactivated successfully. Oct 7 20:30:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c4d0385e-fcbf-4f5c-8776-a3ff5b64480a. Oct 7 20:30:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:30:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.r801p0_0mount_test with fs ext2 Oct 7 20:30:18 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:30:18 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 28850a70-44eb-444c-ae84-60115f9cb837 r/w without journal. Quota mode: none. Oct 7 20:30:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.r801p0_0mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --header '/tmp/testheaderrzA' open /dev/mapper/npo2linear --test-passphrase -q Oct 7 20:30:23 storageqe-109 systemd[1]: tmp-libblockdev.r801p0_0mount_test.mount: Deactivated successfully. Oct 7 20:30:23 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 28850a70-44eb-444c-ae84-60115f9cb837. Oct 7 20:30:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:30:23 storageqe-109 INFO: remove crypt device QwoMEfHaPT Oct 7 20:30:23 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:30:23 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' open /dev/mapper/npo2linear --test-passphrase -q cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:30:33 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:30:43 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.vu_7w_1fmount_test with fs xfs Oct 7 20:30:53 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem bf25221e-d8e4-40dd-8150-4ebac7dadd5a Oct 7 20:30:53 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:30:53 storageqe-109 INFO: will run io in dir /tmp/libblockdev.vu_7w_1fmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:30:58 storageqe-109 systemd[1]: tmp-libblockdev.vu_7w_1fmount_test.mount: Deactivated successfully. Oct 7 20:30:58 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem bf25221e-d8e4-40dd-8150-4ebac7dadd5a Oct 7 20:30:58 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:30:58 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fyh23pydmount_test with fs ext4 Oct 7 20:31:08 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 47dd0582-40b2-4061-bd5d-a45cdda7f75c r/w with ordered data mode. Quota mode: none. Oct 7 20:31:08 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fyh23pydmount_test with fs ext4 Oct 7 20:31:12 storageqe-109 systemd[1]: tmp-libblockdev.fyh23pydmount_test.mount: Deactivated successfully. Oct 7 20:31:12 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 47dd0582-40b2-4061-bd5d-a45cdda7f75c. INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:31:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:31:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.pf0l29kamount_test with fs ext3 Oct 7 20:31:23 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:31:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 45e941a8-2ef6-4e98-8e09-c9e02f6da779 r/w with ordered data mode. Quota mode: none. Oct 7 20:31:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev.pf0l29kamount_test with fs ext3 Oct 7 20:31:27 storageqe-109 systemd[1]: tmp-libblockdev.pf0l29kamount_test.mount: Deactivated successfully. INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:31:28 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 45e941a8-2ef6-4e98-8e09-c9e02f6da779. Oct 7 20:31:28 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:31:28 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:31:38 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:31:38 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 6f0f34a4-6fc5-4527-bbb3-f03f5edafda7 r/w without journal. Quota mode: none. INFO: will run io in dir /tmp/libblockdev.wjwg5c7kmount_test with fs ext2 Oct 7 20:31:38 storageqe-109 INFO: will run io in dir /tmp/libblockdev.wjwg5c7kmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT Oct 7 20:31:42 storageqe-109 systemd[1]: tmp-libblockdev.wjwg5c7kmount_test.mount: Deactivated successfully. Oct 7 20:31:42 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 6f0f34a4-6fc5-4527-bbb3-f03f5edafda7. Oct 7 20:31:42 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:31:42 storageqe-109 INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --key-size '128' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:31:43 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:31:43 storageqe-109 journal: cryptsetup --key-size '128' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --resilience 'journal' --header '/tmp/testheaderrzA' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:32:06 storageqe-109 journal: cryptsetup --resilience 'journal' --header '/tmp/testheaderrzA' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-size '128' --resilience 'none' --header '/tmp/testheaderrzA' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:32:26 storageqe-109 journal: cryptsetup --key-size '128' --resilience 'none' --header '/tmp/testheaderrzA' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --resilience 'checksum' --header '/tmp/testheaderrzA' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q Oct 7 20:32:46 storageqe-109 journal: cryptsetup --resilience 'checksum' --header '/tmp/testheaderrzA' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' reencrypt /dev/mapper/npo2linear -q cryptsetup --key-size '128' --type 'luks2' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:33:06 storageqe-109 journal: cryptsetup --key-size '128' --type 'luks2' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderrzA' open /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:33:16 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' open /dev/mapper/npo2linear QwoMEfHaPT -q cryptsetup --active-name 'QwoMEfHaPT' --header '/tmp/testheaderrzA' reencrypt /dev/mapper/npo2linear -q Oct 7 20:33:26 storageqe-109 journal: cryptsetup --active-name 'QwoMEfHaPT' --header '/tmp/testheaderrzA' reencrypt /dev/mapper/npo2linear -q INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:33:47 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.jdhwqbepmount_test with fs xfs Oct 7 20:33:57 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 86351902-b0dd-4c52-9778-eeebca8ecc75 Oct 7 20:33:57 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:33:57 storageqe-109 INFO: will run io in dir /tmp/libblockdev.jdhwqbepmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:34:02 storageqe-109 systemd[1]: tmp-libblockdev.jdhwqbepmount_test.mount: Deactivated successfully. Oct 7 20:34:02 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 86351902-b0dd-4c52-9778-eeebca8ecc75 Oct 7 20:34:02 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:34:02 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.f_fduqkimount_test with fs ext4 Oct 7 20:34:12 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3cd7676c-5bca-4ba5-bdab-885736e7b8ba r/w with ordered data mode. Quota mode: none. Oct 7 20:34:12 storageqe-109 INFO: will run io in dir /tmp/libblockdev.f_fduqkimount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:34:17 storageqe-109 systemd[1]: tmp-libblockdev.f_fduqkimount_test.mount: Deactivated successfully. Oct 7 20:34:17 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3cd7676c-5bca-4ba5-bdab-885736e7b8ba. Oct 7 20:34:17 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:34:17 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.1z1718x_mount_test with fs ext3 Oct 7 20:34:27 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:34:27 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 8b8a1151-d566-467a-afb6-ff8e4b7cd59e r/w with ordered data mode. Quota mode: none. Oct 7 20:34:27 storageqe-109 INFO: will run io in dir /tmp/libblockdev.1z1718x_mount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:34:32 storageqe-109 systemd[1]: tmp-libblockdev.1z1718x_mount_test.mount: Deactivated successfully. Oct 7 20:34:32 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 8b8a1151-d566-467a-afb6-ff8e4b7cd59e. Oct 7 20:34:32 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:34:32 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.katvilqemount_test with fs ext2 Oct 7 20:34:42 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:34:42 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 3590dbac-232a-4cd3-9a8a-37a845d5484c r/w without journal. Quota mode: none. Oct 7 20:34:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.katvilqemount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --key-size '128' --type 'luks2' --sector-size '512' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:34:47 storageqe-109 systemd[1]: tmp-libblockdev.katvilqemount_test.mount: Deactivated successfully. Oct 7 20:34:47 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 3590dbac-232a-4cd3-9a8a-37a845d5484c. Oct 7 20:34:47 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:34:47 storageqe-109 INFO: remove crypt device QwoMEfHaPT Oct 7 20:34:47 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:34:48 storageqe-109 journal: cryptsetup --key-size '128' --type 'luks2' --sector-size '512' --header '/tmp/testheaderrzA' --cipher 'aes-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:34:58 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:35:08 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.b6oetpe7mount_test with fs xfs Oct 7 20:35:18 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 6263a3a9-8e24-440f-80c0-0a1a56df8cc7 Oct 7 20:35:18 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:35:18 storageqe-109 INFO: will run io in dir /tmp/libblockdev.b6oetpe7mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:35:23 storageqe-109 systemd[1]: tmp-libblockdev.b6oetpe7mount_test.mount: Deactivated successfully. Oct 7 20:35:23 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 6263a3a9-8e24-440f-80c0-0a1a56df8cc7 Oct 7 20:35:23 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:35:23 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.uip4jdd9mount_test with fs ext4 Oct 7 20:35:33 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem ba4cea8a-43b5-4e4c-bc53-35e8d8cd47aa r/w with ordered data mode. Quota mode: none. Oct 7 20:35:33 storageqe-109 INFO: will run io in dir /tmp/libblockdev.uip4jdd9mount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:35:38 storageqe-109 systemd[1]: tmp-libblockdev.uip4jdd9mount_test.mount: Deactivated successfully. Oct 7 20:35:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem ba4cea8a-43b5-4e4c-bc53-35e8d8cd47aa. Oct 7 20:35:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:35:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.h9d7y0samount_test with fs ext3 Oct 7 20:35:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:35:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem cfc11747-6f6e-41db-b7d8-f31dd89a2838 r/w with ordered data mode. Quota mode: none. Oct 7 20:35:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.h9d7y0samount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:35:53 storageqe-109 systemd[1]: tmp-libblockdev.h9d7y0samount_test.mount: Deactivated successfully. Oct 7 20:35:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem cfc11747-6f6e-41db-b7d8-f31dd89a2838. Oct 7 20:35:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:35:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.hcq4a4p0mount_test with fs ext2 Oct 7 20:36:03 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:36:03 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 5affa6dc-0c8f-4188-a309-cb569ea43f78 r/w without journal. Quota mode: none. Oct 7 20:36:03 storageqe-109 INFO: will run io in dir /tmp/libblockdev.hcq4a4p0mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT Oct 7 20:36:08 storageqe-109 systemd[1]: tmp-libblockdev.hcq4a4p0mount_test.mount: Deactivated successfully. Oct 7 20:36:08 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 5affa6dc-0c8f-4188-a309-cb569ea43f78. Oct 7 20:36:08 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:36:08 storageqe-109 INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --header '/tmp/testheaderrzA' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 7 20:36:08 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:36:08 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --header '/tmp/testheaderrzA' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:36:28 storageqe-109 journal: cryptsetup --type 'luks2' --header '/tmp/testheaderrzA' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:36:38 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:36:48 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.7tzrhi0imount_test with fs xfs Oct 7 20:36:58 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem f16de037-e9b7-4d6a-b377-cec34b4b8879 Oct 7 20:36:58 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:36:58 storageqe-109 INFO: will run io in dir /tmp/libblockdev.7tzrhi0imount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:37:03 storageqe-109 systemd[1]: tmp-libblockdev.7tzrhi0imount_test.mount: Deactivated successfully. Oct 7 20:37:03 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem f16de037-e9b7-4d6a-b377-cec34b4b8879 Oct 7 20:37:03 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:37:03 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.90bgxrocmount_test with fs ext4 Oct 7 20:37:13 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem c7cb3218-c989-4d31-91d1-6e8de2b82617 r/w with ordered data mode. Quota mode: none. Oct 7 20:37:13 storageqe-109 INFO: will run io in dir /tmp/libblockdev.90bgxrocmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:37:18 storageqe-109 systemd[1]: tmp-libblockdev.90bgxrocmount_test.mount: Deactivated successfully. Oct 7 20:37:18 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem c7cb3218-c989-4d31-91d1-6e8de2b82617. Oct 7 20:37:18 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:37:18 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.4u14d6fxmount_test with fs ext3 Oct 7 20:37:28 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:37:28 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem eba4b8a5-6f14-493d-be0c-7400f3759dac r/w with ordered data mode. Quota mode: none. Oct 7 20:37:28 storageqe-109 INFO: will run io in dir /tmp/libblockdev.4u14d6fxmount_test with fs ext3 Oct 7 20:37:31 storageqe-109 NetworkManager[995]: [1759883851.6247] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 7 20:37:31 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 7 20:37:31 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:37:33 storageqe-109 systemd[1]: tmp-libblockdev.4u14d6fxmount_test.mount: Deactivated successfully. Oct 7 20:37:33 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem eba4b8a5-6f14-493d-be0c-7400f3759dac. Oct 7 20:37:33 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:37:33 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:37:41 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. INFO: will run io in dir /tmp/libblockdev.c6ldo7oimount_test with fs ext2 Oct 7 20:37:43 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:37:43 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 41311347-fa06-49bd-b44b-24833c39823b r/w without journal. Quota mode: none. Oct 7 20:37:43 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c6ldo7oimount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --header '/tmp/testheaderrzA' --resilience 'journal' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 7 20:37:48 storageqe-109 systemd[1]: tmp-libblockdev.c6ldo7oimount_test.mount: Deactivated successfully. Oct 7 20:37:48 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 41311347-fa06-49bd-b44b-24833c39823b. Oct 7 20:37:48 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:37:48 storageqe-109 INFO: remove crypt device QwoMEfHaPT Oct 7 20:37:48 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:37:48 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' --resilience 'journal' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --key-size '128' --header '/tmp/testheaderrzA' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:38:04 storageqe-109 journal: cryptsetup --type 'luks2' --key-size '128' --header '/tmp/testheaderrzA' --cipher 'twofish-cbc-essiv:sha256' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:38:14 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:38:24 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.64ffodefmount_test with fs xfs Oct 7 20:38:35 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem d8caf436-d8f4-4a9c-9054-c5614b29d666 Oct 7 20:38:35 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:38:35 storageqe-109 INFO: will run io in dir /tmp/libblockdev.64ffodefmount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:38:40 storageqe-109 systemd[1]: tmp-libblockdev.64ffodefmount_test.mount: Deactivated successfully. Oct 7 20:38:40 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem d8caf436-d8f4-4a9c-9054-c5614b29d666 Oct 7 20:38:40 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:38:41 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.bd1jwf2bmount_test with fs ext4 Oct 7 20:38:51 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem bf1a6df5-2f9f-4232-a8f9-8b0c73a3e958 r/w with ordered data mode. Quota mode: none. Oct 7 20:38:51 storageqe-109 INFO: will run io in dir /tmp/libblockdev.bd1jwf2bmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:38:57 storageqe-109 systemd[1]: tmp-libblockdev.bd1jwf2bmount_test.mount: Deactivated successfully. Oct 7 20:38:57 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem bf1a6df5-2f9f-4232-a8f9-8b0c73a3e958. Oct 7 20:38:57 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:38:57 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.c0nnpssemount_test with fs ext3 Oct 7 20:39:07 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:39:07 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 7f7a14a6-ad30-47e5-82f6-2f2fd514db88 r/w with ordered data mode. Quota mode: none. Oct 7 20:39:07 storageqe-109 INFO: will run io in dir /tmp/libblockdev.c0nnpssemount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:39:13 storageqe-109 systemd[1]: tmp-libblockdev.c0nnpssemount_test.mount: Deactivated successfully. Oct 7 20:39:13 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 7f7a14a6-ad30-47e5-82f6-2f2fd514db88. Oct 7 20:39:13 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:39:13 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev._67sdvl2mount_test with fs ext2 Oct 7 20:39:23 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:39:23 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 11bdb0c3-0100-4858-b508-29d2615f5cee r/w without journal. Quota mode: none. Oct 7 20:39:23 storageqe-109 INFO: will run io in dir /tmp/libblockdev._67sdvl2mount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --header '/tmp/testheaderrzA' --resilience 'none' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 7 20:39:29 storageqe-109 systemd[1]: tmp-libblockdev._67sdvl2mount_test.mount: Deactivated successfully. Oct 7 20:39:29 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 11bdb0c3-0100-4858-b508-29d2615f5cee. Oct 7 20:39:29 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:39:29 storageqe-109 INFO: remove crypt device QwoMEfHaPT Oct 7 20:39:29 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:39:29 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' --resilience 'none' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderrzA' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:39:47 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderrzA' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:39:57 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:40:07 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.8h1c8572mount_test with fs xfs Oct 7 20:40:17 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem 1c376bdc-4313-4c45-befb-908bfb11a267 Oct 7 20:40:17 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:40:17 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8h1c8572mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:40:22 storageqe-109 systemd[1]: tmp-libblockdev.8h1c8572mount_test.mount: Deactivated successfully. Oct 7 20:40:22 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem 1c376bdc-4313-4c45-befb-908bfb11a267 Oct 7 20:40:22 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:40:22 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.zn958_mumount_test with fs ext4 Oct 7 20:40:32 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a1cea243-e74b-49ac-b58d-6f2ef904c39c r/w with ordered data mode. Quota mode: none. Oct 7 20:40:32 storageqe-109 INFO: will run io in dir /tmp/libblockdev.zn958_mumount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:40:38 storageqe-109 systemd[1]: tmp-libblockdev.zn958_mumount_test.mount: Deactivated successfully. Oct 7 20:40:38 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a1cea243-e74b-49ac-b58d-6f2ef904c39c. Oct 7 20:40:38 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:40:38 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.d34k8w9lmount_test with fs ext3 Oct 7 20:40:48 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:40:48 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a63d8aa7-c457-4c70-a508-d940f162d64a r/w with ordered data mode. Quota mode: none. Oct 7 20:40:48 storageqe-109 INFO: will run io in dir /tmp/libblockdev.d34k8w9lmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:40:53 storageqe-109 systemd[1]: tmp-libblockdev.d34k8w9lmount_test.mount: Deactivated successfully. Oct 7 20:40:53 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a63d8aa7-c457-4c70-a508-d940f162d64a. Oct 7 20:40:53 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:40:53 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.o3tvnk7qmount_test with fs ext2 Oct 7 20:41:04 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:41:04 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 056c3a91-b670-43c3-bdb2-646b112bcd4a r/w without journal. Quota mode: none. Oct 7 20:41:04 storageqe-109 INFO: will run io in dir /tmp/libblockdev.o3tvnk7qmount_test with fs ext2 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT cryptsetup --header '/tmp/testheaderrzA' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 7 20:41:09 storageqe-109 systemd[1]: tmp-libblockdev.o3tvnk7qmount_test.mount: Deactivated successfully. Oct 7 20:41:09 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 056c3a91-b670-43c3-bdb2-646b112bcd4a. Oct 7 20:41:09 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:41:09 storageqe-109 INFO: remove crypt device QwoMEfHaPT Oct 7 20:41:09 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:41:09 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' --resilience 'checksum' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderrzA' --sector-size '4096' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:41:29 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --header '/tmp/testheaderrzA' --sector-size '4096' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:41:39 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q cryptsetup --header '/tmp/testheaderrzA' status QwoMEfHaPT -q Oct 7 20:41:49 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' status QwoMEfHaPT -q cryptsetup --header '/tmp/testheaderrzA' --resilience 'checksum' --active-name 'QwoMEfHaPT' reencrypt /dev/mapper/npo2linear -q --decrypt Oct 7 20:41:59 storageqe-109 journal: cryptsetup --header '/tmp/testheaderrzA' --resilience 'checksum' --active-name 'QwoMEfHaPT' reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:42:19 storageqe-109 journal: cryptsetup --type 'luks2' --cipher 'serpent-xts-plain' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:42:19 storageqe-109 stratisd[4947]: [2025-10-08T00:42:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:42:19 storageqe-109 stratisd[4947]: [2025-10-08T00:42:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup reencrypt /dev/mapper/npo2linear -q --decrypt Oct 7 20:42:29 storageqe-109 journal: cryptsetup reencrypt /dev/mapper/npo2linear -q --decrypt cryptsetup --type 'luks2' --sector-size '512' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:42:39 storageqe-109 journal: cryptsetup --type 'luks2' --sector-size '512' --offset '8192' --pbkdf-force-iterations '1000' --pbkdf-memory '32' --pbkdf-parallel '1' luksFormat /dev/mapper/npo2linear -q Oct 7 20:42:40 storageqe-109 stratisd[4947]: [2025-10-08T00:42:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:42:40 storageqe-109 stratisd[4947]: [2025-10-08T00:42:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:42:50 storageqe-109 journal: cryptsetup luksOpen /dev/mapper/npo2linear QwoMEfHaPT -q Oct 7 20:42:50 storageqe-109 stratisd[4947]: [2025-10-08T00:42:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:42:50 storageqe-109 stratisd[4947]: [2025-10-08T00:42:50Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:43:00 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: will run io in dir /tmp/libblockdev.3_amdu25mount_test with fs xfs Oct 7 20:43:10 storageqe-109 kernel: XFS (dm-4): Mounting V5 Filesystem efece30b-1295-4e0a-8ca0-90dc2f336adf Oct 7 20:43:10 storageqe-109 kernel: XFS (dm-4): Ending clean mount Oct 7 20:43:10 storageqe-109 INFO: will run io in dir /tmp/libblockdev.3_amdu25mount_test with fs xfs INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:43:14 storageqe-109 systemd[1]: tmp-libblockdev.3_amdu25mount_test.mount: Deactivated successfully. Oct 7 20:43:14 storageqe-109 kernel: XFS (dm-4): Unmounting Filesystem efece30b-1295-4e0a-8ca0-90dc2f336adf Oct 7 20:43:14 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs xfs in remove_crypt Oct 7 20:43:14 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: will run io in dir /tmp/libblockdev.fglxm52xmount_test with fs ext4 Oct 7 20:43:25 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 0216d140-885a-4510-bed5-837359fa3306 r/w with ordered data mode. Quota mode: none. Oct 7 20:43:25 storageqe-109 INFO: will run io in dir /tmp/libblockdev.fglxm52xmount_test with fs ext4 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:43:30 storageqe-109 systemd[1]: tmp-libblockdev.fglxm52xmount_test.mount: Deactivated successfully. Oct 7 20:43:30 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 0216d140-885a-4510-bed5-837359fa3306. Oct 7 20:43:30 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext4 in remove_crypt Oct 7 20:43:30 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: will run io in dir /tmp/libblockdev.kr3ex7anmount_test with fs ext3 Oct 7 20:43:40 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext3 file system using the ext4 subsystem Oct 7 20:43:40 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem a2a4de7d-e202-4212-97d3-727581476892 r/w with ordered data mode. Quota mode: none. Oct 7 20:43:40 storageqe-109 INFO: will run io in dir /tmp/libblockdev.kr3ex7anmount_test with fs ext3 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:43:45 storageqe-109 systemd[1]: tmp-libblockdev.kr3ex7anmount_test.mount: Deactivated successfully. Oct 7 20:43:45 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem a2a4de7d-e202-4212-97d3-727581476892. Oct 7 20:43:45 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext3 in remove_crypt Oct 7 20:43:45 storageqe-109 INFO: start IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: will run io in dir /tmp/libblockdev.8u4fsg_vmount_test with fs ext2 Oct 7 20:43:55 storageqe-109 kernel: EXT4-fs (dm-4): mounting ext2 file system using the ext4 subsystem Oct 7 20:43:55 storageqe-109 systemd[1078]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories... Oct 7 20:43:55 storageqe-109 kernel: EXT4-fs (dm-4): mounted filesystem 4942732a-7e34-4048-8998-2bb47809d05f r/w without journal. Quota mode: none. Oct 7 20:43:55 storageqe-109 INFO: will run io in dir /tmp/libblockdev.8u4fsg_vmount_test with fs ext2 Oct 7 20:43:55 storageqe-109 systemd[1078]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories. INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt INFO: remove crypt device QwoMEfHaPT INFO: finishe the remove crypt device QwoMEfHaPT Oct 7 20:44:00 storageqe-109 systemd[1]: tmp-libblockdev.8u4fsg_vmount_test.mount: Deactivated successfully. Oct 7 20:44:00 storageqe-109 kernel: EXT4-fs (dm-4): unmounting filesystem 4942732a-7e34-4048-8998-2bb47809d05f. Oct 7 20:44:00 storageqe-109 INFO: End IO testing with the luks device /dev/mapper/QwoMEfHaPT and fs ext2 in remove_crypt Oct 7 20:44:00 storageqe-109 INFO: remove crypt device QwoMEfHaPT Oct 7 20:44:00 storageqe-109 INFO: finishe the remove crypt device QwoMEfHaPT INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_reencrypt_with_header[npo2_linear] #### Oct 7 20:44:05 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:44:05 storageqe-109 INFO: #### END test_reencrypt_with_header[npo2_linear] #### Oct 7 20:44:05 storageqe-109 stratisd[4947]: [2025-10-08T00:44:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:05 storageqe-109 stratisd[4947]: [2025-10-08T00:44:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:05 storageqe-109 stratisd[4947]: [2025-10-08T00:44:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:05 storageqe-109 stratisd[4947]: [2025-10-08T00:44:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:06 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 20:44:07 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 20:44:07 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 20:44:07 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 20:44:07 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 20:44:18 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_luks_intergrity[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:44:23 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 20:44:24 storageqe-109 INFO: #### will start test_luks_intergrity[npo2_linear] ##### Oct 7 20:44:24 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 512, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:44:29 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 512, 1, None Oct 7 20:44:29 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:44:29 storageqe-109 stratisd[4947]: [2025-10-08T00:44:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:29 storageqe-109 stratisd[4947]: [2025-10-08T00:44:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:33 storageqe-109 stratisd[4947]: [2025-10-08T00:44:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:33 storageqe-109 stratisd[4947]: [2025-10-08T00:44:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:37 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:44:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:44:43 storageqe-109 stratisd[4947]: [2025-10-08T00:44:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:44:43 storageqe-109 stratisd[4947]: [2025-10-08T00:44:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:44:53 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:45:03 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:45:13 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:45:23 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q Oct 7 20:45:33 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:45:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:45:53 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:46:03 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:46:13 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:46:23 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 20:46:33 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 20:46:33 storageqe-109 stratisd[4947]: [2025-10-08T00:46:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:46:33 storageqe-109 stratisd[4947]: [2025-10-08T00:46:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-plain64, hmac-sha256, 256, 512, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:46:43 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 512, 1, None Oct 7 20:46:43 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:46:44 storageqe-109 stratisd[4947]: [2025-10-08T00:46:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:46:44 storageqe-109 stratisd[4947]: [2025-10-08T00:46:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:46:48 storageqe-109 stratisd[4947]: [2025-10-08T00:46:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:46:48 storageqe-109 stratisd[4947]: [2025-10-08T00:46:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:46:58 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:46:58 storageqe-109 stratisd[4947]: [2025-10-08T00:46:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:46:58 storageqe-109 stratisd[4947]: [2025-10-08T00:46:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:47:08 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:47:18 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:47:28 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:47:38 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q Oct 7 20:47:48 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:47:58 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:48:08 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:48:18 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:48:28 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:48:38 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 20:48:48 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 20:48:48 storageqe-109 stratisd[4947]: [2025-10-08T00:48:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:48:48 storageqe-109 stratisd[4947]: [2025-10-08T00:48:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 256, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:48:58 storageqe-109 INFO: aes-xts-random, hmac-sha256, 256, 512, None, None Oct 7 20:48:59 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:48:59 storageqe-109 stratisd[4947]: [2025-10-08T00:48:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:48:59 storageqe-109 stratisd[4947]: [2025-10-08T00:48:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:49:04 storageqe-109 stratisd[4947]: [2025-10-08T00:49:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:49:04 storageqe-109 stratisd[4947]: [2025-10-08T00:49:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:49:14 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:49:14 storageqe-109 stratisd[4947]: [2025-10-08T00:49:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:49:14 storageqe-109 stratisd[4947]: [2025-10-08T00:49:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:49:24 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:49:34 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:49:44 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:49:54 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:50:04 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 512, None, None Oct 7 20:50:04 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:50:04 storageqe-109 stratisd[4947]: [2025-10-08T00:50:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:50:04 storageqe-109 stratisd[4947]: [2025-10-08T00:50:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:50:10 storageqe-109 stratisd[4947]: [2025-10-08T00:50:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:50:10 storageqe-109 stratisd[4947]: [2025-10-08T00:50:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:50:20 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:50:20 storageqe-109 stratisd[4947]: [2025-10-08T00:50:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:50:20 storageqe-109 stratisd[4947]: [2025-10-08T00:50:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:50:30 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:50:40 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:50:50 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:51:00 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 512, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:51:10 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 512, None, None Oct 7 20:51:10 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:51:10 storageqe-109 stratisd[4947]: [2025-10-08T00:51:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:51:10 storageqe-109 stratisd[4947]: [2025-10-08T00:51:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:51:14 storageqe-109 stratisd[4947]: [2025-10-08T00:51:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:51:14 storageqe-109 stratisd[4947]: [2025-10-08T00:51:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:51:25 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:51:25 storageqe-109 stratisd[4947]: [2025-10-08T00:51:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:51:25 storageqe-109 stratisd[4947]: [2025-10-08T00:51:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:51:35 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:51:45 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:51:55 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:52:05 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-random, hmac-sha256, 512, 512, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:52:15 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 512, None, None Oct 7 20:52:15 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '512' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:52:15 storageqe-109 stratisd[4947]: [2025-10-08T00:52:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:52:15 storageqe-109 stratisd[4947]: [2025-10-08T00:52:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:52:20 storageqe-109 stratisd[4947]: [2025-10-08T00:52:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:52:20 storageqe-109 stratisd[4947]: [2025-10-08T00:52:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:52:30 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:52:30 storageqe-109 stratisd[4947]: [2025-10-08T00:52:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:52:30 storageqe-109 stratisd[4947]: [2025-10-08T00:52:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:52:37 storageqe-109 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Oct 7 20:52:37 storageqe-109 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Oct 7 20:52:37 storageqe-109 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. cryptsetup status vALKgiSGeR -q Oct 7 20:52:40 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:52:50 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:53:00 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:53:10 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:53:20 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, None Oct 7 20:53:20 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:53:20 storageqe-109 stratisd[4947]: [2025-10-08T00:53:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:53:20 storageqe-109 stratisd[4947]: [2025-10-08T00:53:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:53:24 storageqe-109 stratisd[4947]: [2025-10-08T00:53:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:53:24 storageqe-109 stratisd[4947]: [2025-10-08T00:53:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:53:34 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:53:34 storageqe-109 stratisd[4947]: [2025-10-08T00:53:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:53:34 storageqe-109 stratisd[4947]: [2025-10-08T00:53:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:53:44 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:53:54 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:54:04 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:54:14 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:54:24 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, None Oct 7 20:54:24 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:54:24 storageqe-109 stratisd[4947]: [2025-10-08T00:54:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:54:24 storageqe-109 stratisd[4947]: [2025-10-08T00:54:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:54:27 storageqe-109 stratisd[4947]: [2025-10-08T00:54:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:54:27 storageqe-109 stratisd[4947]: [2025-10-08T00:54:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:54:37 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:54:37 storageqe-109 stratisd[4947]: [2025-10-08T00:54:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:54:37 storageqe-109 stratisd[4947]: [2025-10-08T00:54:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:54:47 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:54:57 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:55:07 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:55:17 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:55:27 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None Oct 7 20:55:27 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:55:27 storageqe-109 stratisd[4947]: [2025-10-08T00:55:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:55:27 storageqe-109 stratisd[4947]: [2025-10-08T00:55:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:55:30 storageqe-109 stratisd[4947]: [2025-10-08T00:55:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:55:30 storageqe-109 stratisd[4947]: [2025-10-08T00:55:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:55:40 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:55:40 storageqe-109 stratisd[4947]: [2025-10-08T00:55:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:55:40 storageqe-109 stratisd[4947]: [2025-10-08T00:55:40Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:55:50 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:56:00 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:56:10 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:56:20 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:56:30 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, None Oct 7 20:56:31 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:56:31 storageqe-109 stratisd[4947]: [2025-10-08T00:56:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:56:31 storageqe-109 stratisd[4947]: [2025-10-08T00:56:31Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:56:33 storageqe-109 stratisd[4947]: [2025-10-08T00:56:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:56:33 storageqe-109 stratisd[4947]: [2025-10-08T00:56:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:56:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:56:43 storageqe-109 stratisd[4947]: [2025-10-08T00:56:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:56:43 storageqe-109 stratisd[4947]: [2025-10-08T00:56:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:56:53 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:57:04 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:57:14 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:57:24 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q Oct 7 20:57:34 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:57:44 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:57:54 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:58:04 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 20:58:14 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:58:24 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 20:58:34 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 20:58:34 storageqe-109 stratisd[4947]: [2025-10-08T00:58:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:58:34 storageqe-109 stratisd[4947]: [2025-10-08T00:58:34Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:58:44 storageqe-109 INFO: aes-xts-random, hmac-sha256, 256, 4096, None, None Oct 7 20:58:44 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:58:44 storageqe-109 stratisd[4947]: [2025-10-08T00:58:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:58:44 storageqe-109 stratisd[4947]: [2025-10-08T00:58:44Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:58:47 storageqe-109 stratisd[4947]: [2025-10-08T00:58:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:58:47 storageqe-109 stratisd[4947]: [2025-10-08T00:58:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:58:57 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 20:58:57 storageqe-109 stratisd[4947]: [2025-10-08T00:58:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:58:57 storageqe-109 stratisd[4947]: [2025-10-08T00:58:57Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 20:59:07 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:59:17 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 20:59:27 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 20:59:37 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None Oct 7 20:59:47 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:59:47 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 20:59:48 storageqe-109 stratisd[4947]: [2025-10-08T00:59:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:59:48 storageqe-109 stratisd[4947]: [2025-10-08T00:59:48Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:59:51 storageqe-109 stratisd[4947]: [2025-10-08T00:59:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 20:59:51 storageqe-109 stratisd[4947]: [2025-10-08T00:59:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:00:01 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:00:01 storageqe-109 stratisd[4947]: [2025-10-08T01:00:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:00:01 storageqe-109 stratisd[4947]: [2025-10-08T01:00:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:00:11 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:00:21 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:00:31 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:00:41 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:00:51 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None Oct 7 21:00:51 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:00:52 storageqe-109 stratisd[4947]: [2025-10-08T01:00:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:00:52 storageqe-109 stratisd[4947]: [2025-10-08T01:00:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:00:54 storageqe-109 stratisd[4947]: [2025-10-08T01:00:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:00:54 storageqe-109 stratisd[4947]: [2025-10-08T01:00:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:01:04 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:01:04 storageqe-109 stratisd[4947]: [2025-10-08T01:01:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:01:04 storageqe-109 stratisd[4947]: [2025-10-08T01:01:04Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:01:15 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:01:25 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:01:35 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:01:45 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:01:55 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 4096, None, None Oct 7 21:01:55 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:01:55 storageqe-109 stratisd[4947]: [2025-10-08T01:01:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:01:55 storageqe-109 stratisd[4947]: [2025-10-08T01:01:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:01:58 storageqe-109 stratisd[4947]: [2025-10-08T01:01:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:01:58 storageqe-109 stratisd[4947]: [2025-10-08T01:01:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:02:08 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:02:08 storageqe-109 stratisd[4947]: [2025-10-08T01:02:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:02:08 storageqe-109 stratisd[4947]: [2025-10-08T01:02:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:02:18 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:02:28 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:02:38 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:02:48 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 512, 4096, 1, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:02:58 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 512, 4096, 1, None Oct 7 21:02:58 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:02:58 storageqe-109 stratisd[4947]: [2025-10-08T01:02:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:02:58 storageqe-109 stratisd[4947]: [2025-10-08T01:02:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:03:01 storageqe-109 stratisd[4947]: [2025-10-08T01:03:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:03:01 storageqe-109 stratisd[4947]: [2025-10-08T01:03:01Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:03:11 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:03:11 storageqe-109 stratisd[4947]: [2025-10-08T01:03:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:03:11 storageqe-109 stratisd[4947]: [2025-10-08T01:03:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:03:21 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:03:31 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:03:41 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:03:51 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q Oct 7 21:04:01 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:04:11 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 21:04:21 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 21:04:31 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 21:04:41 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:04:51 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 21:05:02 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 21:05:02 storageqe-109 stratisd[4947]: [2025-10-08T01:05:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:05:02 storageqe-109 stratisd[4947]: [2025-10-08T01:05:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:05:12 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None Oct 7 21:05:12 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:05:12 storageqe-109 stratisd[4947]: [2025-10-08T01:05:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:05:12 storageqe-109 stratisd[4947]: [2025-10-08T01:05:12Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:05:15 storageqe-109 stratisd[4947]: [2025-10-08T01:05:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:05:15 storageqe-109 stratisd[4947]: [2025-10-08T01:05:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:05:25 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:05:25 storageqe-109 stratisd[4947]: [2025-10-08T01:05:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:05:25 storageqe-109 stratisd[4947]: [2025-10-08T01:05:25Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:05:35 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:05:45 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:05:55 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:06:05 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:06:15 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 256, 4096, None, None Oct 7 21:06:15 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:06:15 storageqe-109 stratisd[4947]: [2025-10-08T01:06:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:06:15 storageqe-109 stratisd[4947]: [2025-10-08T01:06:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:06:19 storageqe-109 stratisd[4947]: [2025-10-08T01:06:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:06:19 storageqe-109 stratisd[4947]: [2025-10-08T01:06:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:06:29 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:06:29 storageqe-109 stratisd[4947]: [2025-10-08T01:06:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:06:29 storageqe-109 stratisd[4947]: [2025-10-08T01:06:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:06:39 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:06:49 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:06:59 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:07:09 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:07:19 storageqe-109 INFO: aes-xts-random, hmac-sha256, 512, 4096, None, None Oct 7 21:07:19 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '512' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '512' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:07:19 storageqe-109 stratisd[4947]: [2025-10-08T01:07:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:07:19 storageqe-109 stratisd[4947]: [2025-10-08T01:07:19Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:07:22 storageqe-109 stratisd[4947]: [2025-10-08T01:07:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:07:22 storageqe-109 stratisd[4947]: [2025-10-08T01:07:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:07:32 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:07:32 storageqe-109 stratisd[4947]: [2025-10-08T01:07:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:07:32 storageqe-109 stratisd[4947]: [2025-10-08T01:07:32Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:07:42 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:07:52 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:08:02 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:08:12 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-gcm-random, aead, 128, 512, None, None cryptsetup --integrity 'aead' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:08:22 storageqe-109 INFO: aes-gcm-random, aead, 128, 512, None, None Oct 7 21:08:22 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '512' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:08:22 storageqe-109 stratisd[4947]: [2025-10-08T01:08:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:08:22 storageqe-109 stratisd[4947]: [2025-10-08T01:08:22Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:08:26 storageqe-109 stratisd[4947]: [2025-10-08T01:08:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:08:26 storageqe-109 stratisd[4947]: [2025-10-08T01:08:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:08:36 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:08:36 storageqe-109 stratisd[4947]: [2025-10-08T01:08:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:08:36 storageqe-109 stratisd[4947]: [2025-10-08T01:08:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:08:46 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:08:56 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:09:06 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:09:16 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-gcm-random, aead, 128, 4096, None, None cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:09:27 storageqe-109 INFO: aes-gcm-random, aead, 128, 4096, None, None Oct 7 21:09:27 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:09:27 storageqe-109 stratisd[4947]: [2025-10-08T01:09:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:09:27 storageqe-109 stratisd[4947]: [2025-10-08T01:09:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:09:29 storageqe-109 stratisd[4947]: [2025-10-08T01:09:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:09:29 storageqe-109 stratisd[4947]: [2025-10-08T01:09:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:09:39 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:09:39 storageqe-109 stratisd[4947]: [2025-10-08T01:09:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:09:39 storageqe-109 stratisd[4947]: [2025-10-08T01:09:39Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:09:50 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:10:00 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:10:10 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:10:20 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-gcm-random, aead, 256, 4096, None, None cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:10:30 storageqe-109 INFO: aes-gcm-random, aead, 256, 4096, None, None Oct 7 21:10:30 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:10:30 storageqe-109 stratisd[4947]: [2025-10-08T01:10:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:10:30 storageqe-109 stratisd[4947]: [2025-10-08T01:10:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:10:33 storageqe-109 stratisd[4947]: [2025-10-08T01:10:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:10:33 storageqe-109 stratisd[4947]: [2025-10-08T01:10:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:10:43 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:10:43 storageqe-109 stratisd[4947]: [2025-10-08T01:10:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:10:43 storageqe-109 stratisd[4947]: [2025-10-08T01:10:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:10:53 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:11:03 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:11:13 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:11:23 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: chacha20-plain64, poly1305, 256, 512, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:11:33 storageqe-109 INFO: chacha20-plain64, poly1305, 256, 512, None, None Oct 7 21:11:33 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:11:33 storageqe-109 stratisd[4947]: [2025-10-08T01:11:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:11:33 storageqe-109 stratisd[4947]: [2025-10-08T01:11:33Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:11:37 storageqe-109 stratisd[4947]: [2025-10-08T01:11:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:11:37 storageqe-109 stratisd[4947]: [2025-10-08T01:11:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:11:47 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:11:47 storageqe-109 stratisd[4947]: [2025-10-08T01:11:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:11:47 storageqe-109 stratisd[4947]: [2025-10-08T01:11:47Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:11:57 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:12:07 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:12:17 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:12:27 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: chacha20-random, poly1305, 256, 512, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:12:37 storageqe-109 INFO: chacha20-random, poly1305, 256, 512, None, None Oct 7 21:12:37 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '512' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:12:37 storageqe-109 stratisd[4947]: [2025-10-08T01:12:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:12:37 storageqe-109 stratisd[4947]: [2025-10-08T01:12:37Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:12:42 storageqe-109 stratisd[4947]: [2025-10-08T01:12:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:12:42 storageqe-109 stratisd[4947]: [2025-10-08T01:12:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:12:52 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:12:52 storageqe-109 stratisd[4947]: [2025-10-08T01:12:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:12:52 storageqe-109 stratisd[4947]: [2025-10-08T01:12:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:13:02 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:13:12 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:13:22 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:13:32 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: chacha20-plain64, poly1305, 256, 4096, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:13:43 storageqe-109 INFO: chacha20-plain64, poly1305, 256, 4096, None, None Oct 7 21:13:43 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:13:43 storageqe-109 stratisd[4947]: [2025-10-08T01:13:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:13:43 storageqe-109 stratisd[4947]: [2025-10-08T01:13:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:13:45 storageqe-109 stratisd[4947]: [2025-10-08T01:13:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:13:45 storageqe-109 stratisd[4947]: [2025-10-08T01:13:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:13:55 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:13:55 storageqe-109 stratisd[4947]: [2025-10-08T01:13:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:13:55 storageqe-109 stratisd[4947]: [2025-10-08T01:13:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:14:05 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:14:15 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:14:25 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:14:35 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: chacha20-random, poly1305, 256, 4096, None, None Oct 7 21:14:46 storageqe-109 INFO: chacha20-random, poly1305, 256, 4096, None, None cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:14:46 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:14:46 storageqe-109 stratisd[4947]: [2025-10-08T01:14:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:14:46 storageqe-109 stratisd[4947]: [2025-10-08T01:14:46Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:14:49 storageqe-109 stratisd[4947]: [2025-10-08T01:14:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:14:49 storageqe-109 stratisd[4947]: [2025-10-08T01:14:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:14:59 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:14:59 storageqe-109 stratisd[4947]: [2025-10-08T01:14:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:14:59 storageqe-109 stratisd[4947]: [2025-10-08T01:14:59Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:15:09 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:15:19 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:15:29 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:15:39 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: the add_device_inline device dm-3 support npo2 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True Oct 7 21:15:49 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 7 21:15:49 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:15:49 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:15:49 storageqe-109 stratisd[4947]: [2025-10-08T01:15:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:15:49 storageqe-109 stratisd[4947]: [2025-10-08T01:15:49Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:15:52 storageqe-109 stratisd[4947]: [2025-10-08T01:15:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:15:52 storageqe-109 stratisd[4947]: [2025-10-08T01:15:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:16:02 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:16:02 storageqe-109 stratisd[4947]: [2025-10-08T01:16:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:16:02 storageqe-109 stratisd[4947]: [2025-10-08T01:16:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:16:12 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:16:22 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:16:32 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:16:42 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:16:52 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, None, True Oct 7 21:16:52 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:16:52 storageqe-109 stratisd[4947]: [2025-10-08T01:16:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:16:52 storageqe-109 stratisd[4947]: [2025-10-08T01:16:52Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:16:55 storageqe-109 stratisd[4947]: [2025-10-08T01:16:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:16:55 storageqe-109 stratisd[4947]: [2025-10-08T01:16:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:17:05 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:17:05 storageqe-109 stratisd[4947]: [2025-10-08T01:17:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:17:05 storageqe-109 stratisd[4947]: [2025-10-08T01:17:05Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:17:15 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:17:25 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:17:35 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:17:45 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:17:55 storageqe-109 INFO: aes-xts-plain64, hmac-sha256, 256, 4096, 1, True Oct 7 21:17:55 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-plain64' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:17:55 storageqe-109 stratisd[4947]: [2025-10-08T01:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:17:55 storageqe-109 stratisd[4947]: [2025-10-08T01:17:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:17:58 storageqe-109 stratisd[4947]: [2025-10-08T01:17:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:17:58 storageqe-109 stratisd[4947]: [2025-10-08T01:17:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:18:08 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:18:08 storageqe-109 stratisd[4947]: [2025-10-08T01:18:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:18:08 storageqe-109 stratisd[4947]: [2025-10-08T01:18:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:18:18 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:18:28 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:18:38 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:18:48 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q Oct 7 21:18:58 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderBackup /dev/mapper/npo2linear -q cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:19:08 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' --header '/home/backfilevALKgiSGeR' open /dev/mapper/npo2linear vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 21:19:18 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 21:19:28 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q Oct 7 21:19:38 storageqe-109 journal: cryptsetup --header '/home/backfilevALKgiSGeR' status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:19:48 storageqe-109 journal: cryptsetup close vALKgiSGeR -q cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 21:19:58 storageqe-109 journal: cryptsetup --header-backup-file '/home/backfilevALKgiSGeR' --key-file '/tmp/testfilemlk' luksHeaderRestore /dev/mapper/npo2linear -q Oct 7 21:19:58 storageqe-109 stratisd[4947]: [2025-10-08T01:19:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:19:58 storageqe-109 stratisd[4947]: [2025-10-08T01:19:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. INFO: aes-xts-random, hmac-sha256, 256, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:20:08 storageqe-109 INFO: aes-xts-random, hmac-sha256, 256, 4096, None, True Oct 7 21:20:08 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-xts-random' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:20:08 storageqe-109 stratisd[4947]: [2025-10-08T01:20:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:20:08 storageqe-109 stratisd[4947]: [2025-10-08T01:20:08Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:20:11 storageqe-109 stratisd[4947]: [2025-10-08T01:20:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:20:11 storageqe-109 stratisd[4947]: [2025-10-08T01:20:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:20:21 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:20:21 storageqe-109 stratisd[4947]: [2025-10-08T01:20:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:20:21 storageqe-109 stratisd[4947]: [2025-10-08T01:20:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:20:29 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 21:20:29 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 21:20:29 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. cryptsetup status vALKgiSGeR -q Oct 7 21:20:31 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:20:41 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:20:51 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:21:01 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:21:11 storageqe-109 INFO: aes-cbc-essiv:sha256, hmac-sha256, 128, 4096, None, True Oct 7 21:21:11 storageqe-109 journal: cryptsetup --integrity 'hmac-sha256' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '128' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-cbc-essiv:sha256' --integrity-key-size '256' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:21:11 storageqe-109 stratisd[4947]: [2025-10-08T01:21:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:21:11 storageqe-109 stratisd[4947]: [2025-10-08T01:21:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:21:14 storageqe-109 stratisd[4947]: [2025-10-08T01:21:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:21:14 storageqe-109 stratisd[4947]: [2025-10-08T01:21:14Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:21:24 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:21:24 storageqe-109 stratisd[4947]: [2025-10-08T01:21:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:21:24 storageqe-109 stratisd[4947]: [2025-10-08T01:21:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:21:35 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:21:45 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:21:55 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:22:05 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: aes-gcm-random, aead, 256, 4096, None, True cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:22:15 storageqe-109 INFO: aes-gcm-random, aead, 256, 4096, None, True Oct 7 21:22:15 storageqe-109 journal: cryptsetup --integrity 'aead' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'aes-gcm-random' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:22:15 storageqe-109 stratisd[4947]: [2025-10-08T01:22:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:22:15 storageqe-109 stratisd[4947]: [2025-10-08T01:22:15Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:22:17 storageqe-109 stratisd[4947]: [2025-10-08T01:22:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:22:17 storageqe-109 stratisd[4947]: [2025-10-08T01:22:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:22:27 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:22:27 storageqe-109 stratisd[4947]: [2025-10-08T01:22:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:22:27 storageqe-109 stratisd[4947]: [2025-10-08T01:22:27Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:22:37 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:22:47 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:22:57 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:23:07 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: chacha20-plain64, poly1305, 256, 4096, None, True cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:23:17 storageqe-109 INFO: chacha20-plain64, poly1305, 256, 4096, None, True Oct 7 21:23:18 storageqe-109 journal: cryptsetup --integrity 'poly1305' --type 'luks2' --sector-size '4096' --offset '8192' --key-size '256' --pbkdf 'pbkdf2' --pbkdf-force-iterations '1000' --key-file '/tmp/testfilemlk' --cipher 'chacha20-plain64' luksFormat /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:23:18 storageqe-109 stratisd[4947]: [2025-10-08T01:23:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:23:18 storageqe-109 stratisd[4947]: [2025-10-08T01:23:18Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:23:20 storageqe-109 stratisd[4947]: [2025-10-08T01:23:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:23:20 storageqe-109 stratisd[4947]: [2025-10-08T01:23:20Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:23:30 storageqe-109 journal: cryptsetup --key-file '/tmp/testfilemlk' open /dev/mapper/npo2linear vALKgiSGeR -q Oct 7 21:23:30 storageqe-109 stratisd[4947]: [2025-10-08T01:23:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 7 21:23:30 storageqe-109 stratisd[4947]: [2025-10-08T01:23:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. cryptsetup status vALKgiSGeR -q Oct 7 21:23:40 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:23:50 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup status vALKgiSGeR -q Oct 7 21:24:00 storageqe-109 journal: cryptsetup status vALKgiSGeR -q cryptsetup close vALKgiSGeR -q Oct 7 21:24:10 storageqe-109 journal: cryptsetup close vALKgiSGeR -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_luks_intergrity[npo2_linear] #### INFO: #### will start test_dm_integrity_format[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 21:24:25 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 21:24:25 storageqe-109 INFO: #### END test_luks_intergrity[npo2_linear] #### Oct 7 21:24:25 storageqe-109 INFO: #### will start test_dm_integrity_format[npo2_linear] ##### Oct 7 21:24:25 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:24:30 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:24:48 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:24:58 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:25:08 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:25:18 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:25:43 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:25:53 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:26:03 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:26:13 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:26:30 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:26:50 storageqe-109 journal: integritysetup close JoqdVHrxTS -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:27:00 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:27:13 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:27:23 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:27:33 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:27:44 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:28:07 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:28:17 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:28:27 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:28:37 storageqe-109 journal: integritysetup status JoqdVHrxTS -q Oct 7 21:28:49 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 21:28:49 storageqe-109 dnf[2458627]: Updating Subscription Management repositories. Oct 7 21:28:49 storageqe-109 dnf[2458627]: Unable to read consumer identity Oct 7 21:28:49 storageqe-109 dnf[2458627]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 21:28:49 storageqe-109 dnf[2458627]: Metadata cache refreshed recently. Oct 7 21:28:49 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 21:28:49 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:28:52 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:29:11 storageqe-109 journal: integritysetup close JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:29:21 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:29:35 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:29:45 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:29:55 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:30:05 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:30:29 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:30:39 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:30:49 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:30:59 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:31:14 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:31:33 storageqe-109 journal: integritysetup close JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q Oct 7 21:31:43 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:31:57 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:32:07 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:32:17 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:32:27 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:32:50 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:33:00 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:33:10 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:33:20 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:33:36 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:33:54 storageqe-109 journal: integritysetup close JoqdVHrxTS -q INFO: the add_device_inline device dm-3 support npo2 integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:34:04 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 7 21:34:04 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:34:19 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:34:29 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:34:39 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:34:49 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:35:13 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:35:23 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:35:33 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:35:43 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:35:58 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:36:17 storageqe-109 journal: integritysetup close JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:36:27 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:36:42 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:36:52 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:37:02 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:37:12 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:37:36 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:37:46 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:37:56 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:38:06 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:38:21 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '32' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:38:40 storageqe-109 journal: integritysetup close JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:38:50 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:39:05 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:39:15 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:39:25 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:39:35 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:39:59 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:40:09 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:40:19 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:40:29 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:40:44 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileFRv' --integrity-key-size '4096' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:41:03 storageqe-109 journal: integritysetup close JoqdVHrxTS -q integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline Oct 7 21:41:13 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear --integrity-legacy-padding -q --integrity-inline integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:41:28 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:41:38 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup dump /dev/mapper/npo2linear -q Oct 7 21:41:48 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:41:58 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:42:21 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:42:31 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:42:41 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup status JoqdVHrxTS -q Oct 7 21:42:51 storageqe-109 journal: integritysetup status JoqdVHrxTS -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear JoqdVHrxTS -q Oct 7 21:43:06 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear JoqdVHrxTS -q integritysetup close JoqdVHrxTS -q Oct 7 21:43:25 storageqe-109 journal: integritysetup close JoqdVHrxTS -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_integrity_format[npo2_linear] #### INFO: #### will start test_integrity_error_detection[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 21:43:40 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 21:43:40 storageqe-109 INFO: #### END test_dm_integrity_format[npo2_linear] #### Oct 7 21:43:40 storageqe-109 INFO: #### will start test_integrity_error_detection[npo2_linear] ##### Oct 7 21:43:40 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 21:43:45 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:43:58 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:44:08 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:44:30 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:44:30 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:44:30 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:44:30 storageqe-109 kernel: buffer_io_error: 246 callbacks suppressed Oct 7 21:44:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:44:40 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:44:40 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:44:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:44:40 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 21:44:50 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:45:03 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:45:13 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:45:31 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:45:31 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:45:31 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:45:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:45:41 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:45:41 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:45:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:45:41 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 21:45:51 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:46:04 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:46:14 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:46:36 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:46:36 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:46:36 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:46:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:46:46 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:46:46 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:46:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:46:46 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 21:46:57 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:47:09 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:47:19 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:47:37 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:47:37 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:47:37 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:47:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:47:47 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:47:47 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:47:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:47:47 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 21:47:58 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:48:13 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:48:23 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:49:02 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:49:02 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:49:02 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:49:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:49:12 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:49:12 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:49:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:49:12 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' format /dev/mapper/npo2linear -q Oct 7 21:49:22 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:49:38 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:49:48 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:50:27 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:50:27 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:50:27 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:50:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:50:37 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:50:37 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:50:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:50:37 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 21:50:47 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:51:01 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:51:11 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:51:32 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:51:32 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:51:32 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:51:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:51:42 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:51:42 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:51:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:51:42 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 21:51:52 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:52:09 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:52:19 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:53:11 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:53:11 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:53:11 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:53:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:53:21 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:53:21 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:53:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:53:21 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q Oct 7 21:53:31 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:53:45 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:53:55 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:54:17 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:54:17 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:54:17 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:54:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:54:27 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:54:27 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:54:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:54:27 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 21:54:37 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:54:55 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:55:05 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:55:57 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:55:57 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:55:57 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:55:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:56:07 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:56:07 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:56:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:56:07 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 21:56:17 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:56:31 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 21:56:41 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:57:04 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 21:57:04 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:57:04 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:57:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:57:14 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:57:14 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:57:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:57:14 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -B -q Oct 7 21:57:24 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '512' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 21:57:37 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B integritysetup close WQdHGKgFEe -q Oct 7 21:57:47 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 21:58:09 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 21:58:09 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:58:09 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:58:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:58:19 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:58:19 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:58:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:58:19 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -B -q Oct 7 21:58:29 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 21:58:42 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B integritysetup close WQdHGKgFEe -q Oct 7 21:58:52 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 21:59:10 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 21:59:10 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:59:10 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:59:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 21:59:20 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:59:20 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 21:59:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 21:59:20 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -B -q Oct 7 21:59:31 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '512' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 21:59:48 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B integritysetup close WQdHGKgFEe -q Oct 7 21:59:58 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:00:50 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:00:50 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:00:50 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:00:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:01:00 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:01:00 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:01:00 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -B -q Oct 7 22:01:10 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:01:24 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B integritysetup close WQdHGKgFEe -q Oct 7 22:01:34 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:01:56 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:01:56 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:01:56 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:01:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:02:06 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:02:06 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:02:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:02:06 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q Oct 7 22:02:16 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '512' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:02:34 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B integritysetup close WQdHGKgFEe -q Oct 7 22:02:44 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:03:36 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:03:36 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:03:36 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:03:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:03:46 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:03:46 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:03:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:03:46 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q Oct 7 22:03:56 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -B -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:04:10 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B integritysetup close WQdHGKgFEe -q Oct 7 22:04:20 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:04:43 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q -B Oct 7 22:04:43 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:04:43 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:04:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:04:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:04:53 storageqe-109 kernel: device-mapper: integrity: dm-4: Checksum failed at sector 0x0 Oct 7 22:04:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:04:53 storageqe-109 journal: integritysetup close WQdHGKgFEe -q INFO: the add_device_inline device dm-3 support npo2 integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 7 22:05:03 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 7 22:05:03 storageqe-109 journal: integritysetup --integrity 'crc32c' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:05:16 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 22:05:26 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:05:43 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:05:43 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:05:43 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:05:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:05:53 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:05:53 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:05:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:05:53 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 7 22:06:03 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:06:16 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 22:06:26 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:06:43 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:06:43 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:06:43 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:06:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:06:53 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:06:53 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:06:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:06:53 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 7 22:07:03 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:07:18 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 22:07:28 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:07:45 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:07:45 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:07:45 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:07:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:07:55 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:07:55 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:07:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:07:55 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline Oct 7 22:08:05 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:08:20 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 22:08:30 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:08:47 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:08:47 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:08:47 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:08:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:08:57 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:08:57 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:08:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:08:57 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-inline Oct 7 22:09:07 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --sector-size '4096' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-inline integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:09:22 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q integritysetup close WQdHGKgFEe -q Oct 7 22:09:32 storageqe-109 journal: integritysetup close WQdHGKgFEe -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:09:50 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileyRj' --integrity-key-size '32' open /dev/mapper/npo2linear WQdHGKgFEe --integrity-no-journal -q Oct 7 22:09:50 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:09:50 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:09:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read integritysetup close WQdHGKgFEe -q Oct 7 22:10:00 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:10:00 storageqe-109 kernel: device-mapper: integrity: dm-3: Checksum failed at sector 0x0 Oct 7 22:10:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 22:10:00 storageqe-109 journal: integritysetup close WQdHGKgFEe -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_error_detection[npo2_linear] #### INFO: #### will start test_integrity_int_journal[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:10:15 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:10:15 storageqe-109 INFO: #### END test_integrity_error_detection[npo2_linear] #### Oct 7 22:10:15 storageqe-109 INFO: #### will start test_integrity_int_journal[npo2_linear] ##### Oct 7 22:10:15 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32' --sector-size '512' --tag-size '4' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 22:10:20 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '512' --tag-size '4' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' open /dev/mapper/npo2linear xomAPLlkiN -q Oct 7 22:10:33 storageqe-109 journal: integritysetup --integrity 'crc32' --journal-watermark '66' --journal-commit-time '1000' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' open /dev/mapper/npo2linear xomAPLlkiN -q integritysetup close xomAPLlkiN -q Oct 7 22:10:43 storageqe-109 journal: integritysetup close xomAPLlkiN -q integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '20' format /dev/mapper/npo2linear -q Oct 7 22:10:53 storageqe-109 journal: integritysetup --integrity 'sha256' --sector-size '4096' --tag-size '32' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '20' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '20' open /dev/mapper/npo2linear xomAPLlkiN -q Oct 7 22:11:07 storageqe-109 journal: integritysetup --integrity 'sha256' --journal-watermark '34' --journal-commit-time '5000' --journal-integrity 'hmac-sha1' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '20' open /dev/mapper/npo2linear xomAPLlkiN -q integritysetup close xomAPLlkiN -q Oct 7 22:11:17 storageqe-109 journal: integritysetup close xomAPLlkiN -q integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 22:11:27 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' open /dev/mapper/npo2linear xomAPLlkiN -q Oct 7 22:11:42 storageqe-109 journal: integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '32' open /dev/mapper/npo2linear xomAPLlkiN -q integritysetup close xomAPLlkiN -q Oct 7 22:11:52 storageqe-109 journal: integritysetup close xomAPLlkiN -q integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '4096' format /dev/mapper/npo2linear -q Oct 7 22:12:02 storageqe-109 journal: integritysetup --integrity 'sha1' --sector-size '512' --tag-size '20' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '4096' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '4096' open /dev/mapper/npo2linear xomAPLlkiN -q Oct 7 22:12:18 storageqe-109 journal: integritysetup --integrity 'sha1' --journal-watermark '75' --journal-commit-time '9999' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfilepCe' --journal-integrity-key-size '4096' open /dev/mapper/npo2linear xomAPLlkiN -q integritysetup close xomAPLlkiN -q Oct 7 22:12:28 storageqe-109 journal: integritysetup close xomAPLlkiN -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_int_journal[npo2_linear] #### INFO: #### will start test_integrity_int_journal_crypt[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:12:43 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:12:43 storageqe-109 INFO: #### END test_integrity_int_journal[npo2_linear] #### Oct 7 22:12:43 storageqe-109 INFO: #### will start test_integrity_int_journal_crypt[npo2_linear] ##### Oct 7 22:12:43 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q Oct 7 22:12:48 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' open /dev/mapper/npo2linear gYciyvqhNK -q Oct 7 22:13:01 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' open /dev/mapper/npo2linear gYciyvqhNK -q integritysetup close gYciyvqhNK -q Oct 7 22:13:11 storageqe-109 journal: integritysetup close gYciyvqhNK -q integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q Oct 7 22:13:21 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' open /dev/mapper/npo2linear gYciyvqhNK -q Oct 7 22:13:34 storageqe-109 journal: integritysetup --journal-crypt 'cbc-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' open /dev/mapper/npo2linear gYciyvqhNK -q integritysetup close gYciyvqhNK -q Oct 7 22:13:44 storageqe-109 journal: integritysetup close gYciyvqhNK -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q Oct 7 22:13:54 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' open /dev/mapper/npo2linear gYciyvqhNK -q Oct 7 22:14:07 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '32' open /dev/mapper/npo2linear gYciyvqhNK -q integritysetup close gYciyvqhNK -q Oct 7 22:14:17 storageqe-109 journal: integritysetup close gYciyvqhNK -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q Oct 7 22:14:27 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' format /dev/mapper/npo2linear -q integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' open /dev/mapper/npo2linear gYciyvqhNK -q Oct 7 22:14:40 storageqe-109 journal: integritysetup --journal-crypt 'ctr-aes' --journal-crypt-key-file '/tmp/testfilenPf' --journal-crypt-key-size '16' open /dev/mapper/npo2linear gYciyvqhNK -q integritysetup close gYciyvqhNK -q Oct 7 22:14:50 storageqe-109 journal: integritysetup close gYciyvqhNK -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_int_journal_crypt[npo2_linear] #### INFO: #### will start test_integrity_int_mode[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:15:05 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:15:05 storageqe-109 INFO: #### END test_integrity_int_journal_crypt[npo2_linear] #### Oct 7 22:15:05 storageqe-109 INFO: #### will start test_integrity_int_mode[npo2_linear] ##### Oct 7 22:15:05 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 22:15:10 storageqe-109 journal: integritysetup --integrity 'crc32c' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qVSRuHAWrP -q Oct 7 22:15:23 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:15:33 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:15:43 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:15:53 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal Oct 7 22:16:03 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal integritysetup status qVSRuHAWrP -q Oct 7 22:16:13 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:16:23 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:16:33 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:16:43 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode Oct 7 22:16:53 storageqe-109 journal: integritysetup --integrity 'crc32c' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode integritysetup status qVSRuHAWrP -q Oct 7 22:17:03 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:17:13 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:17:23 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'crc32' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 22:17:33 storageqe-109 journal: integritysetup --integrity 'crc32' --tag-size '4' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qVSRuHAWrP -q Oct 7 22:17:46 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:17:56 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:18:06 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:18:16 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal Oct 7 22:18:26 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal integritysetup status qVSRuHAWrP -q Oct 7 22:18:36 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:18:46 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:18:56 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:19:06 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode Oct 7 22:19:16 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode integritysetup status qVSRuHAWrP -q Oct 7 22:19:26 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:19:36 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:19:46 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'sha1' --tag-size '20' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 22:19:56 storageqe-109 journal: integritysetup --integrity 'sha1' --tag-size '20' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qVSRuHAWrP -q Oct 7 22:20:12 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:20:22 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:20:32 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:20:42 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal Oct 7 22:20:52 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal integritysetup status qVSRuHAWrP -q Oct 7 22:21:02 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:21:12 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:21:22 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:21:32 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode Oct 7 22:21:42 storageqe-109 journal: integritysetup --integrity 'sha1' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode integritysetup status qVSRuHAWrP -q Oct 7 22:21:52 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:22:02 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:22:12 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'sha256' --tag-size '32' --sector-size '512' format /dev/mapper/npo2linear -q Oct 7 22:22:22 storageqe-109 journal: integritysetup --integrity 'sha256' --tag-size '32' --sector-size '512' format /dev/mapper/npo2linear -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qVSRuHAWrP -q Oct 7 22:22:39 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:22:49 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:22:59 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:23:09 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal Oct 7 22:23:19 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal integritysetup status qVSRuHAWrP -q Oct 7 22:23:29 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:23:39 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:23:49 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:23:59 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode Oct 7 22:24:10 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode integritysetup status qVSRuHAWrP -q Oct 7 22:24:20 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:24:30 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:24:40 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '512' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 22:24:50 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '512' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q Oct 7 22:25:07 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:25:18 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:25:28 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:25:38 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal Oct 7 22:25:48 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal integritysetup status qVSRuHAWrP -q Oct 7 22:25:58 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:26:08 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:26:18 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:26:28 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode Oct 7 22:26:38 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode integritysetup status qVSRuHAWrP -q Oct 7 22:26:48 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:26:58 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:27:08 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' format /dev/mapper/npo2linear -q Oct 7 22:27:18 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --tag-size '32' --sector-size '4096' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q Oct 7 22:27:32 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:27:42 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:27:52 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:28:02 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal Oct 7 22:28:12 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-no-journal integritysetup status qVSRuHAWrP -q Oct 7 22:28:22 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:28:32 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:28:42 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:28:52 storageqe-109 journal: integritysetup close qVSRuHAWrP -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode Oct 7 22:29:02 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileqPW' --integrity-key-size '32' open /dev/mapper/npo2linear qVSRuHAWrP -q --integrity-recovery-mode integritysetup status qVSRuHAWrP -q Oct 7 22:29:12 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup status qVSRuHAWrP -q Oct 7 22:29:22 storageqe-109 journal: integritysetup status qVSRuHAWrP -q integritysetup close qVSRuHAWrP -q Oct 7 22:29:32 storageqe-109 journal: integritysetup close qVSRuHAWrP -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_int_mode[npo2_linear] #### INFO: #### will start test_feature_test[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:29:47 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:29:47 storageqe-109 INFO: #### END test_integrity_int_mode[npo2_linear] #### Oct 7 22:29:47 storageqe-109 INFO: #### will start test_feature_test[npo2_linear] ##### Oct 7 22:29:48 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup format /dev/mapper/npo2linear -q --no-wipe Oct 7 22:29:53 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 7 22:29:53 storageqe-109 journal: integritysetup format /dev/mapper/npo2linear -q --no-wipe integritysetup open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:30:03 storageqe-109 journal: integritysetup open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate integritysetup close wMApZefzbH -q Oct 7 22:30:39 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --integrity 'sha256' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate-reset Oct 7 22:30:49 storageqe-109 journal: integritysetup --integrity 'sha256' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate-reset Oct 7 22:31:13 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 22:31:13 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 22:31:13 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. integritysetup close wMApZefzbH -q Oct 7 22:31:25 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --data-device '/dev/loop0' format /dev/mapper/npo2linear -q Oct 7 22:31:35 storageqe-109 journal: integritysetup --data-device '/dev/loop0' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop0' open /dev/mapper/npo2linear wMApZefzbH -q Oct 7 22:31:47 storageqe-109 journal: integritysetup --data-device '/dev/loop0' open /dev/mapper/npo2linear wMApZefzbH -q integritysetup status wMApZefzbH -q Oct 7 22:31:57 storageqe-109 journal: integritysetup status wMApZefzbH -q integritysetup close wMApZefzbH -q Oct 7 22:32:07 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/loop0 Oct 7 22:32:17 storageqe-109 journal: integritysetup format /dev/mapper/npo2linear -q --integrity-bitmap-mode /dev/loop0 integritysetup --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-bitmap-mode Oct 7 22:32:30 storageqe-109 journal: integritysetup --bitmap-sectors-per-bit '65536' --bitmap-flush-time '5000' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-bitmap-mode integritysetup status wMApZefzbH -q Oct 7 22:32:40 storageqe-109 journal: integritysetup status wMApZefzbH -q integritysetup status wMApZefzbH -q Oct 7 22:32:50 storageqe-109 journal: integritysetup status wMApZefzbH -q integritysetup close wMApZefzbH -q Oct 7 22:33:00 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-legacy-hmac --no-wipe Oct 7 22:33:10 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' format /dev/mapper/npo2linear -q --integrity-legacy-hmac --no-wipe integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:33:20 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:33:20 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Recalculating with HMAC is disabled for security reasons - if you really need it, use the argument "legacy_recalculate" (-EOPNOTSUPP) Oct 7 22:33:20 storageqe-109 kernel: device-mapper: ioctl: error adding target to table integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-legacy-recalculate Oct 7 22:33:30 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-legacy-recalculate integritysetup close wMApZefzbH -q Oct 7 22:33:40 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe Oct 7 22:33:50 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:34:00 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:34:00 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Recalculating with HMAC is disabled for security reasons - if you really need it, use the argument "legacy_recalculate" (-EOPNOTSUPP) Oct 7 22:34:00 storageqe-109 kernel: device-mapper: ioctl: error adding target to table integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-legacy-recalculate Oct 7 22:34:10 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-legacy-recalculate integritysetup close wMApZefzbH -q Oct 7 22:34:20 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe --integrity-legacy-hmac Oct 7 22:34:30 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe --integrity-legacy-hmac integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:34:41 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:34:41 storageqe-109 kernel: device-mapper: table: 253:4: integrity: Recalculating with HMAC is disabled for security reasons - if you really need it, use the argument "legacy_recalculate" (-EOPNOTSUPP) Oct 7 22:34:41 storageqe-109 kernel: device-mapper: ioctl: error adding target to table integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-legacy-recalculate Oct 7 22:34:51 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-legacy-recalculate integritysetup close wMApZefzbH -q Oct 7 22:35:01 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe Oct 7 22:35:11 storageqe-109 journal: integritysetup --tag-size '32' --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' format /dev/mapper/npo2linear -q --no-wipe integritysetup dump /dev/mapper/npo2linear -q Oct 7 22:35:21 storageqe-109 journal: integritysetup dump /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate Oct 7 22:35:31 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-file '/tmp/testfileNjZ' --integrity-key-size '32' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileWnt' --journal-integrity-key-size '32' open /dev/mapper/npo2linear wMApZefzbH -q --integrity-recalculate integritysetup close wMApZefzbH -q Oct 7 22:35:41 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 7 22:35:51 storageqe-109 journal: integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear wMApZefzbH -q Oct 7 22:36:04 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear wMApZefzbH -q integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/wMApZefzbH -q Oct 7 22:36:14 storageqe-109 journal: integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/wMApZefzbH -q integritysetup close wMApZefzbH -q Oct 7 22:36:24 storageqe-109 journal: integritysetup close wMApZefzbH -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileNjZ' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileNjZ' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileNjZ' format /dev/mapper/npo2linear -q Oct 7 22:36:34 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileNjZ' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileNjZ' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileNjZ' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileNjZ' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileNjZ' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileNjZ' open /dev/mapper/npo2linear wMApZefzbH -q Oct 7 22:36:52 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfileNjZ' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfileNjZ' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfileNjZ' open /dev/mapper/npo2linear wMApZefzbH -q integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/wMApZefzbH -q Oct 7 22:37:02 storageqe-109 journal: integritysetup --integrity 'crc32' --device-size '8MiB' resize /dev/mapper/wMApZefzbH -q integritysetup close wMApZefzbH -q Oct 7 22:37:12 storageqe-109 journal: integritysetup close wMApZefzbH -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_feature_test[npo2_linear] #### INFO: #### will start test_integrity_resize[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:37:27 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:37:27 storageqe-109 INFO: #### END test_feature_test[npo2_linear] #### Oct 7 22:37:27 storageqe-109 INFO: #### will start test_integrity_resize[npo2_linear] ##### Oct 7 22:37:27 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 7 22:37:32 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 Oct 7 22:37:32 storageqe-109 journal: integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:37:45 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:37:55 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:38:05 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup close HKFPoZTAVh -q Oct 7 22:38:15 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 7 22:38:25 storageqe-109 journal: integritysetup --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:38:38 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:38:48 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:38:58 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup close HKFPoZTAVh -q Oct 7 22:39:08 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 7 22:39:18 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:39:30 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:39:40 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:39:50 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup close HKFPoZTAVh -q Oct 7 22:40:00 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q Oct 7 22:40:10 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:40:22 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:40:32 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:40:42 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup close HKFPoZTAVh -q Oct 7 22:40:52 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q Oct 7 22:41:02 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:41:20 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:41:30 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:41:40 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup close HKFPoZTAVh -q Oct 7 22:41:50 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q Oct 7 22:42:00 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:42:18 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:42:28 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:42:38 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup close HKFPoZTAVh -q Oct 7 22:42:48 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q Oct 7 22:42:58 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:43:15 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:43:25 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:43:35 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup close HKFPoZTAVh -q Oct 7 22:43:45 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q Oct 7 22:43:55 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' format /dev/mapper/npo2linear -q integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:44:12 storageqe-109 journal: integritysetup --data-device '/dev/loop1' --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --journal-integrity 'hmac-sha256' --journal-integrity-key-file '/tmp/testfiledea' --journal-integrity-key-size '128' --journal-crypt 'ctr-aes' --journal-crypt-key-size '16' --journal-crypt-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:44:22 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:44:32 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup close HKFPoZTAVh -q Oct 7 22:44:42 storageqe-109 journal: integritysetup close HKFPoZTAVh -q INFO: the add_device_inline device dm-3 support npo2 integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q Oct 7 22:44:52 storageqe-109 INFO: the add_device_inline device dm-3 support npo2 Oct 7 22:44:52 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:45:05 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:45:15 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q Oct 7 22:45:25 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q integritysetup close HKFPoZTAVh -q Oct 7 22:45:35 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q Oct 7 22:45:45 storageqe-109 journal: integritysetup --integrity 'crc32' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:45:58 storageqe-109 journal: integritysetup --integrity 'crc32' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:46:08 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:46:18 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup close HKFPoZTAVh -q Oct 7 22:46:28 storageqe-109 journal: integritysetup close HKFPoZTAVh -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q Oct 7 22:46:38 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' --sector-size '4096' format /dev/mapper/npo2linear --integrity-inline -q integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q Oct 7 22:46:53 storageqe-109 journal: integritysetup --integrity 'hmac-sha256' --integrity-key-size '128' --integrity-key-file '/tmp/testfiledea' open /dev/mapper/npo2linear HKFPoZTAVh -q integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:47:03 storageqe-109 journal: integritysetup --device-size '1MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe Oct 7 22:47:13 storageqe-109 journal: integritysetup --device-size '10MiB' resize /dev/mapper/HKFPoZTAVh -q --wipe integritysetup close HKFPoZTAVh -q Oct 7 22:47:23 storageqe-109 journal: integritysetup close HKFPoZTAVh -q INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_integrity_resize[npo2_linear] #### Oct 7 22:47:38 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:47:38 storageqe-109 INFO: #### END test_integrity_resize[npo2_linear] #### Oct 7 22:47:39 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 7 22:47:40 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 22:47:41 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 7 22:47:41 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 7 22:47:41 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 7 22:47:51 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_check_fec[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:47:57 storageqe-109 INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:47:57 storageqe-109 INFO: #### will start test_check_fec[npo2_linear] ##### Oct 7 22:47:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 22:48:02 storageqe-109 kernel: loop0: detected capacity change from 0 to 12582912 Oct 7 22:48:02 storageqe-109 kernel: sde: Oct 7 22:48:02 storageqe-109 kernel: sde: sde1 Oct 7 22:48:02 storageqe-109 kernel: loop1: detected capacity change from 0 to 12582912 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 22:48:02 storageqe-109 kernel: sdd: Oct 7 22:48:02 storageqe-109 kernel: sdd: sdd1 Oct 7 22:48:02 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 22:48:11 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 77fe0c0c3da28d70ddbc7c7d85086c031e1abdaf5f82175af096d1fff7be1890 Oct 7 22:48:12 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 77fe0c0c3da28d70ddbc7c7d85086c031e1abdaf5f82175af096d1fff7be1890 Oct 7 22:48:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:48:22 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 77fe0c0c3da28d70ddbc7c7d85086c031e1abdaf5f82175af096d1fff7be1890 Oct 7 22:48:33 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 77fe0c0c3da28d70ddbc7c7d85086c031e1abdaf5f82175af096d1fff7be1890 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 22:48:43 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 22:48:53 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 22:48:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:49:03 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 22:49:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 22:49:23 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 22:49:34 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 22:49:34 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:49:44 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 22:49:54 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 22:50:04 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 22:50:14 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 22:50:14 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:50:24 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 22:50:34 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 22:50:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 22:50:54 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 22:50:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:51:04 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 22:51:14 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 7 22:51:29 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 ebba7a1f807c3299576a8fa39c921cc030e93ff63e7fc7ae378b9f0b7873d816 Oct 7 22:52:35 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 ebba7a1f807c3299576a8fa39c921cc030e93ff63e7fc7ae378b9f0b7873d816 Oct 7 22:52:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:53:02 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 ebba7a1f807c3299576a8fa39c921cc030e93ff63e7fc7ae378b9f0b7873d816 Oct 7 22:53:12 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 ebba7a1f807c3299576a8fa39c921cc030e93ff63e7fc7ae378b9f0b7873d816 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 22:53:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 e8d4df88d2197c3fe50f05dd6f72c5e960f6bda1a84f24150fdcccc70df7e33b Oct 7 22:54:40 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 e8d4df88d2197c3fe50f05dd6f72c5e960f6bda1a84f24150fdcccc70df7e33b Oct 7 22:54:40 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:55:07 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 e8d4df88d2197c3fe50f05dd6f72c5e960f6bda1a84f24150fdcccc70df7e33b Oct 7 22:55:17 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 e8d4df88d2197c3fe50f05dd6f72c5e960f6bda1a84f24150fdcccc70df7e33b veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 22:55:36 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 8cbdf70e259147957fd9fcad307ca44852fcdd02463c233f29a7760fa00e6130 Oct 7 22:56:43 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 8cbdf70e259147957fd9fcad307ca44852fcdd02463c233f29a7760fa00e6130 Oct 7 22:56:43 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:57:10 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 8cbdf70e259147957fd9fcad307ca44852fcdd02463c233f29a7760fa00e6130 Oct 7 22:57:20 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 8cbdf70e259147957fd9fcad307ca44852fcdd02463c233f29a7760fa00e6130 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 22:57:39 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 f30057e92f0b0083fb2a382b8dbbb39c67815ac6c08e91dbdec2804da9039ae6 Oct 7 22:58:47 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 f30057e92f0b0083fb2a382b8dbbb39c67815ac6c08e91dbdec2804da9039ae6 Oct 7 22:58:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LqYTuJdnxm Oct 7 22:59:14 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 f30057e92f0b0083fb2a382b8dbbb39c67815ac6c08e91dbdec2804da9039ae6 Oct 7 22:59:24 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 f30057e92f0b0083fb2a382b8dbbb39c67815ac6c08e91dbdec2804da9039ae6 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 22:59:39 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 14fa1080d598e6d2d19f471431529b27682b71fc25789d1acb4c58539b4547dd Oct 7 22:59:49 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 14fa1080d598e6d2d19f471431529b27682b71fc25789d1acb4c58539b4547dd Oct 7 22:59:49 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 22:59:49 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 22:59:59 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 22:59:59 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 14fa1080d598e6d2d19f471431529b27682b71fc25789d1acb4c58539b4547dd Oct 7 23:00:09 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 14fa1080d598e6d2d19f471431529b27682b71fc25789d1acb4c58539b4547dd veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 23:00:20 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:00:30 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:00:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:00:30 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:00:40 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:00:40 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:00:50 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:01:00 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:01:11 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:01:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:01:11 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:01:21 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:01:21 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:01:31 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 23:01:41 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:01:51 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:01:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:01:51 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:02:01 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:02:01 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:02:11 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:02:21 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:02:31 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:02:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:02:32 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:02:42 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:02:42 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:02:52 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 7 23:03:06 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 da4065d79675ffe5a32dcc30879aef831e7a1e40a2b03d425c47ea239614f66b Oct 7 23:04:12 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 da4065d79675ffe5a32dcc30879aef831e7a1e40a2b03d425c47ea239614f66b Oct 7 23:04:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:04:12 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:04:22 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:04:38 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 da4065d79675ffe5a32dcc30879aef831e7a1e40a2b03d425c47ea239614f66b Oct 7 23:04:49 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 da4065d79675ffe5a32dcc30879aef831e7a1e40a2b03d425c47ea239614f66b veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:05:38 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 1a7ee90b53e14e70cfd007ea02e8e919bced9776e1343dba3c1b39c7d217fe2c Oct 7 23:06:54 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 1a7ee90b53e14e70cfd007ea02e8e919bced9776e1343dba3c1b39c7d217fe2c Oct 7 23:06:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:06:54 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:07:05 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:07:21 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 1a7ee90b53e14e70cfd007ea02e8e919bced9776e1343dba3c1b39c7d217fe2c Oct 7 23:07:31 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 1a7ee90b53e14e70cfd007ea02e8e919bced9776e1343dba3c1b39c7d217fe2c veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:08:21 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 c6f913243976a4b7a34e67cd484c5b4d5d75f409e327dfa36054d0854329202c Oct 7 23:09:36 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 c6f913243976a4b7a34e67cd484c5b4d5d75f409e327dfa36054d0854329202c Oct 7 23:09:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:09:36 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:09:46 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:10:03 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 c6f913243976a4b7a34e67cd484c5b4d5d75f409e327dfa36054d0854329202c Oct 7 23:10:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 c6f913243976a4b7a34e67cd484c5b4d5d75f409e327dfa36054d0854329202c veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:11:02 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 2d0d103424b860cbdf5d95ade038a26fae971447a7f3ad47d3a5faec7f632c53 Oct 7 23:12:10 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 2d0d103424b860cbdf5d95ade038a26fae971447a7f3ad47d3a5faec7f632c53 Oct 7 23:12:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:12:10 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:12:20 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:12:37 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 2d0d103424b860cbdf5d95ade038a26fae971447a7f3ad47d3a5faec7f632c53 Oct 7 23:12:47 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 2d0d103424b860cbdf5d95ade038a26fae971447a7f3ad47d3a5faec7f632c53 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:13:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 3e5a6b16c410dbd354cff6a04e7fa1b5d6943ed6a7328f2e6d9f52c36aef5399 Oct 7 23:13:42 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 3e5a6b16c410dbd354cff6a04e7fa1b5d6943ed6a7328f2e6d9f52c36aef5399 Oct 7 23:13:42 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:13:42 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:13:52 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:13:52 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 3e5a6b16c410dbd354cff6a04e7fa1b5d6943ed6a7328f2e6d9f52c36aef5399 Oct 7 23:14:02 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 3e5a6b16c410dbd354cff6a04e7fa1b5d6943ed6a7328f2e6d9f52c36aef5399 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 23:14:12 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:14:22 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:14:22 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:14:22 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:14:32 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:14:32 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:14:43 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:14:53 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:15:03 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:15:03 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:15:03 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:15:13 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:15:13 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:15:23 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 23:15:33 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:15:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:15:44 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:15:44 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:15:54 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:15:54 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:16:04 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:16:14 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:16:24 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:16:24 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:16:24 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:16:34 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:16:34 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:16:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 7 23:16:59 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 a33c48a5681fcaa614b7ae2a81e46b40baf3cf1eeb557d09b2023c86d698d9c1 Oct 7 23:18:04 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 a33c48a5681fcaa614b7ae2a81e46b40baf3cf1eeb557d09b2023c86d698d9c1 Oct 7 23:18:04 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:18:05 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:18:15 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:18:31 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 a33c48a5681fcaa614b7ae2a81e46b40baf3cf1eeb557d09b2023c86d698d9c1 Oct 7 23:18:41 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 a33c48a5681fcaa614b7ae2a81e46b40baf3cf1eeb557d09b2023c86d698d9c1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:19:30 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 45b3e2a46cafd0a7078725877957f881f1b5ba99a63e3547a5c36f945e00e983 Oct 7 23:20:36 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 45b3e2a46cafd0a7078725877957f881f1b5ba99a63e3547a5c36f945e00e983 Oct 7 23:20:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:20:36 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:20:46 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:21:03 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 45b3e2a46cafd0a7078725877957f881f1b5ba99a63e3547a5c36f945e00e983 Oct 7 23:21:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 45b3e2a46cafd0a7078725877957f881f1b5ba99a63e3547a5c36f945e00e983 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:22:01 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 e6114373139c7cf12a8c00fc62d41e16efce7d476c97d0add4cad2bb36181168 Oct 7 23:23:07 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 e6114373139c7cf12a8c00fc62d41e16efce7d476c97d0add4cad2bb36181168 Oct 7 23:23:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:23:07 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:23:17 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:23:34 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 e6114373139c7cf12a8c00fc62d41e16efce7d476c97d0add4cad2bb36181168 Oct 7 23:23:44 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 e6114373139c7cf12a8c00fc62d41e16efce7d476c97d0add4cad2bb36181168 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:24:33 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 b475ce7669cb6c0f1aeaa7937cd3801fd698c5ac072a6ac3781f1f819a859379 Oct 7 23:25:39 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 b475ce7669cb6c0f1aeaa7937cd3801fd698c5ac072a6ac3781f1f819a859379 Oct 7 23:25:39 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:25:39 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:25:49 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:26:05 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 b475ce7669cb6c0f1aeaa7937cd3801fd698c5ac072a6ac3781f1f819a859379 Oct 7 23:26:16 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 b475ce7669cb6c0f1aeaa7937cd3801fd698c5ac072a6ac3781f1f819a859379 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:27:00 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:27:06 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 7 23:27:06 storageqe-109 dnf[2474353]: Updating Subscription Management repositories. Oct 7 23:27:06 storageqe-109 dnf[2474353]: Unable to read consumer identity Oct 7 23:27:06 storageqe-109 dnf[2474353]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-AppStream 587 kB/s | 2.8 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-AppStream-debuginfo 539 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-BaseOS 822 kB/s | 2.7 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-BaseOS-debuginfo 573 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-CRB 784 kB/s | 2.7 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-CRB-debuginfo 677 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-HighAvailability 897 kB/s | 2.8 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-HighAvailability-debuginfo 663 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-NFV 1.0 MB/s | 2.7 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-NFV-debuginfo 583 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-RT 774 kB/s | 2.7 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-RT-debuginfo 604 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-SAP 836 kB/s | 2.7 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-SAP-debuginfo 554 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-SAPHANA 715 kB/s | 2.7 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: beaker-SAPHANA-debuginfo 631 kB/s | 1.5 kB 00:00 Oct 7 23:27:07 storageqe-109 dnf[2474353]: Beaker Client - RedHatEnterpriseLinux10 2.3 kB/s | 1.3 kB 00:00 Oct 7 23:27:09 storageqe-109 dnf[2474353]: beaker-harness 752 B/s | 1.3 kB 00:01 Oct 7 23:27:09 storageqe-109 dnf[2474353]: Google Cloud CLI 4.1 kB/s | 1.4 kB 00:00 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 3dfb9b705e218bd023afc1a9238aadd4eba342645b994e45fc65f770dc62e0f2 Oct 7 23:27:10 storageqe-109 dnf[2474353]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 7 23:27:10 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear 3dfb9b705e218bd023afc1a9238aadd4eba342645b994e45fc65f770dc62e0f2 Oct 7 23:27:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:27:10 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:27:11 storageqe-109 dnf[2474353]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 7 23:27:12 storageqe-109 dnf[2474353]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 7 23:27:12 storageqe-109 dnf[2474353]: Metadata cache created. Oct 7 23:27:12 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 7 23:27:12 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 7 23:27:12 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 339ms CPU time, 109.9M memory peak. veritysetup close LqYTuJdnxm Oct 7 23:27:21 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:27:21 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 3dfb9b705e218bd023afc1a9238aadd4eba342645b994e45fc65f770dc62e0f2 Oct 7 23:27:31 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '30' --hash-offset '163840' --fec-offset '409600' --fec-device '/dev/mapper/npo2linear' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 3dfb9b705e218bd023afc1a9238aadd4eba342645b994e45fc65f770dc62e0f2 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 23:27:41 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:27:51 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:27:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:27:51 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:28:01 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:28:01 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:28:11 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:28:22 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:28:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:28:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:28:32 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:28:42 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:28:42 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af Oct 7 23:28:52 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '500' --hash-offset '2457600' --fec-offset '4915200' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ba8d7d63f132b3f2214c7be40e4105ac2a69f8946452b330ac3caad30d8650af veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear Oct 7 23:29:02 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:29:12 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:29:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:29:12 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:29:22 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:29:22 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:29:32 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:29:43 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:29:53 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:29:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:29:53 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:30:03 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:30:03 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 Oct 7 23:30:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --data-blocks '64' --hash-offset '4194304' --fec-offset '8388608' --fec-device '/dev/mapper/npo2linear' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e0c7527daef3f8bd5a4147e9a3ad65f40fc78454ab73f019daf3c00d628b58b3 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 Oct 7 23:30:27 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' format /dev/mapper/npo2linear --no-superblock /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 c6ee20342efc4ef79df93c96cfe657e48486a0fda0185349ffa778846c2dd493 Oct 7 23:31:33 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' create LqYTuJdnxm /dev/mapper/npo2linear --no-superblock /dev/sde1 c6ee20342efc4ef79df93c96cfe657e48486a0fda0185349ffa778846c2dd493 Oct 7 23:31:33 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:31:33 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:31:43 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:32:00 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 c6ee20342efc4ef79df93c96cfe657e48486a0fda0185349ffa778846c2dd493 Oct 7 23:32:10 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' verify /dev/mapper/npo2linear --no-superblock /dev/sde1 c6ee20342efc4ef79df93c96cfe657e48486a0fda0185349ffa778846c2dd493 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:32:59 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 5c87fcef7a4bc9576a59fff4801cfd8cf2433ecbeaee193d43538c059b7755da Oct 7 23:34:05 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 5c87fcef7a4bc9576a59fff4801cfd8cf2433ecbeaee193d43538c059b7755da Oct 7 23:34:05 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:34:05 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:34:15 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:34:31 storageqe-109 journal: veritysetup close LqYTuJdnxm Oct 7 23:34:37 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 7 23:34:37 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 7 23:34:37 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 5c87fcef7a4bc9576a59fff4801cfd8cf2433ecbeaee193d43538c059b7755da Oct 7 23:34:41 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 5c87fcef7a4bc9576a59fff4801cfd8cf2433ecbeaee193d43538c059b7755da veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:35:30 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 78c82daf280750db01d1e073eea86e16db6aa09233bcaa9e26d938a82ff85549 Oct 7 23:36:36 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 78c82daf280750db01d1e073eea86e16db6aa09233bcaa9e26d938a82ff85549 Oct 7 23:36:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:36:36 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:36:46 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:37:03 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 78c82daf280750db01d1e073eea86e16db6aa09233bcaa9e26d938a82ff85549 Oct 7 23:37:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 78c82daf280750db01d1e073eea86e16db6aa09233bcaa9e26d938a82ff85549 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:38:02 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' format /dev/mapper/npo2linear /dev/sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 8a69937cd964ce5748068ca81ac0479a18a649fededf242d9542b32774b0087b Oct 7 23:39:08 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' create LqYTuJdnxm /dev/mapper/npo2linear /dev/sde1 8a69937cd964ce5748068ca81ac0479a18a649fededf242d9542b32774b0087b Oct 7 23:39:08 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:39:08 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors Oct 7 23:39:18 storageqe-109 kernel: device-mapper: verity-fec: 253:3: FEC 0: corrected 1 errors veritysetup close LqYTuJdnxm Oct 7 23:39:35 storageqe-109 journal: veritysetup close LqYTuJdnxm veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 8a69937cd964ce5748068ca81ac0479a18a649fededf242d9542b32774b0087b Oct 7 23:39:45 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --fec-device '/dev/sdd1' verify /dev/mapper/npo2linear /dev/sde1 8a69937cd964ce5748068ca81ac0479a18a649fededf242d9542b32774b0087b Oct 7 23:40:29 storageqe-109 kernel: sde: Oct 7 23:40:29 storageqe-109 kernel: sdd: sdd1 Oct 7 23:40:29 storageqe-109 kernel: sdd: INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_check_fec[npo2_linear] #### INFO: #### will start test_offset[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:40:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:40:35 storageqe-109 INFO: #### END test_check_fec[npo2_linear] #### Oct 7 23:40:35 storageqe-109 INFO: #### will start test_offset[npo2_linear] ##### Oct 7 23:40:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### veritysetup --data-blocks '256' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:40:40 storageqe-109 journal: veritysetup --data-blocks '256' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '128' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:40:50 storageqe-109 journal: veritysetup --data-blocks '128' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '512' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:41:00 storageqe-109 journal: veritysetup --data-blocks '512' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '4096' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:41:10 storageqe-109 journal: veritysetup --data-blocks '4096' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --data-blocks '8152' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 7 23:41:20 storageqe-109 journal: veritysetup --data-blocks '8152' --hash-offset '2499997696' format /dev/mapper/npo2linear /dev/mapper/npo2linear INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_offset[npo2_linear] #### INFO: #### will start test_dm_verity_options[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:41:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:41:35 storageqe-109 INFO: #### END test_offset[npo2_linear] #### Oct 7 23:41:35 storageqe-109 INFO: #### will start test_dm_verity_options[npo2_linear] ##### Oct 7 23:41:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:41:40 storageqe-109 kernel: loop2: detected capacity change from 0 to 12582912 Oct 7 23:41:40 storageqe-109 kernel: sde: Oct 7 23:41:40 storageqe-109 kernel: sde: sde1 veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:41:40 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --ignore-corruption Oct 7 23:41:55 storageqe-109 journal: veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --ignore-corruption Oct 7 23:41:55 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BVvfoQEIPp Oct 7 23:42:08 storageqe-109 journal: veritysetup close BVvfoQEIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:42:18 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --restart-on-corruption Oct 7 23:42:34 storageqe-109 journal: veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --restart-on-corruption Oct 7 23:42:34 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BVvfoQEIPp Oct 7 23:42:47 storageqe-109 journal: veritysetup close BVvfoQEIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:42:57 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --ignore-zero-blocks Oct 7 23:43:12 storageqe-109 journal: veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --ignore-zero-blocks Oct 7 23:43:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BVvfoQEIPp Oct 7 23:43:25 storageqe-109 journal: veritysetup close BVvfoQEIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:43:35 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --ignore-corruption --ignore-zero-blocks Oct 7 23:43:50 storageqe-109 journal: veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --ignore-corruption --ignore-zero-blocks Oct 7 23:43:50 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BVvfoQEIPp Oct 7 23:44:03 storageqe-109 journal: veritysetup close BVvfoQEIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:44:13 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --check-at-most-once Oct 7 23:44:28 storageqe-109 journal: veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --check-at-most-once Oct 7 23:44:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BVvfoQEIPp Oct 7 23:44:41 storageqe-109 journal: veritysetup close BVvfoQEIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:44:51 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --panic-on-corruption Oct 7 23:45:07 storageqe-109 journal: veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --panic-on-corruption Oct 7 23:45:07 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BVvfoQEIPp Oct 7 23:45:20 storageqe-109 journal: veritysetup close BVvfoQEIPp veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:45:30 storageqe-109 journal: veritysetup --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --format '1' format /dev/mapper/npo2linear /dev/sde1 veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --use-tasklets Oct 7 23:45:45 storageqe-109 journal: veritysetup create BVvfoQEIPp /dev/mapper/npo2linear /dev/sde1 a6607760059a21ee8eb190a3dc951e89da7fe6125452063432e139935769b670 --use-tasklets Oct 7 23:45:45 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close BVvfoQEIPp Oct 7 23:45:58 storageqe-109 journal: veritysetup close BVvfoQEIPp Oct 7 23:46:08 storageqe-109 kernel: sde: INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_options[npo2_linear] #### INFO: #### will start test_dm_verity_check[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:46:13 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:46:13 storageqe-109 INFO: #### END test_dm_verity_options[npo2_linear] #### Oct 7 23:46:13 storageqe-109 INFO: #### will start test_dm_verity_check[npo2_linear] ##### Oct 7 23:46:13 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 7 23:46:18 storageqe-109 kernel: sde: Oct 7 23:46:18 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:46:23 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:46:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OCYNwFWvrq /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:46:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OCYNwFWvrq /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:46:56 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close OCYNwFWvrq Oct 7 23:47:14 storageqe-109 journal: veritysetup close OCYNwFWvrq veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:47:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JHZFAVSeWR /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:47:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JHZFAVSeWR /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:47:35 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:35 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close JHZFAVSeWR Oct 7 23:47:45 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:47:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:47:45 storageqe-109 journal: veritysetup close JHZFAVSeWR veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:47:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:48:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LhIGclBbRQ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:48:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LhIGclBbRQ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:48:33 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LhIGclBbRQ Oct 7 23:48:51 storageqe-109 journal: veritysetup close LhIGclBbRQ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:49:01 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LunEeRNiPm /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:49:18 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LunEeRNiPm /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:49:18 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:18 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close LunEeRNiPm Oct 7 23:49:28 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:49:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:49:28 storageqe-109 journal: veritysetup close LunEeRNiPm veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 7 23:49:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:49:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xVNawCZpDT /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:50:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xVNawCZpDT /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:50:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close xVNawCZpDT Oct 7 23:50:34 storageqe-109 journal: veritysetup close xVNawCZpDT veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:50:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vRdwzLKOaB /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:50:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vRdwzLKOaB /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:50:54 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:50:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:50:55 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close vRdwzLKOaB Oct 7 23:51:04 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:51:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:51:04 storageqe-109 journal: veritysetup close vRdwzLKOaB veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:51:19 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:51:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create tOIWHlkTKL /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:51:52 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create tOIWHlkTKL /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:51:52 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close tOIWHlkTKL Oct 7 23:52:10 storageqe-109 journal: veritysetup close tOIWHlkTKL veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:52:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UofPcXQCAW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:52:37 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UofPcXQCAW /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:52:37 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:37 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close UofPcXQCAW Oct 7 23:52:47 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:52:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:52:47 storageqe-109 journal: veritysetup close UofPcXQCAW veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:53:02 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:53:19 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xNSleUnaZb /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:53:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xNSleUnaZb /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:53:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close xNSleUnaZb Oct 7 23:53:54 storageqe-109 journal: veritysetup close xNSleUnaZb veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:54:04 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TvFYJRiwks /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:54:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TvFYJRiwks /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:54:14 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:14 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close TvFYJRiwks Oct 7 23:54:24 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:54:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:54:24 storageqe-109 journal: veritysetup close TvFYJRiwks veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:54:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:54:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QDVPCOTluy /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:55:12 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QDVPCOTluy /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:55:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close QDVPCOTluy Oct 7 23:55:31 storageqe-109 journal: veritysetup close QDVPCOTluy veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:55:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pKNjvPqbJD /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:55:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pKNjvPqbJD /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:55:58 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:55:58 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close pKNjvPqbJD Oct 7 23:56:08 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:56:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:56:08 storageqe-109 journal: veritysetup close pKNjvPqbJD veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 7 23:56:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:56:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OhSTDlIQRy /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:56:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OhSTDlIQRy /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:56:56 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close OhSTDlIQRy Oct 7 23:57:13 storageqe-109 journal: veritysetup close OhSTDlIQRy veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:57:23 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create muItUEOlGy /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:57:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create muItUEOlGy /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:57:34 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:34 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close muItUEOlGy Oct 7 23:57:44 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:57:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:57:44 storageqe-109 journal: veritysetup close muItUEOlGy veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:57:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:58:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TglPENHrqZ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:58:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TglPENHrqZ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:58:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close TglPENHrqZ Oct 7 23:58:50 storageqe-109 journal: veritysetup close TglPENHrqZ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:59:00 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BlErMhsWak /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:59:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BlErMhsWak /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 7 23:59:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:17 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close BlErMhsWak Oct 7 23:59:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 7 23:59:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 7 23:59:27 storageqe-109 journal: veritysetup close BlErMhsWak Oct 7 23:59:37 storageqe-109 kernel: sde: Oct 7 23:59:37 storageqe-109 kernel: sde: Oct 7 23:59:37 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 7 23:59:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 7 23:59:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:00:08 storageqe-109 systemd[1]: Starting unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound... Oct 8 00:00:08 storageqe-109 systemd[1]: unbound-anchor.service: Deactivated successfully. Oct 8 00:00:08 storageqe-109 systemd[1]: Finished unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound. veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VwWMjnFIDm /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:00:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VwWMjnFIDm /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:00:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close VwWMjnFIDm Oct 8 00:00:34 storageqe-109 journal: veritysetup close VwWMjnFIDm veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:00:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zKcDjtfkho /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:00:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zKcDjtfkho /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:00:54 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:00:54 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zKcDjtfkho Oct 8 00:01:04 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:01:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:01:04 storageqe-109 journal: veritysetup close zKcDjtfkho veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:01:19 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:01:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lRscWiFCPv /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:01:52 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lRscWiFCPv /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:01:52 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close lRscWiFCPv Oct 8 00:02:10 storageqe-109 journal: veritysetup close lRscWiFCPv veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:02:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PGfTxXCBvV /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:02:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PGfTxXCBvV /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:02:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:02:36 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:02:36 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:36 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:37 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close PGfTxXCBvV Oct 8 00:02:47 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:02:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:02:47 storageqe-109 journal: veritysetup close PGfTxXCBvV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:03:01 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:03:08 storageqe-109 systemd[1]: Starting logrotate.service - Rotate log files... Oct 8 00:03:08 storageqe-109 systemd[1]: logrotate.service: Deactivated successfully. Oct 8 00:03:08 storageqe-109 systemd[1]: Finished logrotate.service - Rotate log files. veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:03:18 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QhIOEiJgqL /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:03:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QhIOEiJgqL /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:03:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close QhIOEiJgqL Oct 8 00:03:53 storageqe-109 journal: veritysetup close QhIOEiJgqL veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:04:03 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jtePcUSnyv /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:04:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jtePcUSnyv /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:04:13 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:13 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close jtePcUSnyv Oct 8 00:04:23 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:04:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:04:23 storageqe-109 journal: veritysetup close jtePcUSnyv veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:04:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:04:55 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HkebghMNvO /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:05:12 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HkebghMNvO /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:05:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close HkebghMNvO Oct 8 00:05:30 storageqe-109 journal: veritysetup close HkebghMNvO veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:05:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SAWnUOrXGu /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:05:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SAWnUOrXGu /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:05:57 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close SAWnUOrXGu Oct 8 00:06:07 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:06:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:06:07 storageqe-109 journal: veritysetup close SAWnUOrXGu veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:06:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:06:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oIqTLtxrMO /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:06:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oIqTLtxrMO /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:06:56 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close oIqTLtxrMO Oct 8 00:07:14 storageqe-109 journal: veritysetup close oIqTLtxrMO veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:07:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nBAqLphcOu /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:07:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nBAqLphcOu /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:07:34 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:34 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close nBAqLphcOu Oct 8 00:07:44 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:07:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:07:44 storageqe-109 journal: veritysetup close nBAqLphcOu veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:07:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:08:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GRgNXTrWYL /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:08:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GRgNXTrWYL /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:08:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close GRgNXTrWYL Oct 8 00:08:50 storageqe-109 journal: veritysetup close GRgNXTrWYL veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:09:00 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CJXhBpQaoG /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:09:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CJXhBpQaoG /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:09:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:18 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close CJXhBpQaoG Oct 8 00:09:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:09:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:09:27 storageqe-109 journal: veritysetup close CJXhBpQaoG veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:09:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:09:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nSrduJvoWq /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:10:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nSrduJvoWq /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:10:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close nSrduJvoWq Oct 8 00:10:34 storageqe-109 journal: veritysetup close nSrduJvoWq veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:10:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create EXgkRjehSt /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:10:54 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create EXgkRjehSt /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:10:54 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:10:55 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close EXgkRjehSt Oct 8 00:11:04 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:11:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:11:04 storageqe-109 journal: veritysetup close EXgkRjehSt veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:11:19 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:11:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sSzWfINkYR /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:11:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sSzWfINkYR /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:11:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close sSzWfINkYR Oct 8 00:12:11 storageqe-109 journal: veritysetup close sSzWfINkYR veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:12:21 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CVlhTwzpIL /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:12:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CVlhTwzpIL /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:12:38 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:12:38 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:12:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:39 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close CVlhTwzpIL Oct 8 00:12:49 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:12:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:12:49 storageqe-109 journal: veritysetup close CVlhTwzpIL Oct 8 00:12:59 storageqe-109 kernel: sde: Oct 8 00:12:59 storageqe-109 kernel: sde: Oct 8 00:12:59 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:13:04 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:13:21 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wqztcYGuXR /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:13:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wqztcYGuXR /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:13:38 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close wqztcYGuXR Oct 8 00:13:56 storageqe-109 journal: veritysetup close wqztcYGuXR veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:14:06 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create KwcCdrxRDj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:14:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create KwcCdrxRDj /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:14:16 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:16 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close KwcCdrxRDj Oct 8 00:14:26 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:14:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:14:26 storageqe-109 journal: veritysetup close KwcCdrxRDj veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:14:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:14:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create khpJNilCzM /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:15:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create khpJNilCzM /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:15:14 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close khpJNilCzM Oct 8 00:15:32 storageqe-109 journal: veritysetup close khpJNilCzM veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:15:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create eMQAgxlkvq /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:15:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create eMQAgxlkvq /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:15:59 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:16:00 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close eMQAgxlkvq Oct 8 00:16:09 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:16:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:16:09 storageqe-109 journal: veritysetup close eMQAgxlkvq veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:16:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:16:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QrAGvIoBRO /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:16:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QrAGvIoBRO /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:16:58 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close QrAGvIoBRO Oct 8 00:17:15 storageqe-109 journal: veritysetup close QrAGvIoBRO veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:17:26 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sKyzjtIurV /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:17:36 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create sKyzjtIurV /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:17:36 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:36 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close sKyzjtIurV Oct 8 00:17:46 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:17:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:17:46 storageqe-109 journal: veritysetup close sKyzjtIurV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:18:00 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:18:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dvoOgFncuf /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:18:35 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dvoOgFncuf /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:18:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close dvoOgFncuf Oct 8 00:18:53 storageqe-109 journal: veritysetup close dvoOgFncuf veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:19:03 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XrHvTPJfzk /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:19:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XrHvTPJfzk /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:19:20 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:20 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close XrHvTPJfzk Oct 8 00:19:30 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:19:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:19:30 storageqe-109 journal: veritysetup close XrHvTPJfzk veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:19:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:20:02 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HzsMaLDdvq /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:20:19 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HzsMaLDdvq /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:20:19 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close HzsMaLDdvq Oct 8 00:20:37 storageqe-109 journal: veritysetup close HzsMaLDdvq veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:20:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MfeCoIAQRZ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:20:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MfeCoIAQRZ /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:20:57 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:20:57 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close MfeCoIAQRZ Oct 8 00:21:07 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:21:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:21:07 storageqe-109 journal: veritysetup close MfeCoIAQRZ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:21:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:21:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ukxJAYvtCT /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:21:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ukxJAYvtCT /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:21:56 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ukxJAYvtCT Oct 8 00:22:14 storageqe-109 journal: veritysetup close ukxJAYvtCT veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:22:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HLCQkMbyta /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:22:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HLCQkMbyta /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:22:41 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:41 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close HLCQkMbyta Oct 8 00:22:51 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:22:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:22:51 storageqe-109 journal: veritysetup close HLCQkMbyta veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:23:05 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:23:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VUvWJBPOKb /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:23:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VUvWJBPOKb /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:23:39 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close VUvWJBPOKb Oct 8 00:23:57 storageqe-109 journal: veritysetup close VUvWJBPOKb veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:24:07 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZYWamqNRrA /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:24:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZYWamqNRrA /dev/mapper/npo2linear /dev/sde1 --no-superblock ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:24:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:17 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ZYWamqNRrA Oct 8 00:24:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:24:27 storageqe-109 journal: veritysetup close ZYWamqNRrA veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:24:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:24:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create eZfbtIGxSH /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:25:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create eZfbtIGxSH /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:25:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close eZfbtIGxSH Oct 8 00:25:34 storageqe-109 journal: veritysetup close eZfbtIGxSH veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:25:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mLgFrfuVTw /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:26:01 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mLgFrfuVTw /dev/mapper/npo2linear /dev/sde1 ff25d4d571a24762a847ea315eded924a0dbd3f9b81548cd2865153365288a58 Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:26:01 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:01 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close mLgFrfuVTw Oct 8 00:26:11 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:26:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:26:11 storageqe-109 journal: veritysetup close mLgFrfuVTw Oct 8 00:26:21 storageqe-109 kernel: sde: Oct 8 00:26:21 storageqe-109 kernel: sde: Oct 8 00:26:21 storageqe-109 kernel: sde: sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:26:26 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:26:43 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create gGivCjXKmN /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:27:00 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create gGivCjXKmN /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:27:00 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close gGivCjXKmN Oct 8 00:27:18 storageqe-109 journal: veritysetup close gGivCjXKmN veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:27:28 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create znyZDtfUaR /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:27:38 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create znyZDtfUaR /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:27:38 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:38 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close znyZDtfUaR Oct 8 00:27:48 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:27:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:27:48 storageqe-109 journal: veritysetup close znyZDtfUaR veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:28:03 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:28:20 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UivOLbnYzV /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:28:36 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UivOLbnYzV /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:28:36 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close UivOLbnYzV Oct 8 00:28:54 storageqe-109 journal: veritysetup close UivOLbnYzV veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:29:04 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TkfvXOmtxn /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:29:21 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TkfvXOmtxn /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:29:21 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:21 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close TkfvXOmtxn Oct 8 00:29:31 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:29:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:29:31 storageqe-109 journal: veritysetup close TkfvXOmtxn veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:29:46 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:30:02 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LhHGNFIzpV /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:30:19 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LhHGNFIzpV /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:30:19 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close LhHGNFIzpV Oct 8 00:30:38 storageqe-109 journal: veritysetup close LhHGNFIzpV veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:30:48 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create thZPxwmLMV /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:30:58 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create thZPxwmLMV /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:30:58 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:30:58 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close thZPxwmLMV Oct 8 00:31:08 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:31:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:31:08 storageqe-109 journal: veritysetup close thZPxwmLMV veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:31:22 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:31:39 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xyIRblVWBU /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:31:56 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create xyIRblVWBU /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:31:56 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close xyIRblVWBU Oct 8 00:32:14 storageqe-109 journal: veritysetup close xyIRblVWBU veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:32:24 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qoFyKpmYvx /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:32:41 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qoFyKpmYvx /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:32:41 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:42 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close qoFyKpmYvx Oct 8 00:32:51 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:32:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:32:51 storageqe-109 journal: veritysetup close qoFyKpmYvx veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:33:06 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:33:23 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:33:30 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 00:33:30 storageqe-109 dnf[2482821]: Updating Subscription Management repositories. Oct 8 00:33:30 storageqe-109 dnf[2482821]: Unable to read consumer identity Oct 8 00:33:30 storageqe-109 dnf[2482821]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 00:33:30 storageqe-109 dnf[2482821]: Metadata cache refreshed recently. Oct 8 00:33:30 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 00:33:30 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dhszMTpRkQ /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:33:39 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dhszMTpRkQ /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:33:40 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close dhszMTpRkQ Oct 8 00:33:57 storageqe-109 journal: veritysetup close dhszMTpRkQ veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:34:08 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RbSVmAdTft /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:34:18 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RbSVmAdTft /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:34:18 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:18 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close RbSVmAdTft Oct 8 00:34:28 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:34:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:34:28 storageqe-109 journal: veritysetup close RbSVmAdTft veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:34:42 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:34:59 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:35:10 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 00:35:10 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 00:35:10 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZnQoOvsEML /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:35:16 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZnQoOvsEML /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:35:16 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close ZnQoOvsEML Oct 8 00:35:34 storageqe-109 journal: veritysetup close ZnQoOvsEML veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:35:44 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QwmNxVieoR /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:36:00 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QwmNxVieoR /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:36:00 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:00 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close QwmNxVieoR Oct 8 00:36:10 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:36:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:36:10 storageqe-109 journal: veritysetup close QwmNxVieoR veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:36:25 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:36:42 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ikNXwPjOzI /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:36:58 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ikNXwPjOzI /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:36:58 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close ikNXwPjOzI Oct 8 00:37:16 storageqe-109 journal: veritysetup close ikNXwPjOzI veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:37:26 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mlTZWILFRq /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:37:36 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mlTZWILFRq /dev/mapper/npo2linear /dev/sde1 --no-superblock eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:37:36 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:37 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close mlTZWILFRq Oct 8 00:37:46 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:37:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:37:46 storageqe-109 journal: veritysetup close mlTZWILFRq veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:38:01 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:38:18 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZUpWKJmOQF /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:38:35 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZUpWKJmOQF /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:38:35 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close ZUpWKJmOQF Oct 8 00:38:53 storageqe-109 journal: veritysetup close ZUpWKJmOQF veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:39:03 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oPDjwCnJXN /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:39:20 storageqe-109 journal: veritysetup --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oPDjwCnJXN /dev/mapper/npo2linear /dev/sde1 eadd50b1c3f0cbb541b5e1cdf025dd69e1e8defd382a9ea4755c44e735b0ec08 Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 00:39:20 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:20 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close oPDjwCnJXN Oct 8 00:39:30 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:39:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:39:30 storageqe-109 journal: veritysetup close oPDjwCnJXN Oct 8 00:39:40 storageqe-109 kernel: sde: Oct 8 00:39:40 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:39:45 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:40:01 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create miKztGFPaW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:40:18 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create miKztGFPaW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:40:18 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close miKztGFPaW Oct 8 00:40:35 storageqe-109 journal: veritysetup close miKztGFPaW veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:40:45 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create UpJSOwQLkn /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:40:55 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create UpJSOwQLkn /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:40:55 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:40:56 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close UpJSOwQLkn Oct 8 00:41:05 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:41:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:41:05 storageqe-109 journal: veritysetup close UpJSOwQLkn veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:41:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:41:37 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create cpAQuSqzPZ /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:41:53 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create cpAQuSqzPZ /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:41:53 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close cpAQuSqzPZ Oct 8 00:42:11 storageqe-109 journal: veritysetup close cpAQuSqzPZ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:42:21 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create UNnPZmgSbd /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:42:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create UNnPZmgSbd /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:42:38 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:38 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close UNnPZmgSbd Oct 8 00:42:48 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:42:48 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:42:48 storageqe-109 journal: veritysetup close UNnPZmgSbd veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:43:03 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:43:20 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create JgmvpwszXV /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:43:37 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create JgmvpwszXV /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:43:37 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close JgmvpwszXV Oct 8 00:43:55 storageqe-109 journal: veritysetup close JgmvpwszXV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:44:05 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create PcRhqkdZLy /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:44:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create PcRhqkdZLy /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:44:15 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:15 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close PcRhqkdZLy Oct 8 00:44:25 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:44:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:44:25 storageqe-109 journal: veritysetup close PcRhqkdZLy veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:44:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:44:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dTVIWgshlU /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:45:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dTVIWgshlU /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:45:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close dTVIWgshlU Oct 8 00:45:30 storageqe-109 journal: veritysetup close dTVIWgshlU veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:45:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create nPfEpAezMV /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:45:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create nPfEpAezMV /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:45:57 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:45:57 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close nPfEpAezMV Oct 8 00:46:07 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:46:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:46:07 storageqe-109 journal: veritysetup close nPfEpAezMV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:46:22 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:46:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create wKbPGARiIM /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:46:55 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create wKbPGARiIM /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:46:55 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close wKbPGARiIM Oct 8 00:47:13 storageqe-109 journal: veritysetup close wKbPGARiIM veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:47:23 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create TIxawrzRGW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:47:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create TIxawrzRGW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:47:33 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:33 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close TIxawrzRGW Oct 8 00:47:43 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:47:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:47:43 storageqe-109 journal: veritysetup close TIxawrzRGW veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:47:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:48:14 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create MpIROAofVi /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:48:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create MpIROAofVi /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:48:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close MpIROAofVi Oct 8 00:48:48 storageqe-109 journal: veritysetup close MpIROAofVi veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:48:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create nPYhZHbMtg /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:49:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create nPYhZHbMtg /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:49:15 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:15 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close nPYhZHbMtg Oct 8 00:49:25 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:49:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:49:25 storageqe-109 journal: veritysetup close nPYhZHbMtg veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:49:39 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:49:56 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create hyvIAgYBPN /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:50:13 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create hyvIAgYBPN /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:50:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close hyvIAgYBPN Oct 8 00:50:31 storageqe-109 journal: veritysetup close hyvIAgYBPN veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:50:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create LeAKtFSEfz /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:50:51 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create LeAKtFSEfz /dev/mapper/npo2linear /dev/sde1 --no-superblock 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:50:51 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:50:51 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close LeAKtFSEfz Oct 8 00:51:01 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:51:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:51:01 storageqe-109 journal: veritysetup close LeAKtFSEfz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:51:16 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:51:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create DYGjwUFTyH /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:51:49 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create DYGjwUFTyH /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:51:49 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close DYGjwUFTyH Oct 8 00:52:07 storageqe-109 journal: veritysetup close DYGjwUFTyH veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:52:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create QTbqgaDdZW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:52:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create QTbqgaDdZW /dev/mapper/npo2linear /dev/sde1 85f703ecc1048a20b1ec24fe78165c0e481ae2dc3c805efc0517e0200b2a5d98 Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 00:52:33 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:33 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close QTbqgaDdZW Oct 8 00:52:43 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:52:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:52:43 storageqe-109 journal: veritysetup close QTbqgaDdZW Oct 8 00:52:53 storageqe-109 kernel: sde: Oct 8 00:52:54 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:52:58 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:53:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AtNxJgpSYO /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:53:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AtNxJgpSYO /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:53:31 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close AtNxJgpSYO Oct 8 00:53:49 storageqe-109 journal: veritysetup close AtNxJgpSYO veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:53:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MZCUuHObjy /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:54:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MZCUuHObjy /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 00:54:09 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:09 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close MZCUuHObjy Oct 8 00:54:19 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:54:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:54:19 storageqe-109 journal: veritysetup close MZCUuHObjy veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:54:33 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:54:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qHJyvUEVZp /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:55:06 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qHJyvUEVZp /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:55:06 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close qHJyvUEVZp Oct 8 00:55:24 storageqe-109 journal: veritysetup close qHJyvUEVZp veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:55:34 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mqgKVpyWFz /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:55:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create mqgKVpyWFz /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 00:55:50 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:55:50 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close mqgKVpyWFz Oct 8 00:56:00 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:56:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:56:00 storageqe-109 journal: veritysetup close mqgKVpyWFz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 00:56:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:56:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dKPCGHtFsv /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:56:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dKPCGHtFsv /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:56:48 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close dKPCGHtFsv Oct 8 00:57:05 storageqe-109 journal: veritysetup close dKPCGHtFsv veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:57:15 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hleaMixdTU /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:57:26 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hleaMixdTU /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 00:57:26 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:26 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close hleaMixdTU Oct 8 00:57:36 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:57:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:57:36 storageqe-109 journal: veritysetup close hleaMixdTU veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:57:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:58:06 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PcexTknpyE /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:58:23 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PcexTknpyE /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:58:23 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close PcexTknpyE Oct 8 00:58:40 storageqe-109 journal: veritysetup close PcexTknpyE veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:58:50 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UXqOmAlJVu /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:59:06 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create UXqOmAlJVu /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 00:59:06 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:06 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:07 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 00:59:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:07 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close UXqOmAlJVu Oct 8 00:59:16 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 00:59:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 00:59:16 storageqe-109 journal: veritysetup close UXqOmAlJVu veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 00:59:31 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 00:59:48 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XVfqRuZyFx /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:00:05 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XVfqRuZyFx /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:00:05 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close XVfqRuZyFx Oct 8 01:00:22 storageqe-109 journal: veritysetup close XVfqRuZyFx veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:00:32 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create npPdqhTyis /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:00:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create npPdqhTyis /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:00:42 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:00:42 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:00:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:43 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close npPdqhTyis Oct 8 01:00:53 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:00:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:00:53 storageqe-109 journal: veritysetup close npPdqhTyis veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:01:07 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:01:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OsqTimIFkC /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:01:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OsqTimIFkC /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:01:41 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close OsqTimIFkC Oct 8 01:01:59 storageqe-109 journal: veritysetup close OsqTimIFkC veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:02:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MIAdaEOKTV /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:02:26 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MIAdaEOKTV /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:02:26 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:26 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close MIAdaEOKTV Oct 8 01:02:36 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:02:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:02:36 storageqe-109 journal: veritysetup close MIAdaEOKTV veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 01:02:51 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:03:08 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pLEMjwNuqD /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:03:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pLEMjwNuqD /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:03:24 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close pLEMjwNuqD Oct 8 01:03:42 storageqe-109 journal: veritysetup close pLEMjwNuqD veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:03:52 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nfQUipNuZK /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:04:02 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nfQUipNuZK /dev/mapper/npo2linear /dev/sde1 --no-superblock aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:04:02 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:02 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close nfQUipNuZK Oct 8 01:04:12 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:04:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:04:12 storageqe-109 journal: veritysetup close nfQUipNuZK veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:04:27 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:04:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SruRoALFjY /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:05:01 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SruRoALFjY /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:05:01 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close SruRoALFjY Oct 8 01:05:18 storageqe-109 journal: veritysetup close SruRoALFjY veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:05:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ubMTOqgJdA /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:05:45 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ubMTOqgJdA /dev/mapper/npo2linear /dev/sde1 aceb1cfcc84d0df55333d6e5e3ab2e42fbf27c86 Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:05:45 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:46 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ubMTOqgJdA Oct 8 01:05:55 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:05:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:05:55 storageqe-109 journal: veritysetup close ubMTOqgJdA Oct 8 01:06:06 storageqe-109 kernel: sde: Oct 8 01:06:06 storageqe-109 kernel: sde: Oct 8 01:06:06 storageqe-109 kernel: sde: sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:06:10 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:06:27 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create kYtnlGZMrS /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:06:43 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create kYtnlGZMrS /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:06:43 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close kYtnlGZMrS Oct 8 01:07:01 storageqe-109 journal: veritysetup close kYtnlGZMrS veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:07:11 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create eWTzlGmnJL /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:07:21 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create eWTzlGmnJL /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:07:21 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:21 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close eWTzlGmnJL Oct 8 01:07:31 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:07:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:07:31 storageqe-109 journal: veritysetup close eWTzlGmnJL veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:07:46 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:08:02 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create oBMSfYitDz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:08:19 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create oBMSfYitDz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:08:19 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close oBMSfYitDz Oct 8 01:08:37 storageqe-109 journal: veritysetup close oBMSfYitDz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:08:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create ZrXAgvOTKy /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:09:03 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create ZrXAgvOTKy /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:09:03 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:03 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ZrXAgvOTKy Oct 8 01:09:13 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:09:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:09:13 storageqe-109 journal: veritysetup close ZrXAgvOTKy veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 01:09:28 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:09:45 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create IhCENJuwGO /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:10:02 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create IhCENJuwGO /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:10:02 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close IhCENJuwGO Oct 8 01:10:20 storageqe-109 journal: veritysetup close IhCENJuwGO veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:10:30 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create sPAlLNhBFQ /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:10:40 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create sPAlLNhBFQ /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:10:40 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:40 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close sPAlLNhBFQ Oct 8 01:10:50 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:10:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:10:50 storageqe-109 journal: veritysetup close sPAlLNhBFQ veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:11:04 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:11:21 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create iOcjfJCZyT /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:11:38 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create iOcjfJCZyT /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:11:38 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close iOcjfJCZyT Oct 8 01:11:56 storageqe-109 journal: veritysetup close iOcjfJCZyT veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:12:06 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create kqXtSIRPaz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:12:23 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create kqXtSIRPaz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:12:23 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:23 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close kqXtSIRPaz Oct 8 01:12:33 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:12:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:12:33 storageqe-109 journal: veritysetup close kqXtSIRPaz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:12:47 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:13:04 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create VuvAUPQMWO /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:13:21 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create VuvAUPQMWO /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:13:21 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close VuvAUPQMWO Oct 8 01:13:39 storageqe-109 journal: veritysetup close VuvAUPQMWO veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:13:49 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create AhPFLuYToz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:13:59 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create AhPFLuYToz /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:13:59 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:13:59 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close AhPFLuYToz Oct 8 01:14:09 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:14:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:14:09 storageqe-109 journal: veritysetup close AhPFLuYToz veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:14:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:14:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create YZzUesycMo /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:14:57 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create YZzUesycMo /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:14:57 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close YZzUesycMo Oct 8 01:15:15 storageqe-109 journal: veritysetup close YZzUesycMo veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:15:25 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create pqTsBzgDRG /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:15:42 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create pqTsBzgDRG /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:15:42 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:15:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:43 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close pqTsBzgDRG Oct 8 01:15:52 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:15:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:15:52 storageqe-109 journal: veritysetup close pqTsBzgDRG veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock Oct 8 01:16:07 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 --no-superblock veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:16:24 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WjtyuDgoPI /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:16:41 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create WjtyuDgoPI /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:16:41 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close WjtyuDgoPI Oct 8 01:16:59 storageqe-109 journal: veritysetup close WjtyuDgoPI veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:17:09 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create aBYvExJfFI /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:17:19 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create aBYvExJfFI /dev/mapper/npo2linear /dev/sde1 --no-superblock 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:17:19 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:19 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close aBYvExJfFI Oct 8 01:17:29 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:17:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:17:29 storageqe-109 journal: veritysetup close aBYvExJfFI veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 Oct 8 01:17:44 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/sde1 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:18:00 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create lyvNmHqJPd /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:18:17 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create lyvNmHqJPd /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:18:17 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close lyvNmHqJPd Oct 8 01:18:35 storageqe-109 journal: veritysetup close lyvNmHqJPd veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:18:45 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create bBWyESAzDa /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:19:02 storageqe-109 journal: veritysetup --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create bBWyESAzDa /dev/mapper/npo2linear /dev/sde1 64db47a2cc91a7f5a78ef9e110c513b3adc10678 Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 01:19:02 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 2 is corrupted Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:02 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close bBWyESAzDa Oct 8 01:19:12 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:19:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:19:12 storageqe-109 journal: veritysetup close bBWyESAzDa Oct 8 01:19:22 storageqe-109 kernel: sde: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:19:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:19:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pOQuPgIvtC /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:19:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pOQuPgIvtC /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:19:46 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close pOQuPgIvtC Oct 8 01:19:56 storageqe-109 journal: veritysetup close pOQuPgIvtC veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:20:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create KlZnytGBLm /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:20:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create KlZnytGBLm /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:20:16 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:16 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close KlZnytGBLm Oct 8 01:20:26 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:20:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:20:26 storageqe-109 journal: veritysetup close KlZnytGBLm veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:20:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:20:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fbwHnQBNjk /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:21:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fbwHnQBNjk /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:21:00 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close fbwHnQBNjk Oct 8 01:21:10 storageqe-109 journal: veritysetup close fbwHnQBNjk veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:21:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wkZUFLKWlH /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:21:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wkZUFLKWlH /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:21:30 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:30 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close wkZUFLKWlH Oct 8 01:21:40 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:21:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:21:40 storageqe-109 journal: veritysetup close wkZUFLKWlH veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:21:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:22:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iRMmltDrWH /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:22:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iRMmltDrWH /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:22:14 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close iRMmltDrWH Oct 8 01:22:24 storageqe-109 journal: veritysetup close iRMmltDrWH veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:22:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vGwxAHnqYb /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:22:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vGwxAHnqYb /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:22:44 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:44 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close vGwxAHnqYb Oct 8 01:22:54 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:22:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:22:54 storageqe-109 journal: veritysetup close vGwxAHnqYb veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:23:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:23:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nfygWvUDqx /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:23:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nfygWvUDqx /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:23:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close nfygWvUDqx Oct 8 01:23:38 storageqe-109 journal: veritysetup close nfygWvUDqx veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:23:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QjrVXWmALK /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:23:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QjrVXWmALK /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:23:58 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:58 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:23:59 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close QjrVXWmALK Oct 8 01:24:08 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:24:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:24:08 storageqe-109 journal: veritysetup close QjrVXWmALK veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:24:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:24:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qafojCzucs /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:24:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create qafojCzucs /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:24:42 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close qafojCzucs Oct 8 01:24:52 storageqe-109 journal: veritysetup close qafojCzucs veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:25:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zIpbMKocGB /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:25:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zIpbMKocGB /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:25:12 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:12 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zIpbMKocGB Oct 8 01:25:22 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:25:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:25:22 storageqe-109 journal: veritysetup close zIpbMKocGB veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:25:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:25:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CmyGLEFYPd /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:25:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CmyGLEFYPd /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:25:56 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close CmyGLEFYPd Oct 8 01:26:06 storageqe-109 journal: veritysetup close CmyGLEFYPd veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:26:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pFMXQfjEmb /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:26:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pFMXQfjEmb /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:26:26 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:27 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close pFMXQfjEmb Oct 8 01:26:36 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:26:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:26:36 storageqe-109 journal: veritysetup close pFMXQfjEmb veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:26:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:27:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ugjxscDTpm /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:27:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ugjxscDTpm /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:27:10 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ugjxscDTpm Oct 8 01:27:20 storageqe-109 journal: veritysetup close ugjxscDTpm veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:27:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ltJRdyxegZ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:27:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ltJRdyxegZ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:27:40 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:27:40 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:27:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:41 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ltJRdyxegZ Oct 8 01:27:50 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:27:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:27:50 storageqe-109 journal: veritysetup close ltJRdyxegZ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:28:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:28:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XYBCLkKmAE /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:28:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XYBCLkKmAE /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:28:24 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close XYBCLkKmAE Oct 8 01:28:34 storageqe-109 journal: veritysetup close XYBCLkKmAE veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:28:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oJLyjsWGmw /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:28:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oJLyjsWGmw /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:28:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:28:54 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:28:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:28:55 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close oJLyjsWGmw Oct 8 01:29:05 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:29:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:29:05 storageqe-109 journal: veritysetup close oJLyjsWGmw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:29:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:29:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LPuQzUgExJ /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:29:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LPuQzUgExJ /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:29:38 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close LPuQzUgExJ Oct 8 01:29:48 storageqe-109 journal: veritysetup close LPuQzUgExJ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:29:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AcSIhOHlBY /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:30:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create AcSIhOHlBY /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:30:09 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:09 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close AcSIhOHlBY Oct 8 01:30:19 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:30:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:30:19 storageqe-109 journal: veritysetup close AcSIhOHlBY veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:30:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:30:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QnDdNcKExL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:30:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create QnDdNcKExL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:30:52 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close QnDdNcKExL Oct 8 01:31:02 storageqe-109 journal: veritysetup close QnDdNcKExL veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:31:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create aBYIpgKCmW /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:31:23 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create aBYIpgKCmW /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:31:23 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:23 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close aBYIpgKCmW Oct 8 01:31:33 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:31:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:31:33 storageqe-109 journal: veritysetup close aBYIpgKCmW veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:31:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:31:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VlShdcDbfq /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:32:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create VlShdcDbfq /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:32:06 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close VlShdcDbfq Oct 8 01:32:16 storageqe-109 journal: veritysetup close VlShdcDbfq veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:32:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vzgchkZDyE /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:32:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vzgchkZDyE /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:32:37 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:37 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close vzgchkZDyE Oct 8 01:32:47 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:32:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:32:47 storageqe-109 journal: veritysetup close vzgchkZDyE veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:33:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:33:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ErKfcYkGBx /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:33:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ErKfcYkGBx /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:33:21 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ErKfcYkGBx Oct 8 01:33:31 storageqe-109 journal: veritysetup close ErKfcYkGBx veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:33:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create yVJAXzZxfs /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:33:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create yVJAXzZxfs /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:33:51 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:33:51 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close yVJAXzZxfs Oct 8 01:34:01 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:34:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:34:01 storageqe-109 journal: veritysetup close yVJAXzZxfs veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:34:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:34:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XaAoycpHsB /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:34:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create XaAoycpHsB /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:34:35 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close XaAoycpHsB Oct 8 01:34:45 storageqe-109 journal: veritysetup close XaAoycpHsB veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:34:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zJsHOeXwAP /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:35:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create zJsHOeXwAP /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:35:05 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:05 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close zJsHOeXwAP Oct 8 01:35:15 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:35:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:35:15 storageqe-109 journal: veritysetup close zJsHOeXwAP veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:35:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:35:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MtTuWLXaBq /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:35:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create MtTuWLXaBq /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:35:49 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close MtTuWLXaBq Oct 8 01:35:59 storageqe-109 journal: veritysetup close MtTuWLXaBq veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:36:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create klgcOEMvSG /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:36:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create klgcOEMvSG /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:36:19 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:19 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close klgcOEMvSG Oct 8 01:36:29 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:36:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:36:29 storageqe-109 journal: veritysetup close klgcOEMvSG veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:36:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:36:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GpTHWbQthw /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:37:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GpTHWbQthw /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:37:03 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close GpTHWbQthw Oct 8 01:37:13 storageqe-109 journal: veritysetup close GpTHWbQthw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:37:23 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iaClFdqDSK /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:37:33 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create iaClFdqDSK /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:37:33 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:33 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close iaClFdqDSK Oct 8 01:37:43 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:37:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:37:43 storageqe-109 journal: veritysetup close iaClFdqDSK veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:37:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:38:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pfGgwVJZUT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:38:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create pfGgwVJZUT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:38:17 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close pfGgwVJZUT Oct 8 01:38:27 storageqe-109 journal: veritysetup close pfGgwVJZUT veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:38:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ICopmgUdbn /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:38:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ICopmgUdbn /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:38:47 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:47 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ICopmgUdbn Oct 8 01:38:57 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:38:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:38:57 storageqe-109 journal: veritysetup close ICopmgUdbn veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:39:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:39:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WXTIUrFoeE /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:39:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WXTIUrFoeE /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:39:31 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close WXTIUrFoeE Oct 8 01:39:41 storageqe-109 journal: veritysetup close WXTIUrFoeE veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:39:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create IYzhCqHbsc /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:40:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create IYzhCqHbsc /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:40:01 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:01 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close IYzhCqHbsc Oct 8 01:40:11 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:40:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:40:11 storageqe-109 journal: veritysetup close IYzhCqHbsc veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:40:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:40:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HucGlytTBh /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:40:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create HucGlytTBh /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:40:45 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close HucGlytTBh Oct 8 01:40:55 storageqe-109 journal: veritysetup close HucGlytTBh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:41:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZSJdeTQgVz /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:41:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ZSJdeTQgVz /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:41:15 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:15 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:16 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ZSJdeTQgVz Oct 8 01:41:25 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:41:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:41:25 storageqe-109 journal: veritysetup close ZSJdeTQgVz veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:41:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:41:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vsLRofqrUN /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:41:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vsLRofqrUN /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:41:59 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close vsLRofqrUN Oct 8 01:42:09 storageqe-109 journal: veritysetup close vsLRofqrUN veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:42:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OEVQzehXoP /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:42:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OEVQzehXoP /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:42:29 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:29 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close OEVQzehXoP Oct 8 01:42:39 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:42:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:42:39 storageqe-109 journal: veritysetup close OEVQzehXoP veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:42:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:43:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create kYhrmFnPsl /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:43:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create kYhrmFnPsl /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:43:13 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close kYhrmFnPsl Oct 8 01:43:23 storageqe-109 journal: veritysetup close kYhrmFnPsl veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:43:33 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create EIrGOMsfSh /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:43:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create EIrGOMsfSh /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:43:43 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:44 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close EIrGOMsfSh Oct 8 01:43:53 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:43:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:43:53 storageqe-109 journal: veritysetup close EIrGOMsfSh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:44:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:44:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CcOySsDzhL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:44:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create CcOySsDzhL /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:44:27 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close CcOySsDzhL Oct 8 01:44:37 storageqe-109 journal: veritysetup close CcOySsDzhL veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:44:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WOPNkKXyMs /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:44:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create WOPNkKXyMs /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:44:57 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:44:58 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close WOPNkKXyMs Oct 8 01:45:07 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:45:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:45:07 storageqe-109 journal: veritysetup close WOPNkKXyMs veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:45:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:45:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create udYVENjtoT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:45:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create udYVENjtoT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:45:41 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close udYVENjtoT Oct 8 01:45:51 storageqe-109 journal: veritysetup close udYVENjtoT veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:46:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create baLRFfhYxg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:46:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create baLRFfhYxg /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:46:11 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:12 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:46:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:12 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:12 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close baLRFfhYxg Oct 8 01:46:21 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:46:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:46:21 storageqe-109 journal: veritysetup close baLRFfhYxg veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:46:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:46:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RuPcXxsMvh /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:46:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create RuPcXxsMvh /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:46:55 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close RuPcXxsMvh Oct 8 01:47:05 storageqe-109 journal: veritysetup close RuPcXxsMvh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:47:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fEOBmrgNDS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:47:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create fEOBmrgNDS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:47:25 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:47:25 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:47:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:26 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close fEOBmrgNDS Oct 8 01:47:36 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:47:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:47:36 storageqe-109 journal: veritysetup close fEOBmrgNDS veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:47:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:47:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FAxHNpwEIT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:48:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FAxHNpwEIT /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:48:09 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close FAxHNpwEIT Oct 8 01:48:19 storageqe-109 journal: veritysetup close FAxHNpwEIT veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:48:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nWkLavMXuI /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:48:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create nWkLavMXuI /dev/mapper/npo2linear /dev/mapper/npo2linear e522df0f97da4febb882ac40f30b37dc0b444bf6df418929463fa25280f09d5c Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:48:40 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:40 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close nWkLavMXuI Oct 8 01:48:50 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:48:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:48:50 storageqe-109 journal: veritysetup close nWkLavMXuI veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:49:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:49:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oyPKTAYShW /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:49:23 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create oyPKTAYShW /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:49:23 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close oyPKTAYShW Oct 8 01:49:33 storageqe-109 journal: veritysetup close oyPKTAYShW veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:49:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lqYTmVyxoa /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:49:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create lqYTmVyxoa /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:49:54 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:49:54 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close lqYTmVyxoa Oct 8 01:50:04 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:50:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:50:04 storageqe-109 journal: veritysetup close lqYTmVyxoa veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:50:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:50:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vQFhteaLMi /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:50:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vQFhteaLMi /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:50:37 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close vQFhteaLMi Oct 8 01:50:47 storageqe-109 journal: veritysetup close vQFhteaLMi veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:50:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BXmUfgtCYP /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:51:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create BXmUfgtCYP /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:51:08 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:08 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close BXmUfgtCYP Oct 8 01:51:18 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:51:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:51:18 storageqe-109 journal: veritysetup close BXmUfgtCYP veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:51:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:51:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NPTJGIdBbZ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:51:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create NPTJGIdBbZ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:51:52 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close NPTJGIdBbZ Oct 8 01:52:02 storageqe-109 journal: veritysetup close NPTJGIdBbZ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:52:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create bRJhwykNqc /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:52:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create bRJhwykNqc /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:52:22 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:22 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close bRJhwykNqc Oct 8 01:52:32 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:52:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:52:32 storageqe-109 journal: veritysetup close bRJhwykNqc veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:52:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:52:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wRmjTrvBal /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:53:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create wRmjTrvBal /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:53:06 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close wRmjTrvBal Oct 8 01:53:16 storageqe-109 journal: veritysetup close wRmjTrvBal veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:53:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PDxbOiCSvg /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:53:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create PDxbOiCSvg /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:53:36 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:36 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close PDxbOiCSvg Oct 8 01:53:46 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:53:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:53:46 storageqe-109 journal: veritysetup close PDxbOiCSvg veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:54:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:54:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SOeirzILdP /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:54:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SOeirzILdP /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:54:20 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close SOeirzILdP Oct 8 01:54:30 storageqe-109 journal: veritysetup close SOeirzILdP veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:54:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SUDYCnBqmA /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:54:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create SUDYCnBqmA /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:54:50 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:54:50 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close SUDYCnBqmA Oct 8 01:55:00 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:55:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:55:00 storageqe-109 journal: veritysetup close SUDYCnBqmA Oct 8 01:55:05 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 01:55:05 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 01:55:05 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:55:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:55:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FkjmBdbJvM /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:55:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FkjmBdbJvM /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:55:34 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close FkjmBdbJvM Oct 8 01:55:44 storageqe-109 journal: veritysetup close FkjmBdbJvM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:55:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create huifjgTRFo /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:56:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create huifjgTRFo /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:56:04 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:04 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close huifjgTRFo Oct 8 01:56:14 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:56:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:56:14 storageqe-109 journal: veritysetup close huifjgTRFo veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 01:56:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:56:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GRyJMSnapi /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:56:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create GRyJMSnapi /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:56:48 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close GRyJMSnapi Oct 8 01:56:58 storageqe-109 journal: veritysetup close GRyJMSnapi veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:57:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TKcOnIlRSr /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:57:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create TKcOnIlRSr /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:57:18 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:18 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close TKcOnIlRSr Oct 8 01:57:28 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:57:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:57:28 storageqe-109 journal: veritysetup close TKcOnIlRSr veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:57:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:57:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JAZeYHyjPK /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:58:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create JAZeYHyjPK /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:58:02 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" veritysetup close JAZeYHyjPK Oct 8 01:58:12 storageqe-109 journal: veritysetup close JAZeYHyjPK veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:58:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create bISnkRozFt /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:58:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '0' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create bISnkRozFt /dev/mapper/npo2linear /dev/mapper/npo2linear cbbf4ebd004ef65e29b935bb635a39cf754d677f3fa10b0126da725bbdf10f7d Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: sha256 using ahash "sha256-ni" Oct 8 01:58:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:32 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors Oct 8 01:58:35 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 01:58:35 storageqe-109 dnf[2496013]: Updating Subscription Management repositories. Oct 8 01:58:35 storageqe-109 dnf[2496013]: Unable to read consumer identity Oct 8 01:58:35 storageqe-109 dnf[2496013]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 01:58:36 storageqe-109 dnf[2496013]: Metadata cache refreshed recently. Oct 8 01:58:36 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 01:58:36 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. veritysetup close bISnkRozFt Oct 8 01:58:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:58:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 01:58:42 storageqe-109 journal: veritysetup close bISnkRozFt veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 01:58:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 01:59:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dZXULOocmY /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 01:59:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dZXULOocmY /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 01:59:16 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close dZXULOocmY Oct 8 01:59:26 storageqe-109 journal: veritysetup close dZXULOocmY veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 01:59:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create JIqWlzgvHD /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 01:59:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create JIqWlzgvHD /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 01:59:46 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:46 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close JIqWlzgvHD Oct 8 01:59:56 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 01:59:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 01:59:56 storageqe-109 journal: veritysetup close JIqWlzgvHD veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:00:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:00:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create NbLKeofOMz /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:00:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create NbLKeofOMz /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:00:30 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close NbLKeofOMz Oct 8 02:00:40 storageqe-109 journal: veritysetup close NbLKeofOMz veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:00:50 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create AuRhPywKEi /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:01:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create AuRhPywKEi /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:01:00 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:00 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:01 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close AuRhPywKEi Oct 8 02:01:10 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:01:10 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:01:10 storageqe-109 journal: veritysetup close AuRhPywKEi veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 02:01:24 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:01:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dQPylsqYAX /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:01:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create dQPylsqYAX /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:01:44 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close dQPylsqYAX Oct 8 02:01:54 storageqe-109 journal: veritysetup close dQPylsqYAX veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:02:04 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create NglRhrEJyd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:02:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create NglRhrEJyd /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:02:14 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:14 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:15 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close NglRhrEJyd Oct 8 02:02:24 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:02:24 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:02:24 storageqe-109 journal: veritysetup close NglRhrEJyd veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:02:38 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:02:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create NuSftMnlTz /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:02:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create NuSftMnlTz /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:02:58 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close NuSftMnlTz Oct 8 02:03:08 storageqe-109 journal: veritysetup close NuSftMnlTz veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:03:18 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create JKSCQItzes /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:03:28 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create JKSCQItzes /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:03:28 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:03:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:28 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:29 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:29 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close JKSCQItzes Oct 8 02:03:38 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:03:38 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:03:38 storageqe-109 journal: veritysetup close JKSCQItzes veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:03:52 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:04:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create SgvnUPVEbX /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:04:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create SgvnUPVEbX /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:04:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close SgvnUPVEbX Oct 8 02:04:22 storageqe-109 journal: veritysetup close SgvnUPVEbX veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:04:32 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create TZbcGFSWmh /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:04:42 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create TZbcGFSWmh /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:04:42 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:43 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:04:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:43 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:43 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close TZbcGFSWmh Oct 8 02:04:52 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:04:52 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:04:52 storageqe-109 journal: veritysetup close TZbcGFSWmh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:05:06 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:05:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create MAdsoGQFgR /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:05:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create MAdsoGQFgR /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:05:26 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close MAdsoGQFgR Oct 8 02:05:36 storageqe-109 journal: veritysetup close MAdsoGQFgR veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:05:46 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create KRkJaMVQAU /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:05:56 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create KRkJaMVQAU /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:05:56 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:05:56 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:05:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:56 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:56 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:05:57 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close KRkJaMVQAU Oct 8 02:06:06 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:06:06 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:06:07 storageqe-109 journal: veritysetup close KRkJaMVQAU veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 02:06:20 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:06:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create ioOtcMmByw /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:06:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create ioOtcMmByw /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:06:40 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close ioOtcMmByw Oct 8 02:06:50 storageqe-109 journal: veritysetup close ioOtcMmByw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:07:00 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create LfpSJnvrCU /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:07:10 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create LfpSJnvrCU /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:07:11 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:11 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close LfpSJnvrCU Oct 8 02:07:21 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:07:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:07:21 storageqe-109 journal: veritysetup close LfpSJnvrCU veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:07:34 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:07:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create bzSDHGFjlV /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:07:54 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create bzSDHGFjlV /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:07:54 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close bzSDHGFjlV Oct 8 02:08:04 storageqe-109 journal: veritysetup close bzSDHGFjlV veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:08:14 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create FSkWjwnNsY /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:08:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha256' --salt '-' --root-hash-file '/tmp/roothash' create FSkWjwnNsY /dev/mapper/npo2linear /dev/mapper/npo2linear ef29c902d87350f1da4bfa536e16cebc162a909bf89abe448b81ec500d4fb9bf Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:08:25 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:25 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close FSkWjwnNsY Oct 8 02:08:35 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:08:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:08:35 storageqe-109 journal: veritysetup close FSkWjwnNsY veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:08:48 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:08:58 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create keAsbrahiw /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:09:08 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create keAsbrahiw /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:09:08 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close keAsbrahiw Oct 8 02:09:18 storageqe-109 journal: veritysetup close keAsbrahiw veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:09:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ekRqFvALIQ /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:09:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ekRqFvALIQ /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:09:39 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:39 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close ekRqFvALIQ Oct 8 02:09:49 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:09:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:09:49 storageqe-109 journal: veritysetup close ekRqFvALIQ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:10:02 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:10:12 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OPowzSXdqM /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:10:22 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create OPowzSXdqM /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:10:22 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close OPowzSXdqM Oct 8 02:10:32 storageqe-109 journal: veritysetup close OPowzSXdqM veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:10:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create tOfbYREonT /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:10:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create tOfbYREonT /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:10:53 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:10:53 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close tOfbYREonT Oct 8 02:11:03 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:11:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:11:03 storageqe-109 journal: veritysetup close tOfbYREonT veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 02:11:16 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:11:26 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LXMDUGgmHS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:11:36 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create LXMDUGgmHS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:11:36 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close LXMDUGgmHS Oct 8 02:11:47 storageqe-109 journal: veritysetup close LXMDUGgmHS veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:11:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create egSVGXsYCo /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:12:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create egSVGXsYCo /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:12:07 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:07 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close egSVGXsYCo Oct 8 02:12:17 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:12:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:12:17 storageqe-109 journal: veritysetup close egSVGXsYCo veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:12:30 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:12:40 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YUDwxHCeuS /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:12:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create YUDwxHCeuS /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:12:51 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close YUDwxHCeuS Oct 8 02:13:01 storageqe-109 journal: veritysetup close YUDwxHCeuS veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:13:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create daoWtBMlDI /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:13:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create daoWtBMlDI /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:13:21 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:21 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close daoWtBMlDI Oct 8 02:13:31 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:13:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:13:31 storageqe-109 journal: veritysetup close daoWtBMlDI veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:13:44 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:13:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dkwfeohuSp /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:14:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create dkwfeohuSp /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:14:05 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close dkwfeohuSp Oct 8 02:14:15 storageqe-109 journal: veritysetup close dkwfeohuSp veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:14:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hmVDCwZMGi /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:14:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create hmVDCwZMGi /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:14:35 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:35 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close hmVDCwZMGi Oct 8 02:14:45 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:14:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:14:45 storageqe-109 journal: veritysetup close hmVDCwZMGi veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:14:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:15:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FcgREonMYh /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:15:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create FcgREonMYh /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:15:19 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close FcgREonMYh Oct 8 02:15:29 storageqe-109 journal: veritysetup close FcgREonMYh veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:15:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create rWOpCscjgq /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:15:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create rWOpCscjgq /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:15:49 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:49 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close rWOpCscjgq Oct 8 02:15:59 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:15:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:15:59 storageqe-109 journal: veritysetup close rWOpCscjgq veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 02:16:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:16:23 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vipjBNdFnI /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:16:33 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create vipjBNdFnI /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:16:33 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close vipjBNdFnI Oct 8 02:16:43 storageqe-109 journal: veritysetup close vipjBNdFnI veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:16:53 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create uzxHdPlEaS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:17:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create uzxHdPlEaS /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:17:03 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:03 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close uzxHdPlEaS Oct 8 02:17:13 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:17:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:17:13 storageqe-109 journal: veritysetup close uzxHdPlEaS veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:17:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:17:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ltIZQwGkDj /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:17:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create ltIZQwGkDj /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:17:47 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close ltIZQwGkDj Oct 8 02:17:57 storageqe-109 journal: veritysetup close ltIZQwGkDj veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:18:07 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jzGFhPtRBV /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:18:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'e48da609055204e89ae53b655ca2216dd983cf3cb829f34f63a297d106d53e2d' --root-hash-file '/tmp/roothash' create jzGFhPtRBV /dev/mapper/npo2linear /dev/mapper/npo2linear 6490266ea2846326927dd39703a32aee7d852a52 Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:18:17 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:17 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close jzGFhPtRBV Oct 8 02:18:27 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:18:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:18:27 storageqe-109 journal: veritysetup close jzGFhPtRBV veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:18:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:18:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create CISLXgyMbY /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:19:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create CISLXgyMbY /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:19:01 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close CISLXgyMbY Oct 8 02:19:11 storageqe-109 journal: veritysetup close CISLXgyMbY veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:19:21 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create oOEmaWqkIN /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:19:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create oOEmaWqkIN /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:19:31 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:31 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close oOEmaWqkIN Oct 8 02:19:41 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:19:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:19:41 storageqe-109 journal: veritysetup close oOEmaWqkIN veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:19:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:20:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create oBTGRsryEg /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:20:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create oBTGRsryEg /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:20:15 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:20:15 storageqe-109 rsyslogd[1103]: imjournal: journal files changed, reloading... [v8.2506.0-2.el10 try https://www.rsyslog.com/e/0 ] Oct 8 02:20:15 storageqe-109 rsyslogd[1103]: imjournal: journal files changed, reloading... [v8.2506.0-2.el10 try https://www.rsyslog.com/e/0 ] veritysetup close oBTGRsryEg Oct 8 02:20:25 storageqe-109 journal: veritysetup close oBTGRsryEg veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:20:35 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create lzxvPcwtoj /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:20:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create lzxvPcwtoj /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:20:45 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:45 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close lzxvPcwtoj Oct 8 02:20:55 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:20:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:20:55 storageqe-109 journal: veritysetup close lzxvPcwtoj veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 02:21:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:21:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create axVTglKZMt /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:21:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create axVTglKZMt /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:21:29 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close axVTglKZMt Oct 8 02:21:39 storageqe-109 journal: veritysetup close axVTglKZMt veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:21:49 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create emqUlwLdiJ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:21:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create emqUlwLdiJ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:21:59 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:21:59 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close emqUlwLdiJ Oct 8 02:22:09 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:22:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:22:09 storageqe-109 journal: veritysetup close emqUlwLdiJ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:22:23 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:22:33 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create nvQsZCUHfB /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:22:43 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create nvQsZCUHfB /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:22:43 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close nvQsZCUHfB Oct 8 02:22:53 storageqe-109 journal: veritysetup close nvQsZCUHfB veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:23:03 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create otJyeCduPK /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:23:13 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create otJyeCduPK /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:23:13 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:13 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:14 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close otJyeCduPK Oct 8 02:23:23 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:23:23 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:23:23 storageqe-109 journal: veritysetup close otJyeCduPK veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:23:37 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:23:47 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create yJTBgodUNt /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:23:57 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create yJTBgodUNt /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:23:57 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close yJTBgodUNt Oct 8 02:24:07 storageqe-109 journal: veritysetup close yJTBgodUNt veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:24:17 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create qyTaFBmKSO /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:24:27 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create qyTaFBmKSO /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:24:27 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:27 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close qyTaFBmKSO Oct 8 02:24:37 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:24:37 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:24:37 storageqe-109 journal: veritysetup close qyTaFBmKSO veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:24:51 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:25:01 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create qSfgtQkJDE /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:25:11 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create qSfgtQkJDE /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:25:11 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close qSfgtQkJDE Oct 8 02:25:21 storageqe-109 journal: veritysetup close qSfgtQkJDE veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:25:31 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create XuDgCEwBbK /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:25:41 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create XuDgCEwBbK /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:25:41 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:41 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:42 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close XuDgCEwBbK Oct 8 02:25:51 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:25:51 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:25:51 storageqe-109 journal: veritysetup close XuDgCEwBbK veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock Oct 8 02:26:05 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:26:15 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create qoCSLaEjDB /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:26:25 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create qoCSLaEjDB /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:26:25 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close qoCSLaEjDB Oct 8 02:26:35 storageqe-109 journal: veritysetup close qoCSLaEjDB veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:26:45 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create vYbknarDuJ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:26:55 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create vYbknarDuJ /dev/mapper/npo2linear /dev/mapper/npo2linear --no-superblock 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:26:55 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: device-mapper: verity: 253:3: data block 0 is corrupted Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:55 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:26:56 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close vYbknarDuJ Oct 8 02:27:05 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:27:05 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:27:05 storageqe-109 journal: veritysetup close vYbknarDuJ veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear Oct 8 02:27:19 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' format /dev/mapper/npo2linear /dev/mapper/npo2linear veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:27:29 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create PdLXofymcu /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:27:39 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create PdLXofymcu /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:27:39 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" veritysetup close PdLXofymcu Oct 8 02:27:49 storageqe-109 journal: veritysetup close PdLXofymcu veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:27:59 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' verify /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create bqSHMuVpgs /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:28:09 storageqe-109 journal: veritysetup --hash-offset '8388608' --data-blocks '2048' --format '1' --data-block-size '4096' --hash-block-size '4096' --hash 'sha1' --salt 'dadada' --root-hash-file '/tmp/roothash' create bqSHMuVpgs /dev/mapper/npo2linear /dev/mapper/npo2linear 6f6679e0f1cedc0deba824470827b2ee3e969fa2 Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: sha1 using shash "sha1-ni" Oct 8 02:28:09 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: device-mapper: verity: 253:3: data block 2 is corrupted Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:09 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:10 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors veritysetup close bqSHMuVpgs Oct 8 02:28:19 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:28:19 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 2, async page read Oct 8 02:28:19 storageqe-109 journal: veritysetup close bqSHMuVpgs INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_check[npo2_linear] #### INFO: #### will start test_dm_verity_format[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 8 02:28:34 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 8 02:28:34 storageqe-109 INFO: #### END test_dm_verity_check[npo2_linear] #### Oct 8 02:28:34 storageqe-109 INFO: #### will start test_dm_verity_format[npo2_linear] ##### Oct 8 02:28:34 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 8 02:28:40 storageqe-109 kernel: loop3: detected capacity change from 0 to 12582912 Oct 8 02:28:40 storageqe-109 kernel: sde: Oct 8 02:28:40 storageqe-109 kernel: sde: sde1 Oct 8 02:28:40 storageqe-109 kernel: loop4: detected capacity change from 0 to 12582912 veritysetup --fec-device '/dev/sdd1' --fec-roots '2' --hash 'sha256' format /dev/mapper/npo2linear /dev/sde1 Oct 8 02:28:40 storageqe-109 kernel: sdd: Oct 8 02:28:40 storageqe-109 kernel: sdd: sdd1 Oct 8 02:28:40 storageqe-109 journal: veritysetup --fec-device '/dev/sdd1' --fec-roots '2' --hash 'sha256' format /dev/mapper/npo2linear /dev/sde1 veritysetup verify /dev/mapper/npo2linear /dev/sde1 9a4248052e8ab652fbb2ba0dbc35357fa5ad5da5ed99d553a24178f2a98638e5 Oct 8 02:29:47 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/sde1 9a4248052e8ab652fbb2ba0dbc35357fa5ad5da5ed99d553a24178f2a98638e5 veritysetup verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 8 02:30:04 storageqe-109 journal: veritysetup verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 veritysetup --fec-device '/dev/sdd1' --fec-roots '2' verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 8 02:30:21 storageqe-109 journal: veritysetup --fec-device '/dev/sdd1' --fec-roots '2' verify /dev/mapper/npo2linear /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 veritysetup open /dev/mapper/npo2linear fuSJAbcTiG /dev/sde1 9a4248052e8ab652fbb2ba0dbc35357fa5ad5da5ed99d553a24178f2a98638e5 Oct 8 02:31:12 storageqe-109 journal: veritysetup open /dev/mapper/npo2linear fuSJAbcTiG /dev/sde1 9a4248052e8ab652fbb2ba0dbc35357fa5ad5da5ed99d553a24178f2a98638e5 Oct 8 02:31:12 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" veritysetup close fuSJAbcTiG Oct 8 02:31:22 storageqe-109 journal: veritysetup close fuSJAbcTiG veritysetup open /dev/mapper/npo2linear fuSJAbcTiG /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 8 02:31:32 storageqe-109 journal: veritysetup open /dev/mapper/npo2linear fuSJAbcTiG /dev/sde1 abcdef0000000000000000000000000000000000000000000000000000000000 Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: sha256 using shash "sha256-ni" Oct 8 02:31:32 storageqe-109 kernel: verity_handle_err: 90 callbacks suppressed Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: metadata block 1 is corrupted Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 1572848, async page read Oct 8 02:31:32 storageqe-109 kernel: device-mapper: verity: 253:3: reached maximum errors Oct 8 02:31:37 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 02:31:37 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 02:31:37 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. veritysetup close fuSJAbcTiG Oct 8 02:31:42 storageqe-109 kernel: buffer_io_error: 91 callbacks suppressed Oct 8 02:31:42 storageqe-109 kernel: Buffer I/O error on dev dm-4, logical block 0, async page read Oct 8 02:31:42 storageqe-109 journal: veritysetup close fuSJAbcTiG Oct 8 02:31:52 storageqe-109 kernel: sde: Oct 8 02:31:52 storageqe-109 kernel: sdd: sdd1 Oct 8 02:31:53 storageqe-109 kernel: sdd: INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_dm_verity_format[npo2_linear] #### Oct 8 02:31:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 8 02:31:58 storageqe-109 INFO: #### END test_dm_verity_format[npo2_linear] #### Oct 8 02:31:59 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 8 02:32:00 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 8 02:32:01 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 8 02:32:01 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 8 02:32:01 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 8 02:32:31 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 8 03:43:22 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 03:43:22 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 03:43:22 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 03:56:02 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 03:56:03 storageqe-109 dnf[2502598]: Updating Subscription Management repositories. Oct 8 03:56:03 storageqe-109 dnf[2502598]: Unable to read consumer identity Oct 8 03:56:03 storageqe-109 dnf[2502598]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-AppStream 574 kB/s | 2.8 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-AppStream-debuginfo 444 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-BaseOS 818 kB/s | 2.7 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-BaseOS-debuginfo 518 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-CRB 793 kB/s | 2.7 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-CRB-debuginfo 543 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-HighAvailability 549 kB/s | 2.8 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-HighAvailability-debuginfo 591 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-NFV 677 kB/s | 2.7 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-NFV-debuginfo 477 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-RT 875 kB/s | 2.7 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-RT-debuginfo 554 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-SAP 734 kB/s | 2.7 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-SAP-debuginfo 430 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-SAPHANA 700 kB/s | 2.7 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: beaker-SAPHANA-debuginfo 432 kB/s | 1.5 kB 00:00 Oct 8 03:56:03 storageqe-109 dnf[2502598]: Beaker Client - RedHatEnterpriseLinux10 2.5 kB/s | 1.3 kB 00:00 Oct 8 03:56:04 storageqe-109 dnf[2502598]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 8 03:56:04 storageqe-109 dnf[2502598]: Google Cloud CLI 4.1 kB/s | 1.4 kB 00:00 Oct 8 03:56:05 storageqe-109 dnf[2502598]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 8 03:56:06 storageqe-109 dnf[2502598]: repo14 1.9 kB/s | 2.3 kB 00:01 Oct 8 03:56:08 storageqe-109 dnf[2502598]: repo14 167 kB/s | 332 kB 00:01 Oct 8 03:56:09 storageqe-109 dnf[2502598]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 8 03:56:09 storageqe-109 dnf[2502598]: Metadata cache created. Oct 8 03:56:09 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 03:56:09 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 03:56:09 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 451ms CPU time, 102.3M memory peak. Oct 8 04:09:23 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 04:09:23 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 04:09:23 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 05:12:27 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 05:12:27 storageqe-109 dnf[2502894]: Updating Subscription Management repositories. Oct 8 05:12:27 storageqe-109 dnf[2502894]: Unable to read consumer identity Oct 8 05:12:27 storageqe-109 dnf[2502894]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 05:12:27 storageqe-109 dnf[2502894]: Metadata cache refreshed recently. Oct 8 05:12:27 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 05:12:27 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 05:31:28 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 05:31:28 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 05:31:28 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 05:39:49 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 8 05:39:49 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 8 05:41:04 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 8 05:41:26 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 8 05:41:26 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 8 05:41:56 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 8 05:42:05 storageqe-109 kernel: __vm_enough_memory: pid: 1176532, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 8 05:42:05 storageqe-109 kernel: __vm_enough_memory: pid: 1176532, comm: claude, bytes: 34356879360 not enough memory for the allocation Oct 8 05:42:05 storageqe-109 kernel: __vm_enough_memory: pid: 1176532, comm: claude, bytes: 34359873536 not enough memory for the allocation Oct 8 05:42:05 storageqe-109 kernel: __vm_enough_memory: pid: 1176532, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 8 05:42:05 storageqe-109 systemd-coredump[2505377]: Process 1176532 (claude) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 8 05:42:05 storageqe-109 systemd[1]: Started systemd-coredump@2-2505377-0.service - Process Core Dump (PID 2505377/UID 0). Oct 8 05:42:07 storageqe-109 systemd-coredump[2505378]: Process 1176532 (claude) of user 0 dumped core.#012#012Module /usr/bin/node-22 from rpm nodejs22-22.19.0-2.el10_0.x86_64#012Stack trace of thread 1176532:#012#0 0x00007f0626cbdfcc n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 8 05:42:07 storageqe-109 systemd[1]: systemd-coredump@2-2505377-0.service: Deactivated successfully. Oct 8 05:42:07 storageqe-109 systemd[1]: systemd-coredump@2-2505377-0.service: Consumed 1.282s CPU time, 378.6M memory peak. Oct 8 05:42:12 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 8 05:42:12 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 8 05:43:22 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 8 05:46:19 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 8 05:46:19 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 8 05:47:03 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 8 06:00:20 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 06:00:20 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 06:00:20 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 07:05:14 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 07:05:14 storageqe-109 dnf[2506341]: Updating Subscription Management repositories. Oct 8 07:05:14 storageqe-109 dnf[2506341]: Unable to read consumer identity Oct 8 07:05:14 storageqe-109 dnf[2506341]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-AppStream 514 kB/s | 2.8 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-AppStream-debuginfo 491 kB/s | 1.5 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-BaseOS 680 kB/s | 2.7 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-BaseOS-debuginfo 502 kB/s | 1.5 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-CRB 573 kB/s | 2.7 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-CRB-debuginfo 582 kB/s | 1.5 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-HighAvailability 878 kB/s | 2.8 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-HighAvailability-debuginfo 589 kB/s | 1.5 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-NFV 835 kB/s | 2.7 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-NFV-debuginfo 493 kB/s | 1.5 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-RT 790 kB/s | 2.7 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-RT-debuginfo 474 kB/s | 1.5 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-SAP 653 kB/s | 2.7 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-SAP-debuginfo 417 kB/s | 1.5 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-SAPHANA 670 kB/s | 2.7 kB 00:00 Oct 8 07:05:14 storageqe-109 dnf[2506341]: beaker-SAPHANA-debuginfo 515 kB/s | 1.5 kB 00:00 Oct 8 07:05:15 storageqe-109 dnf[2506341]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 8 07:05:15 storageqe-109 dnf[2506341]: beaker-harness 2.5 kB/s | 1.3 kB 00:00 Oct 8 07:05:15 storageqe-109 dnf[2506341]: Google Cloud CLI 5.9 kB/s | 1.4 kB 00:00 Oct 8 07:05:16 storageqe-109 dnf[2506341]: Copr repo for python-ssh2-python312 owned by mh 2.0 kB/s | 1.5 kB 00:00 Oct 8 07:05:17 storageqe-109 dnf[2506341]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 8 07:05:17 storageqe-109 dnf[2506341]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 8 07:05:17 storageqe-109 dnf[2506341]: Metadata cache created. Oct 8 07:05:17 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 07:05:17 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 07:05:17 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 342ms CPU time, 103M memory peak. Oct 8 07:25:55 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 07:25:55 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 07:25:55 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 08:08:30 storageqe-109 systemd-logind[1011]: New session 9 of user root. Oct 8 08:08:30 storageqe-109 systemd[1]: Started session-9.scope - Session 9 of User root. Oct 8 08:08:31 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 8 08:08:31 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 8 08:09:01 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 8 08:10:26 storageqe-109 udisksd[1175313]: Couldn't find existing drive object for device /sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0/nvme/nvme0 (uevent action 'change', VPD 'NVMe:hostnqn=nohostnqn+transport=pcie+/sys/devices/pci0000:00/0000:00:01.1/0000:02:00.0/nvme/nvme0') Oct 8 08:37:31 storageqe-109 NetworkManager[995]: [1759927051.7249] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 8 08:37:31 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 8 08:37:31 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 8 08:37:41 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 8 08:40:49 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 08:40:49 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 08:40:49 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 08:44:36 storageqe-109 systemd[1]: Stopping udisks2.service - Disk Manager... Oct 8 08:44:36 storageqe-109 udisksd[1175313]: object_ref: assertion '!object_already_finalized' failed Oct 8 08:44:36 storageqe-109 udisksd[1175313]: ** Oct 8 08:44:36 storageqe-109 udisksd[1175313]: udisks:ERROR:udiskslinuxdriveobject.c:196:udisks_linux_drive_object_constructor: assertion failed: (daemon != NULL) Oct 8 08:44:36 storageqe-109 udisksd[1175313]: Bail out! udisks:ERROR:udiskslinuxdriveobject.c:196:udisks_linux_drive_object_constructor: assertion failed: (daemon != NULL) Oct 8 08:44:36 storageqe-109 systemd-coredump[2506671]: Process 1175313 (udisksd) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 8 08:44:36 storageqe-109 systemd[1]: Started systemd-coredump@3-2506671-0.service - Process Core Dump (PID 2506671/UID 0). Oct 8 08:44:36 storageqe-109 systemd-coredump[2506672]: Process 1175313 (udisksd) of user 0 dumped core.#012#012Module /usr/libexec/udisks2/udisksd from rpm udisks2-2.10.90-6.el10_1.x86_64#012Module legacy.so from rpm openssl-3.5.1-5.el10.x86_64#012Module libyaml-0.so.2 from rpm libyaml-0.2.5-16.el10.x86_64#012Module libbd_lvm.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libudisks2_lvm2.so from rpm udisks2-2.10.90-6.el10_1.x86_64#012Module libpci.so.3 from rpm pciutils-3.13.0-6.el10.x86_64#012Module libsgutils2-1.48.so.2 from rpm sg3_utils-1.48-7.el10.x86_64#012Module libled.so.1 from rpm ledmon-1.1.0-2.el10.x86_64#012Module libstoragemgmt.so.1 from rpm libstoragemgmt-1.10.1-4.el10.x86_64#012Module libudisks2_lsm.so from rpm udisks2-2.10.90-6.el10_1.x86_64#012Module libopeniscsiusr.so.0 from rpm iscsi-initiator-utils-6.2.1.11-0.git4b3e853.el10.x86_64#012Module libiscsi.so.0 from rpm iscsi-initiator-utils-6.2.1.11-0.git4b3e853.el10.x86_64#012Module libudisks2_iscsi.so from rpm udisks2-2.10.90-6.el10_1.x86_64#012Module libbd_smart.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libnvme.so.1 from rpm libnvme-1.13-1.el10.x86_64#012Module libbd_nvme.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libcom_err.so.2 from rpm e2fsprogs-1.47.1-4.el10.x86_64#012Module libe2p.so.2 from rpm e2fsprogs-1.47.1-4.el10.x86_64#012Module libext2fs.so.2 from rpm e2fsprogs-1.47.1-4.el10.x86_64#012Module libbd_fs.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libfdisk.so.1 from rpm util-linux-2.40.2-13.el10.x86_64#012Module libbd_part.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libgmp.so.10 from rpm gmp-6.2.1-12.el10.x86_64#012Module libmpfr.so.6 from rpm mpfr-4.2.1-5.el10.x86_64#012Module libbytesize.so.1 from rpm libbytesize-2.10-5.el10.x86_64#012Module libbd_mdraid.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libjson-c.so.5 from rpm json-c-0.18-3.el10.x86_64#012Module libdevmapper.so.1.02 from rpm lvm2-2.03.32-3.el10.x86_64#012Module libvolume_key.so.1 from rpm volume_key-0.3.12-25.el10.x86_64#012Module libkeyutils.so.1 from rpm keyutils-1.6.3-5.el10.x86_64#012Module libnspr4.so from rpm nss-3.112.0-4.el10_0.x86_64#012Module libplc4.so from rpm nss-3.112.0-4.el10_0.x86_64#012Module libplds4.so from rpm nss-3.112.0-4.el10_0.x86_64#012Module libnssutil3.so from rpm nss-3.112.0-4.el10_0.x86_64#012Module libnss3.so from rpm nss-3.112.0-4.el10_0.x86_64#012Module libsmime3.so from rpm nss-3.112.0-4.el10_0.x86_64#012Module libssl3.so from rpm nss-3.112.0-4.el10_0.x86_64#012Module libcryptsetup.so.12 from rpm cryptsetup-2.8.1-1.el10.x86_64#012Module libbd_crypto.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libbd_loop.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libbd_swap.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libcrypto.so.3 from rpm openssl-3.5.1-5.el10.x86_64#012Module liblzma.so.5 from rpm xz-5.6.2-4.el10_0.x86_64#012Module libzstd.so.1 from rpm zstd-1.5.5-9.el10.x86_64#012Module libpcre2-8.so.0 from rpm pcre2-10.44-1.el10.3.x86_64#012Module libffi.so.8 from rpm libffi-3.4.4-10.el10.x86_64#012Module libz.so.1 from rpm zlib-ng-2.2.3-2.el10.x86_64#012Module libcap.so.2 from rpm libcap-2.69-7.el10.x86_64#012Module libattr.so.1 from rpm attr-2.5.2-5.el10.x86_64#012Module libselinux.so.1 from rpm libselinux-3.9-1.el10.x86_64#012Module libkmod.so.2 from rpm kmod-31-12.el10.x86_64#012Module libudev.so.1 from rpm systemd-257-13.el10.x86_64#012Module libglib-2.0.so.0 from rpm glib2-2.80.4-4.el10_0.6.x86_64#012Module libgobject-2.0.so.0 from rpm glib2-2.80.4-4.el10_0.6.x86_64#012Module libgio-2.0.so.0 from rpm glib2-2.80.4-4.el10_0.6.x86_64#012Module libudisks2.so.0 from rpm udisks2-2.10.90-6.el10_1.x86_64#012Module libsystemd.so.0 from rpm systemd-257-13.el10.x86_64#012Module libacl.so.1 from rpm acl-2.3.2-4.el10.x86_64#012Module libpolkit-gobject-1.so.0 from rpm polkit-125-4.el10.x86_64#012Module libuuid.so.1 from rpm util-linux-2.40.2-13.el10.x86_64#012Module libmount.so.1 from rpm util-linux-2.40.2-13.el10.x86_64#012Module libblkid.so.1 from rpm util-linux-2.40.2-13.el10.x86_64#012Module libbd_utils.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libblockdev.so.3 from rpm libblockdev-3.4.0-1.el10.x86_64#012Module libgudev-1.0.so.0 from rpm libgudev-238-7.el10.x86_64#012Module libgmodule-2.0.so.0 from rpm glib2-2.80.4-4.el10_0.6.x86_64#012Stack trace of thread 1175313:#012#0 0x00007f0332980fcc __pthread_kill_implementation (libc.so.6 + 0x96fcc)#012#1 0x00007f033292af56 raise (libc.so.6 + 0x40f56)#012#2 0x00007f03329128fa abort (libc.so.6 + 0x288fa)#012#3 0x00007f0332b10105 g_assertion_message.cold (libglib-2.0.so.0 + 0x20105)#012#4 0x00007f0332b7aece g_assertion_message_expr (libglib-2.0.so.0 + 0x8aece)#012#5 0x000055c631dca032 udisks_linux_drive_object_constructor (/usr/libexec/udisks2/udisksd + 0x41032)#012#6 0x00007f0332c613a2 g_object_new_with_custom_constructor (libgobject-2.0.so.0 + 0x223a2)#012#7 0x00007f0332c6373d g_object_new_valist (libgobject-2.0.so.0 + 0x2473d)#012#8 0x00007f0332c63f15 g_object_new (libgobject-2.0.so.0 + 0x24f15)#012#9 0x000055c631db0d0a handle_block_uevent_for_drive (/usr/libexec/udisks2/udisksd + 0x27d0a)#012#10 0x000055c631db26b2 udisks_linux_provider_handle_uevent (/usr/libexec/udisks2/udisksd + 0x296b2)#012#11 0x000055c631db2bbe ensure_modules (/usr/libexec/udisks2/udisksd + 0x29bbe)#012#12 0x00007f0332760056 ffi_call_unix64 (libffi.so.8 + 0xa056)#012#13 0x00007f033275b6f1 ffi_call_int.lto_priv.0 (libffi.so.8 + 0x56f1)#012#14 0x00007f033275e6ae ffi_call (libffi.so.8 + 0x86ae)#012#15 0x00007f0332c56eb2 g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x17eb2)#012#16 0x00007f0332c509b0 g_closure_invoke (libgobject-2.0.so.0 + 0x119b0)#012#17 0x00007f0332c7f753 signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x40753)#012#18 0x00007f0332c7084e signal_emit_valist_unlocked (libgobject-2.0.so.0 + 0x3184e)#012#19 0x00007f0332c70b36 g_signal_emit_valist (libgobject-2.0.so.0 + 0x31b36)#012#20 0x00007f0332c70bfb g_signal_emit (libgobject-2.0.so.0 + 0x31bfb)#012#21 0x000055c631dea210 udisks_module_manager_unload_modules (/usr/libexec/udisks2/udisksd + 0x61210)#012#22 0x000055c631dae36a udisks_daemon_finalize (/usr/libexec/udisks2/udisksd + 0x2536a)#012#23 0x00007f0332c5f63b g_object_unref (libgobject-2.0.so.0 + 0x2063b)#012#24 0x000055c631daa4e8 main (/usr/libexec/udisks2/udisksd + 0x214e8)#012#25 0x00007f033291458e __libc_start_call_main (libc.so.6 + 0x2a58e)#012#26 0x00007f0332914649 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2a649)#012#27 0x000055c631daa785 _start (/usr/libexec/udisks2/udisksd + 0x21785)#012#012Stack trace of thread 1175315:#012#0 0x00007f03329ed8fd syscall (libc.so.6 + 0x1038fd)#012#1 0x00007f0332b9e764 g_cond_wait (libglib-2.0.so.0 + 0xae764)#012#2 0x00007f0332b1728b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x2728b)#012#3 0x00007f0332b7c502 g_thread_pool_spawn_thread (libglib-2.0.so.0 + 0x8c502)#012#4 0x00007f0332b7b342 g_thread_proxy (libglib-2.0.so.0 + 0x8b342)#012#5 0x00007f033297f168 start_thread (libc.so.6 + 0x95168)#012#6 0x00007f03329efafc __clone3 (libc.so.6 + 0x105afc)#012#012Stack trace of thread 1175314:#012#0 0x00007f03329e2c2f __poll (libc.so.6 + 0xf8c2f)#012#1 0x00007f0332babc0e g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0xbbc0e)#012#2 0x00007f0332b4d360 g_main_context_iteration (libglib-2.0.so.0 + 0x5d360)#012#3 0x00007f0332b4d3b1 glib_worker_main (libglib-2.0.so.0 + 0x5d3b1)#012#4 0x00007f0332b7b342 g_thread_proxy (libglib-2.0.so.0 + 0x8b342)#012#5 0x00007f033297f168 start_thread (libc.so.6 + 0x95168)#012#6 0x00007f03329efafc __clone3 (libc.so.6 + 0x105afc)#012#012Stack trace of thread 1175318:#012#0 0x00007f03329ed8fd syscall (libc.so.6 + 0x1038fd)#012#1 0x00007f0332b9e764 g_cond_wait (libglib-2.0.so.0 + 0xae764)#012#2 0x00007f0332b1728b g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x2728b)#012#3 0x00007f0332b172eb g_async_queue_pop (libglib-2.0.so.0 + 0x272eb)#012#4 0x000055c631db02d9 probe_request_thread_func (/usr/libexec/udisks2/udisksd + 0x272d9)#012#5 0x00007f0332b7b342 g_thread_prox Oct 8 08:44:36 storageqe-109 systemd[1]: systemd-coredump@3-2506671-0.service: Deactivated successfully. Oct 8 08:44:36 storageqe-109 systemd[1]: systemd-coredump@3-2506671-0.service: Consumed 103ms CPU time, 75.4M memory peak. Oct 8 08:44:36 storageqe-109 systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Oct 8 08:44:36 storageqe-109 systemd[1]: udisks2.service: Failed with result 'core-dump'. Oct 8 08:44:36 storageqe-109 systemd[1]: Stopped udisks2.service - Disk Manager. Oct 8 08:44:36 storageqe-109 systemd[1]: udisks2.service: Consumed 16.706s CPU time, 25.3M memory peak, 1.7M memory swap peak. Oct 8 08:44:36 storageqe-109 systemd[1]: Starting udisks2.service - Disk Manager... Oct 8 08:44:36 storageqe-109 udisksd[2506680]: udisks daemon version 2.10.90 starting Oct 8 08:44:36 storageqe-109 systemd[1]: Started udisks2.service - Disk Manager. Oct 8 08:44:36 storageqe-109 udisksd[2506680]: Unclean shutdown detected, reloading modules from previous session. Oct 8 08:44:36 storageqe-109 udisksd[2506680]: Loading module iscsi ... Oct 8 08:44:36 storageqe-109 udisksd[2506680]: Loading module lvm2 ... Oct 8 08:44:36 storageqe-109 udisksd[2506680]: Acquired the name org.freedesktop.UDisks2 on the system message bus Oct 8 08:47:03 storageqe-109 systemd[1]: session-9.scope: Deactivated successfully. Oct 8 08:47:03 storageqe-109 systemd-logind[1011]: Session 9 logged out. Waiting for processes to exit. Oct 8 08:47:03 storageqe-109 systemd-logind[1011]: Removed session 9. Oct 8 09:04:21 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 09:04:21 storageqe-109 dnf[2506756]: Updating Subscription Management repositories. Oct 8 09:04:21 storageqe-109 dnf[2506756]: Unable to read consumer identity Oct 8 09:04:21 storageqe-109 dnf[2506756]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 09:04:21 storageqe-109 dnf[2506756]: Metadata cache refreshed recently. Oct 8 09:04:21 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 09:04:21 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 09:26:42 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 09:26:42 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 09:26:42 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 10:11:05 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 10:11:05 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 10:11:05 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 10:44:37 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 10:44:37 storageqe-109 dnf[2506906]: Updating Subscription Management repositories. Oct 8 10:44:37 storageqe-109 dnf[2506906]: Unable to read consumer identity Oct 8 10:44:37 storageqe-109 dnf[2506906]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-AppStream 450 kB/s | 2.8 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-AppStream-debuginfo 496 kB/s | 1.5 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-BaseOS 834 kB/s | 2.7 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-BaseOS-debuginfo 409 kB/s | 1.5 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-CRB 784 kB/s | 2.7 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-CRB-debuginfo 455 kB/s | 1.5 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-HighAvailability 1.2 MB/s | 2.8 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-HighAvailability-debuginfo 548 kB/s | 1.5 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-NFV 738 kB/s | 2.7 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-NFV-debuginfo 465 kB/s | 1.5 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-RT 1.2 MB/s | 2.7 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-RT-debuginfo 226 kB/s | 1.5 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-SAP 673 kB/s | 2.7 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-SAP-debuginfo 528 kB/s | 1.5 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-SAPHANA 1.1 MB/s | 2.7 kB 00:00 Oct 8 10:44:37 storageqe-109 dnf[2506906]: beaker-SAPHANA-debuginfo 478 kB/s | 1.5 kB 00:00 Oct 8 10:44:38 storageqe-109 dnf[2506906]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 8 10:44:38 storageqe-109 dnf[2506906]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 8 10:44:39 storageqe-109 dnf[2506906]: Google Cloud CLI 4.1 kB/s | 1.4 kB 00:00 Oct 8 10:44:40 storageqe-109 dnf[2506906]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 8 10:44:40 storageqe-109 dnf[2506906]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 8 10:44:41 storageqe-109 dnf[2506906]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 8 10:44:41 storageqe-109 dnf[2506906]: Metadata cache created. Oct 8 10:44:41 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 10:44:41 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 11:22:19 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 11:22:19 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 11:22:19 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 11:58:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 11:58:53 storageqe-109 dnf[2507068]: Updating Subscription Management repositories. Oct 8 11:58:53 storageqe-109 dnf[2507068]: Unable to read consumer identity Oct 8 11:58:53 storageqe-109 dnf[2507068]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 11:58:53 storageqe-109 dnf[2507068]: Metadata cache refreshed recently. Oct 8 11:58:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 11:58:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 12:53:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 12:53:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 12:53:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 13:13:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 13:13:53 storageqe-109 dnf[2507192]: Updating Subscription Management repositories. Oct 8 13:13:53 storageqe-109 dnf[2507192]: Unable to read consumer identity Oct 8 13:13:53 storageqe-109 dnf[2507192]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 13:13:53 storageqe-109 dnf[2507192]: Metadata cache refreshed recently. Oct 8 13:13:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 13:13:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 13:20:26 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 13:20:26 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 13:20:26 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 14:14:09 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 14:14:10 storageqe-109 dnf[2507288]: Updating Subscription Management repositories. Oct 8 14:14:10 storageqe-109 dnf[2507288]: Unable to read consumer identity Oct 8 14:14:10 storageqe-109 dnf[2507288]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-AppStream 722 kB/s | 2.8 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-AppStream-debuginfo 504 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-BaseOS 671 kB/s | 2.7 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-BaseOS-debuginfo 628 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-CRB 1.0 MB/s | 2.7 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-CRB-debuginfo 466 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-HighAvailability 854 kB/s | 2.8 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-HighAvailability-debuginfo 819 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-NFV 1.1 MB/s | 2.7 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-NFV-debuginfo 631 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-RT 1.0 MB/s | 2.7 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-RT-debuginfo 494 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-SAP 736 kB/s | 2.7 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-SAP-debuginfo 743 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-SAPHANA 1.0 MB/s | 2.7 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: beaker-SAPHANA-debuginfo 547 kB/s | 1.5 kB 00:00 Oct 8 14:14:10 storageqe-109 dnf[2507288]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 8 14:14:11 storageqe-109 dnf[2507288]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 8 14:14:11 storageqe-109 dnf[2507288]: Google Cloud CLI 3.1 kB/s | 1.4 kB 00:00 Oct 8 14:14:12 storageqe-109 dnf[2507288]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 8 14:14:13 storageqe-109 dnf[2507288]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 8 14:14:14 storageqe-109 dnf[2507288]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 8 14:14:14 storageqe-109 dnf[2507288]: Metadata cache created. Oct 8 14:14:14 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 14:14:14 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 14:48:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 14:48:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 14:48:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 15:39:15 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 15:39:15 storageqe-109 dnf[2507461]: Updating Subscription Management repositories. Oct 8 15:39:15 storageqe-109 dnf[2507461]: Unable to read consumer identity Oct 8 15:39:15 storageqe-109 dnf[2507461]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 15:39:15 storageqe-109 dnf[2507461]: Metadata cache refreshed recently. Oct 8 15:39:15 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 15:39:15 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 15:40:05 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 15:40:05 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 15:40:05 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 16:46:39 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 16:46:39 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 16:46:39 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 17:39:02 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 17:39:02 storageqe-109 dnf[2507733]: Updating Subscription Management repositories. Oct 8 17:39:02 storageqe-109 dnf[2507733]: Unable to read consumer identity Oct 8 17:39:02 storageqe-109 dnf[2507733]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-AppStream 543 kB/s | 2.8 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-AppStream-debuginfo 587 kB/s | 1.5 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-BaseOS 811 kB/s | 2.7 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-BaseOS-debuginfo 544 kB/s | 1.5 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-CRB 890 kB/s | 2.7 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-CRB-debuginfo 611 kB/s | 1.5 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-HighAvailability 939 kB/s | 2.8 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-HighAvailability-debuginfo 558 kB/s | 1.5 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-NFV 881 kB/s | 2.7 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-NFV-debuginfo 506 kB/s | 1.5 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-RT 807 kB/s | 2.7 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-RT-debuginfo 450 kB/s | 1.5 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-SAP 665 kB/s | 2.7 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-SAP-debuginfo 492 kB/s | 1.5 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-SAPHANA 763 kB/s | 2.7 kB 00:00 Oct 8 17:39:02 storageqe-109 dnf[2507733]: beaker-SAPHANA-debuginfo 552 kB/s | 1.5 kB 00:00 Oct 8 17:39:03 storageqe-109 dnf[2507733]: Beaker Client - RedHatEnterpriseLinux10 1.6 kB/s | 1.3 kB 00:00 Oct 8 17:39:03 storageqe-109 dnf[2507733]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 8 17:39:04 storageqe-109 dnf[2507733]: Google Cloud CLI 3.6 kB/s | 1.4 kB 00:00 Oct 8 17:39:05 storageqe-109 dnf[2507733]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 8 17:39:05 storageqe-109 dnf[2507733]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 8 17:39:06 storageqe-109 dnf[2507733]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 8 17:39:06 storageqe-109 dnf[2507733]: Metadata cache created. Oct 8 17:39:06 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 17:39:06 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 17:41:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 17:41:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 17:41:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 18:28:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 18:28:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 18:28:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 19:05:07 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 19:05:07 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 19:05:07 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 19:12:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 19:12:53 storageqe-109 dnf[2508051]: Updating Subscription Management repositories. Oct 8 19:12:53 storageqe-109 dnf[2508051]: Unable to read consumer identity Oct 8 19:12:53 storageqe-109 dnf[2508051]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 19:12:53 storageqe-109 dnf[2508051]: Metadata cache refreshed recently. Oct 8 19:12:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 19:12:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 20:14:31 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 20:14:31 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 20:14:31 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 20:37:31 storageqe-109 NetworkManager[995]: [1759970251.6272] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 8 20:37:31 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 8 20:37:31 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 8 20:37:41 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 8 20:44:53 storageqe-109 systemd[1078]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories... Oct 8 20:44:53 storageqe-109 systemd[1078]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories. Oct 8 20:52:43 storageqe-109 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Oct 8 20:52:43 storageqe-109 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Oct 8 20:52:43 storageqe-109 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Oct 8 20:54:13 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 20:54:14 storageqe-109 dnf[2508390]: Updating Subscription Management repositories. Oct 8 20:54:14 storageqe-109 dnf[2508390]: Unable to read consumer identity Oct 8 20:54:14 storageqe-109 dnf[2508390]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-AppStream 524 kB/s | 2.8 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-AppStream-debuginfo 512 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-BaseOS 816 kB/s | 2.7 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-BaseOS-debuginfo 538 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-CRB 754 kB/s | 2.7 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-CRB-debuginfo 557 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-HighAvailability 883 kB/s | 2.8 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-HighAvailability-debuginfo 531 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-NFV 671 kB/s | 2.7 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-NFV-debuginfo 485 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-RT 651 kB/s | 2.7 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-RT-debuginfo 534 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-SAP 609 kB/s | 2.7 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-SAP-debuginfo 459 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-SAPHANA 685 kB/s | 2.7 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: beaker-SAPHANA-debuginfo 462 kB/s | 1.5 kB 00:00 Oct 8 20:54:14 storageqe-109 dnf[2508390]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 8 20:54:15 storageqe-109 dnf[2508390]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 8 20:54:15 storageqe-109 dnf[2508390]: Google Cloud CLI 5.5 kB/s | 1.4 kB 00:00 Oct 8 20:54:16 storageqe-109 dnf[2508390]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 8 20:54:17 storageqe-109 dnf[2508390]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 8 20:54:17 storageqe-109 dnf[2508390]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 8 20:54:17 storageqe-109 dnf[2508390]: Metadata cache created. Oct 8 20:54:17 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 20:54:17 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 21:56:37 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 21:56:37 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 21:56:37 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 22:12:38 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 22:12:38 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 22:12:38 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 8 22:25:59 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 8 22:25:59 storageqe-109 dnf[2508693]: Updating Subscription Management repositories. Oct 8 22:25:59 storageqe-109 dnf[2508693]: Unable to read consumer identity Oct 8 22:25:59 storageqe-109 dnf[2508693]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 8 22:25:59 storageqe-109 dnf[2508693]: Metadata cache refreshed recently. Oct 8 22:25:59 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 8 22:25:59 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 8 23:35:23 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 8 23:35:23 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 8 23:35:23 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 00:00:05 storageqe-109 systemd[1]: Starting unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound... Oct 9 00:00:05 storageqe-109 systemd[1]: unbound-anchor.service: Deactivated successfully. Oct 9 00:00:05 storageqe-109 systemd[1]: Finished unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound. Oct 9 00:15:15 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 00:15:16 storageqe-109 dnf[2508972]: Updating Subscription Management repositories. Oct 9 00:15:16 storageqe-109 dnf[2508972]: Unable to read consumer identity Oct 9 00:15:16 storageqe-109 dnf[2508972]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-AppStream 664 kB/s | 2.8 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-AppStream-debuginfo 499 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-BaseOS 946 kB/s | 2.7 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-BaseOS-debuginfo 483 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-CRB 889 kB/s | 2.7 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-CRB-debuginfo 534 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-HighAvailability 866 kB/s | 2.8 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-HighAvailability-debuginfo 355 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-NFV 757 kB/s | 2.7 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-NFV-debuginfo 514 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-RT 649 kB/s | 2.7 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-RT-debuginfo 537 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-SAP 675 kB/s | 2.7 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-SAP-debuginfo 418 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-SAPHANA 886 kB/s | 2.7 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: beaker-SAPHANA-debuginfo 443 kB/s | 1.5 kB 00:00 Oct 9 00:15:16 storageqe-109 dnf[2508972]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 9 00:15:17 storageqe-109 dnf[2508972]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 9 00:15:17 storageqe-109 dnf[2508972]: Google Cloud CLI 4.1 kB/s | 1.4 kB 00:00 Oct 9 00:15:18 storageqe-109 dnf[2508972]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 9 00:15:19 storageqe-109 dnf[2508972]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 9 00:15:21 storageqe-109 dnf[2508972]: repo14 167 kB/s | 332 kB 00:01 Oct 9 00:15:21 storageqe-109 dnf[2508972]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 9 00:15:21 storageqe-109 dnf[2508972]: Metadata cache created. Oct 9 00:15:21 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 00:15:21 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 00:15:21 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 451ms CPU time, 84.2M memory peak. Oct 9 00:26:36 storageqe-109 systemd[1]: Starting logrotate.service - Rotate log files... Oct 9 00:26:36 storageqe-109 systemd[1]: logrotate.service: Deactivated successfully. Oct 9 00:26:36 storageqe-109 systemd[1]: Finished logrotate.service - Rotate log files. Oct 9 00:37:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 00:37:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 00:37:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 01:47:17 storageqe-109 systemd[1]: Stopping udisks2.service - Disk Manager... Oct 9 01:47:17 storageqe-109 udisksd[2506680]: udisks daemon version 2.10.90 exiting Oct 9 01:47:17 storageqe-109 systemd[1]: udisks2.service: Deactivated successfully. Oct 9 01:47:17 storageqe-109 systemd[1]: Stopped udisks2.service - Disk Manager. Oct 9 01:47:17 storageqe-109 systemd[1]: Starting udisks2.service - Disk Manager... Oct 9 01:47:17 storageqe-109 udisksd[2509309]: udisks daemon version 2.10.90 starting Oct 9 01:47:17 storageqe-109 systemd[1]: Started udisks2.service - Disk Manager. Oct 9 01:47:17 storageqe-109 udisksd[2509309]: Acquired the name org.freedesktop.UDisks2 on the system message bus Oct 9 01:49:21 storageqe-109 systemd[1]: NetworkManager-wait-online.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 systemd[1]: Stopped NetworkManager-wait-online.service - Network Manager Wait Online. Oct 9 01:49:21 storageqe-109 systemd[1]: Stopping NetworkManager-wait-online.service - Network Manager Wait Online... Oct 9 01:49:21 storageqe-109 systemd[1]: Stopping NetworkManager.service - Network Manager... Oct 9 01:49:21 storageqe-109 NetworkManager[995]: [1759988961.4601] caught SIGTERM, shutting down normally. Oct 9 01:49:21 storageqe-109 NetworkManager[995]: [1759988961.4608] dhcp4 (eno8303): canceled DHCP transaction Oct 9 01:49:21 storageqe-109 NetworkManager[995]: [1759988961.4608] dhcp4 (eno8303): activation: beginning transaction (timeout in 90 seconds) Oct 9 01:49:21 storageqe-109 NetworkManager[995]: [1759988961.4608] dhcp4 (eno8303): state changed no lease Oct 9 01:49:21 storageqe-109 NetworkManager[995]: [1759988961.4609] manager: NetworkManager state is now CONNECTED_SITE Oct 9 01:49:21 storageqe-109 NetworkManager[995]: [1759988961.4624] exiting (success) Oct 9 01:49:21 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 9 01:49:21 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 9 01:49:21 storageqe-109 systemd[1]: NetworkManager.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 systemd[1]: Stopped NetworkManager.service - Network Manager. Oct 9 01:49:21 storageqe-109 systemd[1]: NetworkManager.service: Consumed 52.390s CPU time, 15.9M memory peak, 2M memory swap peak. Oct 9 01:49:21 storageqe-109 systemd[1078]: Got disconnect on system bus. Oct 9 01:49:21 storageqe-109 dbus-broker[992]: Dispatched 1152869 messages @ 1(±2)μs / message. Oct 9 01:49:21 storageqe-109 nm-dispatcher[2509369]: Caught signal 15, shutting down... Oct 9 01:49:21 storageqe-109 systemd[1]: Stopping dbus-broker.service - D-Bus System Message Bus... Oct 9 01:49:21 storageqe-109 fwupd[93292]: 05:49:21.485 FuMain another service has claimed the dbus name org.freedesktop.fwupd Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: tpm2-abrmd.service: Main process exited, code=exited, status=74/IOERR Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: tpm2-abrmd.service: Failed with result 'exit-code'. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: lvm2-lvmdbusd.service: Main process exited, code=exited, status=1/FAILURE Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: lvm2-lvmdbusd.service: Failed with result 'exit-code'. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: lvm2-lvmdbusd.service: Consumed 31.398s CPU time, 46.7M memory peak, 12.5M memory swap peak. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: upower.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: polkit.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: polkit.service: Consumed 1.207s CPU time, 6.1M memory peak, 2.9M memory swap peak. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: dbus-broker.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Stopped dbus-broker.service - D-Bus System Message Bus. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: dbus-broker.service: Consumed 8.173s CPU time, 6.5M memory peak, 1.6M memory swap peak. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Starting dbus-broker.service - D-Bus System Message Bus... Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: udisks2.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Started dbus-broker.service - D-Bus System Message Bus. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 dbus-broker-launch[2509398]: Ready Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Starting NetworkManager.service - Network Manager... Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: fwupd.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: fwupd.service: Consumed 10.297s CPU time, 28.5M memory peak, 16.5M memory swap peak. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5371] NetworkManager (version 1.55.4-1.el10) is starting... (after a restart, boot:7f1eabbe-fb6f-41f6-829f-6247606b64b7) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5371] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/99-nvme-nbft-no-ignore-carrier.conf Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5392] manager[0x5593f390dc80]: monitoring kernel firmware directory '/lib/firmware'. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: stratisd.service: Deactivated successfully. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: stratisd.service: Consumed 25.323s CPU time, 17.6M memory peak, 1.9M memory swap peak. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5805] hostname: hostname: using hostnamed Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5805] hostname: static hostname changed from (none) to "storageqe-109.rhts.eng.pek2.redhat.com" Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5808] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5809] manager[0x5593f390dc80]: rfkill: Wi-Fi hardware radio set enabled Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5809] manager[0x5593f390dc80]: rfkill: WWAN hardware radio set enabled Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5817] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5817] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5817] manager: Networking is enabled by state file Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5818] settings: Loaded settings plugin: keyfile (internal) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5835] dhcp: init: Using DHCP client 'internal' Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5835] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5837] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5839] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5841] device (lo): Activation: starting connection 'lo' (8a6d3414-f0c6-4c4c-bcfd-a668a0804e90) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5843] device (eno8303): carrier: link connected Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5845] manager: (eno8303): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5846] manager: (eno8303): assume: will attempt to assume matching connection 'eno8303' (61a49902-271c-4fa4-b4d5-7eacebe644a6) (indicated) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5846] device (eno8303): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'assume') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5848] device (eno8303): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'assume') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5851] device (eno8303): Activation: starting connection 'eno8303' (61a49902-271c-4fa4-b4d5-7eacebe644a6) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5853] manager: (eno8403): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5855] device (eno8403): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5859] manager: (nvme_mp1): new Dummy device (/org/freedesktop/NetworkManager/Devices/4) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5860] device (nvme_mp1): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5862] device (nvme_mp1): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5864] device (nvme_mp1): Activation: starting connection 'nvme_mp1' (1eb983a0-714f-47bf-8b60-228e1f153b4a) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5866] manager: (nvme_mp2): new Dummy device (/org/freedesktop/NetworkManager/Devices/5) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5867] device (nvme_mp2): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5869] device (nvme_mp2): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5871] device (nvme_mp2): Activation: starting connection 'nvme_mp2' (f09d3b87-7412-47f6-876c-8473dbfe22ee) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5872] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager" Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Started NetworkManager.service - Network Manager. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5874] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5874] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5875] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5876] device (eno8303): state change: disconnected -> prepare (reason 'none', managed-type: 'assume') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5876] device (eno8303): state change: prepare -> config (reason 'none', managed-type: 'assume') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5877] device (nvme_mp1): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5878] device (nvme_mp1): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5878] device (nvme_mp1): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5879] device (nvme_mp2): state change: disconnected -> prepare (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5879] device (nvme_mp2): state change: prepare -> config (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5880] device (nvme_mp2): state change: config -> ip-config (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5881] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5883] device (eno8303): state change: config -> ip-config (reason 'none', managed-type: 'assume') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5883] dhcp4 (eno8303): activation: beginning transaction (timeout in 90 seconds) Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5884] device (nvme_mp1): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5886] device (nvme_mp2): state change: ip-config -> ip-check (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Starting NetworkManager-wait-online.service - Network Manager Wait Online... Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5936] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5938] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5941] device (lo): Activation: successful, device activated. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5946] device (nvme_mp1): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5947] device (nvme_mp1): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5948] manager: NetworkManager state is now CONNECTED_LOCAL Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5949] device (nvme_mp1): Activation: successful, device activated. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5952] device (nvme_mp2): state change: ip-check -> secondaries (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5953] device (nvme_mp2): state change: secondaries -> activated (reason 'none', managed-type: 'external') Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 NetworkManager[2509403]: [1759988961.5955] device (nvme_mp2): Activation: successful, device activated. Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 systemd[1]: Reloading iscsi.service - Login and scanning of iSCSI devices... Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? Oct 9 01:49:21 storageqe-109 stratisd[4947]: [2025-10-09T05:49:21Z WARN stratisd::dbus_api::connection] Failed to process D-Bus request: Failed to read/write data, disconnected from D-Bus? cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### test_device before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### will start test_udisks_info[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisks_info[npo2_linear] #### INFO: #### will start test_udisks_info_detailed[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisks_info_detailed[npo2_linear] #### INFO: #### will start test_udisksctl_smart_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_smart_operations[npo2_linear] #### INFO: #### will start test_udisksctl_filesystem_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_filesystem_operations[npo2_linear] #### INFO: #### will start test_udisksctl_power_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_power_operations[npo2_linear] #### INFO: #### will start test_udisksctl_unlock_lock_operations[npo2_linear] ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_unlock_lock_operations[npo2_linear] #### INFO: #### will start test_udisksctl_status ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_status #### INFO: #### will start test_udisksctl_dump ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_dump #### INFO: #### will start test_udisksctl_monitor ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_monitor #### INFO: #### will start test_udisksctl_loop_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_loop_operations #### INFO: #### will start test_udisksctl_help_commands ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_help_commands #### INFO: #### will start test_udisksctl_error_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_error_handling #### INFO: #### will start test_udisksctl_special_characters ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_special_characters #### INFO: #### will start test_udisksctl_concurrent_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_concurrent_operations #### INFO: #### will start test_udisksctl_large_output_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_large_output_handling #### INFO: #### will start test_udisksctl_timeout_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_timeout_handling #### INFO: #### will start test_udisksctl_mount_point_special_characters ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 01:57:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 01:57:24 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e on behalf of uid 0 Oct 9 01:57:24 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e r/w with ordered data mode. Quota mode: none. Oct 9 01:57:24 storageqe-109 rsyslogd[1103]: imjournal: 2433 messages lost due to rate-limiting (20000 allowed within 600 seconds) Oct 9 01:57:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 01:57:49 storageqe-109 systemd[1]: run-media-root-1e14de70\x2df2c5\x2d4bb3\x2d9200\x2dceb91609033e.mount: Deactivated successfully. Oct 9 01:57:49 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e (device 7:0 is not mounted) Oct 9 01:57:49 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 01:57:49 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e. Oct 9 01:58:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 01:58:14 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e on behalf of uid 0 Oct 9 01:58:14 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e r/w with ordered data mode. Quota mode: none. Oct 9 01:58:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 01:58:39 storageqe-109 systemd[1]: run-media-root-1e14de70\x2df2c5\x2d4bb3\x2d9200\x2dceb91609033e.mount: Deactivated successfully. Oct 9 01:58:39 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e. Oct 9 01:58:39 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e (device 7:0 is not mounted) Oct 9 01:58:39 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 01:59:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 01:59:04 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e on behalf of uid 0 Oct 9 01:59:04 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e r/w with ordered data mode. Quota mode: none. Oct 9 01:59:19 storageqe-109 sssd_kcm[2512212]: Shutting down (status = 0) Oct 9 01:59:19 storageqe-109 systemd[1]: sssd-kcm.service: Deactivated successfully. Oct 9 01:59:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 01:59:29 storageqe-109 systemd[1]: run-media-root-1e14de70\x2df2c5\x2d4bb3\x2d9200\x2dceb91609033e.mount: Deactivated successfully. Oct 9 01:59:29 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e. Oct 9 01:59:29 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e (device 7:0 is not mounted) Oct 9 01:59:29 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 01:59:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 01:59:54 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e r/w with ordered data mode. Quota mode: none. Oct 9 01:59:54 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e on behalf of uid 0 Oct 9 02:00:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:00:19 storageqe-109 systemd[1]: run-media-root-1e14de70\x2df2c5\x2d4bb3\x2d9200\x2dceb91609033e.mount: Deactivated successfully. Oct 9 02:00:19 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e. Oct 9 02:00:19 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e (device 7:0 is not mounted) Oct 9 02:00:19 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 02:00:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:00:44 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e r/w with ordered data mode. Quota mode: none. Oct 9 02:00:44 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e on behalf of uid 0 Oct 9 02:01:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:01:10 storageqe-109 systemd[1]: run-media-root-1e14de70\x2df2c5\x2d4bb3\x2d9200\x2dceb91609033e.mount: Deactivated successfully. Oct 9 02:01:10 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e. Oct 9 02:01:10 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e (device 7:0 is not mounted) Oct 9 02:01:10 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 02:01:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:01:35 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e r/w with ordered data mode. Quota mode: none. Oct 9 02:01:35 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e on behalf of uid 0 Oct 9 02:02:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:02:00 storageqe-109 systemd[1]: run-media-root-1e14de70\x2df2c5\x2d4bb3\x2d9200\x2dceb91609033e.mount: Deactivated successfully. Oct 9 02:02:00 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 1e14de70-f2c5-4bb3-9200-ceb91609033e. Oct 9 02:02:00 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1e14de70-f2c5-4bb3-9200-ceb91609033e (device 7:0 is not mounted) Oct 9 02:02:00 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 02:02:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:02:25 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_mount_test.img) Oct 9 02:02:25 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_mount_point_special_characters #### INFO: #### will start test_udisksctl_special_filesystems ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:02:30 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:02:30 storageqe-109 INFO: #### END test_udisksctl_mount_point_special_characters #### Oct 9 02:02:30 storageqe-109 INFO: #### will start test_udisksctl_special_filesystems ##### Oct 9 02:02:30 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:02:35 storageqe-109 kernel: loop0: detected capacity change from 0 to 102400 Oct 9 02:02:35 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /tmp/udisks_fs_test1.img) Oct 9 02:03:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:03:00 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/test label with on behalf of uid 0 Oct 9 02:03:00 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 6f84f28a-b205-40cc-aed2-0ac856444d39 r/w with ordered data mode. Quota mode: none. Oct 9 02:03:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:03:25 storageqe-109 systemd[1]: run-media-root-test\x20label\x20with.mount: Deactivated successfully. Oct 9 02:03:25 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/test label with (device 7:0 is not mounted) Oct 9 02:03:25 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 6f84f28a-b205-40cc-aed2-0ac856444d39. Oct 9 02:03:25 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 02:03:25 storageqe-109 kernel: loop1: detected capacity change from 0 to 102400 Oct 9 02:03:25 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /tmp/udisks_fs_test2.img) Oct 9 02:03:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:03:50 storageqe-109 kernel: EXT4-fs (loop1): mounting ext3 file system using the ext4 subsystem Oct 9 02:03:50 storageqe-109 kernel: EXT4-fs (loop1): mounted filesystem 6bbf5876-d48d-4398-8a30-4b99a7ea5271 r/w with ordered data mode. Quota mode: none. Oct 9 02:03:50 storageqe-109 udisksd[2509680]: Mounted /dev/loop1 at /run/media/root/test label with on behalf of uid 0 Oct 9 02:04:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:04:15 storageqe-109 systemd[1]: run-media-root-test\x20label\x20with.mount: Deactivated successfully. Oct 9 02:04:15 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/test label with (device 7:1 is not mounted) Oct 9 02:04:15 storageqe-109 udisksd[2509680]: Unmounted /dev/loop1 on behalf of uid 0 Oct 9 02:04:15 storageqe-109 kernel: EXT4-fs (loop1): unmounting filesystem 6bbf5876-d48d-4398-8a30-4b99a7ea5271. Oct 9 02:04:15 storageqe-109 kernel: loop2: detected capacity change from 0 to 102400 Oct 9 02:04:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /tmp/udisks_fs_test3.img) Oct 9 02:04:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:04:40 storageqe-109 kernel: EXT4-fs (loop2): mounting ext2 file system using the ext4 subsystem Oct 9 02:04:40 storageqe-109 kernel: EXT4-fs (loop2): mounted filesystem fc3c30c1-ef01-4a7a-b4fb-76254ec5cbd2 r/w without journal. Quota mode: none. Oct 9 02:04:40 storageqe-109 udisksd[2509680]: Mounted /dev/loop2 at /run/media/root/test label with on behalf of uid 0 Oct 9 02:05:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:05:05 storageqe-109 systemd[1]: run-media-root-test\x20label\x20with.mount: Deactivated successfully. Oct 9 02:05:05 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/test label with (device 7:2 is not mounted) Oct 9 02:05:05 storageqe-109 udisksd[2509680]: Unmounted /dev/loop2 on behalf of uid 0 Oct 9 02:05:05 storageqe-109 kernel: EXT4-fs (loop2): unmounting filesystem fc3c30c1-ef01-4a7a-b4fb-76254ec5cbd2. Oct 9 02:05:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:05:31 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_fs_test1.img) Oct 9 02:05:31 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 02:05:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:05:56 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /tmp/udisks_fs_test2.img) Oct 9 02:05:56 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 02:06:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:06:21 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /tmp/udisks_fs_test3.img) Oct 9 02:06:21 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_special_filesystems #### INFO: #### will start test_udisksctl_unicode_and_encoding ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:06:26 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:06:26 storageqe-109 INFO: #### END test_udisksctl_special_filesystems #### Oct 9 02:06:26 storageqe-109 INFO: #### will start test_udisksctl_unicode_and_encoding ##### Oct 9 02:06:26 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_unicode_and_encoding #### INFO: #### will start test_udisksctl_path_traversal_security ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:06:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:06:36 storageqe-109 INFO: #### END test_udisksctl_unicode_and_encoding #### Oct 9 02:06:36 storageqe-109 INFO: #### will start test_udisksctl_path_traversal_security ##### Oct 9 02:06:36 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_path_traversal_security #### INFO: #### will start test_udisksctl_special_filesystem_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:06:47 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:06:47 storageqe-109 INFO: #### END test_udisksctl_path_traversal_security #### Oct 9 02:06:47 storageqe-109 INFO: #### will start test_udisksctl_special_filesystem_operations ##### Oct 9 02:06:47 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:06:52 storageqe-109 kernel: loop0: detected capacity change from 0 to 204800 Oct 9 02:06:52 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /tmp/udisks_special_fs_test.img) Oct 9 02:07:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:07:17 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/c7f9c36e-3ae8-49f0-9036-b5456f615a65 on behalf of uid 0 Oct 9 02:07:17 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem c7f9c36e-3ae8-49f0-9036-b5456f615a65 r/w with ordered data mode. Quota mode: none. Oct 9 02:07:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:07:42 storageqe-109 systemd[1]: run-media-root-c7f9c36e\x2d3ae8\x2d49f0\x2d9036\x2db5456f615a65.mount: Deactivated successfully. Oct 9 02:07:42 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem c7f9c36e-3ae8-49f0-9036-b5456f615a65. Oct 9 02:07:42 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/c7f9c36e-3ae8-49f0-9036-b5456f615a65 (device 7:0 is not mounted) Oct 9 02:07:42 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 02:07:47 storageqe-109 chronyd[999]: Selected source 10.2.32.37 Oct 9 02:08:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:08:07 storageqe-109 kernel: EXT4-fs (loop0): mounting ext3 file system using the ext4 subsystem Oct 9 02:08:07 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem a0c78705-adc2-4b20-8fe5-acfa5d05f5f7 r/w with ordered data mode. Quota mode: none. Oct 9 02:08:07 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/a0c78705-adc2-4b20-8fe5-acfa5d05f5f7 on behalf of uid 0 Oct 9 02:08:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:08:32 storageqe-109 systemd[1]: run-media-root-a0c78705\x2dadc2\x2d4b20\x2d8fe5\x2dacfa5d05f5f7.mount: Deactivated successfully. Oct 9 02:08:32 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem a0c78705-adc2-4b20-8fe5-acfa5d05f5f7. Oct 9 02:08:32 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/a0c78705-adc2-4b20-8fe5-acfa5d05f5f7 (device 7:0 is not mounted) Oct 9 02:08:32 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 02:08:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:08:57 storageqe-109 kernel: EXT4-fs (loop0): mounting ext2 file system using the ext4 subsystem Oct 9 02:08:57 storageqe-109 kernel: EXT4-fs (loop0): mounted filesystem 40bff768-14b3-4892-a8ff-c27fdad05b4a r/w without journal. Quota mode: none. Oct 9 02:08:57 storageqe-109 udisksd[2509680]: Mounted /dev/loop0 at /run/media/root/40bff768-14b3-4892-a8ff-c27fdad05b4a on behalf of uid 0 Oct 9 02:09:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:09:22 storageqe-109 systemd[1]: run-media-root-40bff768\x2d14b3\x2d4892\x2da8ff\x2dc27fdad05b4a.mount: Deactivated successfully. Oct 9 02:09:22 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/40bff768-14b3-4892-a8ff-c27fdad05b4a (device 7:0 is not mounted) Oct 9 02:09:22 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0 on behalf of uid 0 Oct 9 02:09:22 storageqe-109 kernel: EXT4-fs (loop0): unmounting filesystem 40bff768-14b3-4892-a8ff-c27fdad05b4a. Oct 9 02:09:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:09:47 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_special_fs_test.img) Oct 9 02:09:47 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_special_filesystem_operations #### INFO: #### will start test_udisksctl_comprehensive_command_coverage ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:09:52 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:09:52 storageqe-109 INFO: #### END test_udisksctl_special_filesystem_operations #### Oct 9 02:09:52 storageqe-109 INFO: #### will start test_udisksctl_comprehensive_command_coverage ##### Oct 9 02:09:52 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_udisksctl_comprehensive_command_coverage #### Oct 9 02:10:03 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 02:10:03 storageqe-109 INFO: #### END test_udisksctl_comprehensive_command_coverage #### Oct 9 02:10:04 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:10:05 storageqe-109 INFO: #### test_device after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 9 02:10:06 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 9 02:10:06 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 9 02:10:06 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 9 02:10:16 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_init_nvme ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:10:17 storageqe-109 INFO: #### will start test_init_nvme ##### Oct 9 02:10:17 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Namespace object for /dev/nvme0n1: :1.10 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7f8acbf24680> Oct 9 02:10:23 storageqe-109 INFO: Namespace object for /dev/nvme0n1: :1.10 /org/freedesktop/UDisks2/block_devices/nvme0n1 at 0x7f8acbf24680> INFO: Drive path for /dev/nvme0n1: /org/freedesktop/UDisks2/drives/SAMSUNG_MZPLJ1T6HBJR_00007_S55JNC0T900418 INFO: NVMe controller object: :1.10 /org/freedesktop/UDisks2/drives/SAMSUNG_MZPLJ1T6HBJR_00007_S55JNC0T900418 at 0x7f8acbf24290> INFO: NVMe manager interface: :1.10 /org/freedesktop/UDisks2/Manager at 0x7f8acbf246b0> implementing 'org.freedesktop.UDisks2.Manager.NVMe' at 0x7f8acbf242f0> Oct 9 02:10:24 storageqe-109 INFO: Drive path for /dev/nvme0n1: /org/freedesktop/UDisks2/drives/SAMSUNG_MZPLJ1T6HBJR_00007_S55JNC0T900418 Oct 9 02:10:24 storageqe-109 INFO: NVMe controller object: :1.10 /org/freedesktop/UDisks2/drives/SAMSUNG_MZPLJ1T6HBJR_00007_S55JNC0T900418 at 0x7f8acbf24290> Oct 9 02:10:24 storageqe-109 INFO: NVMe manager interface: :1.10 /org/freedesktop/UDisks2/Manager at 0x7f8acbf246b0> implementing 'org.freedesktop.UDisks2.Manager.NVMe' at 0x7f8acbf242f0> INFO: nvme ns NSID 1 Oct 9 02:10:26 storageqe-109 INFO: nvme ns NSID 1 INFO: nvme ns NGUID 35354a30549004180025384300000001 Oct 9 02:10:28 storageqe-109 INFO: nvme ns NGUID 35354a30549004180025384300000001 INFO: nvme ns EUI64 0000000000000000 Oct 9 02:10:30 storageqe-109 INFO: nvme ns EUI64 0000000000000000 INFO: nvme ns UUID Oct 9 02:10:32 storageqe-109 INFO: nvme ns UUID INFO: nvme ns WWN eui.35354a30549004180025384300000001 Oct 9 02:10:34 storageqe-109 INFO: nvme ns WWN eui.35354a30549004180025384300000001 INFO: nvme ns LBAFormats dbus.Array([dbus.Struct((dbus.UInt16(512), dbus.UInt16(0), dbus.Byte(2)), signature=None), dbus.Struct((dbus.UInt16(512), dbus.UInt16(8), dbus.Byte(4)), signature=None), dbus.Struct((dbus.UInt16(4096), dbus.UInt16(0), dbus.Byte(1)), signature=None), dbus.Struct((dbus.UInt16(4096), dbus.UInt16(8), dbus.Byte(3)), signature=None), dbus.Struct((dbus.UInt16(4096), dbus.UInt16(64), dbus.Byte(4)), signature=None)], signature=dbus.Signature('(qqy)'), variant_level=1) Oct 9 02:10:36 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 9 02:10:36 storageqe-109 INFO: nvme ns LBAFormats dbus.Array([dbus.Struct((dbus.UInt16(512), dbus.UInt16(0), dbus.Byte(2)), signature=None), dbus.Struct((dbus.UInt16(512), dbus.UInt16(8), dbus.Byte(4)), signature=None), dbus.Struct((dbus.UInt16(4096), dbus.UInt16(0), dbus.Byte(1)), signature=None), dbus.Struct((dbus.UInt16(4096), dbus.UInt16(8), dbus.Byte(3)), signature=None), dbus.Struct((dbus.UInt16(4096), dbus.UInt16(64), dbus.Byte(4)), signature=None)], signature=dbus.Signature('(qqy)'), variant_level=1) INFO: nvme ns FormattedLBASize dbus.Struct((dbus.UInt16(512), dbus.UInt16(0), dbus.Byte(2)), signature=None, variant_level=1) Oct 9 02:10:38 storageqe-109 INFO: nvme ns FormattedLBASize dbus.Struct((dbus.UInt16(512), dbus.UInt16(0), dbus.Byte(2)), signature=None, variant_level=1) INFO: nvme ns NamespaceSize 3125627568 Oct 9 02:10:40 storageqe-109 INFO: nvme ns NamespaceSize 3125627568 INFO: nvme ns NamespaceCapacity 3125627568 Oct 9 02:10:42 storageqe-109 INFO: nvme ns NamespaceCapacity 3125627568 INFO: nvme ns NamespaceUtilization 3125627568 Oct 9 02:10:44 storageqe-109 INFO: nvme ns NamespaceUtilization 3125627568 INFO: nvme ns FormatPercentRemaining 0 Oct 9 02:10:46 storageqe-109 INFO: nvme ns FormatPercentRemaining 0 INFO: nvme controller State live Oct 9 02:10:48 storageqe-109 INFO: nvme controller State live INFO: nvme controller ControllerID 65 Oct 9 02:10:50 storageqe-109 INFO: nvme controller ControllerID 65 INFO: nvme controller SubsystemNQN dbus.Array([dbus.Byte(110), dbus.Byte(113), dbus.Byte(110), dbus.Byte(46), dbus.Byte(49), dbus.Byte(57), dbus.Byte(57), dbus.Byte(52), dbus.Byte(45), dbus.Byte(49), dbus.Byte(49), dbus.Byte(46), dbus.Byte(99), dbus.Byte(111), dbus.Byte(109), dbus.Byte(46), dbus.Byte(115), dbus.Byte(97), dbus.Byte(109), dbus.Byte(115), dbus.Byte(117), dbus.Byte(110), dbus.Byte(103), dbus.Byte(58), dbus.Byte(110), dbus.Byte(118), dbus.Byte(109), dbus.Byte(101), dbus.Byte(58), dbus.Byte(80), dbus.Byte(77), dbus.Byte(49), dbus.Byte(55), dbus.Byte(51), dbus.Byte(51), dbus.Byte(58), dbus.Byte(72), dbus.Byte(72), dbus.Byte(72), dbus.Byte(76), dbus.Byte(58), dbus.Byte(83), dbus.Byte(53), dbus.Byte(53), dbus.Byte(74), dbus.Byte(78), dbus.Byte(67), dbus.Byte(48), dbus.Byte(84), dbus.Byte(57), dbus.Byte(48), dbus.Byte(48), dbus.Byte(52), dbus.Byte(49), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 9 02:10:52 storageqe-109 INFO: nvme controller SubsystemNQN dbus.Array([dbus.Byte(110), dbus.Byte(113), dbus.Byte(110), dbus.Byte(46), dbus.Byte(49), dbus.Byte(57), dbus.Byte(57), dbus.Byte(52), dbus.Byte(45), dbus.Byte(49), dbus.Byte(49), dbus.Byte(46), dbus.Byte(99), dbus.Byte(111), dbus.Byte(109), dbus.Byte(46), dbus.Byte(115), dbus.Byte(97), dbus.Byte(109), dbus.Byte(115), dbus.Byte(117), dbus.Byte(110), dbus.Byte(103), dbus.Byte(58), dbus.Byte(110), dbus.Byte(118), dbus.Byte(109), dbus.Byte(101), dbus.Byte(58), dbus.Byte(80), dbus.Byte(77), dbus.Byte(49), dbus.Byte(55), dbus.Byte(51), dbus.Byte(51), dbus.Byte(58), dbus.Byte(72), dbus.Byte(72), dbus.Byte(72), dbus.Byte(76), dbus.Byte(58), dbus.Byte(83), dbus.Byte(53), dbus.Byte(53), dbus.Byte(74), dbus.Byte(78), dbus.Byte(67), dbus.Byte(48), dbus.Byte(84), dbus.Byte(57), dbus.Byte(48), dbus.Byte(48), dbus.Byte(52), dbus.Byte(49), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: nvme controller FGUID Oct 9 02:10:54 storageqe-109 INFO: nvme controller FGUID INFO: nvme controller NVMeRevision 1.3 Oct 9 02:10:56 storageqe-109 INFO: nvme controller NVMeRevision 1.3 INFO: nvme controller UnallocatedCapacity 0 Oct 9 02:10:58 storageqe-109 INFO: nvme controller UnallocatedCapacity 0 INFO: nvme controller SmartUpdated 1759990231 Oct 9 02:11:00 storageqe-109 INFO: nvme controller SmartUpdated 1759990231 INFO: nvme controller SmartCriticalWarning dbus.Array([], signature=dbus.Signature('s'), variant_level=1) Oct 9 02:11:02 storageqe-109 INFO: nvme controller SmartCriticalWarning dbus.Array([], signature=dbus.Signature('s'), variant_level=1) INFO: nvme controller SmartPowerOnHours 11981 Oct 9 02:11:04 storageqe-109 INFO: nvme controller SmartPowerOnHours 11981 INFO: nvme controller SmartTemperature 322 Oct 9 02:11:06 storageqe-109 INFO: nvme controller SmartTemperature 322 INFO: nvme controller SmartSelftestStatus success Oct 9 02:11:08 storageqe-109 INFO: nvme controller SmartSelftestStatus success INFO: nvme controller SmartSelftestPercentRemaining -1 Oct 9 02:11:10 storageqe-109 INFO: nvme controller SmartSelftestPercentRemaining -1 INFO: nvme controller SanitizeStatus success Oct 9 02:11:12 storageqe-109 INFO: nvme controller SanitizeStatus success INFO: nvme controller SanitizePercentRemaining -1 Oct 9 02:11:14 storageqe-109 INFO: nvme controller SanitizePercentRemaining -1 INFO: start test test_format Oct 9 02:11:15 storageqe-109 INFO: start test test_format Oct 9 02:11:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:11:43 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 02:12:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:12:08 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 02:12:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:12:34 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 02:13:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:13:00 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 02:13:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:13:25 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 02:13:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:13:51 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: END test test_format INFO: start test test_SmartUpdate Oct 9 02:13:52 storageqe-109 INFO: END test test_format Oct 9 02:13:52 storageqe-109 INFO: start test test_SmartUpdate INFO: END test test_SmartUpdate INFO: start test test_get_attr INFO: avail_spare d INFO: avail_spare d INFO: percent_used  INFO: ctrl_busy_time 1712 INFO: power_cycles 2399 INFO: unsafe_shutdowns 1196 INFO: media_errors 2328 INFO: num_err_log_entries 2330 INFO: temp_sensors dbus.Array([dbus.UInt16(322), dbus.UInt16(321), dbus.UInt16(322), dbus.UInt16(0), dbus.UInt16(0), dbus.UInt16(0), dbus.UInt16(0), dbus.UInt16(0)], signature=dbus.Signature('q'), variant_level=1) INFO: warning_temp_time 0 INFO: critical_temp_time 0 INFO: END test test_get_attr INFO: start test test_self_test Oct 9 02:13:54 storageqe-109 INFO: END test test_SmartUpdate Oct 9 02:13:54 storageqe-109 INFO: start test test_get_attr Oct 9 02:13:54 storageqe-109 INFO: avail_spare d Oct 9 02:13:54 storageqe-109 INFO: avail_spare d Oct 9 02:13:54 storageqe-109 INFO: percent_used #002 Oct 9 02:13:54 storageqe-109 INFO: ctrl_busy_time 1712 Oct 9 02:13:54 storageqe-109 INFO: power_cycles 2399 Oct 9 02:13:54 storageqe-109 INFO: unsafe_shutdowns 1196 Oct 9 02:13:54 storageqe-109 INFO: media_errors 2328 Oct 9 02:13:54 storageqe-109 INFO: num_err_log_entries 2330 Oct 9 02:13:54 storageqe-109 INFO: temp_sensors dbus.Array([dbus.UInt16(322), dbus.UInt16(321), dbus.UInt16(322), dbus.UInt16(0), dbus.UInt16(0), dbus.UInt16(0), dbus.UInt16(0), dbus.UInt16(0)], signature=dbus.Signature('q'), variant_level=1) Oct 9 02:13:54 storageqe-109 INFO: warning_temp_time 0 Oct 9 02:13:54 storageqe-109 INFO: critical_temp_time 0 Oct 9 02:13:54 storageqe-109 INFO: END test test_get_attr Oct 9 02:13:54 storageqe-109 INFO: start test test_self_test Oct 9 02:14:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: SmartSelftestStatus success Oct 9 02:14:20 storageqe-109 INFO: SmartSelftestStatus success INFO: SmartSelftestPercentRemaining -1 Oct 9 02:14:21 storageqe-109 INFO: SmartSelftestPercentRemaining -1 Oct 9 02:14:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: SmartSelftestStatus success Oct 9 02:14:47 storageqe-109 INFO: SmartSelftestStatus success INFO: SmartSelftestPercentRemaining -1 INFO: END test test_self_test INFO: start test test_manger Oct 9 02:14:48 storageqe-109 INFO: SmartSelftestPercentRemaining -1 Oct 9 02:14:48 storageqe-109 INFO: END test test_self_test Oct 9 02:14:48 storageqe-109 INFO: start test test_manger INFO: hostnqn nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 INFO: hostid 4c4c4544-0039-5210-804d-c6c04f463534 Oct 9 02:14:50 storageqe-109 INFO: hostnqn nqn.2014-08.org.nvmexpress:uuid:4c4c4544-0039-5210-804d-c6c04f463534 Oct 9 02:14:50 storageqe-109 INFO: hostid 4c4c4544-0039-5210-804d-c6c04f463534 INFO: END test test_manger Oct 9 02:14:53 storageqe-109 INFO: END test test_manger INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_init_nvme #### INFO: #### will start test_ata_driver ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:14:59 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:14:59 storageqe-109 INFO: #### END test_init_nvme #### Oct 9 02:14:59 storageqe-109 INFO: #### will start test_ata_driver ##### Oct 9 02:14:59 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_ata_driver #### INFO: #### will start test_vdo ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:15:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:15:11 storageqe-109 INFO: #### END test_ata_driver #### Oct 9 02:15:11 storageqe-109 INFO: #### will start test_vdo ##### Oct 9 02:15:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:15:27 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 9 02:15:27 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 9 02:15:27 storageqe-109 kernel: loop0: Oct 9 02:15:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:16:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:16:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:17:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:17:09 storageqe-109 UDS/vdoformat[2514967]: INFO (vdoformat/2514967) Using 2 indexing zones for concurrency. Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo23:lvm: loading device '253:4' Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo23:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo23:lvm: starting device '253:4' Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:physQ0: VDO commencing normal operation Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:journa: Setting UDS index target state to online Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: creating index: 253:3 Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: Using 2 indexing zones for concurrency. Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' started Oct 9 02:17:09 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:17:10 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:17:10 storageqe-109 systemd[1]: Started dm-event.service - Device-mapper event daemon. Oct 9 02:17:10 storageqe-109 dmeventd[2515002]: dmeventd ready for processing. Oct 9 02:17:10 storageqe-109 dmeventd[2515002]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: VDOPool /org/freedesktop/UDisks2/lvm/vg03/udisks_test_vdopool Oct 9 02:17:11 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/vg03/udisks_test_vdopool INFO: OperatingMode normal Oct 9 02:17:12 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 9 02:17:13 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 9 02:17:14 storageqe-109 INFO: IndexState online INFO: UsedSize 4988477440 Oct 9 02:17:15 storageqe-109 INFO: UsedSize 4988477440 INFO: Compression 1 Oct 9 02:17:16 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 9 02:17:17 storageqe-109 INFO: Deduplication 1 Oct 9 02:17:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 9 02:17:42 storageqe-109 dmeventd[2515002]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: beginning save (vcn 18446744073709551615) Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:17:42 storageqe-109 dmeventd[2515002]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:17:42 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: finished save (vcn 18446744073709551615) Oct 9 02:18:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:18:08 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 02:18:08 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 9 02:18:08 storageqe-109 dmeventd[2515002]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:18:08 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:18:08 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:18:08 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:18:08 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is disabled Oct 9 02:18:08 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:18:08 storageqe-109 dmeventd[2515002]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:18:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 9 02:18:35 storageqe-109 dmeventd[2515002]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: loading or rebuilding index: 253:3 Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is disabled Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: Using 2 indexing zones for concurrency. Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:18:35 storageqe-109 dmeventd[2515002]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:18:35 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:dedupe: loaded index from chapter 0 through chapter 0 Oct 9 02:19:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:19:01 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 1741824 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 02:19:01 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 9 02:19:01 storageqe-109 dmeventd[2515002]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:19:01 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:19:01 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:19:01 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:19:01 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 9 02:19:01 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:19:01 storageqe-109 dmeventd[2515002]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:19:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 2266112 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: Preparing to resize physical to 2266112 Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: Done preparing to resize physical Oct 9 02:19:29 storageqe-109 dmeventd[2515002]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: Physical block count was 1741824, now 2266112 Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 9 02:19:29 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:19:29 storageqe-109 dmeventd[2515002]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: the 9281994752 8589934592 Oct 9 02:19:32 storageqe-109 INFO: the 9281994752 8589934592 INFO:before lv vdo 78622228480 Oct 9 02:19:33 storageqe-109 journal: INFO:before lv vdo 78622228480 Oct 9 02:19:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: table line: V4 /dev/dm-3 2266112 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: preparing to modify device '253:4' Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: Preparing to resize logical to 95974656 Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: Done preparing to resize logical Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: Resizing logical to 95974656 Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: Logical blocks now 95974656 Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:19:58 storageqe-109 dmeventd[2515002]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: resuming device '253:4' Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo: dm_vdo23:packer: compression is enabled Oct 9 02:19:58 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' resumed Oct 9 02:19:58 storageqe-109 dmeventd[2515002]: Monitoring VDO pool vg03-udisks_test_vdopool-vpool. INFO: after lv vdo 393111142400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 7 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 63 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 4872976 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 4191472 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 9 02:20:00 storageqe-109 INFO: after lv vdo 393111142400 Oct 9 02:20:00 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 9 02:20:00 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 9 02:20:00 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 7 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics maxVIOs 63 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 4872976 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 4191472 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 23 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 95974656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9064448 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics instance 23 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 95974656 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9064448 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410015090 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 7 INFO: vdo.GetStatistics overheadBlocksUsed 1218244 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 54 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410015090 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 7 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 1218244 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics usedPercent 54 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 9 02:20:01 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2266112 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2266112 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 2 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 2 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 9 02:20:02 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 9 02:20:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:20:27 storageqe-109 dmeventd[2515002]: No longer monitoring VDO pool vg03-udisks_test_vdopool-vpool. Oct 9 02:20:27 storageqe-109 kernel: device-mapper: vdo23:lvm: suspending device '253:4' Oct 9 02:20:27 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' suspended Oct 9 02:20:27 storageqe-109 kernel: device-mapper: vdo23:lvm: stopping device '253:4' Oct 9 02:20:27 storageqe-109 kernel: device-mapper: vdo23:lvm: device '253:4' stopped Oct 9 02:20:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:21:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:21:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:21:49 storageqe-109 kernel: loop0: Oct 9 02:22:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:22:14 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 9 02:22:14 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_vdo #### INFO: #### will start test_bz1567992_luks_resize ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:22:20 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:22:20 storageqe-109 INFO: #### END test_vdo #### Oct 9 02:22:20 storageqe-109 INFO: #### will start test_bz1567992_luks_resize ##### Oct 9 02:22:20 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:22:26 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 02:22:26 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 9 02:22:26 storageqe-109 kernel: loop0: Oct 9 02:22:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks1'}, signature=dbus.Signature('sv')) Oct 9 02:22:52 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks1'}, signature=dbus.Signature('sv')) Oct 9 02:23:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:23:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:24:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: HintEncryptionType Oct 9 02:24:15 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 2097152 Oct 9 02:24:16 storageqe-109 INFO: MetadataSize 2097152 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 9 02:24:17 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 9 02:24:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: changed passwd to redhatredhat Oct 9 02:24:48 storageqe-109 INFO: changed passwd to redhatredhat Oct 9 02:25:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:25:13 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:25:13 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:25:13 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:25:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:25:41 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:26:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:26:08 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:26:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: changed passwd to test123456 Oct 9 02:26:38 storageqe-109 INFO: changed passwd to test123456 Oct 9 02:27:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:27:03 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:27:03 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:27:03 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:27:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:27:30 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:27:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:27:58 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:28:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:28:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:28:53 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 02:28:53 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:29:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:29:20 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:29:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:29:48 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:30:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:30:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:30:43 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 02:30:43 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:31:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:31:10 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:31:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:31:38 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:32:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:32:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:32:33 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 02:32:33 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 9 02:32:33 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 9 02:32:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:32:58 storageqe-109 stratisd[2509653]: [2025-10-09T06:32:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:32:58 storageqe-109 stratisd[2509653]: [2025-10-09T06:32:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:33:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:33:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:33:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:33:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:33:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:33:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: HintEncryptionType Oct 9 02:33:50 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 9 02:33:51 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 9 02:33:52 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 9 02:33:53 storageqe-109 INFO: foramt to luks2 Oct 9 02:33:53 storageqe-109 INFO: foramt to pbkdf2 Oct 9 02:34:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: changed passwd to redhatredhat Oct 9 02:34:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:34:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:34:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:34:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:34:24 storageqe-109 INFO: changed passwd to redhatredhat Oct 9 02:34:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:34:49 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:34:49 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:34:49 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:35:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:35:16 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:35:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:35:43 storageqe-109 stratisd[2509653]: [2025-10-09T06:35:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:35:43 storageqe-109 stratisd[2509653]: [2025-10-09T06:35:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:35:44 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:36:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: changed passwd to test123456 Oct 9 02:36:17 storageqe-109 stratisd[2509653]: [2025-10-09T06:36:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:36:17 storageqe-109 stratisd[2509653]: [2025-10-09T06:36:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:36:17 storageqe-109 INFO: changed passwd to test123456 Oct 9 02:36:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:36:42 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:36:42 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:36:42 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:37:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:37:09 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:37:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:37:36 storageqe-109 stratisd[2509653]: [2025-10-09T06:37:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:37:36 storageqe-109 stratisd[2509653]: [2025-10-09T06:37:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:37:36 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:38:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:38:09 storageqe-109 stratisd[2509653]: [2025-10-09T06:38:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:38:09 storageqe-109 stratisd[2509653]: [2025-10-09T06:38:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:38:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:38:34 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 02:38:34 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:38:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:39:01 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:39:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:39:28 storageqe-109 stratisd[2509653]: [2025-10-09T06:39:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:39:28 storageqe-109 stratisd[2509653]: [2025-10-09T06:39:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:39:29 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:39:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:40:02 storageqe-109 stratisd[2509653]: [2025-10-09T06:40:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:40:02 storageqe-109 stratisd[2509653]: [2025-10-09T06:40:02Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:40:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:40:27 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 02:40:27 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:40:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:40:54 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 02:41:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:41:21 storageqe-109 stratisd[2509653]: [2025-10-09T06:41:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:41:21 storageqe-109 stratisd[2509653]: [2025-10-09T06:41:21Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:41:21 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 02:41:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:41:54 storageqe-109 stratisd[2509653]: [2025-10-09T06:41:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:41:54 storageqe-109 stratisd[2509653]: [2025-10-09T06:41:54Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:42:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:42:20 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 9 02:42:20 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:42:20 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'pbkdf2', 'encrypt.iterations': dbus.UInt32(1000), 'encrypt.threads': dbus.UInt32(5), 'encrypt.time': dbus.UInt32(1000)}, signature=dbus.Signature('sv')) Oct 9 02:42:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:42:45 storageqe-109 stratisd[2509653]: [2025-10-09T06:42:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:42:45 storageqe-109 stratisd[2509653]: [2025-10-09T06:42:45Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:43:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:43:10 storageqe-109 stratisd[2509653]: [2025-10-09T06:43:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:43:10 storageqe-109 stratisd[2509653]: [2025-10-09T06:43:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:43:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: HintEncryptionType Oct 9 02:43:36 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 9 02:43:37 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 9 02:43:38 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to pbkdf2 Oct 9 02:43:39 storageqe-109 INFO: foramt to luks2 Oct 9 02:43:39 storageqe-109 INFO: foramt to pbkdf2 INFO: before convert luks dump info {'keyslots': {'0': {'type': 'luks2', 'key_size': 64, 'af': {'type': 'luks1', 'stripes': 4000, 'hash': 'sha256'}, 'area': {'type': 'raw', 'offset': '32768', 'size': '258048', 'encryption': 'aes-xts-plain64', 'key_size': 64}, 'kdf': {'type': 'pbkdf2', 'hash': 'sha256', 'iterations': 1000, 'salt': 'syTaTLDwW5TftlNwtmGCU60Ic+4pOCgsuR5RBcbe2dM='}}}, 'tokens': {}, 'segments': {'0': {'type': 'crypt', 'offset': '16777216', 'size': 'dynamic', 'iv_tweak': '0', 'encryption': 'aes-xts-plain64', 'sector_size': 512}}, 'digests': {'0': {'type': 'pbkdf2', 'keyslots': ['0'], 'segments': ['0'], 'hash': 'sha256', 'iterations': 1000, 'salt': 'zU2lb6BLhzEUSOliBxM/eDPyLwERQB2xpUEVoczY7fo=', 'digest': 'aOQzCITYo0QxTAXadtNdvga58qrDOKomt0zAQT3sjrk='}}, 'config': {'json_size': '12288', 'keyslots_size': '16744448'}} Oct 9 02:44:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:44:06 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:44:06 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:44:06 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:44:06 storageqe-109 INFO: before convert luks dump info {'keyslots': {'0': {'type': 'luks2', 'key_size': 64, 'af': {'type': 'luks1', 'stripes': 4000, 'hash': 'sha256'}, 'area': {'type': 'raw', 'offset': '32768', 'size': '258048', 'encryption': 'aes-xts-plain64', 'key_size': 64}, 'kdf': {'type': 'pbkdf2', 'hash': 'sha256', 'iterations': 1000, 'salt': 'syTaTLDwW5TftlNwtmGCU60Ic+4pOCgsuR5RBcbe2dM='}}}, 'tokens': {}, 'segments': {'0': {'type': 'crypt', 'offset': '16777216', 'size': 'dynamic', 'iv_tweak': '0', 'encryption': 'aes-xts-plain64', 'sector_size': 512}}, 'digests': {'0': {'type': 'pbkdf2', 'keyslots': ['0'], 'segments': ['0'], 'hash': 'sha256', 'iterations': 1000, 'salt': 'zU2lb6BLhzEUSOliBxM/eDPyLwERQB2xpUEVoczY7fo=', 'digest': 'aOQzCITYo0QxTAXadtNdvga58qrDOKomt0zAQT3sjrk='}}, 'config': {'json_size': '12288', 'keyslots_size': '16744448'}} INFO: will convert to luks1 Oct 9 02:44:36 storageqe-109 INFO: will convert to luks1 INFO: will convert to luks2 Oct 9 02:45:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:45:01 storageqe-109 INFO: will convert to luks2 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2i', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 9 02:45:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:45:26 storageqe-109 stratisd[2509653]: [2025-10-09T06:45:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:45:26 storageqe-109 stratisd[2509653]: [2025-10-09T06:45:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:45:26 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'test123456', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2i', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 9 02:45:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:45:58 storageqe-109 stratisd[2509653]: [2025-10-09T06:45:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:45:58 storageqe-109 stratisd[2509653]: [2025-10-09T06:45:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:46:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:46:26 storageqe-109 stratisd[2509653]: [2025-10-09T06:46:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:46:26 storageqe-109 stratisd[2509653]: [2025-10-09T06:46:26Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:46:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: HintEncryptionType Oct 9 02:46:52 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 9 02:46:53 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 9 02:46:54 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to argon2i Oct 9 02:46:55 storageqe-109 INFO: foramt to luks2 Oct 9 02:46:55 storageqe-109 INFO: foramt to argon2i Oct 9 02:47:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:47:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:47:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:47:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:47:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:47:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:47:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:47:24 storageqe-109 stratisd[2509653]: [2025-10-09T06:47:24Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 02:47:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:47:52 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:47:52 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 02:47:52 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 02:48:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:48:22 storageqe-109 kernel: loop0: Oct 9 02:48:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:48:47 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 9 02:48:47 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1567992_luks_resize #### INFO: #### will start test_part_mount ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:48:54 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:48:54 storageqe-109 INFO: #### END test_bz1567992_luks_resize #### Oct 9 02:48:54 storageqe-109 INFO: #### will start test_part_mount ##### Oct 9 02:48:54 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:49:00 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 02:49:00 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 9 02:49:00 storageqe-109 kernel: loop0: Oct 9 02:49:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:49:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:49:58 storageqe-109 kernel: loop0: p1 Oct 9 02:50:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:50:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:50:48 storageqe-109 kernel: EXT4-fs (loop0p1): mounting ext3 file system using the ext4 subsystem Oct 9 02:50:48 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem 6aa3cfc6-06bb-4895-8113-a8efdf7cb9b5 r/w with ordered data mode. Quota mode: none. Oct 9 02:50:48 storageqe-109 udisksd[2509680]: Mounted /dev/loop0p1 at /run/media/root/6aa3cfc6-06bb-4895-8113-a8efdf7cb9b5 on behalf of uid 0 Oct 9 02:51:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:51:13 storageqe-109 systemd[1]: run-media-root-6aa3cfc6\x2d06bb\x2d4895\x2d8113\x2da8efdf7cb9b5.mount: Deactivated successfully. Oct 9 02:51:13 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/6aa3cfc6-06bb-4895-8113-a8efdf7cb9b5 (device 259:3 is not mounted) Oct 9 02:51:13 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 9 02:51:13 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem 6aa3cfc6-06bb-4895-8113-a8efdf7cb9b5. Oct 9 02:51:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:52:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:52:03 storageqe-109 kernel: XFS (loop0p1): Mounting V5 Filesystem e295f8d6-44d9-4b29-9385-efdd1fb556e1 Oct 9 02:52:03 storageqe-109 kernel: XFS (loop0p1): Ending clean mount Oct 9 02:52:03 storageqe-109 udisksd[2509680]: Mounted /dev/loop0p1 at /run/media/root/e295f8d6-44d9-4b29-9385-efdd1fb556e1 on behalf of uid 0 Oct 9 02:52:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:52:28 storageqe-109 systemd[1]: run-media-root-e295f8d6\x2d44d9\x2d4b29\x2d9385\x2defdd1fb556e1.mount: Deactivated successfully. Oct 9 02:52:28 storageqe-109 kernel: XFS (loop0p1): Unmounting Filesystem e295f8d6-44d9-4b29-9385-efdd1fb556e1 Oct 9 02:52:28 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/e295f8d6-44d9-4b29-9385-efdd1fb556e1 (device 259:3 is not mounted) Oct 9 02:52:28 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 9 02:52:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:53:15 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 02:53:15 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 02:53:15 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 02:53:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:53:18 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem 1d235f84-8cad-446b-a92e-dcb5eb560c6f r/w with ordered data mode. Quota mode: none. Oct 9 02:53:18 storageqe-109 udisksd[2509680]: Mounted /dev/loop0p1 at /run/media/root/1d235f84-8cad-446b-a92e-dcb5eb560c6f on behalf of uid 0 Oct 9 02:53:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:53:43 storageqe-109 systemd[1]: run-media-root-1d235f84\x2d8cad\x2d446b\x2da92e\x2ddcb5eb560c6f.mount: Deactivated successfully. Oct 9 02:53:43 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1d235f84-8cad-446b-a92e-dcb5eb560c6f (device 259:3 is not mounted) Oct 9 02:53:43 storageqe-109 udisksd[2509680]: Unmounted /dev/loop0p1 on behalf of uid 0 Oct 9 02:53:43 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem 1d235f84-8cad-446b-a92e-dcb5eb560c6f. Oct 9 02:54:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:54:13 storageqe-109 kernel: loop0: Oct 9 02:54:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:54:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 9 02:54:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_part_mount #### INFO: #### will start test_bz1400056_md ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:54:45 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:54:45 storageqe-109 INFO: #### END test_part_mount #### Oct 9 02:54:45 storageqe-109 INFO: #### will start test_bz1400056_md ##### Oct 9 02:54:45 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 02:54:51 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 02:54:51 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop10.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 02:54:52 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 02:54:52 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 9 02:54:52 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 02:54:52 storageqe-109 INFO: raid level raid0 Oct 9 02:54:52 storageqe-109 INFO: raid name test_md Oct 9 02:54:52 storageqe-109 INFO: raid chunk 1048576 Oct 9 02:54:52 storageqe-109 INFO: raid bitmap None Oct 9 02:54:52 storageqe-109 INFO: raid version 1.2 Oct 9 02:55:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:55:17 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 INFO: Name test_md Oct 9 02:55:21 storageqe-109 INFO: Name test_md INFO: UUID 19b4db52:ee24350a:e7eecfb5:17c3c7e5 Oct 9 02:55:22 storageqe-109 INFO: UUID 19b4db52:ee24350a:e7eecfb5:17c3c7e5 INFO: Level raid0 Oct 9 02:55:23 storageqe-109 INFO: Level raid0 INFO: NumDevices 2 Oct 9 02:55:24 storageqe-109 INFO: NumDevices 2 INFO: Size 2141192192 Oct 9 02:55:25 storageqe-109 INFO: Size 2141192192 INFO: SyncAction Oct 9 02:55:26 storageqe-109 INFO: SyncAction INFO: SyncCompleted 0.0 Oct 9 02:55:27 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 9 02:55:28 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 9 02:55:29 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 9 02:55:30 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy Oct 9 02:55:31 storageqe-109 INFO: ConsistencyPolicy INFO: BitmapLocation dbus.Array([dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 9 02:55:32 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 9 02:55:33 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 9 02:55:34 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 9 02:55:35 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 9 02:55:36 storageqe-109 INFO: Running 1 INFO: bitma is , Oct 9 02:55:37 storageqe-109 INFO: bitma is , INFO: BitmapLocation Oct 9 02:55:38 storageqe-109 INFO: BitmapLocation Oct 9 02:56:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:56:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:56:34 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 9 02:56:34 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem fef42d3e-4181-4660-8865-ce2d44625238 r/w with ordered data mode. Quota mode: none. Oct 9 02:56:34 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/fef42d3e-4181-4660-8865-ce2d44625238 on behalf of uid 0 Oct 9 02:57:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:57:02 storageqe-109 systemd[1]: run-media-root-fef42d3e\x2d4181\x2d4660\x2d8865\x2dce2d44625238.mount: Deactivated successfully. Oct 9 02:57:02 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem fef42d3e-4181-4660-8865-ce2d44625238. Oct 9 02:57:02 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/fef42d3e-4181-4660-8865-ce2d44625238 (device 9:127 is not mounted) Oct 9 02:57:02 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 02:57:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:57:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 02:57:53 storageqe-109 dnf[2524752]: Updating Subscription Management repositories. Oct 9 02:57:53 storageqe-109 dnf[2524752]: Unable to read consumer identity Oct 9 02:57:53 storageqe-109 dnf[2524752]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 02:57:53 storageqe-109 dnf[2524752]: Metadata cache refreshed recently. Oct 9 02:57:54 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 02:57:54 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 02:58:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:58:00 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem f450744b-cc78-4abb-949f-3630fc9d6a20 Oct 9 02:58:00 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/f450744b-cc78-4abb-949f-3630fc9d6a20 on behalf of uid 0 Oct 9 02:58:00 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 9 02:58:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:58:28 storageqe-109 systemd[1]: run-media-root-f450744b\x2dcc78\x2d4abb\x2d949f\x2d3630fc9d6a20.mount: Deactivated successfully. Oct 9 02:58:28 storageqe-109 kernel: XFS (md127): Unmounting Filesystem f450744b-cc78-4abb-949f-3630fc9d6a20 Oct 9 02:58:28 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/f450744b-cc78-4abb-949f-3630fc9d6a20 (device 9:127 is not mounted) Oct 9 02:58:28 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 02:58:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:59:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:59:27 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/5ca6ef87-dab6-451f-b6b3-83520abf47f5 on behalf of uid 0 Oct 9 02:59:27 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 5ca6ef87-dab6-451f-b6b3-83520abf47f5 r/w with ordered data mode. Quota mode: none. Oct 9 02:59:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 02:59:55 storageqe-109 systemd[1]: run-media-root-5ca6ef87\x2ddab6\x2d451f\x2db6b3\x2d83520abf47f5.mount: Deactivated successfully. Oct 9 02:59:55 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 5ca6ef87-dab6-451f-b6b3-83520abf47f5. Oct 9 02:59:55 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/5ca6ef87-dab6-451f-b6b3-83520abf47f5 (device 9:127 is not mounted) Oct 9 02:59:55 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:00:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:00:24 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 9 03:00:24 storageqe-109 kernel: md: md127 stopped. Oct 9 03:00:24 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 03:00:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:00:52 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 9 03:00:52 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 03:01:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:01:17 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 9 03:01:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 03:01:17 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:01:17 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop10.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.0 Oct 9 03:01:18 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 03:01:18 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 9 03:01:18 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 03:01:18 storageqe-109 INFO: raid level raid1 Oct 9 03:01:18 storageqe-109 INFO: raid name test_md Oct 9 03:01:18 storageqe-109 INFO: raid chunk 0 Oct 9 03:01:18 storageqe-109 INFO: raid bitmap None Oct 9 03:01:18 storageqe-109 INFO: raid version 1.0 Oct 9 03:01:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:01:43 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 03:01:43 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 03:01:43 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 03:01:43 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 03:01:43 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 03:01:43 storageqe-109 kernel: md127: detected capacity change from 0 to 2097024 Oct 9 03:01:43 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 03:01:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:01:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:01:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:01:48 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 9 03:01:51 storageqe-109 INFO: Name test_md INFO: UUID 3d09f78e:0fa639fc:f2b5e221:42dc8689 Oct 9 03:01:52 storageqe-109 INFO: UUID 3d09f78e:0fa639fc:f2b5e221:42dc8689 INFO: Level raid1 Oct 9 03:01:53 storageqe-109 INFO: Level raid1 INFO: NumDevices 2 Oct 9 03:01:54 storageqe-109 INFO: NumDevices 2 INFO: Size 1073676288 Oct 9 03:01:55 storageqe-109 INFO: Size 1073676288 INFO: SyncAction idle Oct 9 03:01:56 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 9 03:01:57 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 9 03:01:58 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 9 03:01:59 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 9 03:02:00 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy resync Oct 9 03:02:01 storageqe-109 INFO: ConsistencyPolicy resync INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 9 03:02:02 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 0 Oct 9 03:02:03 storageqe-109 INFO: ChunkSize 0 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 9 03:02:04 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 9 03:02:05 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 9 03:02:06 storageqe-109 INFO: Running 1 INFO: bitma is none, INFO: looks don't set bitmap Oct 9 03:02:07 storageqe-109 INFO: bitma is none, Oct 9 03:02:07 storageqe-109 INFO: looks don't set bitmap Oct 9 03:02:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:02:32 storageqe-109 kernel: md127: bitmap file is out of date (0 < 17) -- forcing full recovery Oct 9 03:02:32 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery INFO: BitmapLocation -16 Oct 9 03:02:34 storageqe-109 INFO: BitmapLocation -16 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop2 at 0x7f8acbf264b0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop2 /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 03:02:35 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 03:02:35 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/loop0.img) Oct 9 03:02:35 storageqe-109 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop2 at 0x7f8acbf264b0> Oct 9 03:02:35 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop2 /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 03:03:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:03:02 storageqe-109 INFO: Oct 9 03:03:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:03:30 storageqe-109 INFO: Oct 9 03:03:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:03:32 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:03:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:03:57 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:03:57 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:04:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:04:27 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 9 03:04:27 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 9cfc9d37-ea4a-468c-ae79-dc9e7fad3da9 r/w with ordered data mode. Quota mode: none. Oct 9 03:04:27 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/9cfc9d37-ea4a-468c-ae79-dc9e7fad3da9 on behalf of uid 0 Oct 9 03:04:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:04:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:04:55 storageqe-109 systemd[1]: run-media-root-9cfc9d37\x2dea4a\x2d468c\x2dae79\x2ddc9e7fad3da9.mount: Deactivated successfully. Oct 9 03:04:55 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 9cfc9d37-ea4a-468c-ae79-dc9e7fad3da9. Oct 9 03:04:55 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/9cfc9d37-ea4a-468c-ae79-dc9e7fad3da9 (device 9:127 is not mounted) Oct 9 03:04:55 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:04:55 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:04:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:04:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:04:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:04:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:04:58 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:05:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:05:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:05:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:05:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:05:53 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 0474551b-d866-40fc-b098-c1211c93f42d Oct 9 03:05:53 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/0474551b-d866-40fc-b098-c1211c93f42d on behalf of uid 0 Oct 9 03:05:53 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 9 03:05:53 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:06:21 storageqe-109 systemd[1]: run-media-root-0474551b\x2dd866\x2d40fc\x2db098\x2dc1211c93f42d.mount: Deactivated successfully. Oct 9 03:06:21 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 0474551b-d866-40fc-b098-c1211c93f42d Oct 9 03:06:21 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/0474551b-d866-40fc-b098-c1211c93f42d (device 9:127 is not mounted) Oct 9 03:06:21 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:06:21 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:24 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:24 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:24 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:24 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:24 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:06:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:06:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:07:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:07:19 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem cc69566c-a7b5-4769-b3c7-d94ba44e1fb9 r/w with ordered data mode. Quota mode: none. Oct 9 03:07:19 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/cc69566c-a7b5-4769-b3c7-d94ba44e1fb9 on behalf of uid 0 Oct 9 03:07:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:07:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:07:47 storageqe-109 systemd[1]: run-media-root-cc69566c\x2da7b5\x2d4769\x2db3c7\x2dd94ba44e1fb9.mount: Deactivated successfully. Oct 9 03:07:47 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem cc69566c-a7b5-4769-b3c7-d94ba44e1fb9. Oct 9 03:07:47 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/cc69566c-a7b5-4769-b3c7-d94ba44e1fb9 (device 9:127 is not mounted) Oct 9 03:07:47 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:07:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:07:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:07:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:07:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:08:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:08:16 storageqe-109 kernel: md127: detected capacity change from 2097024 to 0 Oct 9 03:08:16 storageqe-109 kernel: md: md127 stopped. Oct 9 03:08:16 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 03:08:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:08:44 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 9 03:08:44 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 03:09:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:09:09 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 9 03:09:09 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 03:09:10 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:09:10 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 9 03:09:10 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 03:09:10 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop11.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid4 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap None INFO: raid version 1.0 Oct 9 03:09:11 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 03:09:11 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/loop12.img) Oct 9 03:09:11 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 9 03:09:11 storageqe-109 INFO: raid level raid4 Oct 9 03:09:11 storageqe-109 INFO: raid name test_md Oct 9 03:09:11 storageqe-109 INFO: raid chunk 1048576 Oct 9 03:09:11 storageqe-109 INFO: raid bitmap None Oct 9 03:09:11 storageqe-109 INFO: raid version 1.0 Oct 9 03:09:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:09:36 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 9 03:09:36 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 9 03:09:36 storageqe-109 kernel: md/raid:md127: raid level 4 active with 2 out of 3 devices, algorithm 0 Oct 9 03:09:36 storageqe-109 kernel: md127: detected capacity change from 0 to 4190208 Oct 9 03:09:36 storageqe-109 kernel: md: recover of RAID array md127 Oct 9 03:09:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:09:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:09:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: Name test_md Oct 9 03:09:40 storageqe-109 INFO: Name test_md INFO: UUID 40179c8c:378dd5bd:90ae5ea6:b7521d23 Oct 9 03:09:41 storageqe-109 INFO: UUID 40179c8c:378dd5bd:90ae5ea6:b7521d23 Oct 9 03:09:41 storageqe-109 kernel: md: md127: recover done. INFO: Level raid4 Oct 9 03:09:42 storageqe-109 INFO: Level raid4 INFO: NumDevices 3 Oct 9 03:09:43 storageqe-109 INFO: NumDevices 3 INFO: Size 2145386496 Oct 9 03:09:44 storageqe-109 INFO: Size 2145386496 INFO: SyncAction idle Oct 9 03:09:45 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 9 03:09:46 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 9 03:09:47 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 9 03:09:48 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 9 03:09:49 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy resync Oct 9 03:09:50 storageqe-109 INFO: ConsistencyPolicy resync INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 9 03:09:51 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 9 03:09:52 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 9 03:09:53 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 9 03:09:54 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 9 03:09:55 storageqe-109 INFO: Running 1 INFO: bitma is none, INFO: looks don't set bitmap Oct 9 03:09:56 storageqe-109 INFO: bitma is none, Oct 9 03:09:56 storageqe-109 INFO: looks don't set bitmap Oct 9 03:10:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:10:21 storageqe-109 kernel: md127: bitmap file is out of date (0 < 18) -- forcing full recovery Oct 9 03:10:21 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery INFO: BitmapLocation -16 Oct 9 03:10:23 storageqe-109 INFO: BitmapLocation -16 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop4 at 0x7f8acbf275c0> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop4 /org/freedesktop/UDisks2/block_devices/loop4 Oct 9 03:10:24 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 9 03:10:24 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop4 (backed by /home/loop0.img) Oct 9 03:10:24 storageqe-109 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop4 at 0x7f8acbf275c0> Oct 9 03:10:24 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop4 /org/freedesktop/UDisks2/block_devices/loop4 Oct 9 03:10:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:10:51 storageqe-109 INFO: Oct 9 03:11:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:11:19 storageqe-109 INFO: Oct 9 03:11:21 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:11:21 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:11:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:11:46 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:11:46 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:12:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:12:16 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 9 03:12:16 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 6ebf3aee-4d6a-4c4e-a8c3-77772f3929f8 r/w with ordered data mode. Quota mode: none. Oct 9 03:12:16 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/6ebf3aee-4d6a-4c4e-a8c3-77772f3929f8 on behalf of uid 0 Oct 9 03:12:16 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:12:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:12:44 storageqe-109 systemd[1]: run-media-root-6ebf3aee\x2d4d6a\x2d4c4e\x2da8c3\x2d77772f3929f8.mount: Deactivated successfully. Oct 9 03:12:44 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 6ebf3aee-4d6a-4c4e-a8c3-77772f3929f8. Oct 9 03:12:44 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/6ebf3aee-4d6a-4c4e-a8c3-77772f3929f8 (device 9:127 is not mounted) Oct 9 03:12:44 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:12:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:12:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:12:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:12:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:12:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:12:47 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:13:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:13:12 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:13:12 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:13:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:13:42 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 8f982473-b8ff-4756-8ad1-3effff187913 Oct 9 03:13:42 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 9 03:13:42 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/8f982473-b8ff-4756-8ad1-3effff187913 on behalf of uid 0 Oct 9 03:13:42 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:14:10 storageqe-109 systemd[1]: run-media-root-8f982473\x2db8ff\x2d4756\x2d8ad1\x2d3effff187913.mount: Deactivated successfully. Oct 9 03:14:10 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 8f982473-b8ff-4756-8ad1-3effff187913 Oct 9 03:14:10 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/8f982473-b8ff-4756-8ad1-3effff187913 (device 9:127 is not mounted) Oct 9 03:14:10 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:14:10 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:13 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:14:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:14:39 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:15:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:15:09 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem d832de62-75fc-4cae-ade2-2c3258bf45a7 r/w with ordered data mode. Quota mode: none. Oct 9 03:15:09 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/d832de62-75fc-4cae-ade2-2c3258bf45a7 on behalf of uid 0 Oct 9 03:15:09 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:15:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:15:37 storageqe-109 systemd[1]: run-media-root-d832de62\x2d75fc\x2d4cae\x2dade2\x2d2c3258bf45a7.mount: Deactivated successfully. Oct 9 03:15:37 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem d832de62-75fc-4cae-ade2-2c3258bf45a7. Oct 9 03:15:37 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/d832de62-75fc-4cae-ade2-2c3258bf45a7 (device 9:127 is not mounted) Oct 9 03:15:37 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:15:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:15:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:15:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:15:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:16:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:16:06 storageqe-109 kernel: md127: detected capacity change from 4190208 to 0 Oct 9 03:16:06 storageqe-109 kernel: md: md127 stopped. Oct 9 03:16:06 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 03:16:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:16:34 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 9 03:16:34 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 03:16:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:16:59 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 9 03:16:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 03:17:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:17:24 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 9 03:17:24 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 03:17:24 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:17:24 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 9 03:17:25 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 03:17:25 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop11.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] INFO: raid level raid5 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap None INFO: raid version 1.0 Oct 9 03:17:25 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 03:17:25 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/loop12.img) Oct 9 03:17:25 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3')] Oct 9 03:17:25 storageqe-109 INFO: raid level raid5 Oct 9 03:17:25 storageqe-109 INFO: raid name test_md Oct 9 03:17:25 storageqe-109 INFO: raid chunk 1048576 Oct 9 03:17:25 storageqe-109 INFO: raid bitmap None Oct 9 03:17:25 storageqe-109 INFO: raid version 1.0 Oct 9 03:17:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:17:50 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 9 03:17:50 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 9 03:17:50 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 9 03:17:50 storageqe-109 kernel: md127: detected capacity change from 0 to 4190208 Oct 9 03:17:50 storageqe-109 kernel: md: recover of RAID array md127 Oct 9 03:17:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:17:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:17:51 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). INFO: Name test_md Oct 9 03:17:55 storageqe-109 INFO: Name test_md INFO: UUID e571220d:acec5b88:f22cdd3c:396b55c9 Oct 9 03:17:56 storageqe-109 INFO: UUID e571220d:acec5b88:f22cdd3c:396b55c9 Oct 9 03:17:56 storageqe-109 kernel: md: md127: recover done. INFO: Level raid5 Oct 9 03:17:57 storageqe-109 INFO: Level raid5 INFO: NumDevices 3 Oct 9 03:17:58 storageqe-109 INFO: NumDevices 3 INFO: Size 2145386496 Oct 9 03:17:59 storageqe-109 INFO: Size 2145386496 INFO: SyncAction idle Oct 9 03:18:00 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 9 03:18:01 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 9 03:18:02 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 9 03:18:03 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 9 03:18:04 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy resync Oct 9 03:18:05 storageqe-109 INFO: ConsistencyPolicy resync INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 9 03:18:06 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(110), dbus.Byte(111), dbus.Byte(110), dbus.Byte(101), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 9 03:18:07 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) Oct 9 03:18:08 storageqe-109 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 9 03:18:09 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 9 03:18:10 storageqe-109 INFO: Running 1 INFO: bitma is none, INFO: looks don't set bitmap Oct 9 03:18:11 storageqe-109 INFO: bitma is none, Oct 9 03:18:11 storageqe-109 INFO: looks don't set bitmap Oct 9 03:18:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:18:36 storageqe-109 kernel: md127: bitmap file is out of date (0 < 18) -- forcing full recovery Oct 9 03:18:36 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery INFO: BitmapLocation -16 Oct 9 03:18:38 storageqe-109 INFO: BitmapLocation -16 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop5 at 0x7f8acbf26f60> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop5 /org/freedesktop/UDisks2/block_devices/loop5 Oct 9 03:18:38 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 9 03:18:38 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop5 (backed by /home/loop0.img) Oct 9 03:18:38 storageqe-109 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop5 at 0x7f8acbf26f60> Oct 9 03:18:38 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop5 /org/freedesktop/UDisks2/block_devices/loop5 Oct 9 03:19:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:19:05 storageqe-109 INFO: Oct 9 03:19:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:19:33 storageqe-109 INFO: Oct 9 03:19:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:19:36 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:20:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:20:01 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:20:01 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:20:28 storageqe-109 dmeventd[2515002]: dmeventd was idle for 3600 second(s), exiting. Oct 9 03:20:28 storageqe-109 dmeventd[2515002]: dmeventd shutting down. Oct 9 03:20:28 storageqe-109 systemd[1]: dm-event.service: Deactivated successfully. Oct 9 03:20:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:20:31 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 9 03:20:31 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 5a3bec02-ca74-4ed6-91a6-13d8ca3fd864 r/w with ordered data mode. Quota mode: none. Oct 9 03:20:31 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/5a3bec02-ca74-4ed6-91a6-13d8ca3fd864 on behalf of uid 0 Oct 9 03:20:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:20:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:20:59 storageqe-109 systemd[1]: run-media-root-5a3bec02\x2dca74\x2d4ed6\x2d91a6\x2d13d8ca3fd864.mount: Deactivated successfully. Oct 9 03:20:59 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 5a3bec02-ca74-4ed6-91a6-13d8ca3fd864. Oct 9 03:20:59 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/5a3bec02-ca74-4ed6-91a6-13d8ca3fd864 (device 9:127 is not mounted) Oct 9 03:20:59 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:20:59 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:02 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:02 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:02 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:02 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:02 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:21:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:21:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:21:57 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 11e01a26-b38f-4ff2-97f7-17eb80cf7da6 Oct 9 03:21:57 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 9 03:21:57 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/11e01a26-b38f-4ff2-97f7-17eb80cf7da6 on behalf of uid 0 Oct 9 03:21:57 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:22:25 storageqe-109 systemd[1]: run-media-root-11e01a26\x2db38f\x2d4ff2\x2d97f7\x2d17eb80cf7da6.mount: Deactivated successfully. Oct 9 03:22:25 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 11e01a26-b38f-4ff2-97f7-17eb80cf7da6 Oct 9 03:22:25 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/11e01a26-b38f-4ff2-97f7-17eb80cf7da6 (device 9:127 is not mounted) Oct 9 03:22:25 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:22:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:28 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:22:53 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:22:53 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:23:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:23:23 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 1d6e86e8-fc94-4b68-a8bc-668760c97e44 r/w with ordered data mode. Quota mode: none. Oct 9 03:23:23 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/1d6e86e8-fc94-4b68-a8bc-668760c97e44 on behalf of uid 0 Oct 9 03:23:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:23:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:23:51 storageqe-109 systemd[1]: run-media-root-1d6e86e8\x2dfc94\x2d4b68\x2da8bc\x2d668760c97e44.mount: Deactivated successfully. Oct 9 03:23:51 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 1d6e86e8-fc94-4b68-a8bc-668760c97e44. Oct 9 03:23:51 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/1d6e86e8-fc94-4b68-a8bc-668760c97e44 (device 9:127 is not mounted) Oct 9 03:23:51 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:23:51 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:23:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:23:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:23:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:24:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:24:20 storageqe-109 kernel: md127: detected capacity change from 4190208 to 0 Oct 9 03:24:20 storageqe-109 kernel: md: md127 stopped. Oct 9 03:24:20 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 03:24:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:24:48 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 9 03:24:48 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 03:25:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:25:13 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 9 03:25:13 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 03:25:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:25:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 9 03:25:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 03:25:39 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:25:39 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 9 03:25:39 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 03:25:39 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 9 03:25:40 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 03:25:40 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/loop12.img) Oct 9 03:25:40 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] INFO: raid level raid6 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.0 Oct 9 03:25:40 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop6 (backed by /home/loop13.img) Oct 9 03:25:40 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] Oct 9 03:25:40 storageqe-109 INFO: raid level raid6 Oct 9 03:25:40 storageqe-109 INFO: raid name test_md Oct 9 03:25:40 storageqe-109 INFO: raid chunk 1048576 Oct 9 03:25:40 storageqe-109 INFO: raid bitmap internal Oct 9 03:25:40 storageqe-109 INFO: raid version 1.0 Oct 9 03:26:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:26:05 storageqe-109 kernel: md/raid:md127: not clean -- starting background reconstruction Oct 9 03:26:05 storageqe-109 kernel: md/raid:md127: device loop6 operational as raid disk 3 Oct 9 03:26:05 storageqe-109 kernel: md/raid:md127: device loop3 operational as raid disk 2 Oct 9 03:26:05 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 9 03:26:05 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 9 03:26:05 storageqe-109 kernel: md/raid:md127: raid level 6 active with 4 out of 4 devices, algorithm 2 Oct 9 03:26:05 storageqe-109 kernel: md127: detected capacity change from 0 to 4190208 Oct 9 03:26:05 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 03:26:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:26:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:26:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:26:10 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 9 03:26:13 storageqe-109 INFO: Name test_md INFO: UUID 36172b3d:7912a46a:4c826489:2f75b3ce Oct 9 03:26:14 storageqe-109 INFO: UUID 36172b3d:7912a46a:4c826489:2f75b3ce INFO: Level raid6 Oct 9 03:26:15 storageqe-109 INFO: Level raid6 INFO: NumDevices 4 Oct 9 03:26:16 storageqe-109 INFO: NumDevices 4 INFO: Size 2145386496 Oct 9 03:26:17 storageqe-109 INFO: Size 2145386496 INFO: SyncAction idle Oct 9 03:26:18 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 9 03:26:19 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 9 03:26:20 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 9 03:26:21 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 9 03:26:22 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 9 03:26:23 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 9 03:26:24 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(45), dbus.Byte(49), dbus.Byte(54), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 9 03:26:25 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6'), dbus.Int32(3), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 9 03:26:27 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 9 03:26:28 storageqe-109 INFO: Running 1 INFO: bitma is -16, Oct 9 03:26:29 storageqe-109 INFO: bitma is -16, INFO: BitmapLocation -16 Oct 9 03:26:30 storageqe-109 INFO: BitmapLocation -16 Oct 9 03:26:30 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop7 at 0x7f8acbf25610> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop7 /org/freedesktop/UDisks2/block_devices/loop7 Oct 9 03:26:30 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop7 (backed by /home/loop0.img) Oct 9 03:26:30 storageqe-109 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop7 at 0x7f8acbf25610> Oct 9 03:26:30 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop7 /org/freedesktop/UDisks2/block_devices/loop7 Oct 9 03:26:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:26:57 storageqe-109 INFO: Oct 9 03:27:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:27:25 storageqe-109 INFO: Oct 9 03:27:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:27:27 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:27:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:27:52 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:27:52 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:28:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:28:22 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 9 03:28:23 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/799dc256-9543-43e5-9416-93fd57bd8929 on behalf of uid 0 Oct 9 03:28:23 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem 799dc256-9543-43e5-9416-93fd57bd8929 r/w with ordered data mode. Quota mode: none. Oct 9 03:28:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:28:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:28:51 storageqe-109 systemd[1]: run-media-root-799dc256\x2d9543\x2d43e5\x2d9416\x2d93fd57bd8929.mount: Deactivated successfully. Oct 9 03:28:51 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem 799dc256-9543-43e5-9416-93fd57bd8929. Oct 9 03:28:51 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/799dc256-9543-43e5-9416-93fd57bd8929 (device 9:127 is not mounted) Oct 9 03:28:51 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:28:51 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:28:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:28:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:28:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:28:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:28:54 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:29:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:29:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:29:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:29:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:29:49 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 2cb2e57d-5792-48d5-ba58-6fc82fd45518 Oct 9 03:29:49 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 9 03:29:49 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/2cb2e57d-5792-48d5-ba58-6fc82fd45518 on behalf of uid 0 Oct 9 03:29:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:30:17 storageqe-109 systemd[1]: run-media-root-2cb2e57d\x2d5792\x2d48d5\x2dba58\x2d6fc82fd45518.mount: Deactivated successfully. Oct 9 03:30:17 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 2cb2e57d-5792-48d5-ba58-6fc82fd45518 Oct 9 03:30:17 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/2cb2e57d-5792-48d5-ba58-6fc82fd45518 (device 9:127 is not mounted) Oct 9 03:30:17 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:30:17 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:20 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:30:45 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:30:45 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:31:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:31:15 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem d090fe3f-22aa-4c6c-8c49-e3a0ea0ddcf5 r/w with ordered data mode. Quota mode: none. Oct 9 03:31:15 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/d090fe3f-22aa-4c6c-8c49-e3a0ea0ddcf5 on behalf of uid 0 Oct 9 03:31:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:31:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:31:43 storageqe-109 systemd[1]: run-media-root-d090fe3f\x2d22aa\x2d4c6c\x2d8c49\x2de3a0ea0ddcf5.mount: Deactivated successfully. Oct 9 03:31:43 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem d090fe3f-22aa-4c6c-8c49-e3a0ea0ddcf5. Oct 9 03:31:43 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/d090fe3f-22aa-4c6c-8c49-e3a0ea0ddcf5 (device 9:127 is not mounted) Oct 9 03:31:43 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:31:43 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:31:46 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:31:46 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:31:46 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:32:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:32:12 storageqe-109 kernel: md127: detected capacity change from 4190208 to 0 Oct 9 03:32:12 storageqe-109 kernel: md: md127 stopped. Oct 9 03:32:12 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 03:32:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:32:40 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 9 03:32:40 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 03:33:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:33:05 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 9 03:33:05 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 03:33:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:33:30 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 9 03:33:30 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 03:33:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:33:55 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop6 (was backed by /home/loop13.img) Oct 9 03:33:55 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop6 Oct 9 03:33:56 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:33:56 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop10.img) Oct 9 03:33:56 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 03:33:56 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop11.img) Oct 9 03:33:56 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 03:33:56 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/loop12.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] INFO: raid level raid10 INFO: raid name test_md INFO: raid chunk 1048576 INFO: raid bitmap internal INFO: raid version 1.2 Oct 9 03:33:57 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 9 03:33:57 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop6 (backed by /home/loop13.img) Oct 9 03:33:57 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6')] Oct 9 03:33:57 storageqe-109 INFO: raid level raid10 Oct 9 03:33:57 storageqe-109 INFO: raid name test_md Oct 9 03:33:57 storageqe-109 INFO: raid chunk 1048576 Oct 9 03:33:57 storageqe-109 INFO: raid bitmap internal Oct 9 03:33:57 storageqe-109 INFO: raid version 1.2 Oct 9 03:34:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:34:22 storageqe-109 kernel: md/raid10:md127: not clean -- starting background reconstruction Oct 9 03:34:22 storageqe-109 kernel: md/raid10:md127: active with 4 out of 4 devices Oct 9 03:34:22 storageqe-109 kernel: md127: detected capacity change from 0 to 4182016 Oct 9 03:34:22 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 03:34:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:34:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:34:22 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:34:32 storageqe-109 kernel: md: md127: resync done. INFO: Name test_md Oct 9 03:34:34 storageqe-109 INFO: Name test_md INFO: UUID 866ee3f2:44d3821f:82ea4c0f:54c1af14 Oct 9 03:34:35 storageqe-109 INFO: UUID 866ee3f2:44d3821f:82ea4c0f:54c1af14 INFO: Level raid10 Oct 9 03:34:36 storageqe-109 INFO: Level raid10 INFO: NumDevices 4 Oct 9 03:34:37 storageqe-109 INFO: NumDevices 4 INFO: Size 2141192192 Oct 9 03:34:38 storageqe-109 INFO: Size 2141192192 INFO: SyncAction idle Oct 9 03:34:39 storageqe-109 INFO: SyncAction idle INFO: SyncCompleted 0.0 Oct 9 03:34:40 storageqe-109 INFO: SyncCompleted 0.0 INFO: SyncRate 0 Oct 9 03:34:41 storageqe-109 INFO: SyncRate 0 INFO: SyncRemainingTime 0 Oct 9 03:34:42 storageqe-109 INFO: SyncRemainingTime 0 INFO: Degraded 0 Oct 9 03:34:43 storageqe-109 INFO: Degraded 0 INFO: ConsistencyPolicy bitmap Oct 9 03:34:44 storageqe-109 INFO: ConsistencyPolicy bitmap INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) Oct 9 03:34:45 storageqe-109 INFO: BitmapLocation dbus.Array([dbus.Byte(43), dbus.Byte(56), dbus.Byte(0)], signature=dbus.Signature('y'), variant_level=1) INFO: ChunkSize 1048576 Oct 9 03:34:46 storageqe-109 INFO: ChunkSize 1048576 INFO: ActiveDevices dbus.Array([dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.Int32(0), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.Int32(1), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop3'), dbus.Int32(2), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None), dbus.Struct((dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop6'), dbus.Int32(3), dbus.Array([dbus.String('in_sync')], signature=dbus.Signature('s')), dbus.UInt64(0), dbus.Dictionary({}, signature=dbus.Signature('sv'))), signature=None)], signature=dbus.Signature('(oiasta{sv})'), variant_level=1) INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) Oct 9 03:34:48 storageqe-109 INFO: ChildConfiguration dbus.Array([], signature=dbus.Signature('(sa{sv})'), variant_level=1) INFO: Running 1 Oct 9 03:34:49 storageqe-109 INFO: Running 1 INFO: bitma is +8, Oct 9 03:34:50 storageqe-109 INFO: bitma is +8, INFO: BitmapLocation +8 Oct 9 03:34:51 storageqe-109 INFO: BitmapLocation +8 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop8 at 0x7f8acbf24b90> INFO: new_path /org/freedesktop/UDisks2/block_devices/loop8 /org/freedesktop/UDisks2/block_devices/loop8 Oct 9 03:34:52 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 9 03:34:52 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop8 (backed by /home/loop0.img) Oct 9 03:34:52 storageqe-109 INFO: new_disk_obj :1.10 /org/freedesktop/UDisks2/block_devices/loop8 at 0x7f8acbf24b90> Oct 9 03:34:52 storageqe-109 INFO: new_path /org/freedesktop/UDisks2/block_devices/loop8 /org/freedesktop/UDisks2/block_devices/loop8 Oct 9 03:35:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:35:19 storageqe-109 INFO: Oct 9 03:35:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Oct 9 03:35:47 storageqe-109 INFO: Oct 9 03:35:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:35:49 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:36:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:36:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:36:14 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:36:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:36:44 storageqe-109 kernel: EXT4-fs (md127): mounting ext3 file system using the ext4 subsystem Oct 9 03:36:44 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/cfe007ad-ef52-43f7-80bc-3a6eaee5ec9d on behalf of uid 0 Oct 9 03:36:44 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem cfe007ad-ef52-43f7-80bc-3a6eaee5ec9d r/w with ordered data mode. Quota mode: none. Oct 9 03:36:44 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:37:12 storageqe-109 systemd[1]: run-media-root-cfe007ad\x2def52\x2d43f7\x2d80bc\x2d3a6eaee5ec9d.mount: Deactivated successfully. Oct 9 03:37:12 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem cfe007ad-ef52-43f7-80bc-3a6eaee5ec9d. Oct 9 03:37:12 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/cfe007ad-ef52-43f7-80bc-3a6eaee5ec9d (device 9:127 is not mounted) Oct 9 03:37:12 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:37:12 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:15 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:37:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:37:40 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:38:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:38:10 storageqe-109 kernel: XFS (md127): Mounting V5 Filesystem 6c2a661b-37dc-480c-909f-b08a963b423c Oct 9 03:38:10 storageqe-109 kernel: XFS (md127): Ending clean mount Oct 9 03:38:10 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/6c2a661b-37dc-480c-909f-b08a963b423c on behalf of uid 0 Oct 9 03:38:10 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:38:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:38:38 storageqe-109 systemd[1]: run-media-root-6c2a661b\x2d37dc\x2d480c\x2d909f\x2db08a963b423c.mount: Deactivated successfully. Oct 9 03:38:38 storageqe-109 kernel: XFS (md127): Unmounting Filesystem 6c2a661b-37dc-480c-909f-b08a963b423c Oct 9 03:38:38 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/6c2a661b-37dc-480c-909f-b08a963b423c (device 9:127 is not mounted) Oct 9 03:38:38 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:38:38 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:38:41 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:38:41 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:38:41 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:38:41 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:38:41 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:39:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:39:07 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:39:07 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:39:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:39:37 storageqe-109 udisksd[2509680]: Mounted /dev/md127 at /run/media/root/aa96bd2d-4db4-4447-9d22-f46313a60861 on behalf of uid 0 Oct 9 03:39:37 storageqe-109 kernel: EXT4-fs (md127): mounted filesystem aa96bd2d-4db4-4447-9d22-f46313a60861 r/w with ordered data mode. Quota mode: none. Oct 9 03:39:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:40:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:40:05 storageqe-109 systemd[1]: run-media-root-aa96bd2d\x2d4db4\x2d4447\x2d9d22\x2df46313a60861.mount: Deactivated successfully. Oct 9 03:40:05 storageqe-109 kernel: EXT4-fs (md127): unmounting filesystem aa96bd2d-4db4-4447-9d22-f46313a60861. Oct 9 03:40:05 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/aa96bd2d-4db4-4447-9d22-f46313a60861 (device 9:127 is not mounted) Oct 9 03:40:05 storageqe-109 udisksd[2509680]: Unmounted /dev/md127 on behalf of uid 0 Oct 9 03:40:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:40:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:40:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:40:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:40:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:40:34 storageqe-109 kernel: md127: detected capacity change from 4182016 to 0 Oct 9 03:40:34 storageqe-109 kernel: md: md127 stopped. Oct 9 03:40:34 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 03:41:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:41:02 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop10.img) Oct 9 03:41:02 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 03:41:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:41:27 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop11.img) Oct 9 03:41:27 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 03:41:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:41:52 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/loop12.img) Oct 9 03:41:52 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 03:42:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:42:17 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop6 (was backed by /home/loop13.img) Oct 9 03:42:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop6 Oct 9 03:42:18 storageqe-109 udisksd[2509680]: udisks_state_check_loop_entry: unexpected name for /dev/loop7 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 9 03:42:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop7 Oct 9 03:42:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop8 Oct 9 03:42:18 storageqe-109 udisksd[2509680]: udisks_state_check_loop_entry: unexpected name for /dev/loop2 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 9 03:42:18 storageqe-109 udisksd[2509680]: udisks_state_check_loop_entry: unexpected name for /dev/loop4 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 9 03:42:18 storageqe-109 udisksd[2509680]: udisks_state_check_loop_entry: unexpected name for /dev/loop5 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 9 03:42:18 storageqe-109 udisksd[2509680]: udisks_state_check_loop_entry: unexpected name for /dev/loop2 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 9 03:42:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 03:42:18 storageqe-109 udisksd[2509680]: udisks_state_check_loop_entry: unexpected name for /dev/loop4 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 9 03:42:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop4 Oct 9 03:42:18 storageqe-109 udisksd[2509680]: udisks_state_check_loop_entry: unexpected name for /dev/loop5 - expected `/home/loop0.img' but got `/home/loop0.img (deleted)' Oct 9 03:42:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop5 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1400056_md #### INFO: #### will start test_bz1710257_iSCSI_initiator_byte ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:42:23 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:42:23 storageqe-109 INFO: #### END test_bz1400056_md #### Oct 9 03:42:23 storageqe-109 INFO: #### will start test_bz1710257_iSCSI_initiator_byte ##### Oct 9 03:42:23 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1710257_iSCSI_initiator_byte #### INFO: #### will start test_bz1668291_snapshot ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:42:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:42:35 storageqe-109 INFO: #### END test_bz1710257_iSCSI_initiator_byte #### Oct 9 03:42:35 storageqe-109 INFO: #### will start test_bz1668291_snapshot ##### Oct 9 03:42:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:42:42 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:42:42 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 9 03:42:42 storageqe-109 kernel: loop0: Oct 9 03:43:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:43:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:43:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:44:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:44:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:44:52 storageqe-109 systemd[1]: Started dm-event.service - Device-mapper event daemon. Oct 9 03:44:52 storageqe-109 dmeventd[2527600]: dmeventd ready for processing. Oct 9 03:44:52 storageqe-109 dmeventd[2527600]: Monitoring snapshot vg03-snap01. Oct 9 03:45:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:45:18 storageqe-109 dmeventd[2527600]: No longer monitoring snapshot vg03-snap01. Oct 9 03:45:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:46:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:46:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:46:39 storageqe-109 kernel: loop0: Oct 9 03:47:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:47:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 9 03:47:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1668291_snapshot #### INFO: #### will start test_bz1534904_get_thin_size ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:47:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:47:11 storageqe-109 INFO: #### END test_bz1668291_snapshot #### Oct 9 03:47:11 storageqe-109 INFO: #### will start test_bz1534904_get_thin_size ##### Oct 9 03:47:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:47:17 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:47:17 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop0.img) Oct 9 03:47:17 storageqe-109 kernel: loop0: Oct 9 03:47:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:48:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:48:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:48:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:48:59 storageqe-109 dmeventd[2527600]: Monitoring thin pool vg03-tp3. Oct 9 03:49:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:49:27 storageqe-109 dmeventd[2527600]: No longer monitoring thin pool vg03-tp3. Oct 9 03:49:28 storageqe-109 dmeventd[2527600]: Monitoring thin pool vg03-tp3-tpool. Oct 9 03:49:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:50:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:50:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:50:46 storageqe-109 dmeventd[2527600]: No longer monitoring thin pool vg03-tp3-tpool. Oct 9 03:51:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:51:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:52:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:52:08 storageqe-109 kernel: loop0: Oct 9 03:52:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:52:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop0.img) Oct 9 03:52:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1534904_get_thin_size #### INFO: #### will start test_bz2120697_ata_secure_erase ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:52:39 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:52:39 storageqe-109 INFO: #### END test_bz1534904_get_thin_size #### Oct 9 03:52:39 storageqe-109 INFO: #### will start test_bz2120697_ata_secure_erase ##### Oct 9 03:52:39 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:52:45 storageqe-109 systemd[1]: Reload requested from client PID 2528442 ('systemctl') (unit session-6.scope)... Oct 9 03:52:45 storageqe-109 systemd[1]: Reloading... Oct 9 03:52:45 storageqe-109 systemd-rc-local-generator: /etc/rc.d/rc.local is not marked executable, skipping. Oct 9 03:52:45 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 9 03:52:45 storageqe-109 systemd[1]: Binding to IPv6 address not available since kernel does not support IPv6. Oct 9 03:52:46 storageqe-109 systemd[1]: Reloading finished in 138 ms. Oct 9 03:52:46 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 03:52:46 storageqe-109 iscsid[2509781]: iscsid shutting down. Oct 9 03:52:46 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 03:52:46 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 03:52:46 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 03:52:46 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 03:52:46 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 9 03:52:46 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 9 03:52:46 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 9 03:52:46 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz2120697_ata_secure_erase #### INFO: #### will start test_journalctl_log_check ##### Oct 9 03:53:03 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:53:03 storageqe-109 INFO: #### END test_bz2120697_ata_secure_erase #### Oct 9 03:53:03 storageqe-109 INFO: #### will start test_journalctl_log_check ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:53:03 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_journalctl_log_check #### INFO: #### will start test_bz1983602_iscsi_login_failed ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:53:15 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:53:15 storageqe-109 INFO: #### END test_journalctl_log_check #### Oct 9 03:53:15 storageqe-109 INFO: #### will start test_bz1983602_iscsi_login_failed ##### Oct 9 03:53:15 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:53:16 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 Oct 9 03:53:21 storageqe-109 INFO: Setting up local iSCSI target... Oct 9 03:53:21 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 9 03:53:21 storageqe-109 INFO: Creating test disk files... Oct 9 03:53:21 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 9 03:53:22 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 03:53:22 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 9 03:53:22 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 9 03:53:22 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 9 03:53:22 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 9 03:53:22 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 9 03:53:22 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 03:53:25 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 03:53:25 storageqe-109 kernel: dev[00000000b76ad584]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:25 storageqe-109 kernel: dev[00000000832fa5ad]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:25 storageqe-109 kernel: dev[00000000e080fe0d]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:25 storageqe-109 kernel: dev[00000000f9ee50b5]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:25 storageqe-109 kernel: dev[00000000df64b567]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:25 storageqe-109 kernel: dev[00000000c31320a7]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:25 storageqe-109 kernel: dev[00000000c688ea06]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:25 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 9 03:53:25 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:25 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:25 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 9 03:53:25 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:25 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 9 03:53:25 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 9 03:53:25 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 9 03:53:25 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 9 03:53:25 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 9 03:53:25 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:25 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 9 03:53:25 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:25 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 9 03:53:25 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 9 03:53:25 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 9 03:53:25 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:25 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 9 03:53:25 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 9 03:53:25 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:25 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 9 03:53:25 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:25 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 9 03:53:25 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 9 03:53:25 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 9 03:53:25 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 9 03:53:25 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 9 03:53:25 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:25 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:25 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 9 03:53:25 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 9 03:53:25 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:25 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 9 03:53:25 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 9 03:53:25 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 9 03:53:25 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 9 03:53:25 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:25 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 9 03:53:25 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 9 03:53:35 storageqe-109 INFO: Verifying iSCSI target setup... Oct 9 03:53:35 storageqe-109 INFO: Found 4 LIO target(s) Oct 9 03:53:35 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 9 03:53:36 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 03:53:36 storageqe-109 iscsid[2528497]: iscsid shutting down. Oct 9 03:53:36 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 03:53:36 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 03:53:36 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 03:53:36 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 03:53:36 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 03:53:36 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 03:53:36 storageqe-109 iscsid[2529534]: iscsid shutting down. Oct 9 03:53:36 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 03:53:36 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 03:53:36 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 03:53:36 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 03:53:36 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 03:53:36 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 03:53:36 storageqe-109 iscsid[2529540]: iscsid: Login authentication failed with target iqn.2003-01.udisks.test:iscsi-test-noauth, T bit set on response, but authenticaton not complete Oct 9 03:53:36 storageqe-109 iscsid[2529540]: iscsid: connection9:0 Login error (Login status 5) Oct 9 03:53:36 storageqe-109 kernel: iSCSI Login negotiation failed. Oct 9 03:53:36 storageqe-109 iscsid[2529540]: iscsid: Connection9:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 9 03:53:37 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 03:53:37 storageqe-109 iscsid[2529540]: iscsid shutting down. Oct 9 03:53:37 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 03:53:37 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 03:53:37 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 03:53:37 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 03:53:37 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 03:53:37 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 03:53:37 storageqe-109 iscsid[2529553]: iscsid shutting down. Oct 9 03:53:37 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 03:53:37 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 03:53:37 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 03:53:37 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 03:53:37 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 03:53:37 storageqe-109 iscsid[2529557]: iscsid: Connection10:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 9 03:53:37 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 03:53:37 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:37 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 9 03:53:37 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 9 03:53:37 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 9 03:53:37 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:37 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 9 03:53:37 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:37 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 9 03:53:37 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 9 03:53:37 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:37 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk Oct 9 03:53:38 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 9 03:53:38 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 9 03:53:38 storageqe-109 iscsid[2529557]: iscsid: Connection10:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 9 03:53:39 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 9 03:53:39 storageqe-109 INFO: Clearing targetcli configuration... Oct 9 03:53:39 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 9 03:53:39 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 9 03:53:39 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 9 03:53:39 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 9 03:53:39 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 9 03:53:39 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 9 03:53:39 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 9 03:53:39 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 9 03:53:39 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 9 03:53:39 storageqe-109 INFO: Removing test disk files... Oct 9 03:53:39 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 9 03:53:39 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 9 03:53:39 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 9 03:53:39 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 9 03:53:39 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 9 03:53:39 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 9 03:53:39 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 9 03:53:39 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz1983602_iscsi_login_failed #### INFO: #### will start test_bz2136557_iscsi_chap ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:53:46 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:53:46 storageqe-109 INFO: #### END test_bz1983602_iscsi_login_failed #### Oct 9 03:53:46 storageqe-109 INFO: #### will start test_bz2136557_iscsi_chap ##### Oct 9 03:53:46 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 03:53:52 storageqe-109 INFO: Setting up local iSCSI target... Oct 9 03:53:52 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 9 03:53:52 storageqe-109 INFO: Creating test disk files... Oct 9 03:53:52 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 9 03:53:52 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 Oct 9 03:53:52 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 Oct 9 03:53:52 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 9 03:53:52 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 9 03:53:52 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 9 03:53:53 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 9 03:53:53 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 03:53:55 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 03:53:55 storageqe-109 kernel: dev[00000000b513f2d3]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:55 storageqe-109 kernel: dev[00000000aab85186]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:55 storageqe-109 kernel: dev[00000000dd8698a8]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:55 storageqe-109 kernel: dev[0000000056b2b8e2]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:55 storageqe-109 kernel: dev[00000000894ab07f]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:55 storageqe-109 kernel: dev[00000000016047eb]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:55 storageqe-109 kernel: dev[0000000076dec2f0]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 03:53:55 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 9 03:53:55 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:55 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:55 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 9 03:53:55 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 9 03:53:55 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:55 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 9 03:53:55 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 9 03:53:55 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 9 03:53:55 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 9 03:53:55 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:55 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:55 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 9 03:53:55 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:55 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 9 03:53:55 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 9 03:53:55 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 9 03:53:55 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 9 03:53:55 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:55 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 9 03:53:55 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:55 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 9 03:53:55 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:55 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 9 03:53:55 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 9 03:53:55 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 9 03:53:55 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 9 03:53:55 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 03:53:55 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 9 03:53:55 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 9 03:53:55 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 9 03:53:55 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:53:55 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 9 03:53:55 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 9 03:53:55 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 9 03:53:55 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 9 03:53:55 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:53:55 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 9 03:53:55 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 9 03:54:05 storageqe-109 INFO: Verifying iSCSI target setup... Oct 9 03:54:05 storageqe-109 INFO: Found 4 LIO target(s) Oct 9 03:54:05 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 9 03:54:05 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 03:54:05 storageqe-109 iscsid[2529557]: iscsid shutting down. Oct 9 03:54:05 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 03:54:05 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 03:54:05 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 03:54:05 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 03:54:05 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 03:54:05 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 03:54:05 storageqe-109 iscsid[2530037]: iscsid: Connection11:0 to [target: iqn.2003-01.udisks.test:iscsi-test-chap, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 9 03:54:05 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 9 03:54:05 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 9 03:54:05 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 2 Oct 9 03:54:05 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 9 03:54:06 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:54:06 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 9 03:54:06 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:54:06 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:54:06 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 9 03:54:06 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 9 03:54:06 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:54:06 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: initfw_name None Oct 9 03:54:06 storageqe-109 INFO: initfw_name None INFO: init_name iqn.1994-05.com.redhat:iscsi-test INFO: init_name_raw iqn.1994-05.com.redhat:iscsi-test Oct 9 03:54:06 storageqe-109 INFO: init_name iqn.1994-05.com.redhat:iscsi-test Oct 9 03:54:06 storageqe-109 INFO: init_name_raw iqn.1994-05.com.redhat:iscsi-test INFO: target_name iqn.2003-01.udisks.test:iscsi-test-chap Oct 9 03:54:08 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-chap INFO: tpgt 1 Oct 9 03:54:09 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 9 03:54:10 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 9 03:54:11 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 9 03:54:12 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 9 03:54:13 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 9 03:54:14 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 9 03:54:15 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 9 03:54:16 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 Oct 9 03:54:17 storageqe-109 INFO: tgt_reset_timeout 30 Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 9 03:54:17 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 9 03:54:17 storageqe-109 iscsid[2530037]: iscsid: Connection11:0 to [target: iqn.2003-01.udisks.test:iscsi-test-chap, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 9 03:54:17 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 03:54:17 storageqe-109 iscsid[2530037]: iscsid shutting down. Oct 9 03:54:17 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 03:54:17 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 03:54:17 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 03:54:17 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 03:54:17 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 03:54:17 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 03:54:17 storageqe-109 iscsid[2530130]: iscsid: Connection12:0 to [target: iqn.2003-01.udisks.test:iscsi-test-mutual, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 9 03:54:17 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 9 03:54:17 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 9 03:54:17 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 3 Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 03:54:17 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 9 03:54:17 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 03:54:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: target_name iqn.2003-01.udisks.test:iscsi-test-mutual Oct 9 03:54:19 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-mutual INFO: tpgt 1 Oct 9 03:54:20 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 9 03:54:21 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 9 03:54:22 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 9 03:54:23 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 9 03:54:24 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 9 03:54:25 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 9 03:54:26 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 9 03:54:27 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 9 03:54:28 storageqe-109 INFO: tgt_reset_timeout 30 Oct 9 03:54:28 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 9 03:54:28 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 9 03:54:28 storageqe-109 iscsid[2530130]: iscsid: Connection12:0 to [target: iqn.2003-01.udisks.test:iscsi-test-mutual, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 9 03:54:28 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 9 03:54:28 storageqe-109 INFO: Clearing targetcli configuration... Oct 9 03:54:29 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 9 03:54:29 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 9 03:54:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 9 03:54:29 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 9 03:54:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 9 03:54:29 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 9 03:54:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 9 03:54:29 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 9 03:54:29 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 9 03:54:29 storageqe-109 INFO: Removing test disk files... Oct 9 03:54:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 9 03:54:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 9 03:54:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 9 03:54:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 9 03:54:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 9 03:54:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 9 03:54:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 9 03:54:29 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_bz2136557_iscsi_chap #### INFO: #### will start test_md_stop ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:54:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:54:35 storageqe-109 INFO: #### END test_bz2136557_iscsi_chap #### Oct 9 03:54:35 storageqe-109 INFO: #### will start test_md_stop ##### Oct 9 03:54:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:54:42 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:54:42 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_stop_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_stop INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 03:54:42 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 03:54:42 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_stop_1.img) Oct 9 03:54:42 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 03:54:42 storageqe-109 INFO: raid level raid1 Oct 9 03:54:42 storageqe-109 INFO: raid name test_md_stop Oct 9 03:54:42 storageqe-109 INFO: raid chunk 0 Oct 9 03:54:42 storageqe-109 INFO: raid bitmap None Oct 9 03:54:42 storageqe-109 INFO: raid version 1.2 Oct 9 03:55:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:55:08 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 03:55:08 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 03:55:08 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 03:55:08 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 03:55:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:55:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:55:08 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 03:55:13 storageqe-109 kernel: md: md127: resync done. Oct 9 03:55:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:55:42 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 03:55:42 storageqe-109 kernel: md: md127 stopped. Oct 9 03:55:42 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 03:56:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:56:11 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_stop_0.img) Oct 9 03:56:11 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 03:56:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:56:36 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_stop_1.img) Oct 9 03:56:36 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_md_stop #### INFO: #### will start test_fs_label_and_resize ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:56:42 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:56:42 storageqe-109 INFO: #### END test_md_stop #### Oct 9 03:56:42 storageqe-109 INFO: #### will start test_fs_label_and_resize ##### Oct 9 03:56:42 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:56:49 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:56:49 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_fs.img) Oct 9 03:56:49 storageqe-109 kernel: loop0: Oct 9 03:57:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:57:37 storageqe-109 chronyd[999]: Selected source 10.2.32.38 Oct 9 03:57:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:58:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:58:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:59:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:59:07 storageqe-109 kernel: loop0: Oct 9 03:59:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 03:59:32 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_fs.img) Oct 9 03:59:32 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fs_label_and_resize #### INFO: #### will start test_fstab_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:59:39 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:59:39 storageqe-109 INFO: #### END test_fs_label_and_resize #### Oct 9 03:59:39 storageqe-109 INFO: #### will start test_fstab_handling ##### Oct 9 03:59:39 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 03:59:45 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 03:59:45 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_fstab.img) Oct 9 03:59:45 storageqe-109 kernel: loop0: Oct 9 04:00:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:00:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:01:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:01:12 storageqe-109 kernel: loop0: Oct 9 04:01:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:01:37 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_fstab.img) Oct 9 04:01:37 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_fstab_handling #### INFO: #### will start test_manager_device_listing_and_resolving ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:01:43 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:01:43 storageqe-109 INFO: #### END test_fstab_handling #### Oct 9 04:01:43 storageqe-109 INFO: #### will start test_manager_device_listing_and_resolving ##### Oct 9 04:01:43 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:01:48 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 04:01:48 storageqe-109 dnf[2531322]: Updating Subscription Management repositories. Oct 9 04:01:48 storageqe-109 dnf[2531322]: Unable to read consumer identity Oct 9 04:01:48 storageqe-109 dnf[2531322]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-AppStream 588 kB/s | 2.8 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-AppStream-debuginfo 529 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-BaseOS 749 kB/s | 2.7 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-BaseOS-debuginfo 452 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-CRB 803 kB/s | 2.7 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-CRB-debuginfo 629 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-HighAvailability 841 kB/s | 2.8 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-HighAvailability-debuginfo 592 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-NFV 912 kB/s | 2.7 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-NFV-debuginfo 421 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-RT 806 kB/s | 2.7 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-RT-debuginfo 532 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-SAP 780 kB/s | 2.7 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-SAP-debuginfo 456 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-SAPHANA 781 kB/s | 2.7 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: beaker-SAPHANA-debuginfo 549 kB/s | 1.5 kB 00:00 Oct 9 04:01:49 storageqe-109 dnf[2531322]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 9 04:01:50 storageqe-109 dnf[2531322]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 9 04:01:50 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:01:50 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_manager.img) Oct 9 04:01:50 storageqe-109 dnf[2531322]: Google Cloud CLI 4.0 kB/s | 1.4 kB 00:00 Oct 9 04:01:51 storageqe-109 dnf[2531322]: Copr repo for python-ssh2-python312 owned by mh 2.0 kB/s | 1.5 kB 00:00 Oct 9 04:01:52 storageqe-109 dnf[2531322]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 9 04:01:52 storageqe-109 dnf[2531322]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 9 04:01:52 storageqe-109 dnf[2531322]: Metadata cache created. Oct 9 04:01:52 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 04:01:52 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 04:02:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:02:15 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_manager.img) Oct 9 04:02:15 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_manager_device_listing_and_resolving #### INFO: #### will start test_luks_change_password ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:02:21 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:02:21 storageqe-109 INFO: #### END test_manager_device_listing_and_resolving #### Oct 9 04:02:21 storageqe-109 INFO: #### will start test_luks_change_password ##### Oct 9 04:02:21 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:02:28 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:02:28 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_luks_passwd.img) Oct 9 04:02:28 storageqe-109 kernel: loop0: Oct 9 04:02:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'initial_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2id', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 9 04:02:53 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'initial_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2id', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 9 04:03:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:03:28 storageqe-109 stratisd[2509653]: [2025-10-09T08:03:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:03:28 storageqe-109 stratisd[2509653]: [2025-10-09T08:03:28Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:03:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:03:55 storageqe-109 stratisd[2509653]: [2025-10-09T08:03:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:03:55 storageqe-109 stratisd[2509653]: [2025-10-09T08:03:55Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:04:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: HintEncryptionType Oct 9 04:04:22 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 9 04:04:23 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 9 04:04:24 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to argon2id Oct 9 04:04:25 storageqe-109 INFO: foramt to luks2 Oct 9 04:04:25 storageqe-109 INFO: foramt to argon2id Oct 9 04:04:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: changed passwd to redhatredhat Oct 9 04:04:58 storageqe-109 stratisd[2509653]: [2025-10-09T08:04:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:04:58 storageqe-109 stratisd[2509653]: [2025-10-09T08:04:58Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:04:58 storageqe-109 INFO: changed passwd to redhatredhat Oct 9 04:05:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:05:23 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 04:05:23 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 04:05:23 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 04:05:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:05:50 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:06:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:06:17 storageqe-109 stratisd[2509653]: [2025-10-09T08:06:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:06:17 storageqe-109 stratisd[2509653]: [2025-10-09T08:06:17Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:06:17 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 04:06:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: changed passwd to initial_password Oct 9 04:06:51 storageqe-109 stratisd[2509653]: [2025-10-09T08:06:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:06:51 storageqe-109 stratisd[2509653]: [2025-10-09T08:06:51Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:06:51 storageqe-109 INFO: changed passwd to initial_password Oct 9 04:07:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:07:16 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 04:07:16 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 04:07:16 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 04:07:29 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 04:07:29 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 04:07:29 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 04:07:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:07:43 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:08:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:08:10 storageqe-109 stratisd[2509653]: [2025-10-09T08:08:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:08:10 storageqe-109 stratisd[2509653]: [2025-10-09T08:08:10Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:08:10 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 04:08:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:08:43 storageqe-109 stratisd[2509653]: [2025-10-09T08:08:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:08:43 storageqe-109 stratisd[2509653]: [2025-10-09T08:08:43Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:09:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:09:08 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 04:09:09 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 04:09:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:09:36 storageqe-109 INFO: the old passwd can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:10:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:10:03 storageqe-109 stratisd[2509653]: [2025-10-09T08:10:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:10:03 storageqe-109 stratisd[2509653]: [2025-10-09T08:10:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:10:03 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 04:10:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:10:36 storageqe-109 stratisd[2509653]: [2025-10-09T08:10:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:10:36 storageqe-109 stratisd[2509653]: [2025-10-09T08:10:36Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:11:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:11:01 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 04:11:02 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 04:11:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:11:29 storageqe-109 INFO: the dbus.Dictionary({'keyfile_contents': '/tmp/passwd'}, signature=dbus.Signature('sv')) can not unlock device org.freedesktop.UDisks2.Error.Failed: Error unlocking /dev/loop0p1: Failed to activate device: Incorrect passphrase. Oct 9 04:11:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:11:56 storageqe-109 stratisd[2509653]: [2025-10-09T08:11:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:11:56 storageqe-109 stratisd[2509653]: [2025-10-09T08:11:56Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:11:56 storageqe-109 udisksd[2509680]: Unlocked device /dev/loop0p1 as /dev/dm-3 Oct 9 04:12:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:12:29 storageqe-109 stratisd[2509653]: [2025-10-09T08:12:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:12:29 storageqe-109 stratisd[2509653]: [2025-10-09T08:12:29Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:12:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:12:54 storageqe-109 udisksd[2509680]: LUKS device 253:3 was manually removed Oct 9 04:12:55 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 04:13:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:13:25 storageqe-109 kernel: loop0: Oct 9 04:13:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:13:50 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_luks_passwd.img) Oct 9 04:13:50 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_change_password #### INFO: #### will start test_manager_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:13:56 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:13:56 storageqe-109 INFO: #### END test_luks_change_password #### Oct 9 04:13:56 storageqe-109 INFO: #### will start test_manager_properties ##### Oct 9 04:13:56 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_manager_properties #### INFO: #### will start test_nvme_manager_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:11 storageqe-109 INFO: #### END test_manager_properties #### Oct 9 04:14:11 storageqe-109 INFO: #### will start test_nvme_manager_properties ##### Oct 9 04:14:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_manager_properties #### INFO: #### will start test_nvme_smart_update ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:29 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:29 storageqe-109 INFO: #### END test_nvme_manager_properties #### Oct 9 04:14:29 storageqe-109 INFO: #### will start test_nvme_smart_update ##### Oct 9 04:14:29 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_update #### INFO: #### will start test_nvme_smart_get_attributes ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:45 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:45 storageqe-109 INFO: #### END test_nvme_smart_update #### Oct 9 04:14:45 storageqe-109 INFO: #### will start test_nvme_smart_get_attributes ##### Oct 9 04:14:45 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_get_attributes #### INFO: #### will start test_nvme_smart_self_test ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:14:58 storageqe-109 INFO: #### END test_nvme_smart_get_attributes #### Oct 9 04:14:58 storageqe-109 INFO: #### will start test_nvme_smart_self_test ##### Oct 9 04:14:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:15:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_self_test #### INFO: #### will start test_nvme_properties_validation ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:15:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:15:38 storageqe-109 INFO: #### END test_nvme_smart_self_test #### Oct 9 04:15:38 storageqe-109 INFO: #### will start test_nvme_properties_validation ##### Oct 9 04:15:38 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_properties_validation #### INFO: #### will start test_iscsi_session_logout_no_interface ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:15:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:15:57 storageqe-109 INFO: #### END test_nvme_properties_validation #### Oct 9 04:15:57 storageqe-109 INFO: #### will start test_iscsi_session_logout_no_interface ##### Oct 9 04:15:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 04:16:03 storageqe-109 INFO: Setting up local iSCSI target... Oct 9 04:16:03 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 9 04:16:03 storageqe-109 INFO: Creating test disk files... Oct 9 04:16:03 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 9 04:16:03 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 04:16:03 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 9 04:16:03 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 9 04:16:04 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 9 04:16:04 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 9 04:16:04 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 9 04:16:04 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 04:16:06 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 04:16:06 storageqe-109 kernel: dev[000000003dbe9af2]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 04:16:06 storageqe-109 kernel: dev[000000009cdbba7b]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 04:16:06 storageqe-109 kernel: dev[00000000e080fe0d]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 04:16:06 storageqe-109 kernel: dev[00000000c31320a7]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 04:16:06 storageqe-109 kernel: dev[00000000c688ea06]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 04:16:06 storageqe-109 kernel: dev[00000000b23ca8f1]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 04:16:06 storageqe-109 kernel: dev[0000000018a82429]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 04:16:06 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 9 04:16:06 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 04:16:06 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 9 04:16:06 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 9 04:16:06 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 9 04:16:06 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 04:16:06 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 9 04:16:06 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 9 04:16:06 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 04:16:06 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:06 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 9 04:16:06 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 04:16:06 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 9 04:16:06 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 9 04:16:06 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 9 04:16:06 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 9 04:16:06 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 04:16:06 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 9 04:16:06 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 9 04:16:06 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:06 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 04:16:06 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:06 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 9 04:16:06 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 04:16:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 9 04:16:07 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 9 04:16:07 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 9 04:16:07 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 9 04:16:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 04:16:07 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 9 04:16:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 9 04:16:07 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 9 04:16:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 04:16:07 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 9 04:16:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 9 04:16:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 9 04:16:07 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 04:16:07 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 9 04:16:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:07 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 9 04:16:07 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 9 04:16:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 04:16:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 9 04:16:07 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 9 04:16:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 04:16:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 9 04:16:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 9 04:16:07 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:07 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 9 04:16:07 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 9 04:16:17 storageqe-109 INFO: Verifying iSCSI target setup... Oct 9 04:16:17 storageqe-109 INFO: Found 4 LIO target(s) Oct 9 04:16:17 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 9 04:16:17 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 04:16:17 storageqe-109 iscsid[2530130]: iscsid shutting down. Oct 9 04:16:17 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 04:16:17 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 04:16:17 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 04:16:17 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 04:16:17 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 04:16:17 storageqe-109 iscsid[2541166]: iscsid: Connection13:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 9 04:16:17 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 04:16:17 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 9 04:16:17 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 9 04:16:17 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 9 04:16:17 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 9 04:16:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 04:16:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 9 04:16:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 04:16:17 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 9 04:16:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 9 04:16:17 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 04:16:17 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: target_name iqn.2003-01.udisks.test:iscsi-test-noauth Oct 9 04:16:19 storageqe-109 INFO: target_name iqn.2003-01.udisks.test:iscsi-test-noauth INFO: tpgt 1 Oct 9 04:16:20 storageqe-109 INFO: tpgt 1 INFO: address 127.0.0.1 Oct 9 04:16:21 storageqe-109 INFO: address 127.0.0.1 INFO: port 0 Oct 9 04:16:22 storageqe-109 INFO: port 0 INFO: persistent_address 127.0.0.1 Oct 9 04:16:23 storageqe-109 INFO: persistent_address 127.0.0.1 INFO: persistent_port 3260 Oct 9 04:16:24 storageqe-109 INFO: persistent_port 3260 INFO: abort_timeout 15 Oct 9 04:16:25 storageqe-109 INFO: abort_timeout 15 INFO: lu_reset_timeout 30 Oct 9 04:16:26 storageqe-109 INFO: lu_reset_timeout 30 INFO: recovery_timeout 120 Oct 9 04:16:27 storageqe-109 INFO: recovery_timeout 120 INFO: tgt_reset_timeout 30 INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 9 04:16:28 storageqe-109 INFO: tgt_reset_timeout 30 Oct 9 04:16:28 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 9 04:16:28 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 9 04:16:28 storageqe-109 iscsid[2541166]: iscsid: Connection13:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 9 04:16:28 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 9 04:16:28 storageqe-109 INFO: Clearing targetcli configuration... Oct 9 04:16:28 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 9 04:16:28 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 9 04:16:29 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 9 04:16:29 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 9 04:16:29 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 9 04:16:29 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 9 04:16:29 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 9 04:16:29 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 9 04:16:29 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 9 04:16:29 storageqe-109 INFO: Removing test disk files... Oct 9 04:16:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 9 04:16:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 9 04:16:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 9 04:16:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 9 04:16:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 9 04:16:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 9 04:16:29 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 9 04:16:29 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_iscsi_session_logout_no_interface #### INFO: #### will start test_iscsi_discover_invalid_target ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:16:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:16:35 storageqe-109 INFO: #### END test_iscsi_session_logout_no_interface #### Oct 9 04:16:35 storageqe-109 INFO: #### will start test_iscsi_discover_invalid_target ##### Oct 9 04:16:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_iscsi_discover_invalid_target #### INFO: #### will start test_vdo_deduplication_and_compression ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:16:48 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:16:48 storageqe-109 INFO: #### END test_iscsi_discover_invalid_target #### Oct 9 04:16:48 storageqe-109 INFO: #### will start test_vdo_deduplication_and_compression ##### Oct 9 04:16:48 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:17:03 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 9 04:17:03 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_vdo_dedup.img) Oct 9 04:17:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:17:29 storageqe-109 lvm[2541798]: PV /dev/loop0 not used. Oct 9 04:17:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:17:54 storageqe-109 lvm[2541806]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:17:54 storageqe-109 systemd[1]: Started lvm-activate-test_vdo_vg.service - [systemd-run] /usr/sbin/lvm vgchange -aay --autoactivation event test_vdo_vg. Oct 9 04:17:54 storageqe-109 lvm[2541810]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:17:54 storageqe-109 lvm[2541810]: VG test_vdo_vg finished Oct 9 04:17:54 storageqe-109 lvm[2541809]: 0 logical volume(s) in volume group "test_vdo_vg" now active Oct 9 04:17:54 storageqe-109 lvm[2541811]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:17:54 storageqe-109 lvm[2541811]: VG test_vdo_vg finished Oct 9 04:17:54 storageqe-109 systemd[1]: lvm-activate-test_vdo_vg.service: Deactivated successfully. Oct 9 04:18:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:18:20 storageqe-109 UDS/vdoformat[2541828]: INFO (vdoformat/2541828) Using 2 indexing zones for concurrency. Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo24:lvm: loading device '253:4' Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo24:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo24:lvm: starting device '253:4' Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:physQ0: VDO commencing normal operation Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:journa: Setting UDS index target state to online Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: creating index: 253:3 Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: Using 2 indexing zones for concurrency. Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' started Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:18:20 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:18:20 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:18:20 storageqe-109 lvm[2541869]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:18:20 storageqe-109 lvm[2541869]: VG test_vdo_vg finished INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_vg/udisks_test_vdopool Oct 9 04:18:22 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_vg/udisks_test_vdopool INFO: OperatingMode normal Oct 9 04:18:23 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 9 04:18:24 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 9 04:18:25 storageqe-109 INFO: IndexState online INFO: UsedSize 3219931136 Oct 9 04:18:26 storageqe-109 INFO: UsedSize 3219931136 INFO: Compression 1 Oct 9 04:18:27 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 9 04:18:28 storageqe-109 INFO: Deduplication 1 Oct 9 04:18:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:18:53 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: beginning save (vcn 18446744073709551615) Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: finished save (vcn 18446744073709551615) Oct 9 04:18:53 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:18:53 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:18:53 storageqe-109 lvm[2541974]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:18:53 storageqe-109 lvm[2541974]: VG test_vdo_vg finished Oct 9 04:19:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:19:19 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:19:19 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:19:19 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:19:19 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:19:19 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:19:19 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:19:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 9 04:19:19 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:19:19 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:19:19 storageqe-109 lvm[2541996]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:19:19 storageqe-109 lvm[2541996]: VG test_vdo_vg finished Oct 9 04:19:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:19:45 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loading or rebuilding index: 253:3 Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: Using 2 indexing zones for concurrency. Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:19:45 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:19:45 storageqe-109 lvm[2542020]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:19:45 storageqe-109 lvm[2542020]: VG test_vdo_vg finished Oct 9 04:19:45 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loaded index from chapter 0 through chapter 0 Oct 9 04:20:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:20:11 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:20:11 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:20:11 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:20:11 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:20:11 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:20:11 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:20:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 9 04:20:11 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:20:11 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:20:11 storageqe-109 lvm[2542045]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:20:11 storageqe-109 lvm[2542045]: VG test_vdo_vg finished Oct 9 04:20:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: Preparing to resize physical to 2358272 Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: Done preparing to resize physical Oct 9 04:20:40 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: Physical block count was 1833984, now 2358272 Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 9 04:20:40 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:20:40 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:20:40 storageqe-109 lvm[2542073]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:20:40 storageqe-109 lvm[2542073]: VG test_vdo_vg finished INFO: the 9659482112 8589934592 Oct 9 04:20:43 storageqe-109 INFO: the 9659482112 8589934592 INFO:before lv vdo 80509665280 Oct 9 04:20:44 storageqe-109 journal: INFO:before lv vdo 80509665280 Oct 9 04:21:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: Preparing to resize logical to 98278656 Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: Done preparing to resize logical Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: Resizing logical to 98278656 Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: Logical blocks now 98278656 Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:21:09 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 9 04:21:09 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:21:09 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:21:09 storageqe-109 lvm[2542108]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:21:09 storageqe-109 lvm[2542108]: VG test_vdo_vg finished INFO: after lv vdo 402548326400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 5 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 63 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 9 04:21:11 storageqe-109 INFO: after lv vdo 402548326400 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 5 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics maxVIOs 63 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 24 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 98278656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9433088 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics instance 24 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 9 04:21:11 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 98278656 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9433088 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573250 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 5 INFO: vdo.GetStatistics overheadBlocksUsed 786470 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 34 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573250 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 5 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 786470 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics usedPercent 34 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2358272 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2358272 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 3 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 3 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 9 04:21:12 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 9 04:21:13 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 9 04:21:13 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 9 04:21:13 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 9 04:21:13 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 9 04:21:13 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 9 04:21:13 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 9 04:21:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:21:40 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:21:40 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:21:40 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:21:40 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:21:40 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:21:40 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:21:40 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 9 04:21:40 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:21:40 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:21:40 storageqe-109 lvm[2542790]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:21:40 storageqe-109 lvm[2542790]: VG test_vdo_vg finished Oct 9 04:22:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:22:05 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:22:05 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:22:05 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:22:05 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:22:05 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:22:05 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:22:05 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 9 04:22:05 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:22:05 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:22:05 storageqe-109 lvm[2542814]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:22:05 storageqe-109 lvm[2542814]: VG test_vdo_vg finished Oct 9 04:22:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:22:32 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loading or rebuilding index: 253:3 Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is disabled Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: Using 2 indexing zones for concurrency. Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:22:32 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:22:32 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:dedupe: loaded index from chapter 0 through chapter 0 Oct 9 04:22:32 storageqe-109 lvm[2542842]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:22:32 storageqe-109 lvm[2542842]: VG test_vdo_vg finished Oct 9 04:22:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:22:57 storageqe-109 kernel: device-mapper: vdo24:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:22:57 storageqe-109 kernel: device-mapper: vdo24:lvm: preparing to modify device '253:4' Oct 9 04:22:57 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:22:57 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:22:57 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:22:57 storageqe-109 kernel: device-mapper: vdo24:lvm: resuming device '253:4' Oct 9 04:22:57 storageqe-109 kernel: device-mapper: vdo: dm_vdo24:packer: compression is enabled Oct 9 04:22:57 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' resumed Oct 9 04:22:57 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:22:57 storageqe-109 lvm[2542865]: PV /dev/loop0 online, VG test_vdo_vg is complete. Oct 9 04:22:57 storageqe-109 lvm[2542865]: VG test_vdo_vg finished Oct 9 04:23:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:23:25 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 04:23:25 storageqe-109 kernel: device-mapper: vdo24:lvm: suspending device '253:4' Oct 9 04:23:25 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' suspended Oct 9 04:23:25 storageqe-109 kernel: device-mapper: vdo24:lvm: stopping device '253:4' Oct 9 04:23:25 storageqe-109 kernel: device-mapper: vdo24:lvm: device '253:4' stopped Oct 9 04:23:26 storageqe-109 lvm[2542881]: PV /dev/loop0 not used. Oct 9 04:23:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:23:51 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_vdo_dedup.img) Oct 9 04:23:51 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_vdo_deduplication_and_compression #### INFO: #### will start test_partition_resize ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:23:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:23:57 storageqe-109 INFO: #### END test_vdo_deduplication_and_compression #### Oct 9 04:23:57 storageqe-109 INFO: #### will start test_partition_resize ##### Oct 9 04:23:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:24:03 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:24:03 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_resize.img) Oct 9 04:24:03 storageqe-109 kernel: loop0: Oct 9 04:24:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:24:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:24:54 storageqe-109 kernel: loop0: p1 Oct 9 04:25:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:25:23 storageqe-109 kernel: loop0: p1 Oct 9 04:25:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:25:58 storageqe-109 kernel: loop0: Oct 9 04:26:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:26:23 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_resize.img) Oct 9 04:26:23 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_partition_resize #### INFO: #### will start test_nvme_size_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:26:29 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:26:29 storageqe-109 INFO: #### END test_partition_resize #### Oct 9 04:26:29 storageqe-109 INFO: #### will start test_nvme_size_properties ##### Oct 9 04:26:29 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_size_properties #### INFO: #### will start test_iscsi_get_firmware_initiator_name_failure ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:26:45 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:26:45 storageqe-109 INFO: #### END test_nvme_size_properties #### Oct 9 04:26:45 storageqe-109 INFO: #### will start test_iscsi_get_firmware_initiator_name_failure ##### Oct 9 04:26:45 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_iscsi_get_firmware_initiator_name_failure #### INFO: #### will start test_mdraid_basic_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:26:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:26:58 storageqe-109 INFO: #### END test_iscsi_get_firmware_initiator_name_failure #### Oct 9 04:26:58 storageqe-109 INFO: #### will start test_mdraid_basic_properties ##### Oct 9 04:26:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:27:04 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:27:04 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_props1.img) Oct 9 04:27:05 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:27:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_props2.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_props INFO: raid chunk 524288 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:27:05 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 04:27:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/loop_md_props3.img) Oct 9 04:27:05 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 9 04:27:05 storageqe-109 INFO: raid level raid5 Oct 9 04:27:05 storageqe-109 INFO: raid name test_md_props Oct 9 04:27:05 storageqe-109 INFO: raid chunk 524288 Oct 9 04:27:05 storageqe-109 INFO: raid bitmap None Oct 9 04:27:05 storageqe-109 INFO: raid version 1.2 Oct 9 04:27:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:27:30 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 9 04:27:30 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 9 04:27:30 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 9 04:27:30 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 9 04:27:30 storageqe-109 kernel: md: recover of RAID array md127 Oct 9 04:27:30 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:27:30 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:27:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:27:36 storageqe-109 kernel: md: md127: recover done. Oct 9 04:28:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:28:04 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 9 04:28:04 storageqe-109 kernel: md: md127 stopped. Oct 9 04:28:04 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:28:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:28:32 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_props1.img) Oct 9 04:28:32 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:28:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:28:57 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_props2.img) Oct 9 04:28:57 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 04:29:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:29:22 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/loop_md_props3.img) Oct 9 04:29:22 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_basic_properties #### INFO: #### will start test_mdraid_set_bitmap_location ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:29:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:29:28 storageqe-109 INFO: #### END test_mdraid_basic_properties #### Oct 9 04:29:28 storageqe-109 INFO: #### will start test_mdraid_set_bitmap_location ##### Oct 9 04:29:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:29:34 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:29:34 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_set_bitmap1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_set_bitmap INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:29:35 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:29:35 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_set_bitmap2.img) Oct 9 04:29:35 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 04:29:35 storageqe-109 INFO: raid level raid1 Oct 9 04:29:35 storageqe-109 INFO: raid name test_md_set_bitmap Oct 9 04:29:35 storageqe-109 INFO: raid chunk 0 Oct 9 04:29:35 storageqe-109 INFO: raid bitmap None Oct 9 04:29:35 storageqe-109 INFO: raid version 1.2 Oct 9 04:30:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:30:00 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 04:30:00 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 04:30:00 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 04:30:00 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 04:30:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:30:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:30:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:30:05 storageqe-109 kernel: md: md127: resync done. Oct 9 04:30:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:30:33 storageqe-109 kernel: md127: bitmap file is out of date (0 < 17) -- forcing full recovery Oct 9 04:30:33 storageqe-109 kernel: md127: bitmap file is out of date, doing full recovery Oct 9 04:31:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:31:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:31:28 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 04:31:28 storageqe-109 kernel: md: md127 stopped. Oct 9 04:31:28 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:31:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:31:56 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_set_bitmap1.img) Oct 9 04:31:56 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:32:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:32:21 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_set_bitmap2.img) Oct 9 04:32:21 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_set_bitmap_location #### INFO: #### will start test_mdraid_with_internal_bitmap ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:32:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:32:28 storageqe-109 INFO: #### END test_mdraid_set_bitmap_location #### Oct 9 04:32:28 storageqe-109 INFO: #### will start test_mdraid_with_internal_bitmap ##### Oct 9 04:32:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:32:34 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:32:34 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_bitmap1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_bitmap INFO: raid chunk 0 INFO: raid bitmap internal INFO: raid version 1.2 Oct 9 04:32:35 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:32:35 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_bitmap2.img) Oct 9 04:32:35 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 04:32:35 storageqe-109 INFO: raid level raid1 Oct 9 04:32:35 storageqe-109 INFO: raid name test_md_bitmap Oct 9 04:32:35 storageqe-109 INFO: raid chunk 0 Oct 9 04:32:35 storageqe-109 INFO: raid bitmap internal Oct 9 04:32:35 storageqe-109 INFO: raid version 1.2 Oct 9 04:33:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:33:00 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 04:33:00 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 04:33:00 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 04:33:00 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 04:33:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:33:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:33:00 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:33:05 storageqe-109 kernel: md: md127: resync done. Oct 9 04:33:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:33:34 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 04:33:34 storageqe-109 kernel: md: md127 stopped. Oct 9 04:33:34 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:34:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:34:02 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_bitmap1.img) Oct 9 04:34:02 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:34:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:34:27 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_bitmap2.img) Oct 9 04:34:27 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_with_internal_bitmap #### INFO: #### will start test_mdraid_sync_progress_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:34:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:34:33 storageqe-109 INFO: #### END test_mdraid_with_internal_bitmap #### Oct 9 04:34:33 storageqe-109 INFO: #### will start test_mdraid_sync_progress_properties ##### Oct 9 04:34:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:34:40 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:34:40 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_progress1.img) Oct 9 04:34:40 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_progress INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:34:40 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_progress2.img) Oct 9 04:34:40 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 04:34:40 storageqe-109 INFO: raid level raid1 Oct 9 04:34:40 storageqe-109 INFO: raid name test_md_progress Oct 9 04:34:40 storageqe-109 INFO: raid chunk 0 Oct 9 04:34:40 storageqe-109 INFO: raid bitmap None Oct 9 04:34:40 storageqe-109 INFO: raid version 1.2 Oct 9 04:35:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:35:05 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 04:35:05 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 04:35:05 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 04:35:05 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 04:35:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:35:05 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:35:06 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:35:11 storageqe-109 kernel: md: md127: resync done. Oct 9 04:35:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:35:48 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 04:35:48 storageqe-109 kernel: md: md127 stopped. Oct 9 04:35:48 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:36:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:36:16 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_progress1.img) Oct 9 04:36:16 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:36:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:36:41 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_progress2.img) Oct 9 04:36:41 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_sync_progress_properties #### INFO: #### will start test_mdraid_consistency_policy ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:36:47 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:36:47 storageqe-109 INFO: #### END test_mdraid_sync_progress_properties #### Oct 9 04:36:47 storageqe-109 INFO: #### will start test_mdraid_consistency_policy ##### Oct 9 04:36:47 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:36:53 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:36:53 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_policy1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_policy INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:36:54 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:36:54 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_policy2.img) Oct 9 04:36:54 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 04:36:54 storageqe-109 INFO: raid level raid1 Oct 9 04:36:54 storageqe-109 INFO: raid name test_md_policy Oct 9 04:36:54 storageqe-109 INFO: raid chunk 0 Oct 9 04:36:54 storageqe-109 INFO: raid bitmap None Oct 9 04:36:54 storageqe-109 INFO: raid version 1.2 Oct 9 04:37:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:37:19 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 04:37:19 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 04:37:19 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 04:37:19 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 04:37:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:37:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:37:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:37:24 storageqe-109 kernel: md: md127: resync done. Oct 9 04:37:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:37:53 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 04:37:53 storageqe-109 kernel: md: md127 stopped. Oct 9 04:37:53 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:38:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:38:21 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_policy1.img) Oct 9 04:38:21 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:38:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:38:46 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_policy2.img) Oct 9 04:38:46 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_consistency_policy #### INFO: #### will start test_mdraid_sync_actions ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:38:52 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:38:52 storageqe-109 INFO: #### END test_mdraid_consistency_policy #### Oct 9 04:38:52 storageqe-109 INFO: #### will start test_mdraid_sync_actions ##### Oct 9 04:38:52 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:38:59 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:38:59 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_sync1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_sync INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:38:59 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:38:59 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_sync2.img) Oct 9 04:38:59 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 04:38:59 storageqe-109 INFO: raid level raid1 Oct 9 04:38:59 storageqe-109 INFO: raid name test_md_sync Oct 9 04:38:59 storageqe-109 INFO: raid chunk 0 Oct 9 04:38:59 storageqe-109 INFO: raid bitmap None Oct 9 04:38:59 storageqe-109 INFO: raid version 1.2 Oct 9 04:39:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:39:25 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 04:39:25 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 04:39:25 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 04:39:25 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 04:39:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:39:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:39:25 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:39:30 storageqe-109 kernel: md: md127: resync done. Oct 9 04:39:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:39:57 storageqe-109 kernel: md: check of RAID array md127 Oct 9 04:40:02 storageqe-109 kernel: md: md127: check done. Oct 9 04:40:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:40:30 storageqe-109 kernel: md: repair of RAID array md127 Oct 9 04:40:35 storageqe-109 kernel: md: md127: repair done. Oct 9 04:40:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:40:57 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 04:40:57 storageqe-109 kernel: md: md127 stopped. Oct 9 04:40:57 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:41:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:41:25 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_sync1.img) Oct 9 04:41:25 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:41:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:41:50 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_sync2.img) Oct 9 04:41:50 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_sync_actions #### INFO: #### will start test_luks_remove_with_teardown ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:41:56 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:41:56 storageqe-109 INFO: #### END test_mdraid_sync_actions #### Oct 9 04:41:56 storageqe-109 INFO: #### will start test_luks_remove_with_teardown ##### Oct 9 04:41:56 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:42:03 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:42:03 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_luks_teardown.img) Oct 9 04:42:03 storageqe-109 kernel: loop0: Oct 9 04:42:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'teardown_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2id', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 9 04:42:28 storageqe-109 INFO: foramt with dbus.Dictionary({'encrypt.passphrase': 'teardown_password', 'encrypt.type': 'luks2', 'encrypt.pbkdf': 'argon2id', 'encrypt.memory': dbus.UInt32(1000000)}, signature=dbus.Signature('sv')) Oct 9 04:42:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:43:03 storageqe-109 stratisd[2509653]: [2025-10-09T08:43:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:43:03 storageqe-109 stratisd[2509653]: [2025-10-09T08:43:03Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:43:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:43:30 storageqe-109 stratisd[2509653]: [2025-10-09T08:43:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:43:30 storageqe-109 stratisd[2509653]: [2025-10-09T08:43:30Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 04:43:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: HintEncryptionType Oct 9 04:43:57 storageqe-109 INFO: HintEncryptionType INFO: MetadataSize 16777216 Oct 9 04:43:58 storageqe-109 INFO: MetadataSize 16777216 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 Oct 9 04:43:59 storageqe-109 INFO: CleartextDevice /org/freedesktop/UDisks2/block_devices/dm_2d3 INFO: foramt to luks2 INFO: foramt to argon2id Oct 9 04:44:00 storageqe-109 INFO: foramt to luks2 Oct 9 04:44:00 storageqe-109 INFO: foramt to argon2id Oct 9 04:44:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:44:27 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 04:44:27 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 04:44:27 storageqe-109 udisksd[2509680]: Locked device /dev/loop0p1 (was unlocked as /dev/dm-3) Oct 9 04:45:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:45:01 storageqe-109 kernel: loop0: Oct 9 04:45:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:45:26 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_luks_teardown.img) Oct 9 04:45:26 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_remove_with_teardown #### INFO: #### will start test_vdo_resize ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:45:32 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:45:32 storageqe-109 INFO: #### END test_luks_remove_with_teardown #### Oct 9 04:45:32 storageqe-109 INFO: #### will start test_vdo_resize ##### Oct 9 04:45:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:45:48 storageqe-109 kernel: loop0: detected capacity change from 0 to 31457280 Oct 9 04:45:48 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_vdo_resize1.img) Oct 9 04:46:02 storageqe-109 kernel: loop1: detected capacity change from 0 to 31457280 Oct 9 04:46:02 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_vdo_resize2.img) Oct 9 04:46:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:46:27 storageqe-109 lvm[2547795]: PV /dev/loop0 not used. Oct 9 04:46:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:46:52 storageqe-109 lvm[2547804]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:46:52 storageqe-109 systemd[1]: Started lvm-activate-test_vdo_resize_vg.service - [systemd-run] /usr/sbin/lvm vgchange -aay --autoactivation event test_vdo_resize_vg. Oct 9 04:46:52 storageqe-109 lvm[2547808]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:46:52 storageqe-109 lvm[2547808]: VG test_vdo_resize_vg finished Oct 9 04:46:52 storageqe-109 lvm[2547807]: 0 logical volume(s) in volume group "test_vdo_resize_vg" now active Oct 9 04:46:52 storageqe-109 lvm[2547809]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:46:52 storageqe-109 lvm[2547809]: VG test_vdo_resize_vg finished Oct 9 04:46:52 storageqe-109 systemd[1]: lvm-activate-test_vdo_resize_vg.service: Deactivated successfully. Oct 9 04:47:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:47:19 storageqe-109 UDS/vdoformat[2547827]: INFO (vdoformat/2547827) Using 2 indexing zones for concurrency. Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo25:lvm: loading device '253:4' Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo25:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo25:lvm: starting device '253:4' Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:physQ0: VDO commencing normal operation Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:journa: Setting UDS index target state to online Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: creating index: 253:3 Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: Using 2 indexing zones for concurrency. Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' started Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:47:19 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:47:19 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:47:19 storageqe-109 lvm[2547868]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:47:19 storageqe-109 lvm[2547868]: VG test_vdo_resize_vg finished INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_resize_vg/udisks_test_vdopool Oct 9 04:47:20 storageqe-109 INFO: VDOPool /org/freedesktop/UDisks2/lvm/test_vdo_resize_vg/udisks_test_vdopool INFO: OperatingMode normal Oct 9 04:47:21 storageqe-109 INFO: OperatingMode normal INFO: CompressionState online Oct 9 04:47:22 storageqe-109 INFO: CompressionState online INFO: IndexState online Oct 9 04:47:23 storageqe-109 INFO: IndexState online INFO: UsedSize 3219931136 Oct 9 04:47:24 storageqe-109 INFO: UsedSize 3219931136 INFO: Compression 1 Oct 9 04:47:25 storageqe-109 INFO: Compression 1 INFO: Deduplication 1 Oct 9 04:47:26 storageqe-109 INFO: Deduplication 1 Oct 9 04:47:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:47:51 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:47:51 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:47:51 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:47:51 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:47:51 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:47:51 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:47:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: beginning save (vcn 18446744073709551615) Oct 9 04:47:51 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:47:52 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:47:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: finished save (vcn 18446744073709551615) Oct 9 04:47:52 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:47:52 storageqe-109 lvm[2547927]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:47:52 storageqe-109 lvm[2547927]: VG test_vdo_resize_vg finished Oct 9 04:48:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:48:18 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:48:18 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:48:18 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:48:18 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:48:18 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:48:18 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:48:18 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is disabled Oct 9 04:48:18 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:48:18 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:48:18 storageqe-109 lvm[2547949]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:48:18 storageqe-109 lvm[2547949]: VG test_vdo_resize_vg finished Oct 9 04:48:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:48:44 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: loading or rebuilding index: 253:3 Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is disabled Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: Using 2 indexing zones for concurrency. Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:48:44 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:48:44 storageqe-109 lvm[2548017]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:48:44 storageqe-109 lvm[2548017]: VG test_vdo_resize_vg finished Oct 9 04:48:44 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:dedupe: loaded index from chapter 0 through chapter 0 Oct 9 04:49:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:49:10 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 1833984 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:49:10 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:49:10 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:49:10 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:49:10 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:49:10 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:49:10 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:49:10 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:49:10 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:49:10 storageqe-109 lvm[2548044]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:49:10 storageqe-109 lvm[2548044]: VG test_vdo_resize_vg finished Oct 9 04:49:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize physical to 2358272 Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize physical Oct 9 04:49:38 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: Physical block count was 1833984, now 2358272 Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:49:38 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:49:38 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:49:38 storageqe-109 lvm[2548072]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:49:38 storageqe-109 lvm[2548072]: VG test_vdo_resize_vg finished INFO: the 9659482112 8589934592 Oct 9 04:49:41 storageqe-109 INFO: the 9659482112 8589934592 INFO:before lv vdo 80509665280 Oct 9 04:49:42 storageqe-109 journal: INFO:before lv vdo 80509665280 Oct 9 04:50:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:50:07 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:50:07 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:50:07 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize logical to 98278656 Oct 9 04:50:07 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize logical Oct 9 04:50:08 storageqe-109 dmeventd[2527600]: Failed to parse status. Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: Resizing logical to 98278656 Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: Logical blocks now 98278656 Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:50:08 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:50:08 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:50:08 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:50:08 storageqe-109 lvm[2548106]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:50:08 storageqe-109 lvm[2548106]: VG test_vdo_resize_vg finished INFO: after lv vdo 402548326400 INFO: vdo.GetStatistics fiveTwelveByteEmulation false INFO: vdo.GetStatistics biosJournalEmptyFlush 0 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 INFO: vdo.GetStatistics slabJournalBlockedCount 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 INFO: vdo.GetStatistics biosJournalRead 0 INFO: vdo.GetStatistics blockMapCacheSize 134217728 INFO: vdo.GetStatistics indexEntriesDiscarded 0 INFO: vdo.GetStatistics blockMapWriteCount 0 INFO: vdo.GetStatistics biosMetaCompletedRead 5 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 INFO: vdo.GetStatistics blockSize 4096 INFO: vdo.GetStatistics blocksStarted 0 INFO: vdo.GetStatistics maxVIOs 63 INFO: vdo.GetStatistics biosInPartialDiscard 0 INFO: vdo.GetStatistics recoveryPercentage 100 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 INFO: vdo.GetStatistics biosInProgressDiscard 0 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 9 04:50:10 storageqe-109 INFO: after lv vdo 402548326400 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics fiveTwelveByteEmulation false Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedWrite 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics slabJournalBlockedCount 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalRead 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapCacheSize 134217728 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics indexEntriesDiscarded 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapWriteCount 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedRead 5 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceValid 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockSize 4096 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blocksStarted 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics maxVIOs 63 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInPartialDiscard 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics recoveryPercentage 100 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedRead 2096 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics oneKBlocksUsed 3145880 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialWrite 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInProgressEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInProgressDiscard 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics oneKBlocksAvailable 6287208 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedWrite 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics hashLockDedupeAdviceStale 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics currentVIOsInProgress 0 INFO: vdo.GetStatistics instance 25 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 INFO: vdo.GetStatistics slabJournalFlushCount 0 INFO: vdo.GetStatistics biosJournalCompletedFua 0 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 INFO: vdo.GetStatistics indexUpdatesNotFound 0 INFO: vdo.GetStatistics savingPercent 100 INFO: vdo.GetStatistics savings 100 INFO: vdo.GetStatistics indexPostsFound 0 INFO: vdo.GetStatistics biosAcknowledgedFua 0 INFO: vdo.GetStatistics indexPostsNotFound 0 INFO: vdo.GetStatistics blockMapReadOutgoing 0 INFO: vdo.GetStatistics journalEntriesWritten 0 INFO: vdo.GetStatistics biosPageCacheFua 0 INFO: vdo.GetStatistics biosJournalFua 0 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 INFO: vdo.GetStatistics biosOutEmptyFlush 0 INFO: vdo.GetStatistics logicalBlocks 98278656 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 INFO: vdo.GetStatistics oneKBlocks 9433088 INFO: vdo.GetStatistics biosInPartialFua 0 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 INFO: vdo.GetStatistics indexUpdatesFound 0 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 INFO: vdo.GetStatistics biosInFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics instance 25 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialRead 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics slabJournalFlushCount 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosMetaEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics errorsInvalidAdvicePBNCount 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedDiscard 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics errorsNoSpaceErrorCount 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics indexUpdatesNotFound 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics savingPercent 100 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics savings 100 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics indexPostsFound 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics indexPostsNotFound 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapReadOutgoing 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics journalEntriesWritten 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics slabSummaryBlocksWritten 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedDiscard 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosOutEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics logicalBlocks 98278656 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics oneKBlocks 9433088 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInPartialFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics slabJournalBlocksWritten 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics indexUpdatesFound 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialFua 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInFua 0 INFO: vdo.GetStatistics blockMapReclaimed 0 INFO: vdo.GetStatistics blockMapFailedWrites 0 INFO: vdo.GetStatistics biosMetaCompletedFua 5 INFO: vdo.GetStatistics blockMapIncomingPages 0 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 INFO: vdo.GetStatistics blockMapWaitForPage 0 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 INFO: vdo.GetStatistics biosPageCacheWrite 0 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 INFO: vdo.GetStatistics journalEntriesCommitted 0 INFO: vdo.GetStatistics blockMapReadCount 0 INFO: vdo.GetStatistics blockMapFoundInCache 0 INFO: vdo.GetStatistics biosInProgressRead 0 INFO: vdo.GetStatistics biosPageCacheFlush 0 INFO: vdo.GetStatistics blocksCommitted 0 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 INFO: vdo.GetStatistics biosInProgressWrite 0 INFO: vdo.GetStatistics logicalBlockSize 4096 INFO: vdo.GetStatistics mode normal INFO: vdo.GetStatistics biosJournalCompletedRead 0 INFO: vdo.GetStatistics logicalBlocksUsed 0 INFO: vdo.GetStatistics biosInRead 2096 INFO: vdo.GetStatistics biosInProgressFlush 0 INFO: vdo.GetStatistics blockMapDirtyPages 0 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 INFO: vdo.GetStatistics biosPageCacheRead 0 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapReclaimed 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapFailedWrites 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFua 5 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapIncomingPages 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentDataMatches 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapWaitForPage 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics packerCompressedBlocksWritten 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosPageCacheWrite 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics writeAmplificationRatio 0.00 INFO: vdo.GetStatistics blockMapOutgoingPages 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedDiscard 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics journalEntriesCommitted 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapReadCount 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapFoundInCache 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInProgressRead 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosPageCacheFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blocksCommitted 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedRead 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInProgressWrite 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics logicalBlockSize 4096 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics mode normal Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosJournalCompletedRead 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics logicalBlocksUsed 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInRead 2096 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosInProgressFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapDirtyPages 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedWrite 6 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosPageCacheRead 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedEmptyFlush 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blockMapOutgoingPages 0 INFO: vdo.GetStatistics allocatorSlabsReopened 0 INFO: vdo.GetStatistics blocksWritten 0 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 INFO: vdo.GetStatistics biosInWrite 0 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 INFO: vdo.GetStatistics biosInProgressFua 0 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 INFO: vdo.GetStatistics biosOutCompletedFua 0 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 INFO: vdo.GetStatistics biosMetaWrite 6 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedPages 0 INFO: vdo.GetStatistics biosInFlush 0 INFO: vdo.GetStatistics biosMetaRead 5 INFO: vdo.GetStatistics overheadBlocksUsed 786470 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 INFO: vdo.GetStatistics biosInPartialRead 0 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 INFO: vdo.GetStatistics biosMetaFlush 5 INFO: vdo.GetStatistics biosInPartialWrite 0 INFO: vdo.GetStatistics indexQueriesFound 0 INFO: vdo.GetStatistics blockMapDiscardRequired 0 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 INFO: vdo.GetStatistics biosPageCacheDiscard 0 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 INFO: vdo.GetStatistics usedPercent 34 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsReopened 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics blocksWritten 0 Oct 9 04:50:10 storageqe-109 INFO: vdo.GetStatistics memoryUsageBytesUsed 410573256 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInWrite 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInProgressFua 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics dedupeAdviceTimeouts 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFua 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosPageCacheEmptyFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosMetaWrite 6 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsInPacker 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInPartialEmptyFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapFailedPages 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosMetaRead 5 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics overheadBlocksUsed 786470 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics memoryUsagePeakBytesUsed 1226871704 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInPartialRead 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics slabJournalTailBusyCount 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosMetaFlush 5 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInPartialWrite 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics indexQueriesFound 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapDiscardRequired 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosPageCacheDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedWrite 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics usedPercent 34 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedPartialEmptyFlush 0 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics journalEntriesStarted 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedDiscard 0 INFO: vdo.GetStatistics biosOutCompletedRead 0 INFO: vdo.GetStatistics biosMetaDiscard 0 INFO: vdo.GetStatistics physicalBlocks 2358272 INFO: vdo.GetStatistics biosInPartialFlush 0 INFO: vdo.GetStatistics blockMapPagesSaved 0 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 INFO: vdo.GetStatistics biosOutCompletedWrite 0 INFO: vdo.GetStatistics biosOutFua 0 INFO: vdo.GetStatistics biosInDiscard 0 INFO: vdo.GetStatistics completeRecoveries 0 INFO: vdo.GetStatistics biosJournalDiscard 0 INFO: vdo.GetStatistics biosOutCompletedFlush 0 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 INFO: vdo.GetStatistics inRecoveryMode 0 INFO: vdo.GetStatistics biosOutDiscard 0 INFO: vdo.GetStatistics blockMapFlushCount 0 INFO: vdo.GetStatistics readOnlyRecoveries 0 INFO: vdo.GetStatistics blockMapFetchRequired 0 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 INFO: vdo.GetStatistics blockMapFreePages 32768 INFO: vdo.GetStatistics biosInEmptyFlush 0 INFO: vdo.GetStatistics blockMapFailedReads 0 INFO: vdo.GetStatistics biosJournalWrite 0 INFO: vdo.GetStatistics blockMapCleanPages 0 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 INFO: vdo.GetStatistics dataBlocksUsed 0 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedRead 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosMetaDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics physicalBlocks 2358272 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInPartialFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapPagesSaved 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosPageCacheCompletedFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedWrite 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutFua 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics completeRecoveries 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosJournalDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics packerCompressedFragmentsWritten 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics inRecoveryMode 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapFlushCount 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics readOnlyRecoveries 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapFetchRequired 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics slabJournalDiskFullCount 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutCompletedEmptyFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapFreePages 32768 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosInEmptyFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapFailedReads 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosJournalWrite 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapCleanPages 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosAcknowledgedEmptyFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosMetaCompletedDiscard 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics dataBlocksUsed 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics hashLockConcurrentHashCollisions 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics errorsReadOnlyErrorCount 0 INFO: vdo.GetStatistics journalDiskFull 0 INFO: vdo.GetStatistics biosJournalFlush 0 INFO: vdo.GetStatistics refCountsBlocksWritten 0 INFO: vdo.GetStatistics blockMapCachePressure 0 INFO: vdo.GetStatistics biosOutWrite 0 INFO: vdo.GetStatistics indexQueriesNotFound 0 INFO: vdo.GetStatistics flushOut 7 INFO: vdo.GetStatistics version 36 INFO: vdo.GetStatistics allocatorSlabCount 3 INFO: vdo.GetStatistics allocatorSlabsOpened 0 INFO: vdo.GetStatistics blockMapPagesLoaded 0 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 INFO: vdo.GetStatistics biosMetaFua 5 INFO: vdo.GetStatistics biosOutFlush 0 INFO: vdo.GetStatistics biosOutRead 0 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics journalDiskFull 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosJournalFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics refCountsBlocksWritten 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapCachePressure 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutWrite 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics indexQueriesNotFound 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics flushOut 7 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics version 36 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics allocatorSlabCount 3 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics allocatorSlabsOpened 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics blockMapPagesLoaded 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics hashLockCurrDedupeQueries 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosMetaFua 5 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutFlush 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics biosOutRead 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics journalSlabJournalCommitsRequested 0 Oct 9 04:50:11 storageqe-109 INFO: vdo.GetStatistics indexEntriesIndexed 0 Oct 9 04:50:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 2358272 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize logical to 196557056 Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize logical Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: Resizing logical to 196557056 Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: Logical blocks now 196557056 Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:50:37 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:50:37 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:50:37 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:50:37 storageqe-109 lvm[2548792]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:50:37 storageqe-109 lvm[2548792]: VG test_vdo_resize_vg finished Oct 9 04:51:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:51:06 storageqe-109 lvm[2548803]: PV /dev/loop1 not used. Oct 9 04:51:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:51:31 storageqe-109 lvm[2548815]: PV /dev/loop1 online, VG test_vdo_resize_vg is complete. Oct 9 04:51:31 storageqe-109 lvm[2548815]: VG test_vdo_resize_vg finished Oct 9 04:51:31 storageqe-109 lvm[2548816]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:51:31 storageqe-109 lvm[2548816]: VG test_vdo_resize_vg finished Oct 9 04:51:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: table line: V4 /dev/dm-3 3668992 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: preparing to modify device '253:4' Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: Preparing to resize physical to 3668992 Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: Done preparing to resize physical Oct 9 04:51:56 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: resuming device '253:4' Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: Physical block count was 2358272, now 3668992 Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo: dm_vdo25:packer: compression is enabled Oct 9 04:51:56 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' resumed Oct 9 04:51:56 storageqe-109 dmeventd[2527600]: Monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:51:56 storageqe-109 lvm[2548846]: PV /dev/loop0 online, VG test_vdo_resize_vg is complete. Oct 9 04:51:56 storageqe-109 lvm[2548845]: PV /dev/loop1 online, VG test_vdo_resize_vg is complete. Oct 9 04:51:56 storageqe-109 lvm[2548846]: VG test_vdo_resize_vg finished Oct 9 04:51:56 storageqe-109 lvm[2548845]: VG test_vdo_resize_vg finished Oct 9 04:52:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:52:23 storageqe-109 dmeventd[2527600]: No longer monitoring VDO pool test_vdo_resize_vg-udisks_test_vdopool-vpool. Oct 9 04:52:23 storageqe-109 kernel: device-mapper: vdo25:lvm: suspending device '253:4' Oct 9 04:52:23 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' suspended Oct 9 04:52:23 storageqe-109 kernel: device-mapper: vdo25:lvm: stopping device '253:4' Oct 9 04:52:23 storageqe-109 kernel: device-mapper: vdo25:lvm: device '253:4' stopped Oct 9 04:52:23 storageqe-109 lvm[2548864]: PV /dev/loop1 not used. Oct 9 04:52:23 storageqe-109 lvm[2548863]: PV /dev/loop0 not used. Oct 9 04:52:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:52:48 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_vdo_resize1.img) Oct 9 04:52:48 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:53:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:53:13 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_vdo_resize2.img) Oct 9 04:53:13 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_vdo_resize #### INFO: #### will start test_mdraid_chunk_size_property ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:53:20 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:53:20 storageqe-109 INFO: #### END test_vdo_resize #### Oct 9 04:53:20 storageqe-109 INFO: #### will start test_mdraid_chunk_size_property ##### Oct 9 04:53:20 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:53:26 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:53:26 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_chunk1.img) Oct 9 04:53:27 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:53:27 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_chunk2.img) Oct 9 04:53:27 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_chunk INFO: raid chunk 262144 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:53:27 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/loop_md_chunk3.img) Oct 9 04:53:27 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 9 04:53:27 storageqe-109 INFO: raid level raid5 Oct 9 04:53:27 storageqe-109 INFO: raid name test_md_chunk Oct 9 04:53:27 storageqe-109 INFO: raid chunk 262144 Oct 9 04:53:27 storageqe-109 INFO: raid bitmap None Oct 9 04:53:27 storageqe-109 INFO: raid version 1.2 Oct 9 04:53:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:53:52 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 9 04:53:52 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 9 04:53:52 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 9 04:53:52 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 9 04:53:52 storageqe-109 kernel: md: recover of RAID array md127 Oct 9 04:53:52 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:53:52 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:53:53 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:53:58 storageqe-109 kernel: md: md127: recover done. Oct 9 04:54:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:54:23 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 9 04:54:23 storageqe-109 kernel: md: md127 stopped. Oct 9 04:54:23 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:54:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:54:51 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_chunk1.img) Oct 9 04:54:51 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:55:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:55:16 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_chunk2.img) Oct 9 04:55:16 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 04:55:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:55:41 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/loop_md_chunk3.img) Oct 9 04:55:41 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_chunk_size_property #### INFO: #### will start test_mdraid_add_and_remove_spare ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:55:47 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:55:47 storageqe-109 INFO: #### END test_mdraid_chunk_size_property #### Oct 9 04:55:47 storageqe-109 INFO: #### will start test_mdraid_add_and_remove_spare ##### Oct 9 04:55:47 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:55:54 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:55:54 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_add_spare1.img) Oct 9 04:55:54 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_add_spare INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:55:54 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_add_spare2.img) Oct 9 04:55:54 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 04:55:54 storageqe-109 INFO: raid level raid1 Oct 9 04:55:54 storageqe-109 INFO: raid name test_md_add_spare Oct 9 04:55:54 storageqe-109 INFO: raid chunk 0 Oct 9 04:55:54 storageqe-109 INFO: raid bitmap None Oct 9 04:55:54 storageqe-109 INFO: raid version 1.2 Oct 9 04:56:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:56:19 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 04:56:19 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 04:56:19 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 04:56:19 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 04:56:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:56:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:56:19 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:56:25 storageqe-109 kernel: md: md127: resync done. Oct 9 04:56:27 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 04:56:27 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/loop_md_spare.img) Oct 9 04:56:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:57:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:57:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:57:49 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 04:57:49 storageqe-109 kernel: md: md127 stopped. Oct 9 04:57:49 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:57:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:57:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 04:57:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_add_and_remove_spare #### INFO: #### will start test_mdraid_degraded_state ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:57:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:57:58 storageqe-109 INFO: #### END test_mdraid_add_and_remove_spare #### Oct 9 04:57:58 storageqe-109 INFO: #### will start test_mdraid_degraded_state ##### Oct 9 04:57:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:58:05 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:58:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_degraded1.img) Oct 9 04:58:05 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:58:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_degraded2.img) Oct 9 04:58:05 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] INFO: raid level raid5 INFO: raid name test_md_degraded INFO: raid chunk 524288 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:58:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/loop_md_degraded3.img) Oct 9 04:58:05 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop2')] Oct 9 04:58:05 storageqe-109 INFO: raid level raid5 Oct 9 04:58:05 storageqe-109 INFO: raid name test_md_degraded Oct 9 04:58:05 storageqe-109 INFO: raid chunk 524288 Oct 9 04:58:06 storageqe-109 INFO: raid bitmap None Oct 9 04:58:06 storageqe-109 INFO: raid version 1.2 Oct 9 04:58:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:58:31 storageqe-109 kernel: md/raid:md127: device loop1 operational as raid disk 1 Oct 9 04:58:31 storageqe-109 kernel: md/raid:md127: device loop0 operational as raid disk 0 Oct 9 04:58:31 storageqe-109 kernel: md/raid:md127: raid level 5 active with 2 out of 3 devices, algorithm 2 Oct 9 04:58:31 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 9 04:58:31 storageqe-109 kernel: md: recover of RAID array md127 Oct 9 04:58:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:58:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:58:31 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 04:58:36 storageqe-109 kernel: md: md127: recover done. Oct 9 04:59:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:59:04 storageqe-109 kernel: md/raid:md127: Disk failure on loop1, disabling device. Oct 9 04:59:04 storageqe-109 kernel: md/raid:md127: Operation continuing on 2 devices. Oct 9 04:59:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 04:59:34 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 9 04:59:34 storageqe-109 kernel: md: md127 stopped. Oct 9 04:59:34 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 04:59:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 04:59:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 04:59:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_degraded_state #### INFO: #### will start test_mdraid_delete_method ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:59:43 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:59:43 storageqe-109 INFO: #### END test_mdraid_degraded_state #### Oct 9 04:59:43 storageqe-109 INFO: #### will start test_mdraid_delete_method ##### Oct 9 04:59:43 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 04:59:50 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 04:59:50 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_delete1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_delete INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 04:59:50 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 04:59:50 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_delete2.img) Oct 9 04:59:50 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 04:59:50 storageqe-109 INFO: raid level raid1 Oct 9 04:59:50 storageqe-109 INFO: raid name test_md_delete Oct 9 04:59:50 storageqe-109 INFO: raid chunk 0 Oct 9 04:59:50 storageqe-109 INFO: raid bitmap None Oct 9 04:59:50 storageqe-109 INFO: raid version 1.2 Oct 9 05:00:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:00:16 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 05:00:16 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 05:00:16 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 05:00:16 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 05:00:16 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:00:16 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:00:16 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:00:21 storageqe-109 kernel: md: md127: resync done. Oct 9 05:00:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:00:49 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 05:00:49 storageqe-109 kernel: md: md127 stopped. Oct 9 05:00:49 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 05:00:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 05:00:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_delete_method #### INFO: #### will start test_mdraid_activedevices_property_structure ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:00:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:00:58 storageqe-109 INFO: #### END test_mdraid_delete_method #### Oct 9 05:00:58 storageqe-109 INFO: #### will start test_mdraid_activedevices_property_structure ##### Oct 9 05:00:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:01:05 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 05:01:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_active1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_active INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 05:01:05 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 05:01:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_active2.img) Oct 9 05:01:05 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 05:01:05 storageqe-109 INFO: raid level raid1 Oct 9 05:01:05 storageqe-109 INFO: raid name test_md_active Oct 9 05:01:05 storageqe-109 INFO: raid chunk 0 Oct 9 05:01:05 storageqe-109 INFO: raid bitmap None Oct 9 05:01:05 storageqe-109 INFO: raid version 1.2 Oct 9 05:01:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:01:30 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 05:01:30 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 05:01:30 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 05:01:30 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 05:01:30 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:01:30 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:01:30 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:01:36 storageqe-109 kernel: md: md127: resync done. Oct 9 05:02:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:02:05 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 05:02:05 storageqe-109 kernel: md: md127 stopped. Oct 9 05:02:06 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 05:02:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:02:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_active1.img) Oct 9 05:02:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 05:02:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:02:58 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_active2.img) Oct 9 05:02:58 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_activedevices_property_structure #### INFO: #### will start test_mdraid_size_property_verification ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:03:05 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:03:05 storageqe-109 INFO: #### END test_mdraid_activedevices_property_structure #### Oct 9 05:03:05 storageqe-109 INFO: #### will start test_mdraid_size_property_verification ##### Oct 9 05:03:05 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:03:11 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 05:03:11 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_size1.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_md_size1 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 05:03:12 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 05:03:12 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_size2.img) Oct 9 05:03:12 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 05:03:12 storageqe-109 INFO: raid level raid1 Oct 9 05:03:12 storageqe-109 INFO: raid name test_md_size1 Oct 9 05:03:12 storageqe-109 INFO: raid chunk 0 Oct 9 05:03:12 storageqe-109 INFO: raid bitmap None Oct 9 05:03:12 storageqe-109 INFO: raid version 1.2 Oct 9 05:03:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:03:37 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 05:03:37 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 05:03:37 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 05:03:37 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 05:03:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:03:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:03:37 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 05:03:42 storageqe-109 kernel: md: md127: resync done. Oct 9 05:04:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:04:11 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 05:04:11 storageqe-109 kernel: md: md127 stopped. Oct 9 05:04:11 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_md_size0 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version 1.2 Oct 9 05:04:16 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 05:04:16 storageqe-109 INFO: raid level raid0 Oct 9 05:04:16 storageqe-109 INFO: raid name test_md_size0 Oct 9 05:04:16 storageqe-109 INFO: raid chunk 0 Oct 9 05:04:16 storageqe-109 INFO: raid bitmap None Oct 9 05:04:16 storageqe-109 INFO: raid version 1.2 Oct 9 05:04:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:04:41 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 9 05:05:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:05:11 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 9 05:05:11 storageqe-109 kernel: md: md127 stopped. Oct 9 05:05:11 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 05:05:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:05:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_size1.img) Oct 9 05:05:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 05:06:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:06:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_size2.img) Oct 9 05:06:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_mdraid_size_property_verification #### INFO: #### will start test_nvme_smart_properties_validation ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:11 storageqe-109 INFO: #### END test_mdraid_size_property_verification #### Oct 9 05:06:11 storageqe-109 INFO: #### will start test_nvme_smart_properties_validation ##### Oct 9 05:06:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_smart_properties_validation #### INFO: #### will start test_nvme_drive_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:26 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:26 storageqe-109 INFO: #### END test_nvme_smart_properties_validation #### Oct 9 05:06:26 storageqe-109 INFO: #### will start test_nvme_drive_properties ##### Oct 9 05:06:26 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_drive_properties #### INFO: #### will start test_nvme_controller_static_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:42 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:42 storageqe-109 INFO: #### END test_nvme_drive_properties #### Oct 9 05:06:42 storageqe-109 INFO: #### will start test_nvme_controller_static_properties ##### Oct 9 05:06:42 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_controller_static_properties #### INFO: #### will start test_nvme_namespace_size_property ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:58 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:06:58 storageqe-109 INFO: #### END test_nvme_controller_static_properties #### Oct 9 05:06:58 storageqe-109 INFO: #### will start test_nvme_namespace_size_property ##### Oct 9 05:06:58 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_size_property #### INFO: #### will start test_nvme_namespace_properties_detailed ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:07:11 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:07:11 storageqe-109 INFO: #### END test_nvme_namespace_size_property #### Oct 9 05:07:11 storageqe-109 INFO: #### will start test_nvme_namespace_properties_detailed ##### Oct 9 05:07:11 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_properties_detailed #### INFO: #### will start test_nvme_namespace_format ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:07:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:07:33 storageqe-109 INFO: #### END test_nvme_namespace_properties_detailed #### Oct 9 05:07:33 storageqe-109 INFO: #### will start test_nvme_namespace_format ##### Oct 9 05:07:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:08:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:08:06 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 05:10:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:10:33 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format #### INFO: #### will start test_nvme_namespace_format_invalid_lba ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:12:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:12:41 storageqe-109 INFO: #### END test_nvme_namespace_format #### Oct 9 05:12:41 storageqe-109 INFO: #### will start test_nvme_namespace_format_invalid_lba ##### Oct 9 05:12:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:13:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:13:12 storageqe-109 udisksd[2509680]: Error formatting namespace /org/freedesktop/UDisks2/block_devices/nvme0n1: Couldn't match desired LBA data block size in a device supported LBA format data sizes (g-bd-nvme-error-quark, 3) INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_invalid_lba #### INFO: #### will start test_nvme_namespace_format_invalid_secure_erase ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:13:18 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:13:18 storageqe-109 INFO: #### END test_nvme_namespace_format_invalid_lba #### Oct 9 05:13:18 storageqe-109 INFO: #### will start test_nvme_namespace_format_invalid_secure_erase ##### Oct 9 05:13:18 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_invalid_secure_erase #### INFO: #### will start test_nvme_block_size_consistency_after_format ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:13:32 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:13:32 storageqe-109 INFO: #### END test_nvme_namespace_format_invalid_secure_erase #### Oct 9 05:13:32 storageqe-109 INFO: #### will start test_nvme_block_size_consistency_after_format ##### Oct 9 05:13:32 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:14:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:14:07 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 05:16:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:16:35 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_block_size_consistency_after_format #### INFO: #### will start test_nvme_namespace_wwn_property ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:18:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:18:41 storageqe-109 INFO: #### END test_nvme_block_size_consistency_after_format #### Oct 9 05:18:41 storageqe-109 INFO: #### will start test_nvme_namespace_wwn_property ##### Oct 9 05:18:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_wwn_property #### INFO: #### will start test_nvme_namespace_utilization ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:18:55 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:18:55 storageqe-109 INFO: #### END test_nvme_namespace_wwn_property #### Oct 9 05:18:55 storageqe-109 INFO: #### will start test_nvme_namespace_utilization ##### Oct 9 05:18:55 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:19:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:20:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:20:03 storageqe-109 kernel: XFS (nvme0n1): Mounting V5 Filesystem add71eb3-e8dc-43d8-b096-43682249d598 Oct 9 05:20:03 storageqe-109 kernel: XFS (nvme0n1): Ending clean mount Oct 9 05:20:03 storageqe-109 udisksd[2509680]: Mounted /dev/nvme0n1 at /run/media/root/add71eb3-e8dc-43d8-b096-43682249d598 on behalf of uid 0 Oct 9 05:20:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:20:28 storageqe-109 systemd[1]: run-media-root-add71eb3\x2de8dc\x2d43d8\x2db096\x2d43682249d598.mount: Deactivated successfully. Oct 9 05:20:28 storageqe-109 kernel: XFS (nvme0n1): Unmounting Filesystem add71eb3-e8dc-43d8-b096-43682249d598 Oct 9 05:20:28 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/add71eb3-e8dc-43d8-b096-43682249d598 (device 259:1 is not mounted) Oct 9 05:20:28 storageqe-109 udisksd[2509680]: Unmounted /dev/nvme0n1 on behalf of uid 0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_utilization #### INFO: #### will start test_luks_on_4k_nvme_namespace ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:20:35 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:20:35 storageqe-109 INFO: #### END test_nvme_namespace_utilization #### Oct 9 05:20:35 storageqe-109 INFO: #### will start test_luks_on_4k_nvme_namespace ##### Oct 9 05:20:35 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:21:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:21:09 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 05:23:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:23:42 storageqe-109 stratisd[2509653]: [2025-10-09T09:23:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 05:23:42 storageqe-109 stratisd[2509653]: [2025-10-09T09:23:42Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 05:24:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:24:09 storageqe-109 stratisd[2509653]: [2025-10-09T09:24:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 05:24:09 storageqe-109 stratisd[2509653]: [2025-10-09T09:24:09Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 05:24:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:25:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:25:04 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 05:25:04 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 05:25:04 storageqe-109 udisksd[2509680]: Locked device /dev/nvme0n1 (was unlocked as /dev/dm-3) Oct 9 05:25:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:25:29 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_luks_on_4k_nvme_namespace #### INFO: #### will start test_nvme_namespace_format_on_mounted_device ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:27:36 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:27:36 storageqe-109 INFO: #### END test_luks_on_4k_nvme_namespace #### Oct 9 05:27:36 storageqe-109 INFO: #### will start test_nvme_namespace_format_on_mounted_device ##### Oct 9 05:27:36 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:28:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:28:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:28:38 storageqe-109 kernel: XFS (nvme0n1): Mounting V5 Filesystem a5c31108-ab23-4b83-8274-e3b039949594 Oct 9 05:28:38 storageqe-109 kernel: XFS (nvme0n1): Ending clean mount Oct 9 05:28:38 storageqe-109 udisksd[2509680]: Mounted /dev/nvme0n1 at /run/media/root/a5c31108-ab23-4b83-8274-e3b039949594 on behalf of uid 0 Oct 9 05:29:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:29:03 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 05:29:05 storageqe-109 udisksd[2509680]: Error re-reading partition table (BLKRRPART ioctl) on /dev/nvme0n1: Device or resource busy Oct 9 05:29:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:29:31 storageqe-109 systemd[1]: run-media-root-a5c31108\x2dab23\x2d4b83\x2d8274\x2de3b039949594.mount: Deactivated successfully. Oct 9 05:29:31 storageqe-109 kernel: XFS (nvme0n1): Unmounting Filesystem a5c31108-ab23-4b83-8274-e3b039949594 Oct 9 05:29:31 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/a5c31108-ab23-4b83-8274-e3b039949594 (device 259:1 is not mounted) Oct 9 05:29:31 storageqe-109 udisksd[2509680]: Unmounted /dev/nvme0n1 on behalf of uid 0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_on_mounted_device #### INFO: #### will start test_nvme_namespace_format_with_metadata ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:29:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:29:37 storageqe-109 INFO: #### END test_nvme_namespace_format_on_mounted_device #### Oct 9 05:29:37 storageqe-109 INFO: #### will start test_nvme_namespace_format_with_metadata ##### Oct 9 05:29:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:30:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:30:10 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 05:32:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:32:37 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_with_metadata #### INFO: #### will start test_nvme_namespace_format_with_extra_options ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:34:44 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:34:44 storageqe-109 INFO: #### END test_nvme_namespace_format_with_metadata #### Oct 9 05:34:44 storageqe-109 INFO: #### will start test_nvme_namespace_format_with_extra_options ##### Oct 9 05:34:44 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:35:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:35:16 storageqe-109 kernel: nvme nvme0: rescanning namespaces. Oct 9 05:37:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:37:43 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_nvme_namespace_format_with_extra_options #### INFO: #### will start test_lvm_on_nvme_namespace ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:39:49 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:39:49 storageqe-109 INFO: #### END test_nvme_namespace_format_with_extra_options #### Oct 9 05:39:50 storageqe-109 INFO: #### will start test_lvm_on_nvme_namespace ##### Oct 9 05:39:50 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:40:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:40:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:41:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:41:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lvm_on_nvme_namespace #### INFO: #### will start test_concurrent_error_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:41:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:41:57 storageqe-109 INFO: #### END test_lvm_on_nvme_namespace #### Oct 9 05:41:57 storageqe-109 INFO: #### will start test_concurrent_error_handling ##### Oct 9 05:41:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:42:02 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 05:42:02 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 05:42:02 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_concurrent_error_handling #### INFO: #### will start test_resource_exhaustion_recovery ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:42:07 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:42:07 storageqe-109 INFO: #### END test_concurrent_error_handling #### Oct 9 05:42:07 storageqe-109 INFO: #### will start test_resource_exhaustion_recovery ##### Oct 9 05:42:07 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:42:12 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 05:42:12 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/resource_0.img) Oct 9 05:42:13 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 05:42:13 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/resource_1.img) Oct 9 05:42:13 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 05:42:13 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/resource_2.img) Oct 9 05:42:13 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 05:42:13 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/resource_3.img) Oct 9 05:42:14 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 9 05:42:14 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop4 (backed by /home/resource_4.img) Oct 9 05:42:14 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 9 05:42:14 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop5 (backed by /home/resource_5.img) Oct 9 05:42:15 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 9 05:42:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop6 (backed by /home/resource_6.img) Oct 9 05:42:15 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 9 05:42:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop7 (backed by /home/resource_7.img) Oct 9 05:42:16 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 9 05:42:16 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop8 (backed by /home/resource_8.img) Oct 9 05:42:17 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 9 05:42:17 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop9 (backed by /home/resource_9.img) Oct 9 05:42:18 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 9 05:42:18 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop10 (backed by /home/resource_10.img) Oct 9 05:42:19 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 9 05:42:19 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop11 (backed by /home/resource_11.img) Oct 9 05:42:20 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 9 05:42:20 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop12 (backed by /home/resource_12.img) Oct 9 05:42:21 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 9 05:42:21 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop13 (backed by /home/resource_13.img) Oct 9 05:42:22 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 9 05:42:22 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop14 (backed by /home/resource_14.img) Oct 9 05:42:23 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 9 05:42:23 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop15 (backed by /home/resource_15.img) Oct 9 05:42:23 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 9 05:42:23 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop16 (backed by /home/resource_16.img) Oct 9 05:42:24 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 9 05:42:24 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop17 (backed by /home/resource_17.img) Oct 9 05:42:25 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 9 05:42:25 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop18 (backed by /home/resource_18.img) Oct 9 05:42:26 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 9 05:42:26 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop19 (backed by /home/resource_19.img) Oct 9 05:42:27 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 9 05:42:27 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop20 (backed by /home/resource_20.img) Oct 9 05:42:28 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 9 05:42:28 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop21 (backed by /home/resource_21.img) Oct 9 05:42:29 storageqe-109 kernel: loop22: detected capacity change from 0 to 2097152 Oct 9 05:42:29 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop22 (backed by /home/resource_22.img) Oct 9 05:42:30 storageqe-109 kernel: loop23: detected capacity change from 0 to 2097152 Oct 9 05:42:30 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop23 (backed by /home/resource_23.img) Oct 9 05:42:31 storageqe-109 kernel: loop24: detected capacity change from 0 to 2097152 Oct 9 05:42:31 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop24 (backed by /home/resource_24.img) Oct 9 05:42:32 storageqe-109 kernel: loop25: detected capacity change from 0 to 2097152 Oct 9 05:42:32 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop25 (backed by /home/resource_25.img) Oct 9 05:42:33 storageqe-109 kernel: loop26: detected capacity change from 0 to 2097152 Oct 9 05:42:33 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop26 (backed by /home/resource_26.img) Oct 9 05:42:34 storageqe-109 kernel: loop27: detected capacity change from 0 to 2097152 Oct 9 05:42:34 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop27 (backed by /home/resource_27.img) Oct 9 05:42:35 storageqe-109 kernel: loop28: detected capacity change from 0 to 2097152 Oct 9 05:42:35 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop28 (backed by /home/resource_28.img) Oct 9 05:42:36 storageqe-109 kernel: loop29: detected capacity change from 0 to 2097152 Oct 9 05:42:36 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop29 (backed by /home/resource_29.img) Oct 9 05:43:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:43:01 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/resource_0.img) Oct 9 05:43:01 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 05:43:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:43:26 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/resource_1.img) Oct 9 05:43:26 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 05:43:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:43:51 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/resource_2.img) Oct 9 05:43:51 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 05:44:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:44:16 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/resource_3.img) Oct 9 05:44:16 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 05:44:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:44:41 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop4 (was backed by /home/resource_4.img) Oct 9 05:44:41 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop4 Oct 9 05:44:41 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 05:44:41 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/recovery.img) Oct 9 05:45:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:45:06 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop5 (was backed by /home/resource_5.img) Oct 9 05:45:06 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop5 Oct 9 05:45:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:45:31 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop6 (was backed by /home/resource_6.img) Oct 9 05:45:31 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop6 Oct 9 05:45:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:45:56 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop7 (was backed by /home/resource_7.img) Oct 9 05:45:56 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop7 Oct 9 05:46:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:46:21 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop8 (was backed by /home/resource_8.img) Oct 9 05:46:21 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop8 Oct 9 05:46:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:46:46 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop9 (was backed by /home/resource_9.img) Oct 9 05:46:46 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop9 Oct 9 05:47:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:47:11 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop10 (was backed by /home/resource_10.img) Oct 9 05:47:11 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop10 Oct 9 05:47:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:47:36 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop11 (was backed by /home/resource_11.img) Oct 9 05:47:36 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop11 Oct 9 05:48:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:48:01 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop12 (was backed by /home/resource_12.img) Oct 9 05:48:01 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop12 Oct 9 05:48:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:48:26 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop13 (was backed by /home/resource_13.img) Oct 9 05:48:26 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop13 Oct 9 05:48:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:48:52 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop14 (was backed by /home/resource_14.img) Oct 9 05:48:52 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop14 Oct 9 05:49:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:49:17 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop15 (was backed by /home/resource_15.img) Oct 9 05:49:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop15 Oct 9 05:49:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:49:42 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop16 (was backed by /home/resource_16.img) Oct 9 05:49:42 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop16 Oct 9 05:50:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:50:07 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop17 (was backed by /home/resource_17.img) Oct 9 05:50:07 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop17 Oct 9 05:50:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:50:32 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop18 (was backed by /home/resource_18.img) Oct 9 05:50:32 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop18 Oct 9 05:50:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 05:50:53 storageqe-109 dnf[2557170]: Updating Subscription Management repositories. Oct 9 05:50:53 storageqe-109 dnf[2557170]: Unable to read consumer identity Oct 9 05:50:53 storageqe-109 dnf[2557170]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 05:50:53 storageqe-109 dnf[2557170]: Metadata cache refreshed recently. Oct 9 05:50:54 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 05:50:54 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 05:50:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:50:57 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop19 (was backed by /home/resource_19.img) Oct 9 05:50:57 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop19 Oct 9 05:51:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:51:22 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop20 (was backed by /home/resource_20.img) Oct 9 05:51:22 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop20 Oct 9 05:51:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:51:47 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop21 (was backed by /home/resource_21.img) Oct 9 05:51:47 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop21 Oct 9 05:52:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:52:12 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop22 (was backed by /home/resource_22.img) Oct 9 05:52:12 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop22 Oct 9 05:52:24 storageqe-109 dmeventd[2527600]: dmeventd was idle for 3600 second(s), exiting. Oct 9 05:52:24 storageqe-109 dmeventd[2527600]: dmeventd shutting down. Oct 9 05:52:24 storageqe-109 systemd[1]: dm-event.service: Deactivated successfully. Oct 9 05:52:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:52:37 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop23 (was backed by /home/resource_23.img) Oct 9 05:52:37 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop23 Oct 9 05:53:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:53:02 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop24 (was backed by /home/resource_24.img) Oct 9 05:53:02 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop24 Oct 9 05:53:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:53:27 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop25 (was backed by /home/resource_25.img) Oct 9 05:53:27 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop25 Oct 9 05:53:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:53:52 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop26 (was backed by /home/resource_26.img) Oct 9 05:53:52 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop26 Oct 9 05:54:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:54:17 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop27 (was backed by /home/resource_27.img) Oct 9 05:54:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop27 Oct 9 05:54:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:54:42 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop28 (was backed by /home/resource_28.img) Oct 9 05:54:42 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop28 Oct 9 05:55:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:55:07 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop29 (was backed by /home/resource_29.img) Oct 9 05:55:07 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop29 Oct 9 05:55:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:55:32 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/recovery.img) Oct 9 05:55:32 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_resource_exhaustion_recovery #### INFO: #### will start test_interrupted_operation_recovery ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:55:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:55:37 storageqe-109 INFO: #### END test_resource_exhaustion_recovery #### Oct 9 05:55:37 storageqe-109 INFO: #### will start test_interrupted_operation_recovery ##### Oct 9 05:55:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:55:42 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 05:55:42 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/interrupt_test.img) Oct 9 05:55:42 storageqe-109 kernel: loop0: Oct 9 05:56:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:56:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:56:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:56:58 storageqe-109 kernel: loop0: Oct 9 05:57:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:57:23 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/interrupt_test.img) Oct 9 05:57:23 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_interrupted_operation_recovery #### INFO: #### will start test_cascading_error_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:57:28 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:57:28 storageqe-109 INFO: #### END test_interrupted_operation_recovery #### Oct 9 05:57:28 storageqe-109 INFO: #### will start test_cascading_error_handling ##### Oct 9 05:57:28 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 05:57:34 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 05:57:34 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/cascade_test.img) Oct 9 05:57:34 storageqe-109 kernel: loop0: Oct 9 05:57:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:58:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:58:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:58:55 storageqe-109 kernel: loop0: Oct 9 05:58:55 storageqe-109 kernel: loop0: Oct 9 05:59:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:59:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 05:59:50 storageqe-109 kernel: loop0: Oct 9 06:00:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:00:15 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/cascade_test.img) Oct 9 06:00:15 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_cascading_error_handling #### INFO: #### will start test_malformed_parameter_handling ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:00:20 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:00:20 storageqe-109 INFO: #### END test_cascading_error_handling #### Oct 9 06:00:20 storageqe-109 INFO: #### will start test_malformed_parameter_handling ##### Oct 9 06:00:21 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_malformed_parameter_handling #### INFO: #### will start test_dbus_error_propagation ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:00:31 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:00:31 storageqe-109 INFO: #### END test_malformed_parameter_handling #### Oct 9 06:00:31 storageqe-109 INFO: #### will start test_dbus_error_propagation ##### Oct 9 06:00:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_dbus_error_propagation #### INFO: #### will start test_state_consistency_after_errors ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:00:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:00:41 storageqe-109 INFO: #### END test_dbus_error_propagation #### Oct 9 06:00:41 storageqe-109 INFO: #### will start test_state_consistency_after_errors ##### Oct 9 06:00:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:00:46 storageqe-109 kernel: blk_print_req_error: 251 callbacks suppressed Oct 9 06:00:46 storageqe-109 kernel: I/O error, dev loop0, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 06:00:46 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop0': Invalid argument Oct 9 06:00:46 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:00:46 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/consistency_test.img) Oct 9 06:01:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:01:11 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/consistency_test.img) Oct 9 06:01:11 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_state_consistency_after_errors #### INFO: #### will start test_error_handling_under_load ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:01:16 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:01:16 storageqe-109 INFO: #### END test_state_consistency_after_errors #### Oct 9 06:01:16 storageqe-109 INFO: #### will start test_error_handling_under_load ##### Oct 9 06:01:16 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_error_handling_under_load #### INFO: #### will start test_basic_and_id_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:01:27 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 06:01:27 storageqe-109 INFO: #### END test_error_handling_under_load #### Oct 9 06:01:27 storageqe-109 INFO: #### will start test_basic_and_id_properties ##### Oct 9 06:01:27 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Testing on real device(s): ['/dev/sdb'] Oct 9 06:01:32 storageqe-109 INFO: Testing on real device(s): ['/dev/sdb'] Oct 9 06:02:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Wiping device /dev/sdb after test. Oct 9 06:02:09 storageqe-109 INFO: Wiping device /dev/sdb after test. INFO: Released device(s) ['/dev/sdb'] back to the pool. Oct 9 06:02:11 storageqe-109 INFO: Released device(s) ['/dev/sdb'] back to the pool. INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_basic_and_id_properties #### INFO: #### will start test_hint_and_misc_properties ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 9 06:02:16 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 9 06:02:16 storageqe-109 INFO: #### END test_basic_and_id_properties #### Oct 9 06:02:16 storageqe-109 INFO: #### will start test_hint_and_misc_properties ##### Oct 9 06:02:16 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: Testing on real device(s): ['/dev/sdc'] Oct 9 06:02:21 storageqe-109 INFO: Testing on real device(s): ['/dev/sdc'] INFO: Wiping device /dev/sdc after test. Oct 9 06:02:26 storageqe-109 INFO: Wiping device /dev/sdc after test. INFO: Released device(s) ['/dev/sdc'] back to the pool. Oct 9 06:02:28 storageqe-109 INFO: Released device(s) ['/dev/sdc'] back to the pool. INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: #### END test_hint_and_misc_properties #### INFO: #### will start test_crypto_backing_device_property ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 9 06:02:33 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### Oct 9 06:02:33 storageqe-109 INFO: #### END test_hint_and_misc_properties #### Oct 9 06:02:33 storageqe-109 INFO: #### will start test_crypto_backing_device_property ##### Oct 9 06:02:33 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc'] #### INFO: Testing on real device(s): ['/dev/sdd'] Oct 9 06:02:38 storageqe-109 INFO: Testing on real device(s): ['/dev/sdd'] Oct 9 06:03:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:03:11 storageqe-109 stratisd[2509653]: [2025-10-09T10:03:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 06:03:11 storageqe-109 stratisd[2509653]: [2025-10-09T10:03:11Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 06:03:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:03:38 storageqe-109 stratisd[2509653]: [2025-10-09T10:03:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 06:03:38 storageqe-109 stratisd[2509653]: [2025-10-09T10:03:38Z DEBUG stratisd::engine::strat_engine::crypt::handle::v1] Operations querying device to determine if it is a Stratis device failed with an error: Device appears to be missing some of the required Stratis LUKS2 tokens; reporting as not a Stratis device. Oct 9 06:04:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:04:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:04:32 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 06:04:32 storageqe-109 udisksd[2509680]: Removing unlocked-crypto-dev entry {uint64 64771, {'crypto-device': , 'dm-uuid': , 'unlocked-by-uid': }} because /dev/dm-3 now has another dm-uuid (NULL) Oct 9 06:04:32 storageqe-109 udisksd[2509680]: Locked device /dev/sdd (was unlocked as /dev/dm-3) INFO: Wiping device /dev/sdd after test. Oct 9 06:04:32 storageqe-109 INFO: Wiping device /dev/sdd after test. INFO: Released device(s) ['/dev/sdd'] back to the pool. Oct 9 06:04:34 storageqe-109 INFO: Released device(s) ['/dev/sdd'] back to the pool. INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_crypto_backing_device_property #### INFO: #### will start test_mdraid_related_properties ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:04:39 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:04:39 storageqe-109 INFO: #### END test_crypto_backing_device_property #### Oct 9 06:04:39 storageqe-109 INFO: #### will start test_mdraid_related_properties ##### Oct 9 06:04:39 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:04:45 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:04:45 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_md_member_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_raid_props INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version None Oct 9 06:04:45 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 06:04:45 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_md_member_1.img) Oct 9 06:04:45 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 06:04:45 storageqe-109 INFO: raid level raid1 Oct 9 06:04:45 storageqe-109 INFO: raid name test_raid_props Oct 9 06:04:45 storageqe-109 INFO: raid chunk 0 Oct 9 06:04:45 storageqe-109 INFO: raid bitmap None Oct 9 06:04:45 storageqe-109 INFO: raid version None Oct 9 06:05:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:05:10 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 06:05:10 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 06:05:10 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 06:05:10 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 06:05:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 06:05:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 06:05:11 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 06:05:16 storageqe-109 kernel: md: md127: resync done. Oct 9 06:05:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:05:49 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 06:05:49 storageqe-109 kernel: md: md127 stopped. Oct 9 06:05:49 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 06:06:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:06:17 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/loop_md_member_0.img) Oct 9 06:06:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 06:06:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:06:42 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop1 (was backed by /home/loop_md_member_1.img) Oct 9 06:06:42 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_mdraid_related_properties #### INFO: #### will start test_drive_properties_and_methods ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:06:47 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:06:47 storageqe-109 INFO: #### END test_mdraid_related_properties #### Oct 9 06:06:47 storageqe-109 INFO: #### will start test_drive_properties_and_methods ##### Oct 9 06:06:47 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_drive_properties_and_methods #### INFO: #### will start test_drive_ata_properties_and_methods ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:06:57 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:06:57 storageqe-109 INFO: #### END test_drive_properties_and_methods #### Oct 9 06:06:57 storageqe-109 INFO: #### will start test_drive_ata_properties_and_methods ##### Oct 9 06:06:57 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_drive_ata_properties_and_methods #### INFO: #### will start test_invalid_device_path_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:07:07 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:07:07 storageqe-109 INFO: #### END test_drive_ata_properties_and_methods #### Oct 9 06:07:07 storageqe-109 INFO: #### will start test_invalid_device_path_handling ##### Oct 9 06:07:07 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:07:13 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:07:13 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/nonexistent_file.img) Oct 9 06:07:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:07:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/nonexistent_file.img) Oct 9 06:07:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 06:07:38 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:07:38 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/file_that_does_not_exist) INFO: start Cleaning up error handling test: test_invalid_device_path_handling INFO: start Cleaning _cleanup_automounts Oct 9 06:08:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:08:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/file_that_does_not_exist) Oct 9 06:08:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 06:08:03 storageqe-109 journal: Oct 9 06:08:03 storageqe-109 INFO: start Cleaning up error handling test: test_invalid_device_path_handling Oct 9 06:08:03 storageqe-109 journal: Oct 9 06:08:03 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_invalid_device_path_handling #### INFO: #### will start test_permission_denied_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:08:08 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:08:08 storageqe-109 INFO: #### END test_invalid_device_path_handling #### Oct 9 06:08:08 storageqe-109 INFO: #### will start test_permission_denied_handling ##### Oct 9 06:08:08 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:08:14 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:08:14 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /tmp/udisks2_error_test_oh39gioy/error_test_permission_test.img) INFO: start Cleaning up error handling test: test_permission_denied_handling INFO: start Cleaning _cleanup_automounts Oct 9 06:08:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:08:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks2_error_test_oh39gioy/error_test_permission_test.img) Oct 9 06:08:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 06:08:39 storageqe-109 journal: Oct 9 06:08:39 storageqe-109 INFO: start Cleaning up error handling test: test_permission_denied_handling Oct 9 06:08:39 storageqe-109 journal: Oct 9 06:08:39 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_permission_denied_handling #### INFO: #### will start test_insufficient_space_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:08:44 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:08:44 storageqe-109 INFO: #### END test_permission_denied_handling #### Oct 9 06:08:44 storageqe-109 INFO: #### will start test_insufficient_space_handling ##### Oct 9 06:08:44 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: start Cleaning up error handling test: test_insufficient_space_handling INFO: start Cleaning _cleanup_automounts Oct 9 06:09:41 storageqe-109 journal: Oct 9 06:09:41 storageqe-109 INFO: start Cleaning up error handling test: test_insufficient_space_handling Oct 9 06:09:41 storageqe-109 journal: Oct 9 06:09:41 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_insufficient_space_handling #### INFO: #### will start test_corrupted_filesystem_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:09:46 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:09:46 storageqe-109 INFO: #### END test_insufficient_space_handling #### Oct 9 06:09:46 storageqe-109 INFO: #### will start test_corrupted_filesystem_handling ##### Oct 9 06:09:46 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:09:51 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:09:51 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/error_test_corrupted_fs.img) Oct 9 06:09:51 storageqe-109 kernel: loop0: Oct 9 06:10:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:10:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: start Cleaning up error handling test: test_corrupted_filesystem_handling INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 9 06:11:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:11:07 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem a0f40337-e689-4c2f-a52d-8013933a40bc r/w with ordered data mode. Quota mode: none. Oct 9 06:11:07 storageqe-109 udisksd[2509680]: Mounted /dev/loop0p1 at /run/media/root/a0f40337-e689-4c2f-a52d-8013933a40bc on behalf of uid 0 Oct 9 06:11:07 storageqe-109 journal: Oct 9 06:11:07 storageqe-109 INFO: start Cleaning up error handling test: test_corrupted_filesystem_handling Oct 9 06:11:07 storageqe-109 journal: Oct 9 06:11:07 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 9 06:11:07 storageqe-109 journal: Oct 9 06:11:07 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 9 06:11:07 storageqe-109 systemd[1]: run-media-root-a0f40337\x2de689\x2d4c2f\x2da52d\x2d8013933a40bc.mount: Deactivated successfully. Oct 9 06:11:07 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/a0f40337-e689-4c2f-a52d-8013933a40bc (device 259:2 is not mounted) Oct 9 06:11:07 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem a0f40337-e689-4c2f-a52d-8013933a40bc. Oct 9 06:11:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:11:32 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/error_test_corrupted_fs.img) Oct 9 06:11:32 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_corrupted_filesystem_handling #### INFO: #### will start test_device_busy_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:11:37 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:11:37 storageqe-109 INFO: #### END test_corrupted_filesystem_handling #### Oct 9 06:11:37 storageqe-109 INFO: #### will start test_device_busy_handling ##### Oct 9 06:11:37 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:11:43 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:11:43 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/error_test_device_busy.img) Oct 9 06:11:43 storageqe-109 kernel: loop0: Oct 9 06:12:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:12:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:12:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 06:12:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 06:12:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 06:12:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:12:59 storageqe-109 kernel: EXT4-fs (loop0p1): mounted filesystem 75a205a2-8c11-4877-8be7-61e35a2e908f r/w with ordered data mode. Quota mode: none. Oct 9 06:12:59 storageqe-109 udisksd[2509680]: Mounted /dev/loop0p1 at /run/media/root/75a205a2-8c11-4877-8be7-61e35a2e908f on behalf of uid 0 INFO: start Cleaning up error handling test: test_device_busy_handling INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 9 06:13:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:13:29 storageqe-109 udisksd[2509680]: [fdisk] Failed to remove partition 1 from system Oct 9 06:13:29 storageqe-109 journal: Oct 9 06:13:29 storageqe-109 INFO: start Cleaning up error handling test: test_device_busy_handling Oct 9 06:13:29 storageqe-109 journal: Oct 9 06:13:29 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 9 06:13:29 storageqe-109 journal: Oct 9 06:13:29 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop0 Oct 9 06:13:29 storageqe-109 systemd[1]: run-media-root-75a205a2\x2d8c11\x2d4877\x2d8be7\x2d61e35a2e908f.mount: Deactivated successfully. Oct 9 06:13:29 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/75a205a2-8c11-4877-8be7-61e35a2e908f (device 259:2 is not mounted) Oct 9 06:13:29 storageqe-109 kernel: EXT4-fs (loop0p1): unmounting filesystem 75a205a2-8c11-4877-8be7-61e35a2e908f. Oct 9 06:13:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:13:54 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/error_test_device_busy.img) Oct 9 06:13:54 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_device_busy_handling #### INFO: #### will start test_invalid_parameters_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:13:59 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:13:59 storageqe-109 INFO: #### END test_device_busy_handling #### Oct 9 06:13:59 storageqe-109 INFO: #### will start test_invalid_parameters_handling ##### Oct 9 06:13:59 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: start Cleaning up error handling test: test_invalid_parameters_handling INFO: start Cleaning _cleanup_automounts Oct 9 06:14:04 storageqe-109 journal: Oct 9 06:14:04 storageqe-109 INFO: start Cleaning up error handling test: test_invalid_parameters_handling Oct 9 06:14:04 storageqe-109 journal: Oct 9 06:14:04 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_invalid_parameters_handling #### INFO: #### will start test_concurrent_operation_conflicts ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:14:09 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:14:09 storageqe-109 INFO: #### END test_invalid_parameters_handling #### Oct 9 06:14:09 storageqe-109 INFO: #### will start test_concurrent_operation_conflicts ##### Oct 9 06:14:09 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:14:15 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 06:14:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/error_test_concurrent_test.img) Oct 9 06:14:15 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 06:14:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/error_test_concurrent_test.img) Oct 9 06:14:15 storageqe-109 kernel: loop0: Oct 9 06:14:15 storageqe-109 kernel: loop1: Oct 9 06:14:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: start Cleaning up error handling test: test_concurrent_operation_conflicts INFO: start Cleaning _cleanup_automounts Oct 9 06:15:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:15:06 storageqe-109 journal: Oct 9 06:15:06 storageqe-109 INFO: start Cleaning up error handling test: test_concurrent_operation_conflicts Oct 9 06:15:06 storageqe-109 journal: Oct 9 06:15:06 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_concurrent_operation_conflicts #### INFO: #### will start test_system_resource_exhaustion ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:15:11 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:15:11 storageqe-109 INFO: #### END test_concurrent_operation_conflicts #### Oct 9 06:15:11 storageqe-109 INFO: #### will start test_system_resource_exhaustion ##### Oct 9 06:15:11 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:15:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:15:31 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:15:31 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/error_test_resource_test_0.img) Oct 9 06:15:31 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 06:15:31 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/error_test_resource_test_1.img) Oct 9 06:15:32 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 9 06:15:32 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop4 (backed by /home/error_test_resource_test_2.img) Oct 9 06:15:32 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 9 06:15:32 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop5 (backed by /home/error_test_resource_test_3.img) Oct 9 06:15:32 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 9 06:15:32 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop6 (backed by /home/error_test_resource_test_4.img) Oct 9 06:15:33 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 9 06:15:33 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop7 (backed by /home/error_test_resource_test_5.img) Oct 9 06:15:33 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 9 06:15:33 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop8 (backed by /home/error_test_resource_test_6.img) Oct 9 06:15:34 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 9 06:15:34 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop9 (backed by /home/error_test_resource_test_7.img) Oct 9 06:15:34 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 9 06:15:34 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop10 (backed by /home/error_test_resource_test_8.img) Oct 9 06:15:35 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 9 06:15:35 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop11 (backed by /home/error_test_resource_test_9.img) Oct 9 06:15:36 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 9 06:15:36 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop12 (backed by /home/error_test_resource_test_10.img) Oct 9 06:15:37 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 9 06:15:37 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop13 (backed by /home/error_test_resource_test_11.img) Oct 9 06:15:38 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 9 06:15:38 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop14 (backed by /home/error_test_resource_test_12.img) Oct 9 06:15:39 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 9 06:15:39 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop15 (backed by /home/error_test_resource_test_13.img) Oct 9 06:15:40 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 9 06:15:40 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop16 (backed by /home/error_test_resource_test_14.img) Oct 9 06:15:41 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 9 06:15:41 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop17 (backed by /home/error_test_resource_test_15.img) Oct 9 06:15:42 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 9 06:15:42 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop18 (backed by /home/error_test_resource_test_16.img) Oct 9 06:15:43 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 9 06:15:43 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop19 (backed by /home/error_test_resource_test_17.img) Oct 9 06:15:43 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 9 06:15:44 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop20 (backed by /home/error_test_resource_test_18.img) Oct 9 06:15:44 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 9 06:15:44 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop21 (backed by /home/error_test_resource_test_19.img) Oct 9 06:15:45 storageqe-109 kernel: loop22: detected capacity change from 0 to 2097152 Oct 9 06:15:45 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop22 (backed by /home/error_test_resource_test_20.img) Oct 9 06:15:46 storageqe-109 kernel: loop23: detected capacity change from 0 to 2097152 Oct 9 06:15:46 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop23 (backed by /home/error_test_resource_test_21.img) Oct 9 06:15:47 storageqe-109 kernel: loop24: detected capacity change from 0 to 2097152 Oct 9 06:15:47 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop24 (backed by /home/error_test_resource_test_22.img) Oct 9 06:15:48 storageqe-109 kernel: loop25: detected capacity change from 0 to 2097152 Oct 9 06:15:48 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop25 (backed by /home/error_test_resource_test_23.img) Oct 9 06:15:49 storageqe-109 kernel: loop26: detected capacity change from 0 to 2097152 Oct 9 06:15:49 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop26 (backed by /home/error_test_resource_test_24.img) Oct 9 06:15:50 storageqe-109 kernel: loop27: detected capacity change from 0 to 2097152 Oct 9 06:15:50 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop27 (backed by /home/error_test_resource_test_25.img) Oct 9 06:15:51 storageqe-109 kernel: loop28: detected capacity change from 0 to 2097152 Oct 9 06:15:51 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop28 (backed by /home/error_test_resource_test_26.img) Oct 9 06:15:52 storageqe-109 kernel: loop29: detected capacity change from 0 to 2097152 Oct 9 06:15:52 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop29 (backed by /home/error_test_resource_test_27.img) Oct 9 06:15:53 storageqe-109 kernel: loop30: detected capacity change from 0 to 2097152 Oct 9 06:15:53 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop30 (backed by /home/error_test_resource_test_28.img) Oct 9 06:15:54 storageqe-109 kernel: loop31: detected capacity change from 0 to 2097152 Oct 9 06:15:54 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop31 (backed by /home/error_test_resource_test_29.img) Oct 9 06:15:55 storageqe-109 kernel: loop32: detected capacity change from 0 to 2097152 Oct 9 06:15:55 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop32 (backed by /home/error_test_resource_test_30.img) Oct 9 06:15:56 storageqe-109 kernel: loop33: detected capacity change from 0 to 2097152 Oct 9 06:15:56 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop33 (backed by /home/error_test_resource_test_31.img) Oct 9 06:15:57 storageqe-109 kernel: loop34: detected capacity change from 0 to 2097152 Oct 9 06:15:57 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop34 (backed by /home/error_test_resource_test_32.img) Oct 9 06:15:58 storageqe-109 kernel: loop35: detected capacity change from 0 to 2097152 Oct 9 06:15:58 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop35 (backed by /home/error_test_resource_test_33.img) Oct 9 06:15:59 storageqe-109 kernel: loop36: detected capacity change from 0 to 2097152 Oct 9 06:15:59 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop36 (backed by /home/error_test_resource_test_34.img) Oct 9 06:16:00 storageqe-109 kernel: loop37: detected capacity change from 0 to 2097152 Oct 9 06:16:00 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop37 (backed by /home/error_test_resource_test_35.img) Oct 9 06:16:01 storageqe-109 kernel: loop38: detected capacity change from 0 to 2097152 Oct 9 06:16:01 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop38 (backed by /home/error_test_resource_test_36.img) Oct 9 06:16:02 storageqe-109 kernel: loop39: detected capacity change from 0 to 2097152 Oct 9 06:16:02 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop39 (backed by /home/error_test_resource_test_37.img) Oct 9 06:16:02 storageqe-109 kernel: loop40: detected capacity change from 0 to 2097152 Oct 9 06:16:02 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop40 (backed by /home/error_test_resource_test_38.img) Oct 9 06:16:03 storageqe-109 kernel: loop41: detected capacity change from 0 to 2097152 Oct 9 06:16:03 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop41 (backed by /home/error_test_resource_test_39.img) Oct 9 06:16:04 storageqe-109 kernel: loop42: detected capacity change from 0 to 2097152 Oct 9 06:16:04 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop42 (backed by /home/error_test_resource_test_40.img) Oct 9 06:16:05 storageqe-109 kernel: loop43: detected capacity change from 0 to 2097152 Oct 9 06:16:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop43 (backed by /home/error_test_resource_test_41.img) Oct 9 06:16:06 storageqe-109 kernel: loop44: detected capacity change from 0 to 2097152 Oct 9 06:16:06 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop44 (backed by /home/error_test_resource_test_42.img) Oct 9 06:16:07 storageqe-109 kernel: loop45: detected capacity change from 0 to 2097152 Oct 9 06:16:07 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop45 (backed by /home/error_test_resource_test_43.img) Oct 9 06:16:08 storageqe-109 kernel: loop46: detected capacity change from 0 to 2097152 Oct 9 06:16:08 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop46 (backed by /home/error_test_resource_test_44.img) Oct 9 06:16:09 storageqe-109 kernel: loop47: detected capacity change from 0 to 2097152 Oct 9 06:16:09 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop47 (backed by /home/error_test_resource_test_45.img) Oct 9 06:16:10 storageqe-109 kernel: loop48: detected capacity change from 0 to 2097152 Oct 9 06:16:10 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop48 (backed by /home/error_test_resource_test_46.img) Oct 9 06:16:11 storageqe-109 kernel: loop49: detected capacity change from 0 to 2097152 Oct 9 06:16:11 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop49 (backed by /home/error_test_resource_test_47.img) Oct 9 06:16:12 storageqe-109 kernel: loop50: detected capacity change from 0 to 2097152 Oct 9 06:16:12 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop50 (backed by /home/error_test_resource_test_48.img) Oct 9 06:16:13 storageqe-109 kernel: loop51: detected capacity change from 0 to 2097152 Oct 9 06:16:13 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop51 (backed by /home/error_test_resource_test_49.img) Oct 9 06:16:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:16:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/error_test_resource_test_0.img) Oct 9 06:16:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:17:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:17:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/error_test_resource_test_1.img) Oct 9 06:17:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 06:17:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:17:28 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop4 (was backed by /home/error_test_resource_test_2.img) Oct 9 06:17:28 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop4 Oct 9 06:17:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:17:53 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop5 (was backed by /home/error_test_resource_test_3.img) Oct 9 06:17:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop5 Oct 9 06:18:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:18:18 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop6 (was backed by /home/error_test_resource_test_4.img) Oct 9 06:18:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop6 Oct 9 06:18:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:18:43 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop7 (was backed by /home/error_test_resource_test_5.img) Oct 9 06:18:43 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop7 Oct 9 06:19:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:19:08 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop8 (was backed by /home/error_test_resource_test_6.img) Oct 9 06:19:08 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop8 Oct 9 06:19:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:19:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop9 (was backed by /home/error_test_resource_test_7.img) Oct 9 06:19:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop9 Oct 9 06:19:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:19:58 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop10 (was backed by /home/error_test_resource_test_8.img) Oct 9 06:19:58 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop10 Oct 9 06:20:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:20:23 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop11 (was backed by /home/error_test_resource_test_9.img) Oct 9 06:20:23 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop11 Oct 9 06:20:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:20:48 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop12 (was backed by /home/error_test_resource_test_10.img) Oct 9 06:20:48 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop12 Oct 9 06:21:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:21:13 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop13 (was backed by /home/error_test_resource_test_11.img) Oct 9 06:21:13 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop13 Oct 9 06:21:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:21:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop14 (was backed by /home/error_test_resource_test_12.img) Oct 9 06:21:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop14 Oct 9 06:22:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:22:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop15 (was backed by /home/error_test_resource_test_13.img) Oct 9 06:22:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop15 Oct 9 06:22:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:22:28 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop16 (was backed by /home/error_test_resource_test_14.img) Oct 9 06:22:28 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop16 Oct 9 06:22:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:22:53 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop17 (was backed by /home/error_test_resource_test_15.img) Oct 9 06:22:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop17 Oct 9 06:23:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:23:18 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop18 (was backed by /home/error_test_resource_test_16.img) Oct 9 06:23:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop18 Oct 9 06:23:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:23:43 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop19 (was backed by /home/error_test_resource_test_17.img) Oct 9 06:23:43 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop19 Oct 9 06:24:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:24:08 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop20 (was backed by /home/error_test_resource_test_18.img) Oct 9 06:24:08 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop20 Oct 9 06:24:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:24:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop21 (was backed by /home/error_test_resource_test_19.img) Oct 9 06:24:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop21 Oct 9 06:24:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:24:58 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop22 (was backed by /home/error_test_resource_test_20.img) Oct 9 06:24:58 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop22 Oct 9 06:25:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:25:23 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop23 (was backed by /home/error_test_resource_test_21.img) Oct 9 06:25:23 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop23 Oct 9 06:25:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:25:49 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop24 (was backed by /home/error_test_resource_test_22.img) Oct 9 06:25:49 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop24 Oct 9 06:26:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:26:14 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop25 (was backed by /home/error_test_resource_test_23.img) Oct 9 06:26:14 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop25 Oct 9 06:26:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:26:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop26 (was backed by /home/error_test_resource_test_24.img) Oct 9 06:26:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop26 Oct 9 06:27:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:27:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop27 (was backed by /home/error_test_resource_test_25.img) Oct 9 06:27:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop27 Oct 9 06:27:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:27:29 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop28 (was backed by /home/error_test_resource_test_26.img) Oct 9 06:27:29 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop28 Oct 9 06:27:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:27:54 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop29 (was backed by /home/error_test_resource_test_27.img) Oct 9 06:27:54 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop29 Oct 9 06:28:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:28:19 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop30 (was backed by /home/error_test_resource_test_28.img) Oct 9 06:28:19 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop30 Oct 9 06:28:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:28:44 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop31 (was backed by /home/error_test_resource_test_29.img) Oct 9 06:28:44 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop31 Oct 9 06:29:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:29:09 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop32 (was backed by /home/error_test_resource_test_30.img) Oct 9 06:29:09 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop32 Oct 9 06:29:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:29:34 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop33 (was backed by /home/error_test_resource_test_31.img) Oct 9 06:29:34 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop33 Oct 9 06:29:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:29:59 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop34 (was backed by /home/error_test_resource_test_32.img) Oct 9 06:29:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop34 Oct 9 06:30:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:30:24 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop35 (was backed by /home/error_test_resource_test_33.img) Oct 9 06:30:24 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop35 Oct 9 06:30:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:30:49 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop36 (was backed by /home/error_test_resource_test_34.img) Oct 9 06:30:49 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop36 Oct 9 06:31:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:31:14 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop37 (was backed by /home/error_test_resource_test_35.img) Oct 9 06:31:14 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop37 Oct 9 06:31:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:31:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop38 (was backed by /home/error_test_resource_test_36.img) Oct 9 06:31:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop38 Oct 9 06:32:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:32:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop39 (was backed by /home/error_test_resource_test_37.img) Oct 9 06:32:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop39 Oct 9 06:32:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:32:29 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop40 (was backed by /home/error_test_resource_test_38.img) Oct 9 06:32:29 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop40 Oct 9 06:32:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:32:54 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop41 (was backed by /home/error_test_resource_test_39.img) Oct 9 06:32:54 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop41 Oct 9 06:33:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:33:19 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop42 (was backed by /home/error_test_resource_test_40.img) Oct 9 06:33:19 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop42 Oct 9 06:33:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:33:44 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop43 (was backed by /home/error_test_resource_test_41.img) Oct 9 06:33:44 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop43 Oct 9 06:34:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:34:09 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop44 (was backed by /home/error_test_resource_test_42.img) Oct 9 06:34:09 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop44 Oct 9 06:34:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:34:34 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop45 (was backed by /home/error_test_resource_test_43.img) Oct 9 06:34:34 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop45 Oct 9 06:34:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:34:59 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop46 (was backed by /home/error_test_resource_test_44.img) Oct 9 06:34:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop46 Oct 9 06:35:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:35:24 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop47 (was backed by /home/error_test_resource_test_45.img) Oct 9 06:35:24 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop47 Oct 9 06:35:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:35:49 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop48 (was backed by /home/error_test_resource_test_46.img) Oct 9 06:35:49 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop48 Oct 9 06:36:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:36:14 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop49 (was backed by /home/error_test_resource_test_47.img) Oct 9 06:36:14 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop49 Oct 9 06:36:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:36:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop50 (was backed by /home/error_test_resource_test_48.img) Oct 9 06:36:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop50 INFO: start Cleaning up error handling test: test_system_resource_exhaustion INFO: start Cleaning _cleanup_automounts Oct 9 06:37:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:37:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop51 (was backed by /home/error_test_resource_test_49.img) Oct 9 06:37:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop51 Oct 9 06:37:04 storageqe-109 journal: Oct 9 06:37:04 storageqe-109 INFO: start Cleaning up error handling test: test_system_resource_exhaustion Oct 9 06:37:04 storageqe-109 journal: Oct 9 06:37:04 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_system_resource_exhaustion #### INFO: #### will start test_interrupted_operations_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:37:09 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:37:09 storageqe-109 INFO: #### END test_system_resource_exhaustion #### Oct 9 06:37:09 storageqe-109 INFO: #### will start test_interrupted_operations_handling ##### Oct 9 06:37:09 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:37:15 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:37:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/error_test_interrupt_test.img) Oct 9 06:37:15 storageqe-109 kernel: loop2: Oct 9 06:37:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: start Cleaning up error handling test: test_interrupted_operations_handling INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 06:37:51 storageqe-109 journal: Oct 9 06:37:51 storageqe-109 INFO: start Cleaning up error handling test: test_interrupted_operations_handling Oct 9 06:37:51 storageqe-109 journal: Oct 9 06:37:51 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 9 06:37:51 storageqe-109 journal: Oct 9 06:37:51 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 06:38:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:38:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:38:30 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/error_test_interrupt_test.img) Oct 9 06:38:30 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_interrupted_operations_handling #### INFO: #### will start test_malformed_dbus_messages_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:38:35 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:38:35 storageqe-109 INFO: #### END test_interrupted_operations_handling #### Oct 9 06:38:35 storageqe-109 INFO: #### will start test_malformed_dbus_messages_handling ##### Oct 9 06:38:35 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: start Cleaning up error handling test: test_malformed_dbus_messages_handling INFO: start Cleaning _cleanup_automounts Oct 9 06:38:41 storageqe-109 journal: Oct 9 06:38:41 storageqe-109 INFO: start Cleaning up error handling test: test_malformed_dbus_messages_handling Oct 9 06:38:41 storageqe-109 journal: Oct 9 06:38:41 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_malformed_dbus_messages_handling #### INFO: #### will start test_cleanup_after_errors ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:38:46 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:38:46 storageqe-109 INFO: #### END test_malformed_dbus_messages_handling #### Oct 9 06:38:46 storageqe-109 INFO: #### will start test_cleanup_after_errors ##### Oct 9 06:38:46 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:38:51 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:38:51 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/error_test_cleanup_test.img) Oct 9 06:38:51 storageqe-109 kernel: loop2: Oct 9 06:39:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:39:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: start Cleaning up error handling test: test_cleanup_after_errors INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 06:40:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:40:07 storageqe-109 udisksd[2509680]: Mounted /dev/loop2p1 at /run/media/root/37b6e105-7e6f-4444-9b32-24df205a665c on behalf of uid 0 Oct 9 06:40:07 storageqe-109 kernel: EXT4-fs (loop2p1): mounted filesystem 37b6e105-7e6f-4444-9b32-24df205a665c r/w with ordered data mode. Quota mode: none. Oct 9 06:40:07 storageqe-109 journal: Oct 9 06:40:07 storageqe-109 INFO: start Cleaning up error handling test: test_cleanup_after_errors Oct 9 06:40:07 storageqe-109 journal: Oct 9 06:40:07 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 9 06:40:07 storageqe-109 journal: Oct 9 06:40:07 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 06:40:07 storageqe-109 systemd[1]: run-media-root-37b6e105\x2d7e6f\x2d4444\x2d9b32\x2d24df205a665c.mount: Deactivated successfully. Oct 9 06:40:07 storageqe-109 udisksd[2509680]: Cleaning up mount point /run/media/root/37b6e105-7e6f-4444-9b32-24df205a665c (device 259:3 is not mounted) Oct 9 06:40:07 storageqe-109 kernel: EXT4-fs (loop2p1): unmounting filesystem 37b6e105-7e6f-4444-9b32-24df205a665c. Oct 9 06:40:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:40:32 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/error_test_cleanup_test.img) Oct 9 06:40:32 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_cleanup_after_errors #### INFO: #### will start test_memory_leak_detection ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:40:37 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:40:37 storageqe-109 INFO: #### END test_cleanup_after_errors #### Oct 9 06:40:37 storageqe-109 INFO: #### will start test_memory_leak_detection ##### Oct 9 06:40:37 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:40:42 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:40:42 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:41:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:41:07 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:41:07 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:41:08 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:41:08 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:41:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:41:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:41:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:41:33 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:41:33 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:41:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:41:58 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:41:58 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:41:59 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:41:59 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:42:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:42:24 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:42:24 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:42:24 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:42:24 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:42:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:42:49 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:42:49 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:42:50 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:42:50 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:43:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:43:15 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:43:15 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:43:15 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:43:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:43:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:43:40 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:43:40 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:43:41 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:43:41 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:44:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:44:06 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:44:06 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:44:06 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:44:06 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:44:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:44:31 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:44:31 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:44:32 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:44:32 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:44:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:44:57 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:44:57 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:44:57 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:44:57 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:45:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:45:22 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:45:22 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:45:23 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:45:23 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:45:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:45:48 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:45:48 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:45:48 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:45:48 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:46:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:46:13 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:46:13 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:46:14 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:46:14 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:46:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:46:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:46:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:46:39 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:46:39 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:47:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:47:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:47:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:47:05 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:47:05 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:47:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:47:30 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:47:30 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:47:30 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:47:30 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:47:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:47:55 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:47:55 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:47:56 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:47:56 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:48:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:48:21 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:48:21 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:48:21 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:48:21 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) Oct 9 06:48:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:48:46 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:48:46 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:48:47 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:48:47 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /dev/nonexistent) INFO: start Cleaning up error handling test: test_memory_leak_detection INFO: start Cleaning _cleanup_automounts Oct 9 06:49:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:49:12 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /dev/nonexistent) Oct 9 06:49:12 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 06:49:12 storageqe-109 journal: Oct 9 06:49:12 storageqe-109 INFO: start Cleaning up error handling test: test_memory_leak_detection Oct 9 06:49:12 storageqe-109 journal: Oct 9 06:49:12 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_memory_leak_detection #### INFO: #### will start test_udisks2_crash_conditions ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:49:17 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:49:17 storageqe-109 INFO: #### END test_memory_leak_detection #### Oct 9 06:49:17 storageqe-109 INFO: #### will start test_udisks2_crash_conditions ##### Oct 9 06:49:17 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 06:49:22 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 06:49:22 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/error_test_crash_test_0.img) Oct 9 06:49:22 storageqe-109 kernel: loop2: Oct 9 06:49:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:49:48 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 06:49:48 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/error_test_crash_test_1.img) Oct 9 06:49:48 storageqe-109 kernel: loop3: Oct 9 06:50:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:50:14 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 9 06:50:15 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop4 (backed by /home/error_test_crash_test_2.img) Oct 9 06:50:15 storageqe-109 kernel: loop4: Oct 9 06:50:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:50:41 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 9 06:50:41 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop5 (backed by /home/error_test_crash_test_3.img) Oct 9 06:50:41 storageqe-109 kernel: loop5: Oct 9 06:51:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:51:07 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 9 06:51:07 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop6 (backed by /home/error_test_crash_test_4.img) Oct 9 06:51:07 storageqe-109 kernel: loop6: Oct 9 06:51:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:51:33 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 9 06:51:33 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop7 (backed by /home/error_test_crash_test_5.img) Oct 9 06:51:33 storageqe-109 kernel: loop7: Oct 9 06:51:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:51:59 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 9 06:51:59 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop8 (backed by /home/error_test_crash_test_6.img) Oct 9 06:51:59 storageqe-109 kernel: loop8: Oct 9 06:52:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:52:26 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 9 06:52:26 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop9 (backed by /home/error_test_crash_test_7.img) Oct 9 06:52:26 storageqe-109 kernel: loop9: Oct 9 06:52:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:52:52 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 9 06:52:52 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop10 (backed by /home/error_test_crash_test_8.img) Oct 9 06:52:52 storageqe-109 kernel: loop10: Oct 9 06:53:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:53:18 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 9 06:53:18 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop11 (backed by /home/error_test_crash_test_9.img) Oct 9 06:53:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:53:44 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 9 06:53:44 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop12 (backed by /home/error_test_crash_test_10.img) Oct 9 06:53:44 storageqe-109 kernel: loop12: Oct 9 06:54:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:54:10 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 9 06:54:10 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop13 (backed by /home/error_test_crash_test_11.img) Oct 9 06:54:10 storageqe-109 kernel: loop13: Oct 9 06:54:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:54:37 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 9 06:54:37 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop14 (backed by /home/error_test_crash_test_12.img) Oct 9 06:54:37 storageqe-109 kernel: loop14: Oct 9 06:55:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:55:03 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 9 06:55:03 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop15 (backed by /home/error_test_crash_test_13.img) Oct 9 06:55:03 storageqe-109 kernel: loop15: Oct 9 06:55:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:55:29 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 9 06:55:29 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop16 (backed by /home/error_test_crash_test_14.img) Oct 9 06:55:29 storageqe-109 kernel: loop16: Oct 9 06:55:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:55:55 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 9 06:55:55 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop17 (backed by /home/error_test_crash_test_15.img) Oct 9 06:55:55 storageqe-109 kernel: loop17: Oct 9 06:56:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:56:22 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 9 06:56:22 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop18 (backed by /home/error_test_crash_test_16.img) Oct 9 06:56:22 storageqe-109 kernel: loop18: Oct 9 06:56:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:56:48 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 9 06:56:48 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop19 (backed by /home/error_test_crash_test_17.img) Oct 9 06:56:48 storageqe-109 kernel: loop19: Oct 9 06:57:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:57:14 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 9 06:57:14 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop20 (backed by /home/error_test_crash_test_18.img) Oct 9 06:57:14 storageqe-109 kernel: loop20: Oct 9 06:57:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:57:40 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 9 06:57:40 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop21 (backed by /home/error_test_crash_test_19.img) Oct 9 06:57:40 storageqe-109 kernel: loop21: Oct 9 06:58:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:58:06 storageqe-109 kernel: loop22: detected capacity change from 0 to 2097152 Oct 9 06:58:06 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop22 (backed by /home/error_test_crash_test_20.img) Oct 9 06:58:06 storageqe-109 kernel: loop22: Oct 9 06:58:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:58:33 storageqe-109 kernel: loop23: detected capacity change from 0 to 2097152 Oct 9 06:58:33 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop23 (backed by /home/error_test_crash_test_21.img) Oct 9 06:58:33 storageqe-109 kernel: loop23: Oct 9 06:58:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:58:59 storageqe-109 kernel: loop24: detected capacity change from 0 to 2097152 Oct 9 06:58:59 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop24 (backed by /home/error_test_crash_test_22.img) Oct 9 06:58:59 storageqe-109 kernel: loop24: Oct 9 06:59:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:59:25 storageqe-109 kernel: loop25: detected capacity change from 0 to 2097152 Oct 9 06:59:25 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop25 (backed by /home/error_test_crash_test_23.img) Oct 9 06:59:25 storageqe-109 kernel: loop25: Oct 9 06:59:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 06:59:51 storageqe-109 kernel: loop26: detected capacity change from 0 to 2097152 Oct 9 06:59:51 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop26 (backed by /home/error_test_crash_test_24.img) Oct 9 06:59:51 storageqe-109 kernel: loop26: Oct 9 07:00:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:00:17 storageqe-109 kernel: loop27: detected capacity change from 0 to 2097152 Oct 9 07:00:17 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop27 (backed by /home/error_test_crash_test_25.img) Oct 9 07:00:18 storageqe-109 kernel: loop27: Oct 9 07:00:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:00:44 storageqe-109 kernel: loop28: detected capacity change from 0 to 2097152 Oct 9 07:00:44 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop28 (backed by /home/error_test_crash_test_26.img) Oct 9 07:00:44 storageqe-109 kernel: loop28: Oct 9 07:01:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:01:10 storageqe-109 kernel: loop29: detected capacity change from 0 to 2097152 Oct 9 07:01:10 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop29 (backed by /home/error_test_crash_test_27.img) Oct 9 07:01:10 storageqe-109 kernel: loop29: Oct 9 07:01:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:01:36 storageqe-109 kernel: loop30: detected capacity change from 0 to 2097152 Oct 9 07:01:36 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop30 (backed by /home/error_test_crash_test_28.img) Oct 9 07:01:36 storageqe-109 kernel: loop30: Oct 9 07:02:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:02:02 storageqe-109 kernel: loop31: detected capacity change from 0 to 2097152 Oct 9 07:02:02 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop31 (backed by /home/error_test_crash_test_29.img) Oct 9 07:02:02 storageqe-109 kernel: loop31: Oct 9 07:02:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:02:29 storageqe-109 kernel: loop32: detected capacity change from 0 to 2097152 Oct 9 07:02:29 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop32 (backed by /home/error_test_crash_test_30.img) Oct 9 07:02:29 storageqe-109 kernel: loop32: Oct 9 07:02:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:02:55 storageqe-109 kernel: loop33: detected capacity change from 0 to 2097152 Oct 9 07:02:55 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop33 (backed by /home/error_test_crash_test_31.img) Oct 9 07:02:55 storageqe-109 kernel: loop33: Oct 9 07:03:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:03:21 storageqe-109 kernel: loop34: detected capacity change from 0 to 2097152 Oct 9 07:03:21 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop34 (backed by /home/error_test_crash_test_32.img) Oct 9 07:03:21 storageqe-109 kernel: loop34: Oct 9 07:03:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:03:47 storageqe-109 kernel: loop35: detected capacity change from 0 to 2097152 Oct 9 07:03:47 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop35 (backed by /home/error_test_crash_test_33.img) Oct 9 07:03:47 storageqe-109 kernel: loop35: Oct 9 07:04:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:04:14 storageqe-109 kernel: loop36: detected capacity change from 0 to 2097152 Oct 9 07:04:14 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop36 (backed by /home/error_test_crash_test_34.img) Oct 9 07:04:14 storageqe-109 kernel: loop36: Oct 9 07:04:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:04:40 storageqe-109 kernel: loop37: detected capacity change from 0 to 2097152 Oct 9 07:04:40 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop37 (backed by /home/error_test_crash_test_35.img) Oct 9 07:04:40 storageqe-109 kernel: loop37: Oct 9 07:05:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:05:06 storageqe-109 kernel: loop38: detected capacity change from 0 to 2097152 Oct 9 07:05:06 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop38 (backed by /home/error_test_crash_test_36.img) Oct 9 07:05:06 storageqe-109 kernel: loop38: Oct 9 07:05:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:05:32 storageqe-109 kernel: loop39: detected capacity change from 0 to 2097152 Oct 9 07:05:32 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop39 (backed by /home/error_test_crash_test_37.img) Oct 9 07:05:32 storageqe-109 kernel: loop39: Oct 9 07:05:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:05:58 storageqe-109 kernel: loop40: detected capacity change from 0 to 2097152 Oct 9 07:05:58 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop40 (backed by /home/error_test_crash_test_38.img) Oct 9 07:05:58 storageqe-109 kernel: loop40: Oct 9 07:06:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:06:25 storageqe-109 kernel: loop41: detected capacity change from 0 to 2097152 Oct 9 07:06:25 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop41 (backed by /home/error_test_crash_test_39.img) Oct 9 07:06:25 storageqe-109 kernel: loop41: Oct 9 07:06:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:06:51 storageqe-109 kernel: loop42: detected capacity change from 0 to 2097152 Oct 9 07:06:51 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop42 (backed by /home/error_test_crash_test_40.img) Oct 9 07:06:51 storageqe-109 kernel: loop42: Oct 9 07:07:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:07:17 storageqe-109 kernel: loop43: detected capacity change from 0 to 2097152 Oct 9 07:07:17 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop43 (backed by /home/error_test_crash_test_41.img) Oct 9 07:07:17 storageqe-109 kernel: loop43: Oct 9 07:07:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:07:43 storageqe-109 kernel: loop44: detected capacity change from 0 to 2097152 Oct 9 07:07:43 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop44 (backed by /home/error_test_crash_test_42.img) Oct 9 07:07:43 storageqe-109 kernel: loop44: Oct 9 07:08:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:08:10 storageqe-109 kernel: loop45: detected capacity change from 0 to 2097152 Oct 9 07:08:10 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop45 (backed by /home/error_test_crash_test_43.img) Oct 9 07:08:10 storageqe-109 kernel: loop45: Oct 9 07:08:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:08:36 storageqe-109 kernel: loop46: detected capacity change from 0 to 2097152 Oct 9 07:08:36 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop46 (backed by /home/error_test_crash_test_44.img) Oct 9 07:08:36 storageqe-109 kernel: loop46: Oct 9 07:09:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:09:02 storageqe-109 kernel: loop47: detected capacity change from 0 to 2097152 Oct 9 07:09:02 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop47 (backed by /home/error_test_crash_test_45.img) Oct 9 07:09:02 storageqe-109 kernel: loop47: Oct 9 07:09:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:09:28 storageqe-109 kernel: loop48: detected capacity change from 0 to 2097152 Oct 9 07:09:28 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop48 (backed by /home/error_test_crash_test_46.img) Oct 9 07:09:28 storageqe-109 kernel: loop48: Oct 9 07:09:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:09:55 storageqe-109 kernel: loop49: detected capacity change from 0 to 2097152 Oct 9 07:09:55 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop49 (backed by /home/error_test_crash_test_47.img) Oct 9 07:10:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:10:21 storageqe-109 kernel: loop50: detected capacity change from 0 to 2097152 Oct 9 07:10:21 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop50 (backed by /home/error_test_crash_test_48.img) Oct 9 07:10:21 storageqe-109 kernel: loop50: Oct 9 07:10:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:10:47 storageqe-109 kernel: loop51: detected capacity change from 0 to 2097152 Oct 9 07:10:47 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop51 (backed by /home/error_test_crash_test_49.img) Oct 9 07:10:47 storageqe-109 kernel: loop51: Oct 9 07:11:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:11:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:11:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/error_test_crash_test_0.img) Oct 9 07:11:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 07:12:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:12:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/error_test_crash_test_1.img) Oct 9 07:12:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 07:12:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:12:28 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop4 (was backed by /home/error_test_crash_test_2.img) Oct 9 07:12:28 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop4 Oct 9 07:12:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:12:53 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop5 (was backed by /home/error_test_crash_test_3.img) Oct 9 07:12:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop5 Oct 9 07:13:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:13:18 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop6 (was backed by /home/error_test_crash_test_4.img) Oct 9 07:13:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop6 Oct 9 07:13:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:13:43 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop7 (was backed by /home/error_test_crash_test_5.img) Oct 9 07:13:43 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop7 Oct 9 07:14:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:14:08 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop8 (was backed by /home/error_test_crash_test_6.img) Oct 9 07:14:08 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop8 Oct 9 07:14:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:14:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop9 (was backed by /home/error_test_crash_test_7.img) Oct 9 07:14:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop9 Oct 9 07:14:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:14:58 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop10 (was backed by /home/error_test_crash_test_8.img) Oct 9 07:14:58 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop10 Oct 9 07:15:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:15:23 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop11 (was backed by /home/error_test_crash_test_9.img) Oct 9 07:15:23 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop11 Oct 9 07:15:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:15:48 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop12 (was backed by /home/error_test_crash_test_10.img) Oct 9 07:15:48 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop12 Oct 9 07:16:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:16:13 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop13 (was backed by /home/error_test_crash_test_11.img) Oct 9 07:16:13 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop13 Oct 9 07:16:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:16:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop14 (was backed by /home/error_test_crash_test_12.img) Oct 9 07:16:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop14 Oct 9 07:17:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:17:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop15 (was backed by /home/error_test_crash_test_13.img) Oct 9 07:17:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop15 Oct 9 07:17:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:17:28 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop16 (was backed by /home/error_test_crash_test_14.img) Oct 9 07:17:28 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop16 Oct 9 07:17:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:17:53 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop17 (was backed by /home/error_test_crash_test_15.img) Oct 9 07:17:53 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop17 Oct 9 07:18:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:18:18 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop18 (was backed by /home/error_test_crash_test_16.img) Oct 9 07:18:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop18 Oct 9 07:18:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:18:43 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop19 (was backed by /home/error_test_crash_test_17.img) Oct 9 07:18:43 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop19 Oct 9 07:19:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:19:08 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop20 (was backed by /home/error_test_crash_test_18.img) Oct 9 07:19:08 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop20 Oct 9 07:19:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:19:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop21 (was backed by /home/error_test_crash_test_19.img) Oct 9 07:19:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop21 Oct 9 07:19:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:19:58 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop22 (was backed by /home/error_test_crash_test_20.img) Oct 9 07:19:58 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop22 Oct 9 07:20:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:20:23 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop23 (was backed by /home/error_test_crash_test_21.img) Oct 9 07:20:23 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop23 Oct 9 07:20:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:20:48 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop24 (was backed by /home/error_test_crash_test_22.img) Oct 9 07:20:48 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop24 Oct 9 07:21:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:21:13 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop25 (was backed by /home/error_test_crash_test_23.img) Oct 9 07:21:13 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop25 Oct 9 07:21:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:21:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop26 (was backed by /home/error_test_crash_test_24.img) Oct 9 07:21:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop26 Oct 9 07:22:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:22:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop27 (was backed by /home/error_test_crash_test_25.img) Oct 9 07:22:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop27 Oct 9 07:22:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:22:29 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop28 (was backed by /home/error_test_crash_test_26.img) Oct 9 07:22:29 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop28 Oct 9 07:22:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:22:54 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop29 (was backed by /home/error_test_crash_test_27.img) Oct 9 07:22:54 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop29 Oct 9 07:23:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:23:19 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop30 (was backed by /home/error_test_crash_test_28.img) Oct 9 07:23:19 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop30 Oct 9 07:23:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:23:44 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop31 (was backed by /home/error_test_crash_test_29.img) Oct 9 07:23:44 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop31 Oct 9 07:24:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:24:09 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop32 (was backed by /home/error_test_crash_test_30.img) Oct 9 07:24:09 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop32 Oct 9 07:24:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:24:34 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop33 (was backed by /home/error_test_crash_test_31.img) Oct 9 07:24:34 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop33 Oct 9 07:24:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:24:59 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop34 (was backed by /home/error_test_crash_test_32.img) Oct 9 07:24:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop34 Oct 9 07:25:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:25:24 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop35 (was backed by /home/error_test_crash_test_33.img) Oct 9 07:25:24 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop35 Oct 9 07:25:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:25:49 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop36 (was backed by /home/error_test_crash_test_34.img) Oct 9 07:25:49 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop36 Oct 9 07:26:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:26:14 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop37 (was backed by /home/error_test_crash_test_35.img) Oct 9 07:26:14 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop37 Oct 9 07:26:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:26:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop38 (was backed by /home/error_test_crash_test_36.img) Oct 9 07:26:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop38 Oct 9 07:27:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:27:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop39 (was backed by /home/error_test_crash_test_37.img) Oct 9 07:27:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop39 Oct 9 07:27:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:27:29 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop40 (was backed by /home/error_test_crash_test_38.img) Oct 9 07:27:29 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop40 Oct 9 07:27:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:27:54 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop41 (was backed by /home/error_test_crash_test_39.img) Oct 9 07:27:54 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop41 Oct 9 07:28:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:28:19 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop42 (was backed by /home/error_test_crash_test_40.img) Oct 9 07:28:19 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop42 Oct 9 07:28:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:28:44 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop43 (was backed by /home/error_test_crash_test_41.img) Oct 9 07:28:44 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop43 Oct 9 07:29:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:29:09 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop44 (was backed by /home/error_test_crash_test_42.img) Oct 9 07:29:09 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop44 Oct 9 07:29:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:29:34 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop45 (was backed by /home/error_test_crash_test_43.img) Oct 9 07:29:34 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop45 Oct 9 07:29:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:29:59 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop46 (was backed by /home/error_test_crash_test_44.img) Oct 9 07:29:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop46 Oct 9 07:30:02 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 07:30:02 storageqe-109 dnf[2560812]: Updating Subscription Management repositories. Oct 9 07:30:02 storageqe-109 dnf[2560812]: Unable to read consumer identity Oct 9 07:30:02 storageqe-109 dnf[2560812]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-AppStream 613 kB/s | 2.8 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-AppStream-debuginfo 574 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-BaseOS 863 kB/s | 2.7 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-BaseOS-debuginfo 562 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-CRB 786 kB/s | 2.7 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-CRB-debuginfo 613 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-HighAvailability 950 kB/s | 2.8 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-HighAvailability-debuginfo 287 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-NFV 918 kB/s | 2.7 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-NFV-debuginfo 557 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-RT 881 kB/s | 2.7 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-RT-debuginfo 569 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-SAP 902 kB/s | 2.7 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-SAP-debuginfo 560 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-SAPHANA 899 kB/s | 2.7 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: beaker-SAPHANA-debuginfo 539 kB/s | 1.5 kB 00:00 Oct 9 07:30:02 storageqe-109 dnf[2560812]: Beaker Client - RedHatEnterpriseLinux10 2.4 kB/s | 1.3 kB 00:00 Oct 9 07:30:03 storageqe-109 dnf[2560812]: beaker-harness 2.5 kB/s | 1.3 kB 00:00 Oct 9 07:30:03 storageqe-109 dnf[2560812]: Google Cloud CLI 3.3 kB/s | 1.4 kB 00:00 Oct 9 07:30:04 storageqe-109 dnf[2560812]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 9 07:30:05 storageqe-109 dnf[2560812]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 9 07:30:05 storageqe-109 dnf[2560812]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 9 07:30:05 storageqe-109 dnf[2560812]: Metadata cache created. Oct 9 07:30:05 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 07:30:05 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 07:30:05 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 338ms CPU time, 86.2M memory peak. Oct 9 07:30:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:30:24 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop47 (was backed by /home/error_test_crash_test_45.img) Oct 9 07:30:24 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop47 Oct 9 07:30:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:30:49 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop48 (was backed by /home/error_test_crash_test_46.img) Oct 9 07:30:49 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop48 Oct 9 07:31:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:31:14 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop49 (was backed by /home/error_test_crash_test_47.img) Oct 9 07:31:14 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop49 Oct 9 07:31:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:31:39 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop50 (was backed by /home/error_test_crash_test_48.img) Oct 9 07:31:39 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop50 Oct 9 07:32:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:32:04 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop51 (was backed by /home/error_test_crash_test_49.img) Oct 9 07:32:04 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop51 Oct 9 07:32:04 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 07:32:04 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/error_test_concurrent_crash_test.img) Oct 9 07:32:04 storageqe-109 kernel: loop2: Oct 9 07:32:04 storageqe-109 kernel: loop2: Oct 9 07:32:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:32:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:32:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:32:55 storageqe-109 kernel: loop2: Oct 9 07:32:55 storageqe-109 kernel: loop2: Oct 9 07:33:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:33:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:33:46 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 07:33:46 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/error_test_invalid_params_test.img) Oct 9 07:34:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:34:11 storageqe-109 kernel: loop2: Oct 9 07:34:11 storageqe-109 kernel: loop2: Oct 9 07:34:11 storageqe-109 kernel: loop2: Oct 9 07:34:11 storageqe-109 kernel: loop2: Oct 9 07:34:11 storageqe-109 kernel: loop3: Oct 9 07:34:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: start Cleaning up error handling test: test_udisks2_crash_conditions INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 07:34:37 storageqe-109 journal: Oct 9 07:34:37 storageqe-109 INFO: start Cleaning up error handling test: test_udisks2_crash_conditions Oct 9 07:34:37 storageqe-109 journal: Oct 9 07:34:37 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 9 07:34:37 storageqe-109 journal: Oct 9 07:34:37 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 07:35:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:35:02 storageqe-109 kernel: loop3: INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop3 Oct 9 07:35:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:35:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:35:27 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/error_test_concurrent_crash_test.img) Oct 9 07:35:27 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 07:35:27 storageqe-109 journal: Oct 9 07:35:27 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop3 Oct 9 07:35:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:36:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:36:18 storageqe-109 kernel: loop3: Oct 9 07:36:18 storageqe-109 kernel: loop3: Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/error_test_invalid_params_test.img) Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:36:43 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 kernel: I/O error, dev loop3, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument Oct 9 07:36:43 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop3': Invalid argument INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_udisks2_crash_conditions #### INFO: #### will start test_force_udisks2_crash ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 07:36:48 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 07:36:48 storageqe-109 INFO: #### END test_udisks2_crash_conditions #### Oct 9 07:36:48 storageqe-109 INFO: #### will start test_force_udisks2_crash ##### Oct 9 07:36:48 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 07:36:53 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 07:36:53 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/error_test_force_crash.img) Oct 9 07:36:53 storageqe-109 kernel: loop2: Oct 9 07:36:53 storageqe-109 kernel: loop2: Oct 9 07:37:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:37:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:37:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:37:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:38:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:38:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:38:39 storageqe-109 kernel: loop2: Oct 9 07:38:39 storageqe-109 kernel: loop2: Oct 9 07:38:39 storageqe-109 kernel: loop2: Oct 9 07:38:39 storageqe-109 kernel: loop2: Oct 9 07:38:39 storageqe-109 kernel: loop2: Oct 9 07:38:39 storageqe-109 kernel: loop2: Oct 9 07:39:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:39:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:39:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:39:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:39:04 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:39:04 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:39:04 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system INFO: start Cleaning up error handling test: test_force_udisks2_crash INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 07:39:23 storageqe-109 journal: Oct 9 07:39:23 storageqe-109 INFO: start Cleaning up error handling test: test_force_udisks2_crash Oct 9 07:39:23 storageqe-109 journal: Oct 9 07:39:23 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 9 07:39:23 storageqe-109 journal: Oct 9 07:39:23 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop2 Oct 9 07:39:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:39:30 storageqe-109 kernel: loop2: Oct 9 07:39:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:39:55 storageqe-109 kernel: loop2: Oct 9 07:39:55 storageqe-109 kernel: loop2: Oct 9 07:40:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:40:20 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/error_test_force_crash.img) Oct 9 07:40:20 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 07:40:20 storageqe-109 kernel: blk_print_req_error: 9 callbacks suppressed Oct 9 07:40:20 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 07:40:21 storageqe-109 udisksd[2509680]: Error re-reading partition table (BLKRRPART ioctl) on /dev/loop2: Invalid argument Oct 9 07:40:21 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_force_udisks2_crash #### INFO: #### will start test_context_assignment_crash ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 07:40:25 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 07:40:25 storageqe-109 INFO: #### END test_force_udisks2_crash #### Oct 9 07:40:25 storageqe-109 INFO: #### will start test_context_assignment_crash ##### Oct 9 07:40:25 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 07:40:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:40:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:40:45 storageqe-109 kernel: loop2: detected capacity change from 0 to 2097152 Oct 9 07:40:45 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop2 (backed by /home/error_test_context_test_0.img) Oct 9 07:40:45 storageqe-109 kernel: loop2: Oct 9 07:40:45 storageqe-109 kernel: loop2: Oct 9 07:40:45 storageqe-109 kernel: loop2: Oct 9 07:41:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:41:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:41:10 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:41:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:41:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:41:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:41:36 storageqe-109 kernel: loop2: Oct 9 07:41:36 storageqe-109 kernel: loop2: Oct 9 07:42:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:42:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:42:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:42:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:43:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:43:17 storageqe-109 kernel: loop2: Oct 9 07:43:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:43:42 storageqe-109 kernel: loop2: Oct 9 07:43:42 storageqe-109 kernel: loop2: Oct 9 07:44:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:44:07 storageqe-109 kernel: loop2: Oct 9 07:44:07 storageqe-109 kernel: loop2: Oct 9 07:44:07 storageqe-109 kernel: loop2: Oct 9 07:44:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:44:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:44:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:44:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:44:32 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:44:32 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:44:32 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:44:32 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 07:44:32 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 07:44:32 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 07:44:32 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 07:44:32 storageqe-109 kernel: loop2: Oct 9 07:44:32 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/error_test_context_test_1.img) Oct 9 07:44:32 storageqe-109 kernel: loop2: Oct 9 07:44:32 storageqe-109 kernel: loop3: Oct 9 07:44:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:45:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:45:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:45:48 storageqe-109 kernel: loop4: detected capacity change from 0 to 2097152 Oct 9 07:45:48 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop4 (backed by /home/error_test_context_test_2.img) Oct 9 07:46:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:46:13 storageqe-109 kernel: loop2: Oct 9 07:46:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:46:38 storageqe-109 kernel: loop2: Oct 9 07:46:38 storageqe-109 kernel: loop2: Oct 9 07:46:38 storageqe-109 kernel: loop4: Oct 9 07:46:39 storageqe-109 kernel: loop2: Oct 9 07:47:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:47:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:47:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:47:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:47:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:47:29 storageqe-109 kernel: loop2: Oct 9 07:47:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:47:54 storageqe-109 kernel: loop2: Oct 9 07:47:54 storageqe-109 kernel: loop2: Oct 9 07:47:54 storageqe-109 kernel: loop2: Oct 9 07:48:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:48:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:48:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:48:20 storageqe-109 kernel: loop5: detected capacity change from 0 to 2097152 Oct 9 07:48:20 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop5 (backed by /home/error_test_context_test_3.img) Oct 9 07:48:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:48:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:49:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:49:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:49:10 storageqe-109 kernel: loop2: Oct 9 07:49:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:49:35 storageqe-109 kernel: loop2: Oct 9 07:49:35 storageqe-109 kernel: loop5: Oct 9 07:49:35 storageqe-109 kernel: loop2: Oct 9 07:50:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:29 storageqe-109 kernel: loop2: Oct 9 07:50:29 storageqe-109 kernel: loop2: Oct 9 07:50:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:50:55 storageqe-109 kernel: loop6: detected capacity change from 0 to 2097152 Oct 9 07:50:55 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop6 (backed by /home/error_test_context_test_4.img) Oct 9 07:50:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:51:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:51:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:51:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:51:23 storageqe-109 kernel: loop2: Oct 9 07:51:23 storageqe-109 kernel: loop6: Oct 9 07:51:23 storageqe-109 kernel: loop2: Oct 9 07:51:23 storageqe-109 kernel: loop2: Oct 9 07:51:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:51:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:51:48 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:51:49 storageqe-109 kernel: loop7: detected capacity change from 0 to 2097152 Oct 9 07:51:49 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop7 (backed by /home/error_test_context_test_5.img) Oct 9 07:51:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:51:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:52:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:52:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:52:38 storageqe-109 kernel: loop2: Oct 9 07:52:39 storageqe-109 kernel: loop2: Oct 9 07:52:39 storageqe-109 kernel: loop2: Oct 9 07:52:39 storageqe-109 kernel: loop2: Oct 9 07:52:39 storageqe-109 kernel: loop7: Oct 9 07:53:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:53:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:53:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:53:04 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:53:04 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:53:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:53:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:53:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:53:29 storageqe-109 kernel: loop2: Oct 9 07:53:29 storageqe-109 kernel: loop2: Oct 9 07:53:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:53:55 storageqe-109 kernel: loop8: detected capacity change from 0 to 2097152 Oct 9 07:53:55 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop8 (backed by /home/error_test_context_test_6.img) Oct 9 07:54:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:54:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:54:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:54:45 storageqe-109 kernel: loop2: Oct 9 07:54:45 storageqe-109 kernel: loop2: Oct 9 07:54:45 storageqe-109 kernel: loop2: Oct 9 07:54:45 storageqe-109 kernel: loop8: Oct 9 07:55:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:55:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:55:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:55:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:55:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:56:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:56:02 storageqe-109 kernel: loop2: Oct 9 07:56:02 storageqe-109 kernel: loop2: Oct 9 07:56:02 storageqe-109 kernel: loop2: Oct 9 07:56:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:56:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:56:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:56:29 storageqe-109 kernel: loop9: detected capacity change from 0 to 2097152 Oct 9 07:56:29 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop9 (backed by /home/error_test_context_test_7.img) Oct 9 07:56:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:56:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:57:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:57:17 storageqe-109 kernel: loop2: Oct 9 07:57:17 storageqe-109 kernel: loop9: Oct 9 07:57:17 storageqe-109 kernel: loop2: Oct 9 07:57:17 storageqe-109 kernel: loop2: Oct 9 07:57:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:57:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:57:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:57:42 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:57:43 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:57:43 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 07:58:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:58:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:58:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:59:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:59:24 storageqe-109 kernel: loop2: Oct 9 07:59:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:59:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 07:59:49 storageqe-109 kernel: loop2: Oct 9 07:59:49 storageqe-109 kernel: loop10: detected capacity change from 0 to 2097152 Oct 9 07:59:49 storageqe-109 kernel: loop2: Oct 9 07:59:49 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop10 (backed by /home/error_test_context_test_8.img) Oct 9 08:00:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:00:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:00:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:00:40 storageqe-109 kernel: loop2: Oct 9 08:01:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:01:05 storageqe-109 kernel: loop2: Oct 9 08:01:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:01:30 storageqe-109 kernel: loop2: Oct 9 08:01:30 storageqe-109 kernel: loop2: Oct 9 08:01:30 storageqe-109 kernel: loop2: Oct 9 08:01:30 storageqe-109 kernel: loop10: Oct 9 08:01:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:01:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:01:56 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:01:56 storageqe-109 kernel: loop11: detected capacity change from 0 to 2097152 Oct 9 08:01:56 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop11 (backed by /home/error_test_context_test_9.img) Oct 9 08:01:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:02:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:02:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:02:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:02:46 storageqe-109 kernel: loop2: Oct 9 08:02:46 storageqe-109 kernel: loop2: Oct 9 08:02:46 storageqe-109 kernel: loop2: Oct 9 08:02:46 storageqe-109 kernel: loop2: Oct 9 08:02:46 storageqe-109 kernel: loop11: Oct 9 08:03:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:03:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:03:12 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:03:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:03:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:03:37 storageqe-109 kernel: loop12: detected capacity change from 0 to 2097152 Oct 9 08:03:37 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop12 (backed by /home/error_test_context_test_10.img) Oct 9 08:04:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:04:02 storageqe-109 kernel: loop2: Oct 9 08:04:02 storageqe-109 kernel: loop2: Oct 9 08:04:02 storageqe-109 kernel: loop12: Oct 9 08:04:02 storageqe-109 kernel: loop2: Oct 9 08:04:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:04:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:04:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:04:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:04:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:04:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:04:54 storageqe-109 kernel: loop2: Oct 9 08:04:54 storageqe-109 kernel: loop2: Oct 9 08:04:54 storageqe-109 kernel: loop2: Oct 9 08:04:55 storageqe-109 kernel: loop13: detected capacity change from 0 to 2097152 Oct 9 08:04:55 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop13 (backed by /home/error_test_context_test_11.img) Oct 9 08:05:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:05:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:05:19 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:05:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:05:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:05:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:05:47 storageqe-109 kernel: loop2: Oct 9 08:05:47 storageqe-109 kernel: loop2: Oct 9 08:05:47 storageqe-109 kernel: loop13: Oct 9 08:05:47 storageqe-109 kernel: loop2: Oct 9 08:05:49 storageqe-109 kernel: loop14: detected capacity change from 0 to 2097152 Oct 9 08:05:49 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop14 (backed by /home/error_test_context_test_12.img) Oct 9 08:06:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:06:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:06:13 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:06:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:06:14 storageqe-109 kernel: loop14: Oct 9 08:06:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:06:39 storageqe-109 kernel: loop2: Oct 9 08:07:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:07:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:07:06 storageqe-109 kernel: loop15: detected capacity change from 0 to 2097152 Oct 9 08:07:06 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop15 (backed by /home/error_test_context_test_13.img) Oct 9 08:07:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:07:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:07:30 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:07:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:07:55 storageqe-109 kernel: loop2: Oct 9 08:08:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:08:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:08:46 storageqe-109 kernel: loop2: Oct 9 08:08:46 storageqe-109 kernel: loop15: Oct 9 08:09:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:09:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:09:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:10:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:10:01 storageqe-109 kernel: loop2: Oct 9 08:10:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:10:27 storageqe-109 kernel: loop2: Oct 9 08:10:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:11:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:11:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:11:19 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:11:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:11:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:11:44 storageqe-109 kernel: loop2: Oct 9 08:11:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:11:44 storageqe-109 kernel: loop2: Oct 9 08:12:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:12:09 storageqe-109 kernel: loop16: detected capacity change from 0 to 2097152 Oct 9 08:12:09 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop16 (backed by /home/error_test_context_test_14.img) Oct 9 08:12:34 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:12:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:12:59 storageqe-109 kernel: loop2: Oct 9 08:12:59 storageqe-109 kernel: loop16: Oct 9 08:13:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:13:24 storageqe-109 kernel: loop2: Oct 9 08:13:25 storageqe-109 kernel: loop2: Oct 9 08:13:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:13:49 storageqe-109 kernel: loop2: Oct 9 08:14:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:14:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:14:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:14:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:14:41 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:15:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:15:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:15:07 storageqe-109 kernel: loop2: Oct 9 08:15:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:15:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:15:32 storageqe-109 kernel: loop2: Oct 9 08:15:32 storageqe-109 kernel: loop2: Oct 9 08:15:33 storageqe-109 kernel: loop17: detected capacity change from 0 to 2097152 Oct 9 08:15:33 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop17 (backed by /home/error_test_context_test_15.img) Oct 9 08:15:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:15:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:16:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:16:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:16:47 storageqe-109 kernel: loop2: Oct 9 08:16:47 storageqe-109 kernel: loop2: Oct 9 08:16:47 storageqe-109 kernel: loop2: Oct 9 08:16:47 storageqe-109 kernel: loop17: Oct 9 08:17:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:17:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:17:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:17:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:17:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:17:38 storageqe-109 kernel: loop2: Oct 9 08:18:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:18:03 storageqe-109 kernel: loop2: Oct 9 08:18:03 storageqe-109 kernel: loop18: detected capacity change from 0 to 2097152 Oct 9 08:18:03 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop18 (backed by /home/error_test_context_test_16.img) Oct 9 08:18:03 storageqe-109 kernel: loop2: Oct 9 08:18:06 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 08:18:06 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 08:18:06 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 08:18:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:18:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:18:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:18:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:18:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:18:59 storageqe-109 kernel: loop2: Oct 9 08:18:59 storageqe-109 kernel: loop2: Oct 9 08:18:59 storageqe-109 kernel: loop18: Oct 9 08:19:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:19:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:19:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:19:50 storageqe-109 kernel: loop2: Oct 9 08:19:50 storageqe-109 kernel: loop2: Oct 9 08:20:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:20:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:20:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:21:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:21:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:21:31 storageqe-109 kernel: loop2: Oct 9 08:21:31 storageqe-109 kernel: loop19: detected capacity change from 0 to 2097152 Oct 9 08:21:31 storageqe-109 kernel: loop2: Oct 9 08:21:31 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop19 (backed by /home/error_test_context_test_17.img) Oct 9 08:21:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:21:56 storageqe-109 kernel: loop2: Oct 9 08:22:21 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:22:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:22:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:22:24 storageqe-109 kernel: loop19: Oct 9 08:22:25 storageqe-109 kernel: loop2: Oct 9 08:22:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:22:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:22:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:23:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:23:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:23:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:23:40 storageqe-109 kernel: loop2: Oct 9 08:23:40 storageqe-109 kernel: loop2: Oct 9 08:23:40 storageqe-109 kernel: loop2: Oct 9 08:23:40 storageqe-109 kernel: loop2: Oct 9 08:24:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:24:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:24:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:24:06 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:24:06 storageqe-109 kernel: loop20: detected capacity change from 0 to 2097152 Oct 9 08:24:06 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop20 (backed by /home/error_test_context_test_18.img) Oct 9 08:24:06 storageqe-109 kernel: loop2: Oct 9 08:24:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:24:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:24:32 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:24:32 storageqe-109 kernel: loop20: Oct 9 08:24:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:25:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:25:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:25:23 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:25:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:25:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:25:49 storageqe-109 kernel: loop2: Oct 9 08:26:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:26:14 storageqe-109 kernel: loop2: Oct 9 08:26:14 storageqe-109 kernel: loop2: Oct 9 08:26:14 storageqe-109 kernel: loop2: Oct 9 08:26:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:26:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:26:39 storageqe-109 kernel: loop21: detected capacity change from 0 to 2097152 Oct 9 08:26:39 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop21 (backed by /home/error_test_context_test_19.img) Oct 9 08:27:04 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:27:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:27:29 storageqe-109 kernel: loop2: Oct 9 08:27:29 storageqe-109 kernel: loop21: Oct 9 08:27:29 storageqe-109 kernel: loop2: Oct 9 08:27:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:27:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:27:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:28:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:28:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:28:20 storageqe-109 kernel: loop2: Oct 9 08:28:20 storageqe-109 kernel: loop2: Oct 9 08:28:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:28:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:28:46 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:28:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:29:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:29:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:29:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:29:36 storageqe-109 kernel: loop2: Oct 9 08:29:37 storageqe-109 kernel: loop2: Oct 9 08:29:37 storageqe-109 kernel: loop2: Oct 9 08:29:37 storageqe-109 kernel: loop14: Oct 9 08:29:37 storageqe-109 kernel: loop2: Oct 9 08:29:37 storageqe-109 kernel: loop2: Oct 9 08:29:37 storageqe-109 kernel: loop8: Oct 9 08:29:37 storageqe-109 kernel: loop2: Oct 9 08:30:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:02 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:30:02 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:30:02 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:30:02 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:30:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:27 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:30:52 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop21 (was backed by /home/error_test_context_test_19.img) Oct 9 08:30:52 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop21 Oct 9 08:30:52 storageqe-109 kernel: loop9: Oct 9 08:30:52 storageqe-109 kernel: loop3: Oct 9 08:30:52 storageqe-109 kernel: loop2: Oct 9 08:30:52 storageqe-109 kernel: loop2: Oct 9 08:30:52 storageqe-109 kernel: loop2: Oct 9 08:31:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:31:17 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop20 (was backed by /home/error_test_context_test_18.img) Oct 9 08:31:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop20 Oct 9 08:31:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:31:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:31:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:31:17 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:31:18 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:31:18 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:31:18 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:31:18 storageqe-109 kernel: loop4: Oct 9 08:31:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:31:43 storageqe-109 kernel: loop2: Oct 9 08:32:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:32:08 storageqe-109 kernel: loop2: Oct 9 08:32:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:32:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:32:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop19 (was backed by /home/error_test_context_test_17.img) Oct 9 08:32:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop19 Oct 9 08:32:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:32:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:32:58 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:33:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:33:23 storageqe-109 kernel: loop2: Oct 9 08:33:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:33:48 storageqe-109 kernel: loop2: Oct 9 08:33:48 storageqe-109 kernel: loop10: Oct 9 08:33:48 storageqe-109 kernel: loop2: Oct 9 08:33:48 storageqe-109 kernel: loop2: Oct 9 08:33:48 storageqe-109 kernel: loop2: Oct 9 08:34:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:34:13 storageqe-109 kernel: loop2: Oct 9 08:34:13 storageqe-109 kernel: loop2: Oct 9 08:34:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:34:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:34:38 storageqe-109 udisksd[2509680]: [fdisk] Start sector 2048 out of range. Oct 9 08:34:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:34:38 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop18 (was backed by /home/error_test_context_test_16.img) Oct 9 08:34:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:34:38 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop18 Oct 9 08:34:38 storageqe-109 kernel: loop15: Oct 9 08:35:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:35:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:35:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop17 (was backed by /home/error_test_context_test_15.img) Oct 9 08:35:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop17 Oct 9 08:35:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:35:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:35:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:35:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:35:29 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:35:29 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:35:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:36:20 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:36:20 storageqe-109 kernel: loop5: Oct 9 08:36:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:36:45 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:36:45 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop16 (was backed by /home/error_test_context_test_14.img) Oct 9 08:36:45 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop16 Oct 9 08:36:45 storageqe-109 kernel: loop2: Oct 9 08:36:45 storageqe-109 kernel: I/O error, dev loop16, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:36:45 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop16': Invalid argument Oct 9 08:37:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:37:10 storageqe-109 kernel: loop2: Oct 9 08:37:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:37:35 storageqe-109 kernel: loop2: Oct 9 08:38:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:38:00 storageqe-109 kernel: loop2: Oct 9 08:38:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:38:25 storageqe-109 kernel: loop2: Oct 9 08:38:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:38:51 storageqe-109 kernel: I/O error, dev loop17, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:38:51 storageqe-109 kernel: loop2: Oct 9 08:38:51 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop17': Invalid argument Oct 9 08:38:51 storageqe-109 kernel: loop11: Oct 9 08:39:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:39:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:39:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:39:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:39:16 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop15 (was backed by /home/error_test_context_test_13.img) Oct 9 08:39:16 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop15 Oct 9 08:39:16 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:39:19 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:39:19 storageqe-109 kernel: I/O error, dev loop18, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:39:19 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop18': Invalid argument Oct 9 08:39:19 storageqe-109 kernel: loop2: Oct 9 08:39:19 storageqe-109 kernel: I/O error, dev loop19, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:39:19 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop19': Invalid argument Oct 9 08:39:19 storageqe-109 kernel: loop2: Oct 9 08:39:19 storageqe-109 kernel: loop2: Oct 9 08:39:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:39:41 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop14 (was backed by /home/error_test_context_test_12.img) Oct 9 08:39:41 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop14 Oct 9 08:39:41 storageqe-109 kernel: loop12: Oct 9 08:40:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:07 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:40:07 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:40:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:32 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:32 storageqe-109 kernel: loop2: Oct 9 08:40:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:57 storageqe-109 kernel: loop2: Oct 9 08:40:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:40:57 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop13 (was backed by /home/error_test_context_test_11.img) Oct 9 08:40:57 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop13 Oct 9 08:40:57 storageqe-109 kernel: I/O error, dev loop20, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:40:57 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop20': Invalid argument Oct 9 08:40:57 storageqe-109 kernel: I/O error, dev loop13, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:40:57 storageqe-109 kernel: loop6: Oct 9 08:40:57 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop13': Invalid argument Oct 9 08:40:57 storageqe-109 kernel: loop2: Oct 9 08:40:57 storageqe-109 kernel: loop2: Oct 9 08:41:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:41:22 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop12 (was backed by /home/error_test_context_test_10.img) Oct 9 08:41:22 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop12 Oct 9 08:41:22 storageqe-109 kernel: I/O error, dev loop21, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:41:22 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop21': Invalid argument Oct 9 08:41:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:41:47 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop11 (was backed by /home/error_test_context_test_9.img) Oct 9 08:41:47 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop11 Oct 9 08:41:47 storageqe-109 kernel: loop2: Oct 9 08:41:47 storageqe-109 kernel: loop2: Oct 9 08:41:47 storageqe-109 kernel: loop2: Oct 9 08:41:47 storageqe-109 kernel: loop2: Oct 9 08:41:47 storageqe-109 kernel: loop7: Oct 9 08:42:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:42:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:42:12 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop10 (was backed by /home/error_test_context_test_8.img) Oct 9 08:42:12 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop10 Oct 9 08:42:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:42:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:42:13 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:42:13 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:42:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:42:38 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:42:38 storageqe-109 kernel: loop2: Oct 9 08:42:38 storageqe-109 kernel: loop2: Oct 9 08:43:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:43:03 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop9 (was backed by /home/error_test_context_test_7.img) Oct 9 08:43:03 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop9 Oct 9 08:43:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:43:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:43:28 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:43:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:44:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:44:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:44:18 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop8 (was backed by /home/error_test_context_test_6.img) Oct 9 08:44:18 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop8 Oct 9 08:44:18 storageqe-109 kernel: loop2: Oct 9 08:44:18 storageqe-109 kernel: loop2: Oct 9 08:44:19 storageqe-109 kernel: loop2: Oct 9 08:44:43 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:44:43 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop7 (was backed by /home/error_test_context_test_5.img) Oct 9 08:44:43 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop7 Oct 9 08:44:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:33 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:33 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop6 (was backed by /home/error_test_context_test_4.img) Oct 9 08:45:33 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop6 Oct 9 08:45:33 storageqe-109 kernel: loop2: Oct 9 08:45:34 storageqe-109 kernel: loop2: Oct 9 08:45:34 storageqe-109 kernel: loop2: Oct 9 08:45:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:45:59 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop5 (was backed by /home/error_test_context_test_3.img) Oct 9 08:45:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop5 Oct 9 08:45:59 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:46:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:46:24 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:46:24 storageqe-109 kernel: loop2: Oct 9 08:46:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:46:49 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop4 (was backed by /home/error_test_context_test_2.img) Oct 9 08:46:49 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop4 Oct 9 08:47:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:47:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:47:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:47:39 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:47:40 storageqe-109 udisksd[2509680]: [fdisk] Failed to add partition 1 to system Oct 9 08:47:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:47:41 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/error_test_context_test_1.img) Oct 9 08:47:41 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 08:48:05 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:48:05 storageqe-109 kernel: loop2: Oct 9 08:48:05 storageqe-109 kernel: loop2: Oct 9 08:48:30 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:48:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: start Cleaning up error handling test: test_context_assignment_crash INFO: start Cleaning _cleanup_automounts Oct 9 08:48:57 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:48:57 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop2 (was backed by /home/error_test_context_test_0.img) Oct 9 08:48:57 storageqe-109 journal: Oct 9 08:48:57 storageqe-109 INFO: start Cleaning up error handling test: test_context_assignment_crash Oct 9 08:48:58 storageqe-109 journal: Oct 9 08:48:58 storageqe-109 INFO: start Cleaning _cleanup_automounts INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_context_assignment_crash #### INFO: #### will start test_dbus_method_abuse_crash ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:49:03 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:49:03 storageqe-109 INFO: #### END test_context_assignment_crash #### Oct 9 08:49:03 storageqe-109 INFO: #### will start test_dbus_method_abuse_crash ##### Oct 9 08:49:03 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:49:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:49:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:49:22 storageqe-109 kernel: loop3: detected capacity change from 0 to 2097152 Oct 9 08:49:22 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop3 (backed by /home/error_test_dbus_abuse.img) Oct 9 08:49:22 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop2 Oct 9 08:49:47 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument INFO: start Cleaning up error handling test: test_dbus_method_abuse_crash INFO: start Cleaning _cleanup_automounts INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop3 Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:12 storageqe-109 journal: Oct 9 08:50:12 storageqe-109 INFO: start Cleaning up error handling test: test_dbus_method_abuse_crash Oct 9 08:50:12 storageqe-109 journal: Oct 9 08:50:12 storageqe-109 INFO: start Cleaning _cleanup_automounts Oct 9 08:50:12 storageqe-109 journal: Oct 9 08:50:12 storageqe-109 INFO: start Cleaning _cleanup_loop_partitions /org/freedesktop/UDisks2/block_devices/loop3 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop3 (was backed by /home/error_test_dbus_abuse.img) Oct 9 08:50:37 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop3 Oct 9 08:50:37 storageqe-109 kernel: blk_print_req_error: 172 callbacks suppressed Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 kernel: I/O error, dev loop2, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:37 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument Oct 9 08:50:38 storageqe-109 udisksd[2509680]: Failed to assign the new context to disk '/dev/loop2': Invalid argument INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_dbus_method_abuse_crash #### INFO: #### will start test_iscsi_session_properties ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:50:42 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:50:42 storageqe-109 INFO: #### END test_dbus_method_abuse_crash #### Oct 9 08:50:42 storageqe-109 INFO: #### will start test_iscsi_session_properties ##### Oct 9 08:50:42 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 08:50:47 storageqe-109 INFO: Setting up local iSCSI target... Oct 9 08:50:47 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 9 08:50:47 storageqe-109 INFO: Creating test disk files... Oct 9 08:50:47 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 9 08:50:48 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 08:50:48 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 9 08:50:48 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 9 08:50:48 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 9 08:50:48 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 9 08:50:48 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 9 08:50:48 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 08:50:51 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 08:50:51 storageqe-109 kernel: dev[0000000082e6e329]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:50:51 storageqe-109 kernel: dev[00000000a15741cd]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:50:51 storageqe-109 kernel: dev[00000000c79b6287]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:50:51 storageqe-109 kernel: dev[00000000ac489793]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:50:51 storageqe-109 kernel: dev[00000000016047eb]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:50:51 storageqe-109 kernel: dev[00000000cf36992a]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:50:51 storageqe-109 kernel: dev[00000000894ab07f]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:50:51 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 9 08:50:51 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:50:51 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:50:51 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 9 08:50:51 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 9 08:50:51 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:50:51 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 9 08:50:51 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 9 08:50:51 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 9 08:50:51 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:50:51 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 9 08:50:51 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:50:51 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 9 08:50:51 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 9 08:50:51 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:50:51 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 9 08:50:51 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 9 08:50:51 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 9 08:50:51 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:50:51 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 9 08:50:51 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:50:51 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 9 08:50:51 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 9 08:50:51 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:50:51 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 9 08:50:51 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 9 08:50:51 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 9 08:50:51 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:50:51 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:50:51 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 9 08:50:51 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 9 08:50:51 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 9 08:50:51 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 9 08:50:51 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:50:51 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 9 08:50:51 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 9 08:50:51 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 9 08:50:51 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:50:51 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk Oct 9 08:50:51 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 9 08:50:51 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 9 08:51:01 storageqe-109 INFO: Verifying iSCSI target setup... Oct 9 08:51:01 storageqe-109 INFO: Found 4 LIO target(s) Oct 9 08:51:01 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 9 08:51:01 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 08:51:01 storageqe-109 iscsid[2541166]: iscsid shutting down. Oct 9 08:51:01 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 08:51:01 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 08:51:01 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 08:51:01 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 08:51:01 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 08:51:01 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 08:51:01 storageqe-109 iscsid[2562187]: iscsid: Connection14:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 9 08:51:01 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:01 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 9 08:51:01 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 9 08:51:01 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 9 08:51:01 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:01 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 9 08:51:01 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:01 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 9 08:51:01 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 9 08:51:01 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:01 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk Oct 9 08:51:01 storageqe-109 INFO: Fetching all properties for ISCSI.Session interface... INFO: Fetching all properties for ISCSI.Session interface... INFO: Checking property 'target_name'... INFO: Checking property 'tpgt'... INFO: Checking property 'address'... INFO: Checking property 'port'... INFO: Checking property 'persistent_address'... INFO: Checking property 'persistent_port'... INFO: Checking property 'abort_timeout'... INFO: Checking property 'lu_reset_timeout'... INFO: Checking property 'recovery_timeout'... INFO: Checking property 'tgt_reset_timeout'... INFO: Checking specific property values... INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 9 08:51:01 storageqe-109 INFO: Checking property 'target_name'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'tpgt'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'address'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'port'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'persistent_address'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'persistent_port'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'abort_timeout'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'lu_reset_timeout'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'recovery_timeout'... Oct 9 08:51:02 storageqe-109 INFO: Checking property 'tgt_reset_timeout'... Oct 9 08:51:02 storageqe-109 INFO: Checking specific property values... Oct 9 08:51:02 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 9 08:51:02 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 9 08:51:02 storageqe-109 iscsid[2562187]: iscsid: Connection14:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. Oct 9 08:51:02 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 9 08:51:02 storageqe-109 INFO: Clearing targetcli configuration... Oct 9 08:51:02 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 9 08:51:02 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 9 08:51:02 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 9 08:51:02 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 9 08:51:02 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 9 08:51:02 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 9 08:51:02 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 9 08:51:02 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached Oct 9 08:51:02 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 9 08:51:02 storageqe-109 INFO: Removing test disk files... Oct 9 08:51:02 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 9 08:51:02 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 9 08:51:02 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 9 08:51:02 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 9 08:51:02 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 9 08:51:02 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 9 08:51:02 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 9 08:51:02 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_iscsi_session_properties #### INFO: #### will start test_iscsi_session_logout_methods ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:51:07 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:51:08 storageqe-109 INFO: #### END test_iscsi_session_properties #### Oct 9 08:51:08 storageqe-109 INFO: #### will start test_iscsi_session_logout_methods ##### Oct 9 08:51:08 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 08:51:13 storageqe-109 INFO: Setting up local iSCSI target... Oct 9 08:51:13 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 9 08:51:13 storageqe-109 INFO: Creating test disk files... Oct 9 08:51:13 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 9 08:51:13 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 08:51:13 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 9 08:51:13 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 9 08:51:13 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 9 08:51:13 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 9 08:51:13 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 9 08:51:14 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 08:51:16 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 08:51:16 storageqe-109 kernel: dev[000000000b1d2e11]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:16 storageqe-109 kernel: dev[000000008f1217eb]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:16 storageqe-109 kernel: dev[00000000ee548f3a]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:16 storageqe-109 kernel: dev[000000009e2355a6]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:16 storageqe-109 kernel: dev[0000000076dec2f0]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:16 storageqe-109 kernel: dev[0000000082e6e329]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:16 storageqe-109 kernel: dev[00000000a15741cd]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:16 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 9 08:51:16 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:16 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:16 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 9 08:51:16 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 9 08:51:16 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:16 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 9 08:51:16 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 9 08:51:16 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 9 08:51:16 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 9 08:51:16 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:16 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:16 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 9 08:51:16 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:16 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 9 08:51:16 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 9 08:51:16 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 9 08:51:16 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 9 08:51:16 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:16 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:16 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 9 08:51:16 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 9 08:51:16 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 9 08:51:16 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:16 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 9 08:51:16 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 9 08:51:16 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 9 08:51:16 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:16 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:16 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 9 08:51:16 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:16 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 9 08:51:16 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 9 08:51:16 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 9 08:51:16 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 9 08:51:16 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 9 08:51:16 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:16 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 9 08:51:16 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 9 08:51:26 storageqe-109 INFO: Verifying iSCSI target setup... Oct 9 08:51:26 storageqe-109 INFO: Found 4 LIO target(s) Oct 9 08:51:26 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 9 08:51:26 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 08:51:26 storageqe-109 iscsid[2562187]: iscsid shutting down. Oct 9 08:51:26 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 08:51:26 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 08:51:26 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 08:51:26 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 08:51:26 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 08:51:26 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 08:51:26 storageqe-109 iscsid[2562490]: iscsid: Connection15:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 9 08:51:26 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:26 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 9 08:51:26 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 9 08:51:26 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 9 08:51:26 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:26 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 9 08:51:26 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:26 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:26 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 9 08:51:26 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 9 08:51:26 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:26 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk INFO: Testing Logout() method... Oct 9 08:51:27 storageqe-109 INFO: Testing Logout() method... Oct 9 08:51:27 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 9 08:51:27 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 9 08:51:27 storageqe-109 iscsid[2562490]: iscsid: Connection15:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 9 08:51:30 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 9 08:51:30 storageqe-109 INFO: Clearing targetcli configuration... Oct 9 08:51:30 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 9 08:51:30 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 9 08:51:30 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 9 08:51:30 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 9 08:51:30 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 9 08:51:30 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 9 08:51:30 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 9 08:51:30 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed INFO: Setting up local iSCSI target... INFO: Found target configuration file: targetcli_config.json INFO: Creating test disk files... INFO: Creating test disk: /home/udisks_test_disk1 INFO: Creating test disk: /home/udisks_test_disk2 Oct 9 08:51:30 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 9 08:51:30 storageqe-109 INFO: Removing test disk files... Oct 9 08:51:30 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 9 08:51:30 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 9 08:51:30 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 9 08:51:30 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 9 08:51:30 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 9 08:51:30 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 9 08:51:30 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 9 08:51:30 storageqe-109 INFO: Local iSCSI target cleanup completed Oct 9 08:51:30 storageqe-109 INFO: Setting up local iSCSI target... Oct 9 08:51:30 storageqe-109 INFO: Found target configuration file: targetcli_config.json Oct 9 08:51:30 storageqe-109 INFO: Creating test disk files... Oct 9 08:51:30 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk1 Oct 9 08:51:31 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk2 INFO: Creating test disk: /home/udisks_test_disk3 INFO: Creating test disk: /home/udisks_test_disk4 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 Oct 9 08:51:31 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk3 Oct 9 08:51:31 storageqe-109 INFO: Creating test disk: /home/udisks_test_disk4 Oct 9 08:51:31 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi1 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 INFO: Clearing existing targetcli configuration... Oct 9 08:51:31 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi2 Oct 9 08:51:31 storageqe-109 INFO: Creating iSCSI test disk: /home/udisks_test_disk_iscsi3 Oct 9 08:51:31 storageqe-109 INFO: Clearing existing targetcli configuration... INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 08:51:34 storageqe-109 INFO: Restoring targetcli configuration from targetcli_config.json Oct 9 08:51:34 storageqe-109 kernel: dev[00000000aab85186]: Backstore name 'udisks_test_disk4' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:34 storageqe-109 kernel: dev[0000000056b2b8e2]: Backstore name 'udisks_test_disk3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:34 storageqe-109 kernel: dev[00000000dd8698a8]: Backstore name 'udisks_test_disk2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:34 storageqe-109 kernel: dev[00000000c688ea06]: Backstore name 'udisks_test_disk1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:34 storageqe-109 kernel: dev[00000000b23ca8f1]: Backstore name 'udisks_test_iscsi1' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:34 storageqe-109 kernel: dev[00000000c31320a7]: Backstore name 'udisks_test_iscsi2' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:34 storageqe-109 kernel: dev[000000005422450a]: Backstore name 'udisks_test_iscsi3' is too long for INQUIRY_MODEL, truncating to 15 characters Oct 9 08:51:34 storageqe-109 kernel: scsi host9: TCM_Loopback Oct 9 08:51:34 storageqe-109 kernel: scsi 9:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:34 storageqe-109 kernel: scsi 9:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:34 storageqe-109 kernel: scsi 9:0:1:0: alua: device naa.600140565541bbc0ffc42cbb6396ce91 port group 0 rel port 0 Oct 9 08:51:34 storageqe-109 kernel: sd 9:0:1:0: Attached scsi generic sg5 type 0 Oct 9 08:51:34 storageqe-109 kernel: sd 9:0:1:0: [sdf] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:34 storageqe-109 kernel: scsi host10: TCM_Loopback Oct 9 08:51:34 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write Protect is off Oct 9 08:51:34 storageqe-109 kernel: sd 9:0:1:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: sd 9:0:1:0: [sdf] Preferred minimum I/O size 512 bytes Oct 9 08:51:34 storageqe-109 kernel: scsi 10:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:34 storageqe-109 kernel: sd 9:0:1:0: [sdf] Optimal transfer size 1048576 bytes Oct 9 08:51:34 storageqe-109 kernel: scsi 10:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:34 storageqe-109 kernel: scsi 10:0:1:0: alua: device naa.60014055282611e2e7440198ca5d8ceb port group 0 rel port 0 Oct 9 08:51:34 storageqe-109 kernel: sd 10:0:1:0: Attached scsi generic sg6 type 0 Oct 9 08:51:34 storageqe-109 kernel: sd 10:0:1:0: [sdg] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:34 storageqe-109 kernel: scsi host11: TCM_Loopback Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write Protect is off Oct 9 08:51:34 storageqe-109 kernel: sd 10:0:1:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: sd 9:0:1:0: [sdf] Attached SCSI disk Oct 9 08:51:34 storageqe-109 kernel: sd 10:0:1:0: [sdg] Preferred minimum I/O size 512 bytes Oct 9 08:51:34 storageqe-109 kernel: scsi 11:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:34 storageqe-109 kernel: sd 10:0:1:0: [sdg] Optimal transfer size 1048576 bytes Oct 9 08:51:34 storageqe-109 kernel: scsi 11:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: scsi 11:0:1:0: alua: device naa.6001405dd927109b9e7462cb95aae787 port group 0 rel port 0 Oct 9 08:51:34 storageqe-109 kernel: sd 11:0:1:0: Attached scsi generic sg7 type 0 Oct 9 08:51:34 storageqe-109 kernel: sd 11:0:1:0: [sdh] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:34 storageqe-109 kernel: scsi host12: TCM_Loopback Oct 9 08:51:34 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write Protect is off Oct 9 08:51:34 storageqe-109 kernel: sd 11:0:1:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: sd 11:0:1:0: [sdh] Preferred minimum I/O size 512 bytes Oct 9 08:51:34 storageqe-109 kernel: sd 10:0:1:0: [sdg] Attached SCSI disk Oct 9 08:51:34 storageqe-109 kernel: sd 11:0:1:0: [sdh] Optimal transfer size 1048576 bytes Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: scsi 12:0:1:0: Direct-Access LIO-ORG udisks_test_dis 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:34 storageqe-109 kernel: scsi 12:0:1:0: alua: supports implicit and explicit TPGS Oct 9 08:51:34 storageqe-109 kernel: scsi 12:0:1:0: alua: device naa.60014050604a813ce7945faa9ffeaf82 port group 0 rel port 0 Oct 9 08:51:34 storageqe-109 kernel: sd 11:0:1:0: [sdh] Attached SCSI disk Oct 9 08:51:34 storageqe-109 kernel: sd 12:0:1:0: Attached scsi generic sg8 type 0 Oct 9 08:51:34 storageqe-109 kernel: sd 12:0:1:0: [sdi] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:34 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write Protect is off Oct 9 08:51:34 storageqe-109 kernel: sd 12:0:1:0: [sdi] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: sd 12:0:1:0: [sdi] Preferred minimum I/O size 512 bytes Oct 9 08:51:34 storageqe-109 kernel: sd 12:0:1:0: [sdi] Optimal transfer size 1048576 bytes Oct 9 08:51:34 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:34 storageqe-109 kernel: sd 12:0:1:0: [sdi] Attached SCSI disk INFO: Waiting for targetcli configuration to take effect... Oct 9 08:51:34 storageqe-109 INFO: Waiting for targetcli configuration to take effect... INFO: Verifying iSCSI target setup... INFO: Found 4 LIO target(s) INFO: Local iSCSI target setup completed successfully Oct 9 08:51:44 storageqe-109 INFO: Verifying iSCSI target setup... Oct 9 08:51:44 storageqe-109 INFO: Found 4 LIO target(s) Oct 9 08:51:44 storageqe-109 INFO: Local iSCSI target setup completed successfully Oct 9 08:51:44 storageqe-109 systemd[1]: Stopping iscsid.service - Open-iSCSI... Oct 9 08:51:44 storageqe-109 iscsid[2562490]: iscsid shutting down. Oct 9 08:51:44 storageqe-109 systemd[1]: iscsid.service: Deactivated successfully. Oct 9 08:51:44 storageqe-109 systemd[1]: Stopped iscsid.service - Open-iSCSI. Oct 9 08:51:44 storageqe-109 systemd[1]: iscsi-init.service - One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). Oct 9 08:51:44 storageqe-109 systemd[1]: Starting iscsid.service - Open-iSCSI... Oct 9 08:51:44 storageqe-109 systemd[1]: Started iscsid.service - Open-iSCSI. Oct 9 08:51:44 storageqe-109 kernel: scsi host13: iSCSI Initiator over TCP/IP Oct 9 08:51:44 storageqe-109 iscsid[2562719]: iscsid: Connection16:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is operational now Oct 9 08:51:44 storageqe-109 kernel: scsi 13:0:0:0: Direct-Access LIO-ORG udisks_test_isc 4.0 PQ: 0 ANSI: 6 Oct 9 08:51:44 storageqe-109 kernel: scsi 13:0:0:0: alua: supports implicit and explicit TPGS Oct 9 08:51:44 storageqe-109 kernel: scsi 13:0:0:0: alua: device naa.6001405ee5473b793ce400281412ef99 port group 0 rel port 1 Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: Attached scsi generic sg9 type 0 Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: [sdj] 1024000 512-byte logical blocks: (524 MB/500 MiB) Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write Protect is off Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA Oct 9 08:51:44 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: [sdj] Preferred minimum I/O size 512 bytes Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: [sdj] Optimal transfer size 1048576 bytes Oct 9 08:51:44 storageqe-109 kernel: MODE SENSE: unimplemented page/subpage: 0x0a/0x05 Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: [sdj] Attached SCSI disk Oct 9 08:51:44 storageqe-109 INFO: Testing LogoutInterface() method... INFO: Testing LogoutInterface() method... Oct 9 08:51:44 storageqe-109 kernel: sd 13:0:0:0: [sdj] Synchronizing SCSI cache Oct 9 08:51:44 storageqe-109 kernel: scsi 13:0:0:0: alua: Detached Oct 9 08:51:44 storageqe-109 iscsid[2562719]: iscsid: Connection16:0 to [target: iqn.2003-01.udisks.test:iscsi-test-noauth, portal: 127.0.0.1,3260] through [iface: default] is shutdown. INFO: Cleaning up local iSCSI target... INFO: Clearing targetcli configuration... Oct 9 08:51:48 storageqe-109 INFO: Cleaning up local iSCSI target... Oct 9 08:51:48 storageqe-109 INFO: Clearing targetcli configuration... Oct 9 08:51:48 storageqe-109 kernel: sd 12:0:1:0: [sdi] Synchronizing SCSI cache Oct 9 08:51:48 storageqe-109 kernel: scsi 12:0:1:0: alua: Detached Oct 9 08:51:48 storageqe-109 kernel: sd 11:0:1:0: [sdh] Synchronizing SCSI cache Oct 9 08:51:48 storageqe-109 kernel: scsi 11:0:1:0: alua: Detached Oct 9 08:51:48 storageqe-109 kernel: sd 10:0:1:0: [sdg] Synchronizing SCSI cache Oct 9 08:51:48 storageqe-109 kernel: scsi 10:0:1:0: alua: Detached Oct 9 08:51:48 storageqe-109 kernel: sd 9:0:1:0: [sdf] Synchronizing SCSI cache Oct 9 08:51:48 storageqe-109 kernel: scsi 9:0:1:0: alua: Detached WARN: Failed to clear targetcli configuration, continuing cleanup... INFO: Removing test disk files... INFO: Removing disk file: /home/udisks_test_disk1 INFO: Removing disk file: /home/udisks_test_disk2 INFO: Removing disk file: /home/udisks_test_disk3 INFO: Removing disk file: /home/udisks_test_disk4 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 INFO: Local iSCSI target cleanup completed Oct 9 08:51:48 storageqe-109 WARN: Failed to clear targetcli configuration, continuing cleanup... Oct 9 08:51:48 storageqe-109 INFO: Removing test disk files... Oct 9 08:51:48 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk1 Oct 9 08:51:48 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk2 Oct 9 08:51:48 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk3 Oct 9 08:51:48 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk4 Oct 9 08:51:48 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi1 Oct 9 08:51:48 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi2 Oct 9 08:51:48 storageqe-109 INFO: Removing disk file: /home/udisks_test_disk_iscsi3 Oct 9 08:51:48 storageqe-109 INFO: Local iSCSI target cleanup completed INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: #### END test_iscsi_session_logout_methods #### INFO: #### will start test_plain_lv_properties_and_methods ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:51:53 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### Oct 9 08:51:53 storageqe-109 INFO: #### END test_iscsi_session_logout_methods #### Oct 9 08:51:53 storageqe-109 INFO: #### will start test_plain_lv_properties_and_methods ##### Oct 9 08:51:53 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd'] #### INFO: Creating VG 'udisks_test_vg' on device /dev/sde Oct 9 08:51:58 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/sde Oct 9 08:52:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:52:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: VG object for 'udisks_test_vg' is now live. Oct 9 08:52:50 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. INFO: Validating LV properties... Oct 9 08:53:15 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:53:15 storageqe-109 INFO: Validating LV properties... INFO: Testing Rename()... Oct 9 08:53:19 storageqe-109 INFO: Testing Rename()... Oct 9 08:53:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Testing Resize()... Oct 9 08:55:49 storageqe-109 INFO: Testing Resize()... Oct 9 08:56:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Testing Delete()... Oct 9 08:56:16 storageqe-109 INFO: Testing Delete()... Oct 9 08:56:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 08:56:42 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 08:57:08 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### INFO: #### END test_plain_lv_properties_and_methods #### INFO: #### will start test_lv_snapshot_creation_and_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 08:57:13 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 08:57:13 storageqe-109 INFO: #### END test_plain_lv_properties_and_methods #### Oct 9 08:57:13 storageqe-109 INFO: #### will start test_lv_snapshot_creation_and_properties ##### Oct 9 08:57:13 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde'] #### Oct 9 08:57:18 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: Creating VG 'udisks_test_vg' on device /dev/nvme0n1 Oct 9 08:57:19 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/nvme0n1 Oct 9 08:57:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:58:09 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: VG object for 'udisks_test_vg' is now live. Oct 9 08:58:10 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. Oct 9 08:58:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Creating snapshot 'test_snapshot'... Oct 9 08:58:36 storageqe-109 INFO: Creating snapshot 'test_snapshot'... INFO: Validating snapshot properties... Oct 9 08:59:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:59:01 storageqe-109 systemd[1]: Started dm-event.service - Device-mapper event daemon. Oct 9 08:59:01 storageqe-109 dmeventd[2563240]: dmeventd ready for processing. Oct 9 08:59:01 storageqe-109 dmeventd[2563240]: Monitoring snapshot udisks_test_vg-test_snapshot. Oct 9 08:59:01 storageqe-109 INFO: Validating snapshot properties... INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 08:59:02 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 08:59:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 08:59:28 storageqe-109 dmeventd[2563240]: No longer monitoring snapshot udisks_test_vg-test_snapshot. INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_lv_snapshot_creation_and_properties #### INFO: #### will start test_logical_volume_all_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 08:59:33 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 08:59:33 storageqe-109 INFO: #### END test_lv_snapshot_creation_and_properties #### Oct 9 08:59:33 storageqe-109 INFO: #### will start test_logical_volume_all_properties ##### Oct 9 08:59:33 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1'] #### INFO: Creating VG 'udisks_test_vg' on device /dev/sdb Oct 9 08:59:38 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/sdb Oct 9 09:00:03 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:00:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: VG object for 'udisks_test_vg' is now live. Oct 9 09:00:30 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. Oct 9 09:00:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Fetching all properties for LogicalVolume interface... INFO: Checking property 'VolumeGroup'... INFO: Checking property 'Name'... INFO: Checking property 'Active'... INFO: Checking property 'UUID'... INFO: Checking property 'Size'... INFO: Checking property 'DataAllocatedRatio'... INFO: Checking property 'MetadataAllocatedRatio'... INFO: Checking property 'Type'... INFO: Checking property 'Layout'... INFO: Checking property 'Structure'... INFO: Checking property 'SyncRatio'... INFO: Checking property 'ThinPool'... INFO: Checking property 'Origin'... INFO: Checking property 'ChildConfiguration'... INFO: Checking property 'BlockDevice'... INFO: Checking specific property values... INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 09:01:00 storageqe-109 INFO: Fetching all properties for LogicalVolume interface... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'VolumeGroup'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'Name'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'Active'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'UUID'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'Size'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'DataAllocatedRatio'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'MetadataAllocatedRatio'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'Type'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'Layout'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'Structure'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'SyncRatio'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'ThinPool'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'Origin'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'ChildConfiguration'... Oct 9 09:01:00 storageqe-109 INFO: Checking property 'BlockDevice'... Oct 9 09:01:00 storageqe-109 INFO: Checking specific property values... Oct 9 09:01:00 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 09:01:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_logical_volume_all_properties #### INFO: #### will start test_lvm_cache_operations ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 9 09:01:31 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 9 09:01:31 storageqe-109 INFO: #### END test_logical_volume_all_properties #### Oct 9 09:01:31 storageqe-109 INFO: #### will start test_lvm_cache_operations ##### Oct 9 09:01:31 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: Starting LVM cache operations test with enhanced error handling INFO: Creating VG 'udisks_test_vg' on device /dev/sdc Oct 9 09:01:36 storageqe-109 INFO: Starting LVM cache operations test with enhanced error handling Oct 9 09:01:36 storageqe-109 INFO: Creating VG 'udisks_test_vg' on device /dev/sdc Oct 9 09:02:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:02:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: VG object for 'udisks_test_vg' is now live. INFO: Getting cache device... Oct 9 09:02:28 storageqe-109 INFO: VG object for 'udisks_test_vg' is now live. Oct 9 09:02:28 storageqe-109 INFO: Getting cache device... INFO: Cache device /dev/sdd ready Oct 9 09:02:30 storageqe-109 INFO: Cache device /dev/sdd ready INFO: Creating logical volume of size 536870912 bytes... Oct 9 09:02:30 storageqe-109 INFO: Creating logical volume of size 536870912 bytes... Oct 9 09:02:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:02:55 storageqe-109 INFO: Waiting for object /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv to be ready... INFO: Waiting for object /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv to be ready... INFO: Object at /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv is now live with name='udisks_test_lv', active=1 INFO: === Testing LVM Cache Attach/Detach === INFO: Verifying initial state (no cache)... INFO: Attaching cache... INFO: Executing CacheAttach operation... Oct 9 09:02:56 storageqe-109 INFO: Object at /org/freedesktop/UDisks2/lvm/udisks_test_vg/udisks_test_lv is now live with name='udisks_test_lv', active=1 Oct 9 09:02:56 storageqe-109 INFO: === Testing LVM Cache Attach/Detach === Oct 9 09:02:56 storageqe-109 INFO: Verifying initial state (no cache)... Oct 9 09:02:56 storageqe-109 INFO: Attaching cache... Oct 9 09:02:56 storageqe-109 INFO: Executing CacheAttach operation... INFO: Cache device name: sdd INFO: Cache device path: /dev/sdd INFO: Cache device object: /org/freedesktop/UDisks2/block_devices/sdd Oct 9 09:02:57 storageqe-109 INFO: Cache device name: sdd Oct 9 09:02:57 storageqe-109 INFO: Cache device path: /dev/sdd Oct 9 09:02:57 storageqe-109 INFO: Cache device object: /org/freedesktop/UDisks2/block_devices/sdd ERROR: CacheAttach failed: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdd not found. INFO: Cache operation failed as expected - cache pool not found: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdd not found. INFO: This indicates the D-Bus interface is working correctly INFO: Skipping remaining cache tests due to cache pool requirement INFO: Performing cleanup... INFO: Releasing cache device /dev/sdd INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 09:03:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:03:22 storageqe-109 ERROR: CacheAttach failed: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdd not found. Oct 9 09:03:22 storageqe-109 journal: Oct 9 09:03:22 storageqe-109 INFO: Cache operation failed as expected - cache pool not found: org.freedesktop.UDisks2.Error.Failed: Error converting volume: Process reported exit code 5: Cache pool sdd not found. Oct 9 09:03:22 storageqe-109 journal: Oct 9 09:03:22 storageqe-109 INFO: This indicates the D-Bus interface is working correctly Oct 9 09:03:22 storageqe-109 INFO: Skipping remaining cache tests due to cache pool requirement Oct 9 09:03:22 storageqe-109 INFO: Performing cleanup... Oct 9 09:03:22 storageqe-109 INFO: Releasing cache device /dev/sdd Oct 9 09:03:22 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vg' Oct 9 09:03:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_lvm_cache_operations #### INFO: #### will start test_mdraid_properties_by_level[raid0-2-None] ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:03:53 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:03:53 storageqe-109 INFO: #### END test_lvm_cache_operations #### Oct 9 09:03:53 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid0-2-None] ##### Oct 9 09:03:53 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:03:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 09:03:59 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 Oct 9 09:04:00 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 09:04:00 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid0_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid0 INFO: raid name test_raid0 INFO: raid chunk 65536 INFO: raid bitmap None INFO: raid version None Oct 9 09:04:00 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 09:04:00 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid0_1.img) Oct 9 09:04:00 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 09:04:00 storageqe-109 INFO: raid level raid0 Oct 9 09:04:00 storageqe-109 INFO: raid name test_raid0 Oct 9 09:04:00 storageqe-109 INFO: raid chunk 65536 Oct 9 09:04:00 storageqe-109 INFO: raid bitmap None Oct 9 09:04:00 storageqe-109 INFO: raid version None Oct 9 09:04:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:04:25 storageqe-109 kernel: md127: detected capacity change from 0 to 4186112 Oct 9 09:05:07 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:05:07 storageqe-109 kernel: md127: detected capacity change from 4186112 to 0 Oct 9 09:05:07 storageqe-109 kernel: md: md127 stopped. Oct 9 09:05:08 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 09:05:10 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 09:05:11 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 09:05:11 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 09:05:12 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 09:05:12 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_mdraid_properties_by_level[raid0-2-None] #### INFO: #### will start test_mdraid_properties_by_level[raid1-2-None] ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:05:18 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:05:18 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid0-2-None] #### Oct 9 09:05:18 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid1-2-None] ##### Oct 9 09:05:18 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:05:24 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 09:05:24 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid1_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_raid1 INFO: raid chunk 0 INFO: raid bitmap None INFO: raid version None Oct 9 09:05:25 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 09:05:25 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid1_1.img) Oct 9 09:05:25 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 09:05:25 storageqe-109 INFO: raid level raid1 Oct 9 09:05:25 storageqe-109 INFO: raid name test_raid1 Oct 9 09:05:25 storageqe-109 INFO: raid chunk 0 Oct 9 09:05:25 storageqe-109 INFO: raid bitmap None Oct 9 09:05:25 storageqe-109 INFO: raid version None Oct 9 09:05:50 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:05:50 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 09:05:50 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 09:05:50 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 09:05:50 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 09:05:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 09:05:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 09:05:50 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 09:05:55 storageqe-109 kernel: md: md127: resync done. Oct 9 09:06:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:06:40 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 09:06:40 storageqe-109 kernel: md: md127 stopped. Oct 9 09:06:40 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 09:06:44 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 09:06:44 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_mdraid_properties_by_level[raid1-2-None] #### INFO: #### will start test_mdraid_properties_by_level[raid1-2-internal] ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:06:51 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:06:51 storageqe-109 INFO: #### END test_mdraid_properties_by_level[raid1-2-None] #### Oct 9 09:06:51 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid1-2-internal] ##### Oct 9 09:06:51 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:06:57 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 09:06:57 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/loop_test_raid1_bitmap_0.img) INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] INFO: raid level raid1 INFO: raid name test_raid1_bitmap INFO: raid chunk 0 INFO: raid bitmap internal INFO: raid version None Oct 9 09:06:58 storageqe-109 kernel: loop1: detected capacity change from 0 to 2097152 Oct 9 09:06:58 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop1 (backed by /home/loop_test_raid1_bitmap_1.img) Oct 9 09:06:58 storageqe-109 INFO: raid disk [dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop0'), dbus.ObjectPath('/org/freedesktop/UDisks2/block_devices/loop1')] Oct 9 09:06:58 storageqe-109 INFO: raid level raid1 Oct 9 09:06:58 storageqe-109 INFO: raid name test_raid1_bitmap Oct 9 09:06:58 storageqe-109 INFO: raid chunk 0 Oct 9 09:06:58 storageqe-109 INFO: raid bitmap internal Oct 9 09:06:58 storageqe-109 INFO: raid version None Oct 9 09:07:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:07:23 storageqe-109 kernel: md/raid1:md127: not clean -- starting background reconstruction Oct 9 09:07:23 storageqe-109 kernel: md/raid1:md127: active with 2 out of 2 mirrors Oct 9 09:07:23 storageqe-109 kernel: md127: detected capacity change from 0 to 2093056 Oct 9 09:07:23 storageqe-109 kernel: md: resync of RAID array md127 Oct 9 09:07:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 09:07:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 09:07:23 storageqe-109 systemd[1]: mdmonitor.service - Software RAID monitoring and management was skipped because of an unmet condition check (ConditionPathExists=/etc/mdadm.conf). Oct 9 09:07:28 storageqe-109 kernel: md: md127: resync done. Oct 9 09:07:53 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 9 09:07:53 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 9 09:08:13 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:08:13 storageqe-109 kernel: md127: detected capacity change from 2093056 to 0 Oct 9 09:08:13 storageqe-109 kernel: md: md127 stopped. Oct 9 09:08:13 storageqe-109 udisksd[2509680]: No longer watching mdraid device 9:127 Oct 9 09:08:14 storageqe-109 kernel: __vm_enough_memory: pid: 2505384, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 9 09:08:14 storageqe-109 kernel: __vm_enough_memory: pid: 2505384, comm: claude, bytes: 34357534720 not enough memory for the allocation Oct 9 09:08:14 storageqe-109 kernel: __vm_enough_memory: pid: 2505384, comm: claude, bytes: 34359873536 not enough memory for the allocation Oct 9 09:08:14 storageqe-109 kernel: __vm_enough_memory: pid: 2505384, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 9 09:08:14 storageqe-109 systemd-coredump[2565398]: Process 2505384 (claude) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 9 09:08:14 storageqe-109 systemd[1]: Started systemd-coredump@4-2565398-0.service - Process Core Dump (PID 2565398/UID 0). Oct 9 09:08:15 storageqe-109 systemd-coredump[2565399]: Process 2505384 (claude) of user 0 dumped core.#012#012Module /usr/bin/node-22 from rpm nodejs22-22.19.0-2.el10_0.x86_64#012Stack trace of thread 2505384:#012#0 0x00007fa7d34b6fcc n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 9 09:08:15 storageqe-109 systemd[1]: systemd-coredump@4-2565398-0.service: Deactivated successfully. Oct 9 09:08:15 storageqe-109 systemd[1]: systemd-coredump@4-2565398-0.service: Consumed 1.032s CPU time, 1G memory peak. Oct 9 09:08:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop1 Oct 9 09:08:17 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### will start test_mdraid_properties_by_level[raid5-3-internal] ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:08:24 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid5-3-internal] ##### Oct 9 09:08:24 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_mdraid_properties_by_level[raid6-4-None] ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:08:29 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid6-4-None] ##### Oct 9 09:08:29 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_mdraid_properties_by_level[raid10-4-None] ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:08:34 storageqe-109 INFO: #### will start test_mdraid_properties_by_level[raid10-4-None] ##### Oct 9 09:08:34 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisks2_nvme_ay_type_read_write_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:08:39 storageqe-109 INFO: #### will start test_udisks2_nvme_ay_type_read_write_operations ##### Oct 9 09:08:39 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisks2_nvme_set_host_nqn ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:08:44 storageqe-109 INFO: #### will start test_udisks2_nvme_set_host_nqn ##### Oct 9 09:08:44 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisks2_nvme_set_host_id ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:08:50 storageqe-109 INFO: #### will start test_udisks2_nvme_set_host_id ##### Oct 9 09:08:50 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 9 09:08:56 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 9 09:09:06 storageqe-109 kernel: nvme nvme0: rescanning namespaces. INFO: #### will start test_udisks2_nvme_connect_tcp ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:09:07 storageqe-109 INFO: #### will start test_udisks2_nvme_connect_tcp ##### Oct 9 09:09:07 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisks2_nvme_comprehensive_workflow ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:09:12 storageqe-109 INFO: #### will start test_udisks2_nvme_comprehensive_workflow ##### Oct 9 09:09:12 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:09:26 storageqe-109 kernel: nvmet: adding nsid 1 to subsystem nqn.2025-01.udisks2.workflow:target-CjkNWv Oct 9 09:09:26 storageqe-109 kernel: nvmet_tcp: enabling port 4450 (127.0.0.1:4450) Oct 9 09:09:29 storageqe-109 kernel: nvmet: Created nvm controller 1 for subsystem nqn.2025-01.udisks2.workflow:target-CjkNWv for NQN nqn.2025-01.udisks2.workflow:uuid:11111111-2222-3333-4444-555555555555. Oct 9 09:09:29 storageqe-109 kernel: nvme nvme1: creating 2 I/O queues. Oct 9 09:09:29 storageqe-109 kernel: nvme nvme1: mapped 2/0/0 default/read/poll queues. Oct 9 09:09:29 storageqe-109 kernel: nvme nvme1: new ctrl: NQN "nqn.2025-01.udisks2.workflow:target-CjkNWv", addr 127.0.0.1:4450, hostnqn: nqn.2025-01.udisks2.workflow:uuid:11111111-2222-3333-4444-555555555555 Oct 9 09:09:49 storageqe-109 kernel: nvme nvme1: starting error recovery Oct 9 09:09:50 storageqe-109 kernel: nvmet_tcp: queue 1 unhandled state 11 Oct 9 09:09:50 storageqe-109 kernel: nvme nvme1: queue 1 socket state 11 Oct 9 09:09:50 storageqe-109 kernel: nvme nvme1: Reconnecting in 10 seconds... Oct 9 09:09:50 storageqe-109 kernel: nvme nvme1: Removing ctrl: NQN "nqn.2025-01.udisks2.workflow:target-CjkNWv" Oct 9 09:09:50 storageqe-109 kernel: nvme nvme1: Property Set error: 880, offset 0x14 Oct 9 09:09:56 storageqe-109 kernel: __vm_enough_memory: pid: 2565571, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 9 09:09:56 storageqe-109 kernel: __vm_enough_memory: pid: 2565571, comm: claude, bytes: 34357440512 not enough memory for the allocation Oct 9 09:09:56 storageqe-109 kernel: __vm_enough_memory: pid: 2565571, comm: claude, bytes: 34359873536 not enough memory for the allocation Oct 9 09:09:56 storageqe-109 kernel: __vm_enough_memory: pid: 2565571, comm: claude, bytes: 34359742464 not enough memory for the allocation Oct 9 09:09:56 storageqe-109 systemd-coredump[2566747]: Process 2565571 (claude) of user 0 terminated abnormally with signal 6/ABRT, processing... Oct 9 09:09:56 storageqe-109 systemd[1]: Started systemd-coredump@5-2566747-0.service - Process Core Dump (PID 2566747/UID 0). Oct 9 09:09:58 storageqe-109 systemd-coredump[2566748]: Process 2565571 (claude) of user 0 dumped core.#012#012Module /usr/bin/node-22 from rpm nodejs22-22.19.0-2.el10_0.x86_64#012Stack trace of thread 2565571:#012#0 0x00007f34418bdfcc n/a (n/a + 0x0)#012ELF object binary architecture: AMD x86-64 Oct 9 09:09:58 storageqe-109 systemd[1]: systemd-coredump@5-2566747-0.service: Deactivated successfully. Oct 9 09:09:58 storageqe-109 systemd[1]: systemd-coredump@5-2566747-0.service: Consumed 1.035s CPU time, 1G memory peak. INFO: #### will start test_udisks2_nvme_connect_all_parameters ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:01 storageqe-109 INFO: #### will start test_udisks2_nvme_connect_all_parameters ##### Oct 9 09:10:01 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:04 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. INFO: #### will start test_udisks2_nvme_error_scenarios ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:06 storageqe-109 INFO: #### will start test_udisks2_nvme_error_scenarios ##### Oct 9 09:10:06 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisks2_nvme_fabrics_interface_properties ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:12 storageqe-109 INFO: #### will start test_udisks2_nvme_fabrics_interface_properties ##### Oct 9 09:10:12 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisks2_nvme_multipath_namespace_persistence ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:17 storageqe-109 INFO: #### will start test_udisks2_nvme_multipath_namespace_persistence ##### Oct 9 09:10:17 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisks2_nvme_multipath_controller_failover ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:22 storageqe-109 INFO: #### will start test_udisks2_nvme_multipath_controller_failover ##### Oct 9 09:10:22 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisksctl_invalid_commands ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:27 storageqe-109 INFO: #### will start test_udisksctl_invalid_commands ##### Oct 9 09:10:27 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisksctl_missing_required_parameters ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:32 storageqe-109 INFO: #### will start test_udisksctl_missing_required_parameters ##### Oct 9 09:10:32 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisksctl_invalid_parameter_values ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:38 storageqe-109 INFO: #### will start test_udisksctl_invalid_parameter_values ##### Oct 9 09:10:38 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisksctl_invalid_option_combinations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:43 storageqe-109 INFO: #### will start test_udisksctl_invalid_option_combinations ##### Oct 9 09:10:43 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisksctl_malformed_device_paths ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:48 storageqe-109 INFO: #### will start test_udisksctl_malformed_device_paths ##### Oct 9 09:10:48 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### will start test_udisksctl_resource_limits ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:53 storageqe-109 INFO: #### will start test_udisksctl_resource_limits ##### Oct 9 09:10:53 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:10:58 storageqe-109 kernel: loop0: detected capacity change from 0 to 209715200 Oct 9 09:10:58 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /tmp/udisks_large_test.img) Oct 9 09:11:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:11:23 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /tmp/udisks_large_test.img) Oct 9 09:11:23 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_udisksctl_resource_limits #### INFO: #### will start test_udisksctl_concurrent_error_operations ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:11:28 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:11:28 storageqe-109 INFO: #### END test_udisksctl_resource_limits #### Oct 9 09:11:28 storageqe-109 INFO: #### will start test_udisksctl_concurrent_error_operations ##### Oct 9 09:11:28 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_udisksctl_concurrent_error_operations #### INFO: #### will start test_udisksctl_permission_errors ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:11:39 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:11:39 storageqe-109 INFO: #### END test_udisksctl_concurrent_error_operations #### Oct 9 09:11:39 storageqe-109 INFO: #### will start test_udisksctl_permission_errors ##### Oct 9 09:11:39 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_udisksctl_permission_errors #### INFO: #### will start test_udisksctl_signal_interruption ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:11:49 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:11:49 storageqe-109 INFO: #### END test_udisksctl_permission_errors #### Oct 9 09:11:49 storageqe-109 INFO: #### will start test_udisksctl_signal_interruption ##### Oct 9 09:11:49 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_udisksctl_signal_interruption #### INFO: #### will start test_udisksctl_environment_variable_injection ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:11:59 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:12:00 storageqe-109 INFO: #### END test_udisksctl_signal_interruption #### Oct 9 09:12:00 storageqe-109 INFO: #### will start test_udisksctl_environment_variable_injection ##### Oct 9 09:12:00 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_udisksctl_environment_variable_injection #### INFO: #### will start test_udisksctl_dbus_error_handling ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:12:10 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:12:10 storageqe-109 INFO: #### END test_udisksctl_environment_variable_injection #### Oct 9 09:12:10 storageqe-109 INFO: #### will start test_udisksctl_dbus_error_handling ##### Oct 9 09:12:10 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_udisksctl_dbus_error_handling #### INFO: #### will start test_udisksctl_memory_stress ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:12:20 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:12:20 storageqe-109 INFO: #### END test_udisksctl_dbus_error_handling #### Oct 9 09:12:20 storageqe-109 INFO: #### will start test_udisksctl_memory_stress ##### Oct 9 09:12:20 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_udisksctl_memory_stress #### INFO: #### will start test_partition_table_and_partition_lifecycle ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:12:31 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:12:31 storageqe-109 INFO: #### END test_udisksctl_memory_stress #### Oct 9 09:12:31 storageqe-109 INFO: #### will start test_partition_table_and_partition_lifecycle ##### Oct 9 09:12:31 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: Creating GPT partition table... Oct 9 09:12:38 storageqe-109 INFO: Creating GPT partition table... Oct 9 09:12:38 storageqe-109 kernel: sde: INFO: Creating a new partition... Oct 9 09:12:41 storageqe-109 INFO: Creating a new partition... Oct 9 09:13:06 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Validating PartitionTable properties... INFO: Validating Partition properties... INFO: Testing SetName, SetType, SetFlags, and SetUUID... Oct 9 09:13:11 storageqe-109 INFO: Validating PartitionTable properties... Oct 9 09:13:11 storageqe-109 INFO: Validating Partition properties... Oct 9 09:13:11 storageqe-109 INFO: Testing SetName, SetType, SetFlags, and SetUUID... Oct 9 09:13:36 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:14:01 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:14:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:14:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Testing Resize... Oct 9 09:14:57 storageqe-109 INFO: Testing Resize... Oct 9 09:15:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:15:22 storageqe-109 kernel: sde: sde1 INFO: Testing Delete... Oct 9 09:15:26 storageqe-109 INFO: Testing Delete... Oct 9 09:15:51 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:15:51 storageqe-109 kernel: sde: INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### INFO: #### END test_partition_table_and_partition_lifecycle #### INFO: #### will start test_physical_volume_properties ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### Oct 9 09:15:59 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### Oct 9 09:15:59 storageqe-109 INFO: #### END test_partition_table_and_partition_lifecycle #### Oct 9 09:15:59 storageqe-109 INFO: #### will start test_physical_volume_properties ##### Oct 9 09:15:59 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### INFO: Creating VG 'udisks_test_pv_vg' on device /dev/nvme0n1 to create a PV Oct 9 09:16:04 storageqe-109 INFO: Creating VG 'udisks_test_pv_vg' on device /dev/nvme0n1 to create a PV Oct 9 09:16:29 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:16:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Fetching all properties for PhysicalVolume interface... INFO: Checking property 'Size'... INFO: Checking property 'FreeSize'... INFO: Checking property 'VolumeGroup'... INFO: Checking specific property values... INFO: Cleaning up Volume Group 'udisks_test_pv_vg' Oct 9 09:17:00 storageqe-109 INFO: Fetching all properties for PhysicalVolume interface... Oct 9 09:17:00 storageqe-109 INFO: Checking property 'Size'... Oct 9 09:17:00 storageqe-109 INFO: Checking property 'FreeSize'... Oct 9 09:17:00 storageqe-109 INFO: Checking property 'VolumeGroup'... Oct 9 09:17:00 storageqe-109 INFO: Checking specific property values... Oct 9 09:17:00 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_pv_vg' Oct 9 09:17:26 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_physical_volume_properties #### INFO: #### will start test_invalid_filesystem_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:17:31 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:17:31 storageqe-109 INFO: #### END test_physical_volume_properties #### Oct 9 09:17:31 storageqe-109 INFO: #### will start test_invalid_filesystem_operations ##### Oct 9 09:17:31 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_invalid_filesystem_operations #### INFO: #### will start test_invalid_partition_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:17:41 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:17:41 storageqe-109 INFO: #### END test_invalid_filesystem_operations #### Oct 9 09:17:41 storageqe-109 INFO: #### will start test_invalid_partition_operations ##### Oct 9 09:17:41 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:17:46 storageqe-109 kernel: nvme0n1: Oct 9 09:18:11 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_invalid_partition_operations #### INFO: #### will start test_invalid_lvm_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:17 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:17 storageqe-109 INFO: #### END test_invalid_partition_operations #### Oct 9 09:18:17 storageqe-109 INFO: #### will start test_invalid_lvm_operations ##### Oct 9 09:18:17 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_invalid_lvm_operations #### INFO: #### will start test_invalid_luks_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:27 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 09:18:27 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:27 storageqe-109 INFO: #### END test_invalid_lvm_operations #### Oct 9 09:18:27 storageqe-109 INFO: #### will start test_invalid_luks_operations ##### Oct 9 09:18:27 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:27 storageqe-109 dnf[2568081]: Updating Subscription Management repositories. Oct 9 09:18:27 storageqe-109 dnf[2568081]: Unable to read consumer identity Oct 9 09:18:27 storageqe-109 dnf[2568081]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 09:18:27 storageqe-109 dnf[2568081]: Metadata cache refreshed recently. Oct 9 09:18:27 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 09:18:27 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 09:18:27 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 233ms CPU time, 66.8M memory peak. INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_invalid_luks_operations #### INFO: #### will start test_invalid_mount_operations ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:37 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:37 storageqe-109 INFO: #### END test_invalid_luks_operations #### Oct 9 09:18:37 storageqe-109 INFO: #### will start test_invalid_mount_operations ##### Oct 9 09:18:37 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_invalid_mount_operations #### INFO: #### will start test_empty_string_parameters ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:47 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:47 storageqe-109 INFO: #### END test_invalid_mount_operations #### Oct 9 09:18:47 storageqe-109 INFO: #### will start test_empty_string_parameters ##### Oct 9 09:18:47 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_empty_string_parameters #### INFO: #### will start test_basic_cleanup_after_errors ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:57 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:18:57 storageqe-109 INFO: #### END test_empty_string_parameters #### Oct 9 09:18:57 storageqe-109 INFO: #### will start test_basic_cleanup_after_errors ##### Oct 9 09:18:57 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:19:03 storageqe-109 kernel: nvme0n1: Oct 9 09:19:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:19:29 storageqe-109 kernel: loop0: detected capacity change from 0 to 2097152 Oct 9 09:19:29 storageqe-109 udisksd[2509680]: Set up loop device /dev/loop0 (backed by /home/tmpakuvae6n.img) Oct 9 09:19:54 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:19:54 storageqe-109 udisksd[2509680]: Deleted loop device /dev/loop0 (was backed by /home/tmpakuvae6n.img) Oct 9 09:19:54 storageqe-109 udisksd[2509680]: No longer watching loop device /dev/loop0 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_basic_cleanup_after_errors #### INFO: #### will start test_dbus_connection_errors ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:19:59 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:19:59 storageqe-109 INFO: #### END test_basic_cleanup_after_errors #### Oct 9 09:19:59 storageqe-109 INFO: #### will start test_dbus_connection_errors ##### Oct 9 09:19:59 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_dbus_connection_errors #### INFO: #### will start test_error_message_quality ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:20:09 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:20:09 storageqe-109 INFO: #### END test_dbus_connection_errors #### Oct 9 09:20:09 storageqe-109 INFO: #### will start test_error_message_quality ##### Oct 9 09:20:09 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: #### END test_error_message_quality #### INFO: #### will start test_thin_pool_properties ##### INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:20:19 storageqe-109 INFO: #### after available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### Oct 9 09:20:19 storageqe-109 INFO: #### END test_error_message_quality #### Oct 9 09:20:19 storageqe-109 INFO: #### will start test_thin_pool_properties ##### Oct 9 09:20:19 storageqe-109 INFO: #### before available_disks ['/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1'] #### INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdb Oct 9 09:20:24 storageqe-109 INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdb Oct 9 09:20:49 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:21:14 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 9 09:21:18 storageqe-109 INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 9 09:21:44 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:21:44 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 9 09:21:44 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Validating thin pool properties... INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 9 09:21:51 storageqe-109 INFO: Validating thin pool properties... Oct 9 09:21:51 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 9 09:21:52 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 9 09:21:52 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 9 09:22:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:22:18 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 9 09:22:18 storageqe-109 INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down INFO: #### after available_disks ['/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_thin_pool_properties #### INFO: #### will start test_thin_volume_properties ##### INFO: #### before available_disks ['/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 9 09:22:23 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 9 09:22:23 storageqe-109 INFO: #### END test_thin_pool_properties #### Oct 9 09:22:23 storageqe-109 INFO: #### will start test_thin_volume_properties ##### Oct 9 09:22:23 storageqe-109 INFO: #### before available_disks ['/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdd Oct 9 09:22:28 storageqe-109 INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdd Oct 9 09:22:53 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:23:18 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 9 09:23:22 storageqe-109 INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 9 09:23:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:23:48 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 9 09:23:48 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Creating thin volume 'udisks_test_thin_lv' in pool 'udisks_test_thin_pool' Oct 9 09:23:55 storageqe-109 INFO: Creating thin volume 'udisks_test_thin_lv' in pool 'udisks_test_thin_pool' Oct 9 09:24:22 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:24:22 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 9 09:24:24 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 9 09:24:24 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. INFO: Validating thin volume properties... INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 9 09:24:29 storageqe-109 INFO: Validating thin volume properties... Oct 9 09:24:29 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 9 09:24:29 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 9 09:24:29 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 9 09:24:29 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 9 09:24:29 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 9 09:24:55 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:24:55 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool-tpool. Oct 9 09:24:55 storageqe-109 INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down INFO: #### after available_disks ['/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd'] #### INFO: #### END test_thin_volume_properties #### INFO: #### will start test_thin_pool_cleanup_verification ##### INFO: #### before available_disks ['/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd'] #### Oct 9 09:25:01 storageqe-109 INFO: #### after available_disks ['/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd'] #### Oct 9 09:25:01 storageqe-109 INFO: #### END test_thin_volume_properties #### Oct 9 09:25:01 storageqe-109 INFO: #### will start test_thin_pool_cleanup_verification ##### Oct 9 09:25:01 storageqe-109 INFO: #### before available_disks ['/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd'] #### INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdc Oct 9 09:25:06 storageqe-109 INFO: Creating VG 'udisks_test_thin_vg' on device /dev/sdc Oct 9 09:25:31 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:25:56 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 9 09:25:59 storageqe-109 INFO: Creating thin pool 'udisks_test_thin_pool' in VG 'udisks_test_thin_vg' Oct 9 09:26:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:26:26 storageqe-109 kernel: device-mapper: thin: Data device (dm-4) discard unsupported: Disabling discard passdown. Oct 9 09:26:26 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Testing thin pool cleanup verification... INFO: Thin pool objects verified successfully INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 9 09:26:33 storageqe-109 INFO: Testing thin pool cleanup verification... Oct 9 09:26:33 storageqe-109 INFO: Thin pool objects verified successfully Oct 9 09:26:33 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_thin_vg' Oct 9 09:26:33 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 9 09:26:33 storageqe-109 dmeventd[2563240]: Monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 9 09:26:59 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:26:59 storageqe-109 dmeventd[2563240]: No longer monitoring thin pool udisks_test_thin_vg-udisks_test_thin_pool. Oct 9 09:26:59 storageqe-109 INFO: Successfully removed VG 'udisks_test_thin_vg' with tear_down Oct 9 09:27:00 storageqe-109 INFO: Verifying VG cleanup... INFO: Verifying VG cleanup... INFO: VG udisks_test_thin_vg successfully removed Oct 9 09:27:02 storageqe-109 INFO: VG udisks_test_thin_vg successfully removed INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: #### END test_thin_pool_cleanup_verification #### INFO: #### will start test_vdovolume_properties ##### INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:27:07 storageqe-109 INFO: #### after available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### Oct 9 09:27:07 storageqe-109 INFO: #### END test_thin_pool_cleanup_verification #### Oct 9 09:27:07 storageqe-109 INFO: #### will start test_vdovolume_properties ##### Oct 9 09:27:07 storageqe-109 INFO: #### before available_disks ['/dev/sde', '/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc'] #### INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/sde'] Oct 9 09:27:12 storageqe-109 INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/sde'] Oct 9 09:27:37 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:28:02 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:28:02 storageqe-109 INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' Oct 9 09:28:28 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:28:28 storageqe-109 UDS/vdoformat[2569508]: INFO (vdoformat/2569508) Using 2 indexing zones for concurrency. Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo26:lvm: table line: V4 /dev/dm-3 114981888 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo26:lvm: loading device '253:4' Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo26:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo26:lvm: starting device '253:4' Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo: dm_vdo26:physQ0: VDO commencing normal operation Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo: dm_vdo26:journa: Setting UDS index target state to online Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo: dm_vdo26:dedupe: creating index: 253:3 Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo26:lvm: device '253:4' started Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo: dm_vdo26:dedupe: Using 2 indexing zones for concurrency. Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo26:lvm: resuming device '253:4' Oct 9 09:28:28 storageqe-109 kernel: device-mapper: vdo26:lvm: device '253:4' resumed Oct 9 09:28:28 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Fetching all properties for VDOVolume interface... INFO: Checking property 'VDOPool'... INFO: Checking property 'OperatingMode'... INFO: Checking property 'CompressionState'... INFO: Checking property 'IndexState'... INFO: Checking property 'UsedSize'... INFO: Checking property 'Compression'... INFO: Checking property 'Deduplication'... INFO: Checking initial property values... INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 9 09:28:34 storageqe-109 INFO: Fetching all properties for VDOVolume interface... Oct 9 09:28:34 storageqe-109 INFO: Checking property 'VDOPool'... Oct 9 09:28:34 storageqe-109 INFO: Checking property 'OperatingMode'... Oct 9 09:28:34 storageqe-109 INFO: Checking property 'CompressionState'... Oct 9 09:28:34 storageqe-109 INFO: Checking property 'IndexState'... Oct 9 09:28:34 storageqe-109 INFO: Checking property 'UsedSize'... Oct 9 09:28:34 storageqe-109 INFO: Checking property 'Compression'... Oct 9 09:28:34 storageqe-109 INFO: Checking property 'Deduplication'... Oct 9 09:28:34 storageqe-109 INFO: Checking initial property values... Oct 9 09:28:34 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 9 09:29:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:29:00 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:29:00 storageqe-109 kernel: device-mapper: vdo26:lvm: suspending device '253:4' Oct 9 09:29:00 storageqe-109 kernel: device-mapper: vdo: dm_vdo26:journa: beginning save (vcn 18446744073709551615) Oct 9 09:29:00 storageqe-109 kernel: device-mapper: vdo: dm_vdo26:journa: finished save (vcn 18446744073709551615) Oct 9 09:29:00 storageqe-109 kernel: device-mapper: vdo26:lvm: device '253:4' suspended Oct 9 09:29:00 storageqe-109 kernel: device-mapper: vdo26:lvm: stopping device '253:4' Oct 9 09:29:00 storageqe-109 kernel: device-mapper: vdo26:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### INFO: #### END test_vdovolume_properties #### INFO: #### will start test_vdovolume_methods ##### INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### Oct 9 09:29:05 storageqe-109 INFO: #### after available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### Oct 9 09:29:05 storageqe-109 INFO: #### END test_vdovolume_properties #### Oct 9 09:29:05 storageqe-109 INFO: #### will start test_vdovolume_methods ##### Oct 9 09:29:05 storageqe-109 INFO: #### before available_disks ['/dev/nvme0n1', '/dev/sdb', '/dev/sdd', '/dev/sdc', '/dev/sde'] #### INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/nvme0n1', '/dev/sdb'] Oct 9 09:29:10 storageqe-109 INFO: Creating VG 'udisks_test_vdo_vg' on devices ['/dev/nvme0n1', '/dev/sdb'] Oct 9 09:29:35 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:30:00 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:30:25 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' Oct 9 09:30:26 storageqe-109 INFO: Creating VDO volume 'udisks_test_vdo_lv' in VG 'udisks_test_vdo_vg' Oct 9 09:30:52 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:30:52 storageqe-109 UDS/vdoformat[2569820]: INFO (vdoformat/2569820) Using 2 indexing zones for concurrency. Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo27:lvm: table line: V4 /dev/dm-3 583803904 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo27:lvm: loading device '253:4' Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo27:lvm: zones: 1 logical, 1 physical, 1 hash; total threads: 12 Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo27:lvm: starting device '253:4' Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:physQ0: VDO commencing normal operation Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:journa: Setting UDS index target state to online Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:dedupe: creating index: 253:3 Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' started Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:dedupe: Using 2 indexing zones for concurrency. Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:30:52 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:30:52 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing EnableDeduplication/EnableCompression... Oct 9 09:30:58 storageqe-109 INFO: Testing EnableDeduplication/EnableCompression... Oct 9 09:31:23 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo27:lvm: table line: V4 /dev/dm-3 583803904 4096 32768 16380 deduplication off compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo27:lvm: preparing to modify device '253:4' Oct 9 09:31:23 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:dedupe: beginning save (vcn 18446744073709551615) Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:packer: compression is enabled Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:31:23 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:dedupe: finished save (vcn 18446744073709551615) Oct 9 09:31:23 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:31:48 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:31:48 storageqe-109 kernel: device-mapper: vdo27:lvm: table line: V4 /dev/dm-3 583803904 4096 32768 16380 deduplication off compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:31:48 storageqe-109 kernel: device-mapper: vdo27:lvm: preparing to modify device '253:4' Oct 9 09:31:48 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:31:48 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:31:48 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:31:48 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:31:48 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:packer: compression is disabled Oct 9 09:31:48 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:31:48 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:32:16 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo27:lvm: table line: V4 /dev/dm-3 583803904 4096 32768 16380 deduplication on compression off maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo27:lvm: preparing to modify device '253:4' Oct 9 09:32:16 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:dedupe: loading or rebuilding index: 253:3 Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:packer: compression is disabled Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:dedupe: Using 2 indexing zones for concurrency. Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:32:16 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:32:16 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:dedupe: loaded index from chapter 0 through chapter 0 Oct 9 09:32:41 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:32:41 storageqe-109 kernel: device-mapper: vdo27:lvm: table line: V4 /dev/dm-3 583803904 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:32:41 storageqe-109 kernel: device-mapper: vdo27:lvm: preparing to modify device '253:4' Oct 9 09:32:41 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:32:41 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:32:41 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:32:41 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:32:41 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:packer: compression is enabled Oct 9 09:32:41 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:32:41 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing ResizeLogical... Oct 9 09:32:44 storageqe-109 INFO: Testing ResizeLogical... Oct 9 09:33:10 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:33:10 storageqe-109 kernel: device-mapper: vdo27:lvm: table line: V4 /dev/dm-3 583803904 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:33:10 storageqe-109 kernel: device-mapper: vdo27:lvm: preparing to modify device '253:4' Oct 9 09:33:10 storageqe-109 kernel: device-mapper: vdo27:lvm: Preparing to resize logical to 5859010816 Oct 9 09:33:10 storageqe-109 kernel: device-mapper: vdo27:lvm: Done preparing to resize logical Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: Resizing logical to 5859010816 Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: Logical blocks now 5859010816 Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:packer: compression is enabled Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:33:11 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:packer: compression is enabled Oct 9 09:33:11 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:33:11 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing ResizePhysical... Oct 9 09:33:13 storageqe-109 INFO: Testing ResizePhysical... Oct 9 09:33:40 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: table line: V4 /dev/dm-3 584328192 4096 32768 16380 deduplication on compression on maxDiscard 1 ack 1 bio 4 bioRotationInterval 64 cpu 2 hash 1 logical 1 physical 1 Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: preparing to modify device '253:4' Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: Preparing to resize physical to 584328192 Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: Done preparing to resize physical Oct 9 09:33:40 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: resuming device '253:4' Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: Physical block count was 583803904, now 584328192 Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo: dm_vdo27:packer: compression is enabled Oct 9 09:33:40 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' resumed Oct 9 09:33:40 storageqe-109 dmeventd[2563240]: Monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. INFO: Testing GetStatistics... INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 9 09:33:46 storageqe-109 INFO: Testing GetStatistics... Oct 9 09:33:46 storageqe-109 INFO: Cleaning up Volume Group 'udisks_test_vdo_vg' Oct 9 09:34:12 storageqe-109 udisksd[2509680]: Error inhibiting: Timeout was reached (g-io-error-quark, 24) Oct 9 09:34:12 storageqe-109 dmeventd[2563240]: No longer monitoring VDO pool udisks_test_vdo_vg-udisks_test_vdopool-vpool. Oct 9 09:34:12 storageqe-109 kernel: device-mapper: vdo27:lvm: suspending device '253:4' Oct 9 09:34:12 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' suspended Oct 9 09:34:12 storageqe-109 kernel: device-mapper: vdo27:lvm: stopping device '253:4' Oct 9 09:34:12 storageqe-109 kernel: device-mapper: vdo27:lvm: device '253:4' stopped INFO: #### after available_disks ['/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### INFO: #### END test_vdovolume_methods #### Oct 9 09:34:18 storageqe-109 INFO: #### after available_disks ['/dev/sdd', '/dev/sdc', '/dev/sde', '/dev/nvme0n1', '/dev/sdb'] #### Oct 9 09:34:18 storageqe-109 INFO: #### END test_vdovolume_methods #### cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 9 09:34:19 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 9 09:34:19 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 9 09:34:19 storageqe-109 journal: cryptsetup erase /dev/nvme0n1 -q --hw-opal-factory-reset Oct 9 09:34:49 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 9 10:33:33 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 10:33:33 storageqe-109 dnf[2570640]: Updating Subscription Management repositories. Oct 9 10:33:33 storageqe-109 dnf[2570640]: Unable to read consumer identity Oct 9 10:33:33 storageqe-109 dnf[2570640]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-AppStream 443 kB/s | 2.8 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-AppStream-debuginfo 422 kB/s | 1.5 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-BaseOS 693 kB/s | 2.7 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-BaseOS-debuginfo 346 kB/s | 1.5 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-CRB 646 kB/s | 2.7 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-CRB-debuginfo 495 kB/s | 1.5 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-HighAvailability 821 kB/s | 2.8 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-HighAvailability-debuginfo 573 kB/s | 1.5 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-NFV 719 kB/s | 2.7 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-NFV-debuginfo 383 kB/s | 1.5 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-RT 628 kB/s | 2.7 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-RT-debuginfo 459 kB/s | 1.5 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-SAP 549 kB/s | 2.7 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-SAP-debuginfo 426 kB/s | 1.5 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-SAPHANA 725 kB/s | 2.7 kB 00:00 Oct 9 10:33:33 storageqe-109 dnf[2570640]: beaker-SAPHANA-debuginfo 478 kB/s | 1.5 kB 00:00 Oct 9 10:33:34 storageqe-109 dnf[2570640]: Beaker Client - RedHatEnterpriseLinux10 1.6 kB/s | 1.3 kB 00:00 Oct 9 10:33:34 storageqe-109 dnf[2570640]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 9 10:33:34 storageqe-109 dnf[2570640]: Google Cloud CLI 5.2 kB/s | 1.4 kB 00:00 Oct 9 10:33:36 storageqe-109 dnf[2570640]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 9 10:33:36 storageqe-109 dnf[2570640]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 9 10:33:37 storageqe-109 dnf[2570640]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 9 10:33:37 storageqe-109 dnf[2570640]: Metadata cache created. Oct 9 10:33:37 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 10:33:37 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 10:33:37 storageqe-109 systemd[1]: dnf-makecache.service: Consumed 335ms CPU time, 82M memory peak. Oct 9 10:34:13 storageqe-109 dmeventd[2563240]: dmeventd was idle for 3600 second(s), exiting. Oct 9 10:34:13 storageqe-109 dmeventd[2563240]: dmeventd shutting down. Oct 9 10:34:13 storageqe-109 systemd[1]: dm-event.service: Deactivated successfully. Oct 9 10:41:03 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 10:41:03 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 10:41:03 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 11:38:46 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 11:38:47 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 11:38:47 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 11:53:47 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 11:53:48 storageqe-109 dnf[2570788]: Updating Subscription Management repositories. Oct 9 11:53:48 storageqe-109 dnf[2570788]: Unable to read consumer identity Oct 9 11:53:48 storageqe-109 dnf[2570788]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 11:53:48 storageqe-109 dnf[2570788]: Metadata cache refreshed recently. Oct 9 11:53:48 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 11:53:48 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 12:01:08 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 12:01:08 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 12:01:08 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 13:20:03 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 13:20:03 storageqe-109 dnf[2570892]: Updating Subscription Management repositories. Oct 9 13:20:03 storageqe-109 dnf[2570892]: Unable to read consumer identity Oct 9 13:20:03 storageqe-109 dnf[2570892]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 13:20:03 storageqe-109 dnf[2570892]: Metadata cache refreshed recently. Oct 9 13:20:03 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 13:20:03 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 13:49:21 storageqe-109 NetworkManager[2509403]: [1760032161.9838] dhcp4 (eno8303): state changed new lease, address=10.73.194.89 Oct 9 13:49:21 storageqe-109 systemd[1]: Starting NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service... Oct 9 13:49:22 storageqe-109 systemd[1]: Started NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service. Oct 9 13:49:32 storageqe-109 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Oct 9 13:58:35 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 13:58:35 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 13:58:35 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 14:24:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 14:24:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 14:24:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 15:07:09 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 15:07:09 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 15:07:09 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 15:11:29 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 15:11:29 storageqe-109 dnf[2571074]: Updating Subscription Management repositories. Oct 9 15:11:29 storageqe-109 dnf[2571074]: Unable to read consumer identity Oct 9 15:11:29 storageqe-109 dnf[2571074]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 15:11:29 storageqe-109 dnf[2571074]: beaker-AppStream 548 kB/s | 2.8 kB 00:00 Oct 9 15:11:29 storageqe-109 dnf[2571074]: beaker-AppStream-debuginfo 333 kB/s | 1.5 kB 00:00 Oct 9 15:11:29 storageqe-109 dnf[2571074]: beaker-BaseOS 883 kB/s | 2.7 kB 00:00 Oct 9 15:11:29 storageqe-109 dnf[2571074]: beaker-BaseOS-debuginfo 420 kB/s | 1.5 kB 00:00 Oct 9 15:11:29 storageqe-109 dnf[2571074]: beaker-CRB 703 kB/s | 2.7 kB 00:00 Oct 9 15:11:29 storageqe-109 dnf[2571074]: beaker-CRB-debuginfo 348 kB/s | 1.5 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-HighAvailability 555 kB/s | 2.8 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-HighAvailability-debuginfo 485 kB/s | 1.5 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-NFV 549 kB/s | 2.7 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-NFV-debuginfo 355 kB/s | 1.5 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-RT 643 kB/s | 2.7 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-RT-debuginfo 465 kB/s | 1.5 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-SAP 633 kB/s | 2.7 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-SAP-debuginfo 438 kB/s | 1.5 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-SAPHANA 653 kB/s | 2.7 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: beaker-SAPHANA-debuginfo 447 kB/s | 1.5 kB 00:00 Oct 9 15:11:30 storageqe-109 dnf[2571074]: Beaker Client - RedHatEnterpriseLinux10 2.3 kB/s | 1.3 kB 00:00 Oct 9 15:11:31 storageqe-109 dnf[2571074]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 9 15:11:31 storageqe-109 dnf[2571074]: Google Cloud CLI 4.2 kB/s | 1.4 kB 00:00 Oct 9 15:11:32 storageqe-109 dnf[2571074]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 9 15:11:32 storageqe-109 dnf[2571074]: repo14 4.6 kB/s | 2.3 kB 00:00 Oct 9 15:11:33 storageqe-109 dnf[2571074]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 9 15:11:33 storageqe-109 dnf[2571074]: Metadata cache created. Oct 9 15:11:33 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 15:11:33 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 16:23:24 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 16:23:24 storageqe-109 dnf[2571190]: Updating Subscription Management repositories. Oct 9 16:23:24 storageqe-109 dnf[2571190]: Unable to read consumer identity Oct 9 16:23:24 storageqe-109 dnf[2571190]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 16:23:24 storageqe-109 dnf[2571190]: Metadata cache refreshed recently. Oct 9 16:23:24 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 16:23:24 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 16:54:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 16:54:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 16:54:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 17:24:53 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 17:24:53 storageqe-109 dnf[2571263]: Updating Subscription Management repositories. Oct 9 17:24:53 storageqe-109 dnf[2571263]: Unable to read consumer identity Oct 9 17:24:53 storageqe-109 dnf[2571263]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 17:24:53 storageqe-109 dnf[2571263]: Metadata cache refreshed recently. Oct 9 17:24:53 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 17:24:53 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 17:36:28 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 17:36:28 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 17:36:28 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 18:22:51 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 18:22:51 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 18:22:51 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 19:21:04 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 19:21:04 storageqe-109 dnf[2571398]: Updating Subscription Management repositories. Oct 9 19:21:04 storageqe-109 dnf[2571398]: Unable to read consumer identity Oct 9 19:21:04 storageqe-109 dnf[2571398]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-AppStream 459 kB/s | 2.8 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-AppStream-debuginfo 347 kB/s | 1.5 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-BaseOS 696 kB/s | 2.7 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-BaseOS-debuginfo 489 kB/s | 1.5 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-CRB 794 kB/s | 2.7 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-CRB-debuginfo 456 kB/s | 1.5 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-HighAvailability 724 kB/s | 2.8 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-HighAvailability-debuginfo 530 kB/s | 1.5 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-NFV 561 kB/s | 2.7 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-NFV-debuginfo 400 kB/s | 1.5 kB 00:00 Oct 9 19:21:04 storageqe-109 dnf[2571398]: beaker-RT 741 kB/s | 2.7 kB 00:00 Oct 9 19:21:05 storageqe-109 dnf[2571398]: beaker-RT-debuginfo 523 kB/s | 1.5 kB 00:00 Oct 9 19:21:05 storageqe-109 dnf[2571398]: beaker-SAP 618 kB/s | 2.7 kB 00:00 Oct 9 19:21:05 storageqe-109 dnf[2571398]: beaker-SAP-debuginfo 434 kB/s | 1.5 kB 00:00 Oct 9 19:21:05 storageqe-109 dnf[2571398]: beaker-SAPHANA 760 kB/s | 2.7 kB 00:00 Oct 9 19:21:05 storageqe-109 dnf[2571398]: beaker-SAPHANA-debuginfo 463 kB/s | 1.5 kB 00:00 Oct 9 19:21:05 storageqe-109 dnf[2571398]: Beaker Client - RedHatEnterpriseLinux10 2.3 kB/s | 1.3 kB 00:00 Oct 9 19:21:06 storageqe-109 dnf[2571398]: beaker-harness 2.3 kB/s | 1.3 kB 00:00 Oct 9 19:21:06 storageqe-109 dnf[2571398]: Google Cloud CLI 4.2 kB/s | 1.4 kB 00:00 Oct 9 19:21:07 storageqe-109 dnf[2571398]: Copr repo for python-ssh2-python312 owned by mh 2.0 kB/s | 1.5 kB 00:00 Oct 9 19:21:08 storageqe-109 dnf[2571398]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 9 19:21:08 storageqe-109 dnf[2571398]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 9 19:21:08 storageqe-109 dnf[2571398]: Metadata cache created. Oct 9 19:21:08 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 19:21:08 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 19:37:40 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 19:37:40 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 19:37:40 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 20:07:07 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 20:07:07 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 20:07:07 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 20:45:53 storageqe-109 systemd[1078]: Starting systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories... Oct 9 20:45:53 storageqe-109 systemd[1078]: Finished systemd-tmpfiles-clean.service - Cleanup of User's Temporary Files and Directories. Oct 9 20:52:50 storageqe-109 systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Oct 9 20:52:50 storageqe-109 systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Oct 9 20:52:50 storageqe-109 systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Oct 9 21:10:51 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 21:10:51 storageqe-109 dnf[2571582]: Updating Subscription Management repositories. Oct 9 21:10:51 storageqe-109 dnf[2571582]: Unable to read consumer identity Oct 9 21:10:51 storageqe-109 dnf[2571582]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 21:10:51 storageqe-109 dnf[2571582]: Metadata cache refreshed recently. Oct 9 21:10:51 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 21:10:51 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 21:31:02 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 21:31:02 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 21:31:02 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 22:10:34 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 22:10:34 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 22:10:34 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 9 23:01:43 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 9 23:01:43 storageqe-109 dnf[2571720]: Updating Subscription Management repositories. Oct 9 23:01:43 storageqe-109 dnf[2571720]: Unable to read consumer identity Oct 9 23:01:43 storageqe-109 dnf[2571720]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 9 23:01:43 storageqe-109 dnf[2571720]: beaker-AppStream 460 kB/s | 2.8 kB 00:00 Oct 9 23:01:43 storageqe-109 dnf[2571720]: beaker-AppStream-debuginfo 339 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-BaseOS 612 kB/s | 2.7 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-BaseOS-debuginfo 370 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-CRB 582 kB/s | 2.7 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-CRB-debuginfo 378 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-HighAvailability 584 kB/s | 2.8 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-HighAvailability-debuginfo 523 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-NFV 569 kB/s | 2.7 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-NFV-debuginfo 347 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-RT 800 kB/s | 2.7 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-RT-debuginfo 442 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-SAP 553 kB/s | 2.7 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-SAP-debuginfo 452 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-SAPHANA 815 kB/s | 2.7 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: beaker-SAPHANA-debuginfo 346 kB/s | 1.5 kB 00:00 Oct 9 23:01:44 storageqe-109 dnf[2571720]: Beaker Client - RedHatEnterpriseLinux10 1.6 kB/s | 1.3 kB 00:00 Oct 9 23:01:45 storageqe-109 dnf[2571720]: beaker-harness 2.6 kB/s | 1.3 kB 00:00 Oct 9 23:01:45 storageqe-109 dnf[2571720]: Google Cloud CLI 4.4 kB/s | 1.4 kB 00:00 Oct 9 23:01:46 storageqe-109 dnf[2571720]: Copr repo for python-ssh2-python312 owned by mh 1.5 kB/s | 1.5 kB 00:01 Oct 9 23:01:47 storageqe-109 dnf[2571720]: repo14 3.1 kB/s | 2.3 kB 00:00 Oct 9 23:01:48 storageqe-109 dnf[2571720]: Storage-QE 1.8 kB/s | 951 B 00:00 Oct 9 23:01:48 storageqe-109 dnf[2571720]: Metadata cache created. Oct 9 23:01:48 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 9 23:01:48 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 9 23:07:54 storageqe-109 systemd[1]: Starting systemd-hostnamed.service - Hostname Service... Oct 9 23:07:54 storageqe-109 systemd[1]: Started systemd-hostnamed.service - Hostname Service. Oct 9 23:08:24 storageqe-109 systemd[1]: systemd-hostnamed.service: Deactivated successfully. Oct 9 23:41:43 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 9 23:41:43 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 9 23:41:43 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 10 00:00:01 storageqe-109 systemd[1]: Starting unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound... Oct 10 00:00:01 storageqe-109 systemd[1]: unbound-anchor.service: Deactivated successfully. Oct 10 00:00:01 storageqe-109 systemd[1]: Finished unbound-anchor.service - update of the root trust anchor for DNSSEC validation in unbound. Oct 10 00:30:43 storageqe-109 systemd[1]: Starting dnf-makecache.service - dnf makecache... Oct 10 00:30:43 storageqe-109 dnf[2572384]: Updating Subscription Management repositories. Oct 10 00:30:43 storageqe-109 dnf[2572384]: Unable to read consumer identity Oct 10 00:30:43 storageqe-109 dnf[2572384]: This system is not registered with an entitlement server. You can use "rhc" or "subscription-manager" to register. Oct 10 00:30:43 storageqe-109 dnf[2572384]: Metadata cache refreshed recently. Oct 10 00:30:43 storageqe-109 systemd[1]: dnf-makecache.service: Deactivated successfully. Oct 10 00:30:43 storageqe-109 systemd[1]: Finished dnf-makecache.service - dnf makecache. Oct 10 00:43:03 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 10 00:43:04 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 10 00:43:04 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd. Oct 10 00:55:11 storageqe-109 systemd[1]: Starting logrotate.service - Rotate log files... Oct 10 00:55:11 storageqe-109 systemd[1]: logrotate.service: Deactivated successfully. Oct 10 00:55:11 storageqe-109 systemd[1]: Finished logrotate.service - Rotate log files. Oct 10 01:34:53 storageqe-109 systemd[1]: Starting fwupd-refresh.service - Refresh fwupd metadata and update motd... Oct 10 01:34:53 storageqe-109 systemd[1]: fwupd-refresh.service: Deactivated successfully. Oct 10 01:34:53 storageqe-109 systemd[1]: Finished fwupd-refresh.service - Refresh fwupd metadata and update motd.